As games become more complex, the volume of potential data points can be enormous, but collecting everything isn't always practical or necessary. I'm curious about how you decide what data to track and what to ignore. Do you start with comprehensive tracking and narrow down, or build incrementally based on specific questions? How do you balance granular event tracking with system performance and storage costs? What criteria help you prioritize which player actions warrant dedicated analytics events? Do you use sampling techniques for high-frequency events, or do you track everything and aggregate later? How do you handle the lifecycle of analytics events as your game evolves - deprecating old events, adding new ones? What governance processes ensure teams don't create redundant or poorly-defined tracking events? I'd love to hear about frameworks that keep your data collection focused and actionable.
Welcome!
Share and discuss the best content and new marketing ideas, build your professional profile and become a better marketer together.
This question has been flagged
28
Views
Enjoying the discussion? Don't just read, join in!
Create an account today to enjoy exclusive features and engage with our awesome community!
Sign up