**LinkedIn | Website | Upwork**
An Event tracking plan is a structured document that lists down all the user interactions that need to be tracked, along with the data to be sent with each interaction.
User interactions are called events, & data sent with them are called properties.
Here’s a sample tracking plan for your reference. Feel free to duplicate it, & use it for your product.
<aside> 💡 Note: Please ensure to use User profile properties & Super properties in your tracking. They will allow you to do deeper analysis.
To read more about what are super properties, & user profile properties, read this article.
</aside>
Once the tracking plan is ready, ask your Developer to follow the tracking plan & insert code accordingly.
Next, fire events from your product, go to Amplitude, & ensure all events & properties are flowing in the right manner.
If they’re not, talk to the developer & get them fixed.
The objective of the analytics strategy is to be able to build a story around your product, about how users are using the product.
There are multiple frameworks that you can use to create an analytics strategy. The one, I love the most is using the AAARRR funnel.
Here’s a quick article on how you can use AAARRR funnel to create the analytics strategy.
<aside> 💡 Make sure you have a north star metric for each piece of the AAARRR funnel, & then KPIs that can inform the north star metric.
</aside>
A dashboard should tell a story, & should be on point. Hence, it’s very important to structure them in the right way.
Follow the analytics strategy, & build out those metrics on Amplitude.
While building dashboards, ensure the following: