Free Video Course:
How to create a Posthog tracking plan
Grow your business and product by tracking the right event data in the right shape every day.
Free Video Course:
Why is data so hard?
Why is your tracking not working
Don't worry. Most business struggle with their data tracking setup. Because it's not easy to set up, it takes some effort to do it right from the design and implementation.
Not the right data
- Always when you analyze the data, something is missing. Or you can't get the data you need to analyze an entire funnel because the user id is changing somewhere in between.
Too many events
- Most setups have way too many events. Over 30-40 events get hard to manage and maintain. And even with tracking almost everything, you usually miss the important ones.
No trust in data
- Because people don't find suitable events to answer their questions. Or because some data looks wrong. Or doesn't match with other systems' data.
No idea what to do with it
- Even with reliable tracking data, the critical question remains: what can I get from the data that makes my product better and my business more revenue and fewer costs?
A good tracking plan design will solve your problem.
In our course we show you how to structure your data based on your business, product and marketing.
Posthog
Create a Posthog tracking plan
Posthog is one of the most exiting new analytics platforms out there.
Calling themselve a Product OS platform is not an exaggeration. Posthog goes beyond classic product analytics by providing more context with experiments, feature flags, session recording and more.
You can use explicit events, auto-tracking, and session recording in one tool - When I worked as a product manager, I had to use 2-3 tools for that and kind of combined all (which never worked)
You will get the ability to extend the setup with apps - you can use existing apps from Posthog or the community or build your own to receive or transform data before it gets into Posthog or to send data from Posthog to other destinations (e.g., I send data to BigQuery and Avo). I am currently working on an app to receive webhook data
And feature flags and experimentation - I don’t use it for now. Still, feature flags are something I fell in love with when working in a more extensive product organization. Changes the way you do deployments and experiments.
Our course: Get the right data with the right event design.
Insufficient data or too many events is a design problem, not an implementation problem. You get the correct data by tracking 20-30 core events with the right design.
“Excellent as always - really helped develop our analytics platform further and assisted with direct comms to our client so they were able to articulate their needs and explain how this data could be provided. Much appreciated as always.”
How this course can help you
We have developed two frameworks to design better event data and tracking plans.
Three-layer event schema
We work with three layers of event data to focus on suitable events. We are going from a high-level business focus to a granular interaction focus.
Core Business events
- Your business works specifically, and so does your customer journey. These events need to cover how your business works and the core touchpoints of your customer journey.
Product events
- Define the events based on your product features to understand how your users use your features to create successful sessions.
Interaction events
- Especially for your UX, design, and product teams, it's essential to see how users interact with your platform in granular detail. But these events you usually don't add to a tracking plan.
Entity & Activity Model
Define your business and product entities first. They define the scope you want to look at your data. Then explain the activities of these entities and, finally, their properties.
Entity
- These are your essential business objects (not teams) or your product features (high-level). They define a specific view of the data.
Activity
- All the events that can happen within an entity. From a business perspective, these usually form a lifetime funnel within an entity.
Property
- Properties are usually defined for an entity. They bring context to the data, and they are the dimensions you will later segment and break down your data.
learn with deepskydata
You can find these topics in the online video course
01 - Welcome to how to create good tracking plans
02 - What makes tracking so hard?
03 - An existing setup with the “just dump the data” model
04 - What do you want to achieve with data
05 - How does Posthog work and what features does it offer?
06 - Building a business blueprint to collect the right data
07 - Mapping your business and product events with event storming
08 - Mapping product use cases and critical paths
09 - How to develop a good event schema
10 - The power of event properties
11 - How to develop, manage, implement and own a Tracking plan
12 - How to implement tracking for Posthog
Sign up today to our free course:Learn how to design a good tracking plan.
We walk you through how to define the actual events and give them a scalable structure that still works in some years.
Sign up for free