What should I track?
In order to understand what people do in your product you need to know:
- Who your users are (e.g. their email address, role, etc.)
- What they do (e.g. what actions they take)
If you don’t have anything in place to track this information yet, don’t worry. We’ll walk you through how to set it up. But before we do that I want to give you a couple of tips, so you can get the most out of Bigdelta.
Start with 3 events
When you’re just getting started with Bigdelta, it’s easy to get overwhelmed by all the things you could track. Therefore, we suggest you limit yourself to just 5 events as a starting point. If you’re not sure what to track, here are some ideas:
- Signed up
- Logged in
- Used an important feature (e.g. placed an order, created a project, sent a message)
Make sure you keep your event names short and descriptive. What we like to use is the Object-Action convention:
The aim is for event names to be clear even without additional context.
Start with 3 properties
You can think of traits as a way to filter in and out the users and companies you care about. Our recommendation for traits is include information about:
- Subscription status (e.g. free, trial, paid)
- Role (e.g. admin, editor, viewer)
- Source of signup (e.g. organic, referral, paid)
If you’re a B2B company, you’ll want most of your traits to be company-wide. If you’re a B2C company, you’ll want your traits to be user-specific.
Keep most of your tracking server-side
Adblockers and modern browsers are making it harder and harder to track users on the client-side. So if you want to make sure the data you’re collecting is accurate, you’ll want to do most of your tracking server-side.
Based on our observations, client-side events result in a loss of between 15% and 30% of events. Therefore, if you’re tracking events exclusively on the client-side, a significant amount of data is not accounted for, even when using a reverse proxy.
Next steps
Let’s jump right in and get started with setting up Bigdelta.
What should I track?
In order to understand what people do in your product you need to know:
- Who your users are (e.g. their email address, role, etc.)
- What they do (e.g. what actions they take)
If you don’t have anything in place to track this information yet, don’t worry. We’ll walk you through how to set it up. But before we do that I want to give you a couple of tips, so you can get the most out of Bigdelta.
Start with 3 events
When you’re just getting started with Bigdelta, it’s easy to get overwhelmed by all the things you could track. Therefore, we suggest you limit yourself to just 5 events as a starting point. If you’re not sure what to track, here are some ideas:
- Signed up
- Logged in
- Used an important feature (e.g. placed an order, created a project, sent a message)
Make sure you keep your event names short and descriptive. What we like to use is the Object-Action convention:
The aim is for event names to be clear even without additional context.
Start with 3 properties
You can think of traits as a way to filter in and out the users and companies you care about. Our recommendation for traits is include information about:
- Subscription status (e.g. free, trial, paid)
- Role (e.g. admin, editor, viewer)
- Source of signup (e.g. organic, referral, paid)
If you’re a B2B company, you’ll want most of your traits to be company-wide. If you’re a B2C company, you’ll want your traits to be user-specific.
Keep most of your tracking server-side
Adblockers and modern browsers are making it harder and harder to track users on the client-side. So if you want to make sure the data you’re collecting is accurate, you’ll want to do most of your tracking server-side.
Based on our observations, client-side events result in a loss of between 15% and 30% of events. Therefore, if you’re tracking events exclusively on the client-side, a significant amount of data is not accounted for, even when using a reverse proxy.
Next steps
Let’s jump right in and get started with setting up Bigdelta.