In our product, customer page URLs include dynamic values in the format like /stores/:id/popular. Currently, when testing the integration with Amplitude, the actual id values are being sent, which makes it difficult to analyze the data effectively.
How can I ensure events are sent correctly to Amplitude while addressing this issue?
Any updates on this we need an answer on this desperately. Almost every URL on our platform is a dynamic path. We need to filter events using this. We have sent URL’s with events as well.
There are a couple of methods you could use to consolidate.
One popular option going forward would be to send Amplitude a property like page_type, which could represent the consolidated format that you prefer for analysis.
Users on Enterprise plans have access to derived properties and one could create a page_type grouping leveraging regex_extract() or glob match.
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.