Hi, I have a (hopefully) simple question regarding setting up a retention analysis.
We have an event called ‘user_login’, where this event could trigger many times for the same user over their lifespan on the product, but the first time it triggers represents a new user. We’d like to use this event as our starting event for retention analysis, but I’m a little unclear about what happens on each subsequent trigger of ‘user_login’ for the same user...
Is it possible to setup the analysis so that it will only look at the first ‘user_login’ trigger per user? Or any other tips on how we can set something like this up?
Thanks in advance!
Best answer by MikkoKarvonen
malston wrote:
Hi, I have a (hopefully) simple question regarding setting up a retention analysis.
We have an event called ‘user_login’, where this event could trigger many times for the same user over their lifespan on the product, but the first time it triggers represents a new user. We’d like to use this event as our starting event for retention analysis, but I’m a little unclear about what happens on each subsequent trigger of ‘user_login’ for the same user...
Is it possible to setup the analysis so that it will only look at the first ‘user_login’ trigger per user? Or any other tips on how we can set something like this up?
If not, the best solution is to make sure your data is set up in a way that allows you to answer the questions you want to be answered. In this specific case, I would either create a separate event for the sign-ups (which I assume user login for a new user is) or, if you have some reason to avoid this, add an event property to user_login event that allows you to differentiate these cases. I’d recommend a separate event, as your analysis and ability to fully utilize Amplitude features will benefit from having dedicated events to all your key actions (which sign-up definitely is), but the event property approach will also allow you to answer this quetsion.
Hi, I have a (hopefully) simple question regarding setting up a retention analysis.
We have an event called ‘user_login’, where this event could trigger many times for the same user over their lifespan on the product, but the first time it triggers represents a new user. We’d like to use this event as our starting event for retention analysis, but I’m a little unclear about what happens on each subsequent trigger of ‘user_login’ for the same user...
Is it possible to setup the analysis so that it will only look at the first ‘user_login’ trigger per user? Or any other tips on how we can set something like this up?
If not, the best solution is to make sure your data is set up in a way that allows you to answer the questions you want to be answered. In this specific case, I would either create a separate event for the sign-ups (which I assume user login for a new user is) or, if you have some reason to avoid this, add an event property to user_login event that allows you to differentiate these cases. I’d recommend a separate event, as your analysis and ability to fully utilize Amplitude features will benefit from having dedicated events to all your key actions (which sign-up definitely is), but the event property approach will also allow you to answer this quetsion.
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're a current customer, select the domain you use to sign in with Amplitude.
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.
If you're a current customer, select the domain you use to sign in with Amplitude.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
