Data quality is one of the big topics in the modern data stack, and it starts already in the measurement layer.
Dear Data-Traveller, please note that this is a Linkedin-Remix.
I posted this content already on Linkedin in March 2022, but I want to make sure it doesn´t get lost in the social network abyss.
For your accessibility-experience and also for our own content backup, we repost the original text here.
Have a look, leave a like if you like it, and join the conversation in the comments if this sparks a thought!
Original Post:
Plain Text:
Should we call it a tracking plan, measurement plan, or solution design document?
Is plan the right word for it when it is not just a plan but more a part of a constant process?
Who should work on a tracking plan?
How important are metrics when creating a tracking plan?
These are some questions I will ask Stef tomorrow in our webinar.
Data quality is one of the big topics in the modern data stack, and it starts already in the measurement layer.
Measure the correct event data, with the proper context in the same way across platforms, helps you:
– to build the funnels and cohorts in products like Amplitude or Mixpanel that can monitor your business
– save time by not transforming a hell of data in your data warehouse
– build common ground on how events are measured so other applications can build on top of it.
Link to the Webinar: https://bit.ly/36KAzyr%0A