We have multiple flows by which you can create an account for our product. Each uses the same pages; however, the origin point is naturally different. We're creating events largely based on cta clicks and page loads. I want to be able to track each flow independently. What is the easiest way to distinguish each of the flows from each other given they ultimately use the same pages?
Best answer by Naryie Vasquez
Hey
To track multiple account creation flows that use the same pages, you can consider two options based on your codebase:
Create different events for each state change using code. If your codebase allows you to identify and catch when something triggers the same page load on different events (such as a change in the state's component of your app), you can create different events for each state change using code. While this option requires maintaining more events, it offers more flexibility when analyzing which path a user took, using the pathfinder chart or the user path option within the microscope feature in the funnel chart.
Create an event property with different values for each state change using code. Alternatively, you can create an event property with different values for each state change using code. This option requires maintaining fewer events, but it may limit your ability to analyze user paths or the flow of the account creation process in detail.
In either case, you will need help from a developer to implement the necessary changes in your codebase. Once you have set up the events or event properties, you can use Amplitude to analyze each flow independently based on the events and properties you have created.
Hope it helps!
Hey
To track multiple account creation flows that use the same pages, you can consider two options based on your codebase:
Create different events for each state change using code. If your codebase allows you to identify and catch when something triggers the same page load on different events (such as a change in the state's component of your app), you can create different events for each state change using code. While this option requires maintaining more events, it offers more flexibility when analyzing which path a user took, using the pathfinder chart or the user path option within the microscope feature in the funnel chart.
Create an event property with different values for each state change using code. Alternatively, you can create an event property with different values for each state change using code. This option requires maintaining fewer events, but it may limit your ability to analyze user paths or the flow of the account creation process in detail.
In either case, you will need help from a developer to implement the necessary changes in your codebase. Once you have set up the events or event properties, you can use Amplitude to analyze each flow independently based on the events and properties you have created.
Hope it helps!
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.
