When you want to analyze your users' behavior and use that information in your analytics tool, or in Screeb to show your surveys at the right time, event tracking is essential.
The highest-performing teams plan their tracking by creating a tracking and implementation plan. In this article, we'll share a very simple but powerful way to create this plan so you can start tracking events effectively as soon as possible.
What is event tracking?
Event tracking is the process of collecting and qualifying individual usage of your app by users, so you can use it in your analytics tool or to show Screeb surveys to your users.
For Screeb, you can implement our tracker in your app's code to collect events in a few minutes. You can also use customer data platforms such as Segment, which also let you send your events to other tools, such as analytics or marketing automation software.
What is an event tracking plan?
An event tracking plan is a specification that lists and clarifies all the events you want to track, and how and where you'll track them in your app. An event tracking plan covers as much detail as possible, such as the exact place in the codebase where we'll add the tracker, or the business reasons that require us to track it.
Planning event tracking will help all stakeholders stay on the same page during implementation, and also make sure we track data for every product, every technology, and sales or customer success needs.
A complete tracking plan covers the following:
- The list of events you want to track and their properties
- The rationale for why each one needs to be tracked
- Details on where in the codebase the tracking should be added
- Tracking of the actual implementation of the trackers
How do you choose the right events to track?
Event tracking should help you answer key questions, whether as part of an analytics tool or by showing a Screeb survey to your users.
So you need to think about what you need to learn in order to choose the right events to track.
You'll also track the main events specific to your business (for Screeb, for example, we track the creation of a survey).
How do you define the properties of my events?
In Screeb (but this is also true for CDPs like Segment), you can add properties to each of your events. We recommend doing so, because it will help you filter your events and better analyze your users' behavior.
For example, at Screeb, for each survey created, we track the organization ID so we know who created it. It's the best way to learn from the events you track.
Even though you could send as many properties as you have for your events, we recommend choosing the right ones. It will help you focus on your analysis or make it easier to create your display rules in Screeb.
Best practices
Before creating your event tracking plan, here are some best practices we recommend following:
- Choose your event names carefully. Don't generate them dynamically, and always use the same naming convention. It will be easier to find them in Screeb.
- Don't create events to track properties. Use events to track actions and add properties to them.
- Make sure your events help you answer questions, and make sure every question you have has at least one corresponding event to get the answer.
- Start with your core events, the events that track your product's main features, the most important funnel your users have to go through.
- A tracking plan is never finished! Add events when you release a new feature or when you think some are missing.