Importance of Aligning Event Structure Definitions and Implementation

Hey there! Friendly bump on this question. It would be a huge unlock, as it would prevent drift between the folks defining the event structure and those implementing them. Cheers!

9 comments

Josh L.
·
·
Hey Kim W. thanks for the nudge here
Josh L.
·
·
I would use the tracking specification planner template to do this in GSheets/Excel first. That way you can share all of this information with the organisation and get it right BEFORE it is all implemented.
Josh L.
·
·
you will have a chance to review the naming conventions, the properties set with each event and the way in which this information is captured ahead of the implementation
Josh L.
·
·
I always say "a tracking spec is for life, not just for Christmas". It's cheesy BUT it is so true; utilise this document for all changes and new events, even the removal of events as the front line of your data governance before making any changes in the code and/or Mixpanel
😂1
❤️1
Josh L.
·
·
you can hide events, rename them and add descriptions in the Lexicon to reflect changes as well
Josh L.
·
·
this is an extra step, but it is important in keeping your governance on track and your data hygiene up to scratch
Josh L.
·
·
hope this helps ✌️
Kim W.
·
·
that's awesome! It's very validating to hear Josh L. - and "tracking spec for life, not just for Christmas" resonates pretty strongly. I am starting to find that the lack of rigor/rigidity at this step causes all sorts of issues downstream
🙌1
Josh L.
·
·
It definitely will cause issues Kim W. - let me know if you need any further assistance