Event Segmentation

After selecting an event to analyze in a chart, you can use +Group-by and +Filter by to query event and user properties further. The +Filter by will filter your results for specific property values. The +Group-by will group your results by your selected property. 

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 are found in the top right of your chart.

For example, if you’d like to see data for the last 90 days, click Last 90 days. If you’d like 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 will then be updated with the custom date range.

In the Measured as section of the Event Segmentation chart, select Average of Property Value from the Properties drop-down shown below to calculate the average value: 

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 desired number of events next to count.
4. Choose the timeframe by clicking on Last 30 Days. This option is like the date picker, and allows you to choose a date range in the last number or days or a custom date range.
5. If desired, 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 can then be used in other charts. 

In the Segment By module, there is a drop-down menu where you can select Accounts instead of Users.

For daily and weekly, the maximum date range you can query is 365 days. For monthly, you can look up the last 36 months.

Use the Compare drop down to choose the desired comparison. From your chart, click Compare and choose Previous year to compare the current year's data to last year's. The Compare feature allows you to choose a custom date range by clicking Select custom date range. Enter your end date in the modal that appears and click Apply. 

Amplitude doesn't support creating goal lines nor horizontal annotations.

However, for a similar result, try using a custom formula to set a "target" for a specific metric. In the below example, the Measured As module contains the following custom formula: 

UNIQUES(A); UNIQUES(A) * 0 + 90000

As a result, the custom formula produces a goal line. If desired, you can then rename the y-axis to identify the desired goal.

As an example, you'd like to see how many users downloaded a song or video compared to all the users who favorited a song or video each day. You could use a custom formula to calculate the ratio of those events as a percentage. To create that custom formula, follow the below steps:

1. From the Measured as module, click Advanced.
2. Enter the formula's syntax: %:UNIQUES(A) / UNIQUES(B).
3. The ratio will then display as a percentage in your chart.

How do I create a DAU or a MAU chart? Use the ROLLWIN custom formula in the Event Segmentation chart. Rolling windows track a rolling total of unique users over the desired time frame (hours, days, weeks, or months).

For more information, see how custom formulas work in Amplitude Analytics for more information.

Null values aren't considered in the calculation for PROP() formulas.

The PROP() formulas will only consider integer values in their calculations. For example, a value of $30 will not be calculable, but a value of 30 will be. 

Line charts return values per date interval (eg. per day, per week, per month) while bar charts return values for the entire date range. The date interval selected will not matter when using 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 will only count the user once. In other words, the bar chart will deduplicate the counts.

For example, if a user triggered event A on November 2nd and November 6th, and you have a chart that counts uniques daily between November 1st and November 30th, this user will be counted twice in the line chart but only once in the bar chart. Thus the bar chart will return a count smaller than the sum of each daily data point. 

A new user is a user who has logged an event to Amplitude for the first time (this includes inactive events). The time of when the user is new is the time of when they logged their earliest event. 

In an Event Segmentation chart, when choosing New Users, Amplitude will look for the events triggered by new users within each day/week/month (whichever interval was chosen) 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 will appear on the chart, regardless if the user also triggered events the next day, on July 18.

Find the definitions of Amplitude user properties here.

The Active %metric graphs the percentage of users who triggered a specific event, compared to the total number of active users (users who have triggered any active event) at each data point.

If you have a cohort or segment filters applied to the chart, the denominator will only include users who have triggered an active event and meet your segmentation requirements. 

For more information on how each metric is defined, see this article on interpreting your event segmentation analysis. 

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, the group-by is applied only to the event (numerator). The formula for Active % will be:

count of users who performed the event and who meet the group by property

/``number of active users * 100

However, when you apply a group-by in the Segment By module, the Active % metric will take into account the number of active users matching the group-by property in both the numerator and the denominator. The formula in this case will be:

count of users who performed the event and who meet the group by property

/``number of active users **who meet the group by property** * 100

This is usually because you are querying on an inactive event. It's possible that the number of users who have performed an inactive event is higher than the number of active users.

Amplitude servers ingest high volumes of data, and there is the potential for some data processing delays. Rest assured that no data is lost. Incomplete data means only that data has been received by Amplitude, but the servers are taking longer to ingest and process the data for you to query.

To stay up to date, see the Amplitude status page: https://status.amplitude.com/

• Microscope: In a chart, click on a data point you're interested in. A popup will appear; click Download users.
• Cohort: Create a cohort definition and click Export CSV.
• Create a chart: Use Any Active Event, grouped by Amplitude or user ID. Then click Export CSV in the breakdown table below the chart.

Sometimes users instrument event and user properties that have the same naming convention. When choosing the property make sure you are selecting the correct type of property. For example, 'url' could be used as a name for both an event property and user property. If you're filtering or grouping by the 'url' user property instead of the 'url' event property, you may see different results returned in the chart than expected.

Amplitude will only display the top 100 property values in the breakdown table. If you export the breakdown table to CSV, the file will max out at the first 10,000 values.

An important note regarding the glob match feature is that the asterisk only matches non-"/" characters. To search for strings that contain "/", you will have to use two asterisks, because "**" can match anything. In this case, since the referrer property contains URLs, there are going to be lots of "/" characters.

More information on glob matching can be found here.

When there are multiple segments, Amplitude “splits” the group by cap between each segment. This means with 2 segments, each segment only gets 5000 group-by values, hence the limiting seen in the exported CSV. This behavior is similar to how when there are multiple events, we will reduce the number of rows allotted to each event.