The magic of tracking plans (2/5)

A good tracking plan is no rocket science just some simple rules applied.

Today I will share my learnings of building a lot tracking plans:

🐯 Naming events is simple: Object + Action – Action in past tense (because the event already happened): Registration submitted. Sometimes I like to give a bit more context to the Object: Signup Onboarding finished

🪢 Event attributes adds context to each event. These are later your segmentations in the analysis. Make sure to use similar naming across the plan. Not “plan” and “subscription_plan”

🤷‍♂️ Everyone can understand the events without a lot of context – Test the tracking plan with different teams and stakeholders if they get the events

🏃‍♀️ Keep the number of events as small as possible. Use attributes for context. You don’t need a single event for each signup button (cta_placement: navigation, hero, pricing – will do the job).

⚖️ Balance between events and attributes – Sometimes you could merge 2 events into one with attributes but these events are so important so it is cool to leave them unmerged.

What are your best practices?

Part 3 – “Think ahead – what are you analysis scenarios” coming tomorrow. Follow me, so you don’t miss the other magic things about tracking plans.