Mixpanel Community Icon

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 🙏

  • Avatar of Andrew S.
    Andrew S.
    ·
    ·

    Not sure I follow exactly but I would record an explicit event for “initial_screen” or something that so you can explicitly measure initial screen views and then could use it in a flow to see starting at that initial screen event.

  • Avatar of Santi (.
    Santi (.
    ·
    ·

    Sophie, my recommendation is always to start with the KPIs. Define the metrics you need/track/improve and from that create a tracking plan. These resources in the "guides" section are very useful: https://docs.mixpanel.com/guides/plan/tracking-strategy#creating-a-tracking-plan We have templates for tracking plans: Saas for example: https://docs.google.com/spreadsheets/d/1A5wm5MKzRfSOZfUfCAg8YpePiz8Jn3Ar_u8KBo5lD6g/edit?gid=1641519238#gid=1641519238

  • Avatar of Sophie P.
    Sophie P.
    ·
    ·

    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...

  • Avatar of Andrew S.
    Andrew S.
    ·
    ·

    yeah, if the "property" you want to track is "where were they", make that the same with the value for the location. And you can then do another property then for "source_name" or something like that. Otherwise, you have to create a custom property that basically combines the three properties (page name, top nav, sub-nav) so you can then treat the singular custom property like the alternative structure.

  • Avatar of Sophie P.
    Sophie P.
    ·
    ·

    thanks Andrew S.!