Funnel Analysis FAQ

Either one. To switch from unique users to event totals, select Totals from the Counting by dropdown.

You can also use the Holding Property Constant feature to count by unique user-property pairs. For example, if you hold Session ID constant, you can count a user multiple times when they perform the funnel events in different sessions.

The conversion window uses a 24-hour window when looking at conversion from Step 1 to Step 2. The window isn't based on strict calendar dates.

In the Measured As module, check Calculate sum of property for final step from within the Advanced dropdown. Then, in the field labeled Property sum for final step, select the revenue property you want Amplitude to calculate.

The result appears in the breakdown table.

By default, the conversion Funnel Analysis chart counts unique users. A single user can only appear in the chart once. However, the Conversion Over Time funnel chart can count a user in multiple data points.

For example, imagine a user who triggered Step 1 of your funnel on January 1, January 5, and January 20, and triggered Step 2 of the funnel on January 2 and January 6. In a Conversion Funnel chart with a date range of January 1-31, the user counts as 100% converted because they completed the funnel steps within those dates. In a Conversion Over Time Funnel chart, the user counts as 100% converted for January 1 and January 5, but 0% converted on January 20. As a result, the conversion rate for January 20 may appear lower than in the regular conversion chart.

Event segmentation and funnel charts are different types of analyses, so they can show different results.

In a funnel chart, users must perform the first step within the selected date range to enter the funnel. They must then complete the remaining steps in a defined order within the conversion window to count as converted.

In an event segmentation chart, users must fire the chosen events within the selected date range to appear in the chart.

In addition, if you apply a segment filter in the segmentation module, the filter only applies to the first step in the funnel chart. In a segmentation chart, the filter applies to every event.

For more, refer to How Amplitude computes conversions and this community post.

When the funnel chart looks at the median time to convert in distribution view, it only counts the first conversion per user in the entire date range. When you switch to the time to convert over time view, Amplitude counts the first conversion of each user in each day of the date range. For example, if users can convert more than once in a day, only the first conversion of that day counts.

In both cases, Amplitude uses an approximate algorithm to estimate the median time to convert. The median time to convert is only an approximation.

Amplitude calculates it using the entire data set. Amplitude calculates the percentages on the Y-axis using the bin min/max limits.

Users who performed the excluded steps don't necessarily count as dropped off. Users can have multiple conversions in the funnel. As long as at least one of their conversions satisfies the exclusion constraint, they count as converted.

Yes, you can hold an array property constant in a funnel. Amplitude treats each item in the array as an independent value.

Consider a two-step funnel (Event A > Event B). A user performed the events with the following item_id property values:

Event A where item_id = [1, 2, 3]

Event B where item_id = 3

When the funnel holds item_id constant, the user counts as converted because the item_id value in Event B matches one of the values in the array in Event A. In other words, the value of the property held constant isn't necessarily the same across all the funnel events.

"Any Order" requires users to perform the first event within the date range to count as part of the funnel. Users who fire the later events without firing the first event don't count as part of the funnel. In other words, users don't have to perform the first event as the first step in their sequence to count as converted.

In an "Any Order" funnel, the number for the first event is the number of users who fire the first event to enter the funnel. Users must do all the events in the funnel to count for the last step, because no step can be skipped. Although users can complete the events in any order, they must complete all the other steps and the last step to count as converted for the last step. If the funnel has only two or three events, moving the first and last events around changes the results, because the ordering of the first and last events still matters.

In an "Exact Order" funnel, if an event that isn't part of the funnel definition fires in the same second as a funnel event, the user still counts as converted. A second is the default resolution Amplitude currently supports.

This also applies to excluding events from a funnel. If the excluded event happens in the same second as an event included in the funnel, the user still counts as converted.

If you need a more detailed level of time resolution, select Millisecond resolution in the Advanced drop-down.

Cohorts created directly from Microscope on a Funnel Analysis chart are dynamic if only events were added to the chart. If the chart uses "holding property constant", "broken down by", or any inline cohorting, the cohort is static.

Also, you can't create dynamic cohorts from funnel charts that contain exclusions. Any such cohorts are static.

In a funnel chart, the segment filter only applies to the first funnel event. Add individual filters to each step in the Event module if you want them to apply to each funnel event. For more information, refer to How filters work in a Funnel Analysis chart.

Click the Export CSV button in the breakdown table to export the data. If a group-by filter applies in the funnel chart, the export limit is 300 group-by values. Learn more about CSV download limits.

Alternatively, export the funnel result through the Dashboard REST API. The default group-by limit is 100, but you can edit the limit parameter to export up to 1000 group-by values.