Challenges and Solutions for Cross-Platform Analytics Event Taxonomy Implementation
Hey ! I'm running into some implementation challenges with my analytics event taxonomy and would love to hear if others have faced similar issues or found good solutions. My event template: {Section}.{Component}.{Action} (e.g. Home Page.Provider Card.Call / Benefit Page.Provider Card.Book) Problem 1 - Reusing components across pages: When an existing component is placed on a new page, I still need to open a dev ticket to implement new analytics for it, instead of it automatically inheriting the Component and Action and just updating the Section based on the current page. This creates a lot of unnecessary overhead. Problem 2 - Web vs. Native inconsistency: We run on two tech stacks (web app + native mobile). Every event implemented on web needs to be mirrored on native. The issue is that on native, the analytics function keeps pulling the wrong Section - so if a user starts on the Home Page and navigates to the Benefit Page, the event still fires with Home Page instead of Benefit Page, giving us dirty data. What I'm looking for:
Has anyone dealt with similar issues, especially on cross-platform setups?
Is there a practical way to fix the implementation approach without changing the taxonomy itself? (We already have historical data built around this structure, so changing the template isn't really an option)
Any experience or advice would be hugely appreciated! 🙏
