Event-Tracking plan for measuring adoption of the feature release.

In space of product analytics , each click matters, but we should not be tracking everything. A plan works to keep things in place what we should track and what we should not.

We were trying to solve the following questions :

• Are customers finding and using all the comments functionalities?
• What should we track for adoption?
• Is the UX good enough for users?
• How might we identify different comment users?
• How are comments driving other key actions within the app?
• Are customers who use comments more valuable to us?

GUIDE :

Naming conventions used for event :
1. Title Case
2. Present tense
3 Action word first, Object word second

Name: Name of the event

Why?/Trigger: reason of event or trigger when the event is generated

Distinguished Properties: The properties specific to the event other than default properties

Property Possible Values: Example values/description of the possible values of properties

Location: URL of the event

Ready? : Status of the event

Tested?: Status of the event

Notes : Notes/comments

Naming conventions used for event :
1. Title Case
2. Present tense
3 Action word first, Object word second

Let’s create a dashboard out of it so that numbers can be visualised and we can have a performance impact of the feature on the product.

Thanks!