I generated a below retention report. Starting and returning events are same, but I am segmenting return events based on an additional attribute. The attribute only has two possible values and both of them are used as below.
In the report, shouldn’t sum of the return events equal to 100%?
Best answer by MikkoKarvonen
Retention does not tell you how the users split between the two options you have chosen. It tells you that out of all the users that have done Journey.AddedPhoto at least once, 88.19% have done so again with context = dashboard, and 29.85% with context=my_journey. It does not stop tracking a user once one of those conditions have been met, so if the same user adds photos using both methods, they’ll be counted for both groups. This is why you are seeing more than 100%.
What is the exact question you are trying to answer?
+3I generated a below retention report. Starting and returning events are same, but I am segmenting return events based on an additional attribute. The attribute only has two possible values and both of them are used as below.
In the report, shouldn’t sum of the return events equal to 100%?
Isn’t it 100%? 88.19 + 11.81 = 100 and 29.85 + 70.15 = 100?
I generated a below retention report. Starting and returning events are same, but I am segmenting return events based on an additional attribute. The attribute only has two possible values and both of them are used as below.
In the report, shouldn’t sum of the return events equal to 100%?
Isn’t it 100%? 88.19 + 11.81 = 100 and 29.85 + 70.15 = 100?
I meant 88.19 + 29.85
+3Retention does not tell you how the users split between the two options you have chosen. It tells you that out of all the users that have done Journey.AddedPhoto at least once, 88.19% have done so again with context = dashboard, and 29.85% with context=my_journey. It does not stop tracking a user once one of those conditions have been met, so if the same user adds photos using both methods, they’ll be counted for both groups. This is why you are seeing more than 100%.
What is the exact question you are trying to answer?
Thanks for the explanation. I wan to distinguish between the context repeat users engage with. The current report answers the question, but I wanted to double check the Discrepancy as I didn’t expect an overlap
+3Thanks for the explanation. I wan to distinguish between the context repeat users engage with. The current report answers the question, but I wanted to double check the Discrepancy as I didn’t expect an overlap
I would do this kind of chart in event segmentation by setting up a cohort for users who have performend Journey.AddedPhoto 2 or more times, and then chosing the Journey.AddedPhoto event and grouping the results by context. If you set the graph to bar diagram and use Active%, you’ll get a very good picture on how the users split between different options.
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
