Josh L.

It definitely will cause issues Kim W. - let me know if you need any further assistance

hope this helps ✌️

this is an extra step, but it is important in keeping your governance on track and your data hygiene up to scratch

you can hide events, rename them and add descriptions in the Lexicon to reflect changes as well

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

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

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.

Hey Kim W. thanks for the nudge here

You will also notice in the debugger in Segment that it would generally pass through the referrer and path as standard. In Mixpanel you can create custom properties which can group certain values together, where you can actually provide a proxy name and also utilise this for traffic source measurement in Mixpanel 👌

If you haven't already - look at this