For a funnel, why does conversion rate on uniques produce a result of 1, but conversion rate totals produce a result of 3? For context, I'm holding a constant id that is different for all 3 results in conversion rate totals.
Hi Jorge C., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
When you use the "Uniques" counting method in a Mixpanel funnel, each user (as identified by their distinct_id) can only enter the funnel once, and the property value held constant is taken from their first Step 1 event. So, even if a user performs the funnel steps multiple times with different constant IDs, only their first attempt (with the first constant ID) is counted. This is why the conversion rate for uniques is 1 in your scenario—only one unique user is counted, regardless of how many different constant IDs they use in subsequent attempts.
In contrast, with the "Totals" counting method, users can re-enter the funnel after exiting a previous attempt. When you hold a property constant (such as an ID), each new value of that property allows the user to re-enter the funnel as a new attempt. If the user completes the funnel three times, each with a different constant ID, all three are counted as separate conversions. This is why the conversion rate for totals is 3 in your case—each unique constant ID (and thus each funnel attempt) is counted as a separate conversion, even though it’s the same user.
This behavior is described in the documentation:
- For Uniques: "users will only enter the funnel once, on the first time they do Step 1. Mixpanel will hold constant the property value from the first Step 1 event." - For Totals: "users can re-enter the funnel. Mixpanel will hold the property constant that is set with each new re-entry at the Step 1 event. This means the user can enter multiple times with different property values." See more details here.
So, your results are expected: - Uniques: 1 conversion (first constant ID only) - Totals: 3 conversions (one for each different constant ID)
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
If I do a breakdown of distinct id against conversion rate uniques on the last step defined, then I see 3 different ids. Yet if i dont break down by distinct id I still only see 1. why?
Let me check the knowledge base for you again. One moment! 📚
When you break down by distinct_id in a funnel report using the uniques counting method and "last step defined" property attribution, you see 3 different IDs because the breakdown shows the conversion rate for each unique value of distinct_id that completed the funnel. Each row in the breakdown represents a unique user (distinct_id) who converted, so you see all distinct_ids that reached the last step.
However, when you do not break down by distinct_id, Mixpanel aggregates the data and counts each user only once, regardless of how many times they completed the funnel. With the uniques counting method, the overall conversion rate reflects the number of unique users (distinct_ids) who converted, not the number of times they converted. If all conversions are from the same user (same distinct_id), you will see a count of 1. If they are from different users, you will see the count of unique users.
So, the difference is: - With breakdown by distinct_id: You see each unique user (distinct_id) who converted, so you see all 3 IDs. - Without breakdown: You see the total number of unique users who converted, which, with the uniques method, is 1 if all conversions are from the same user, or the count of unique users otherwise.
This behavior is consistent with how Mixpanel handles breakdowns and the uniques counting method: "When you apply a breakdown to a metric, by default, Mixpanel tells you how many unique users contributed to each segment... By default, Mixpanel answers the question: per segment, tell me the number of unique users..." See more details here.
If you are seeing 3 different distinct_ids in the breakdown, but only 1 in the aggregate, it means that the aggregate is counting unique users (not attempts), and the breakdown is showing each unique user as a separate row.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! 📚
You're correct: if all conversions are performed by users with different distinct_ids, they should be counted as unique users. In Mixpanel, when using the uniques counting method, the aggregate (no breakdown) should show the total number of unique users (distinct_ids) who converted, not just 1, if there are 3 different distinct_ids.
If you see 3 distinct_ids in the breakdown but only 1 in the aggregate, this is unexpected based on Mixpanel's documented behavior. The documentation states:
"Distinct IDs are used to determine uniqueness, which is crucial for aggregation methods like Uniques and Average per User." "If the Distinct ID on two events are two different values, they will be considered as coming from two separate users."
And for breakdowns:
"When you apply a breakdown to a metric, by default, Mixpanel tells you how many unique users contributed to each segment... By default, Mixpanel answers the question: per segment, tell me the number of unique users..."
Therefore, if you have 3 different distinct_ids, the aggregate should show 3 unique users, not 1. If it does not, there may be a configuration issue, a misunderstanding of the data, or a possible delay in identity resolution (for example, if ID merges are still propagating, which can take up to 24 hours) Funnels FAQ.
If you continue to see this discrepancy, I recommend: - Double-checking the funnel configuration and filters. - Ensuring there are no merges or identity clusters that could be grouping the distinct_ids. - Waiting for any recent identity merges to fully propagate.
If the issue persists, it may be best to contact Mixpanel support with your specific report details, as the knowledge sources do not describe a scenario where unique distinct_ids would be lumped together in the aggregate count.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! 📚
Yes, filtering on Step 5 of a 5-step funnel (rather than using "last step defined" property attribution) does change your expected result.
When you apply a filter specifically to Step 5, Mixpanel only considers events at that step that match your filter criteria. This means that only users whose Step 5 event meets the filter will be counted as conversions. The aggregate count (without breakdown) will show the number of unique users who completed Step 5 and matched the filter, regardless of their distinct_id values.
However, if you break down by distinct_id, you will see each unique user who completed Step 5 and matched the filter as a separate row. If all three users have different distinct_ids and all three completed Step 5 with the filter criteria, both the aggregate and the breakdown should show 3 unique users.
The key difference is that filtering on a specific step restricts the conversion count to only those users whose event at that step matches the filter, while "last step defined" property attribution determines which property value is used for breakdowns and filters applied globally, not just at a specific step. This can affect which users are included in the conversion count, especially if not all users have the property set at Step 5 or if the property value changes between steps.
From the documentation:
"Inline filters allow you to apply event or user property filters to each step of your funnel. This adds granularity and specificity to your conversion criteria... Inline filters are performed pre-query. Thus, these filters will impact your funnel’s conversion by removing events that don’t qualify from consideration of being included in a funnel calculation."
"Event property values can vary from step to step in your funnel, you can choose which step the value is derived from for breakdowns and filters."
Funnels Advanced: Property Attribution
So, yes, filtering on Step 5 (inline filter) versus using "last step defined" (property attribution) can lead to different results in your funnel, especially in the aggregate view. If all three users meet the filter at Step 5, you should see 3 unique users in the aggregate. If not, only those who match the filter at Step 5 will be counted.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
