For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.
Group, filter, and segment metrics in Metric Explorer
이 페이지는 아직 귀하의 언어로 번역되지 않았습니다. 현재 작업 중이므로 곧 다시 확인해 주십시오.
Metric Explorer narrows and splits data at two levels. Filters and group-bys on a metric change that metric only. Segments in the Segment by block choose the users for every metric on the chart. Use metric-level settings to ask different questions of different metrics, and segments to compare populations across all of them.
Filter a metric
A filter keeps only the events or sessions that match a condition, for that metric alone.
- On the metric, click + Filter by.
- Choose a property, for example
Country. - Choose an operator and values, for example is
United States.
Filters offer the same operators as other Amplitude charts: is, is not, contains, does not contain, starts with, does not start with, numeric comparisons, set operators, and glob match. For event metrics, cart (array) properties are available as filters and group-bys.
Session metrics use session filters, such as [Amplitude] Contains Event, instead of event property filters. For session filters, go to Analyze sessions.
Group a metric by a property
A group-by splits a metric into one series per property value.
- On the metric, click + Group-by.
- Choose an event or user property, for example
platform. - To split further, add more group-bys. Each metric takes up to 5.
A group-by on one metric leaves the others unchanged. For example, group Purchase by product_category and keep Sign Up as a single line. When a property has many values, the chart shows the top values, and the breakdown table shows the top 100. For how Amplitude orders and limits groups, go to Group-by.
A metric keeps its group-bys when you change its measurement.
Group session metrics by entry, exit, or any value
A session can contain many values of the same property, such as several page paths. When you group a session metric, choose which value assigns each session to a group:
- [Amplitude] Any Property Value: The session counts under every value it contains.
- [Amplitude] First Property Value: The session counts under its first value, such as the landing page or the channel that started the visit.
- [Amplitude] Last Property Value: The session counts under its last value, such as the exit page.
You also choose which event supplies the value: the metric's own event, or [Amplitude] Any Active Event for any event in the session. For steps and examples, go to Group sessions by entry, exit, or any value.
To compare event metrics and session metrics by the same breakdown, add a group-by on the same property to each metric. To compare populations instead, use segments.
Choose users with segments
The Segment by block applies to every metric. With no conditions, the chart includes all users.
- Filter by: Users whose user properties match, for example
CountryisUnited Kingdom. - Performed: Users who performed an event a number of times in a time window, for example
Add to Cartat least once in the last 30 days. - In Cohort: Users in a saved cohort.
- User type: New, Active, or Any users.
To reuse a segment, click Saved and choose a saved segment. To save the current segment, click Save Segment and name it. For segment conditions and Advanced Segments, go to Add user segments.
Compare segments
Add a second segment to compare populations side by side, for example users in the United States and all users. Every metric then appears once per segment.
To compare segments in one number, write a formula across them. The letter refers to the metric and the number to the segment, so A2/A1 divides metric A in segment 2 by metric A in segment 1. For formula syntax, go to Write formulas in Metric Explorer.
Group every metric by a user property
Group Segment by splits every metric by a user property, for example City. Unlike a group-by on a metric, Group Segment by applies to the whole chart and changes the denominator of % of Active Users to active users with the same property value.
Count accounts instead of users
If your project uses account-level reporting, the count selector in the Metrics block header switches from Users to a group type, such as companies. Unique counts then count groups, and Microscope offers View Groups and Download Groups.
이 내용이 도움이 되었나요?