Sophie P.

Commented on Best Practices for Tracking Multi-Level Navigation...·Posted inCommunity Questions

Thanks for the example! It's very helpfuI. I see you used values for the different ''entry point''. I think it could be better than what we were doing...We were using properties for each entry point like (Nav name, Page name, Tab name etc...) Which I think was bad. Event name : View report Event Property: Entry Point Property Value: Top Nav, Sub-Nav, Dashboard We were doing Event name : View Survey Event Property: Page Name, Top nav, Sub-nav ... Value : Name of the page, name of the top nav etc...

Posted in Community Questions·

Sophie P.

Best Practices for Tracking Multi-Level Navigation in Mixpanel

Hello everyone, I'm pretty new to Mixpanel and tracking data (and so is our startup). We just been implementing it and we are fine-tuning our naming convention and the basic events we would like to track.

I would need help to answer this ➡️ 'What would be the best way or best-practices to track a multi-level navigation''. Is anyone has a similar usecase?

We want to understand how user navigate.
In our survey details, the first tab is alway implicitly ''seen'' by our user because it's where he's landing.

If we use events on click, we will miss this first tabs. Is that the right way to do it?
If we put the event trigger on the page loading; this seem to cause to many events. (Clicks on a specific survey + Page view)

Here's a screenshot that better explain our hierarchy. I dont know if it's clearly explained, but I would certainly appreciated any tips! Thank you for your help 🙏

1 attachment

5Comments