# Event Segmentation FAQ Frequently asked questions about Event Segmentation charts. Source: https://amplitude.com/docs/analytics/charts/event-segmentation/faq --- On this page - [How do I analyze event and user properties and not just events?](#how-do-i-analyze-event-and-user-properties-and-not-just-events) - [How do I look at data older than the last 30 days?](#how-do-i-look-at-data-older-than-the-last-30-days) - [How do I find the average of this property?](#how-do-i-find-the-average-of-this-property) - [How do I segment by a user's past performance?](#how-do-i-segment-by-a-users-past-performance) - [How do I filter by accounts instead of users?](#how-do-i-filter-by-accounts-instead-of-users) - [What is the maximum date range in the Event Segmentation chart?](#what-is-the-maximum-date-range-in-the-event-segmentation-chart) - [How can I compare this year's data to last year's?](#how-can-i-compare-this-years-data-to-last-years) - [How can I set a goal line or horizontal annotation in my chart?](#how-can-i-set-a-goal-line-or-horizontal-annotation-in-my-chart) - [How do I calculate a ratio as a percentage?](#how-do-i-calculate-a-ratio-as-a-percentage) - [How do I create a DAU or a MAU chart?](#how-do-i-create-a-dau-or-a-mau-chart) - [How does Amplitude handle null values in formulas?](#how-does-amplitude-handle-null-values-in-formulas) - [Why don't my formulas return any values?](#why-dont-my-formulas-return-any-values) - [Why don't my line chart data points add up to my bar chart total?](#why-dont-my-line-chart-data-points-add-up-to-my-bar-chart-total) - [What does New User mean?](#what-does-new-user-mean) - [What is the definition of ?](#what-is-the-definition-of) - [Why do I get a different result for when I apply the group-by on the Events module versus the Segment By module?](#why-do-i-get-a-different-result-for-when-i-apply-the-group-by-on-the-events-module-versus-the-segment-by-module) - [Why is my metric more than 100%?](#why-is-my-metric-more-than-100) - [Why am I getting an incomplete data error?](#why-am-i-getting-an-incomplete-data-error) - [How do I download a list of users?](#how-do-i-download-a-list-of-users) - [Why don't I see a specific value I know Amplitude ingested?](#why-dont-i-see-a-specific-value-i-know-amplitude-ingested) - [Why doesn't my chart display all possible values for this event/user property?](#why-doesnt-my-chart-display-all-possible-values-for-this-eventuser-property) - [Why doesn't my glob match filter return any results?](#why-doesnt-my-glob-match-filter-return-any-results) - [Why is my CSV Export missing values, even though the data is under the 10,000 values group-by limit stated in your documentation?](#why-is-my-csv-export-missing-values-even-though-the-data-is-under-the-10000-values-group-by-limit-stated-in-your-documentation) # Event Segmentation FAQ This page answers common questions about the Event Segmentation chart. ## How do I analyze event and user properties and not just events? After you select an event to analyze in a chart, use *+Group-by* and *+Filter by* to query event and user properties further. *+Filter by* filters your results for specific property values. *+Group-by* groups your results by your selected property. ## How do I look at data older than the last 30 days? To see data beyond the last 30 days, use the date picker and date interval options to select different date ranges of data. The date options appear in the top right of your chart. For example, to see data for the last 90 days, click *Last 90 days*. To see data for a specific date range, click the calendar to open the custom date range fly-out. Enter your custom dates in the *Between* section, and click *Apply* to save. Your chart updates with the custom date range. ## How do I find the average of this property? In the Measured as section of the Event Segmentation chart, select *Average of Property Value* from the *Properties* drop-down to calculate the average value. ## How do I segment by a user's past performance? Customers on Scholarship, Growth, or Enterprise plans can add a *who performed* filter to the specified users in the Segment By module. To add an in-line behavioral cohort, follow these steps: 1. Click More options and choose *Add who performed*. 2. Click the Amplitude logo *Any Event* and choose the event you want the cohort to have performed. 3. Enter the number of events you want next to *count*. 4. Choose the timeframe by clicking *Last 30 Days*. This option behaves like the date picker, and lets you choose a date range in the last number of days or a custom date range. 5. To add an offset, click More options next to the date picker and choose *Add offset*. You can also define and save a cohort in the Segment By module, which you can then use in other charts. ## How do I filter by accounts instead of users? In the Segment By module, a drop-down menu lets you select *Accounts* instead of *Users*. ## What is the maximum date range in the Event Segmentation chart? For daily and weekly intervals, the maximum date range you can query is 365 days. For monthly, you can look up the last 36 months. ## How can I compare this year's data to last year's? Use the [Compare](/docs/analytics/charts/event-segmentation/event-segmentation-interpret-2) drop-down to choose the comparison you want. From your chart, click *Compare* and choose *Previous year* to compare the current year's data to last year's. The *Compare* feature also lets you choose a custom date range. Click *Select custom date range*, enter your end date in the modal that appears, and click *Apply*. ## How can I set a goal line or horizontal annotation in my chart? Amplitude doesn't support creating goal lines or horizontal annotations. For a similar result, use a custom formula to set a "target" for a specific metric. In this example, the Measured As module contains the following custom formula: `UNIQUES(A); UNIQUES(A) * 0 + 90000` The custom formula produces a goal line. Rename the y-axis to identify the goal. ## How do I calculate a ratio as a percentage? For example, suppose you want to see how many users downloaded a song or video compared to all the users that favorited a song or video each day. Use a custom formula to calculate the ratio of those events as a percentage. To create that custom formula, follow these steps: 1. From the *Measured as* module, click *Advanced*. 2. Enter the formula's syntax: `%:UNIQUES(A) / UNIQUES(B)`. 3. The ratio displays as a percentage in your chart. ## How do I create a DAU or a MAU chart? Use the [`ROLLWIN` custom formula](/docs/analytics/charts/event-segmentation/event-segmentation-custom-formulas) in the Event Segmentation chart. Rolling windows track a rolling total of unique users over the time frame you specify (hours, days, weeks, or months). For more information, refer to [how custom formulas work in Amplitude Analytics](/docs/analytics/charts/event-segmentation/event-segmentation-custom-formulas). ## How does Amplitude handle null values in formulas? Amplitude doesn't consider null values in the calculation for `PROP()` formulas. ## Why don't my formulas return any values? `PROP()` formulas consider only integer values in their calculations. For example, a value of $30 isn't calculable, but a value of 30 is. ## Why don't my line chart data points add up to my bar chart total? Line charts return values per date interval (such as per day, per week, or per month), while bar charts return values for the entire date range. The date interval doesn't matter for a bar chart. If a user triggers an event on multiple days, the line chart counts a user for each day they triggered the event, while the bar chart counts the user once. The bar chart deduplicates the counts. For example, if a user triggered event A on November 2 and November 6, and you have a chart that counts uniques daily between November 1 and November 30, the line chart counts this user twice but the bar chart counts the user once. The bar chart returns a count smaller than the sum of each daily data point. ## What does New User mean? A new user is a user that logged an event to Amplitude for the first time (this includes inactive events). The user's "new" time matches the time they logged their earliest event. In an Event Segmentation chart, when you choose *New Users*, Amplitude looks for the events triggered by new users within each day, week, or month (whichever interval you chose) that the user was new. For example, if the interval is set to *daily* and a user was new on July 17, only the events that happened on July 17 appear on the chart, regardless of whether the user also triggered events the next day, on July 18. [Find the definitions of Amplitude user properties here](/docs/get-started/user-property-definitions). ## What is the definition of ? The `Active %` metric graphs the percentage of users that triggered a specific event, compared to the total number of active users (users that triggered any active event) at each data point. If you apply a cohort or segment filters to the chart, the denominator includes only users that triggered an active event and meet your segmentation requirements. For more information on how Amplitude defines each metric, refer to [this article on interpreting your event segmentation analysis](/docs/analytics/charts/event-segmentation/event-segmentation-interpret-1). ## Why do I get a different result for when I apply the group-by on the Events module versus the Segment By module? Because of the definition of the `Active %` metric, the denominator changes when you apply a group-by in the Events module versus the Segment By module. When you apply group-by in the **Events** module, Amplitude applies the group-by **only** to the event (numerator). The formula for `Active %` is: `count of users that performed the event and meet the group-by property` `/``number of active users * 100` When you apply a group-by in the Segment By module, the `Active %` metric considers the **number of active users** that match the group-by property in both the numerator and the denominator. The formula in this case is: `/``number of active users **that meet the group-by property** * 100` ## Why is my metric more than 100%? This usually happens because you're querying an inactive event. The number of users that performed an inactive event can exceed the number of active users. ## Why am I getting an incomplete data error? Amplitude servers ingest high volumes of data, and some data processing delays can occur. Amplitude doesn't lose data. Incomplete data means only that Amplitude received the data, but the servers are taking longer to ingest and process the data for you to query. To stay up to date, refer to the Amplitude status page: ## How do I download a list of users? - **Microscope**: in a chart, click a data point you're interested in. A pop-up appears; click *Download users*. - **Cohort**: create a cohort definition and click *Export CSV*. - **Create a chart**: use *Any Active Event*, grouped by Amplitude ID or user ID. Then click *Export CSV* in the breakdown table below the chart. ## Why don't I see a specific value I know Amplitude ingested? Sometimes users instrument event and user properties that share the same naming convention. When choosing the property, select the correct type of property. For example, you can use 'url' as a name for both an event property and a user property. If you filter or group by the 'url' user property instead of the 'url' event property, the chart can return different results than you expect. ## Why doesn't my chart display all possible values for this event/user property? Amplitude displays only the top 100 property values in the breakdown table. If you export the breakdown table to CSV, the file maxes out at the first 10,000 values. ## Why doesn't my glob match filter return any results? The asterisk in glob match matches only non-"/" characters. To search for strings that contain "/", use two asterisks, because "\*\*" matches anything. The referrer property contains URLs, which include many "/" characters. Refer to the [glob pattern overview on Wikipedia](https://en.wikipedia.org/wiki/Glob_%28programming%29) for more information on glob matching. ## Why is my CSV Export missing values, even though the data is under the 10,000 values group-by limit stated in your documentation? When you have multiple segments, Amplitude "splits" the group-by cap between each segment. With 2 segments, each segment gets 5,000 group-by values, which causes the limit you see in the exported CSV. This behavior matches how Amplitude reduces the number of rows allotted to each event when you have multiple events. Was this helpful?