How can you test your tracking setup while keeping clean data in production? Anuj Sharma, Sr. Customer Success Architect at Amplitude, shares some tips:
“We would always recommend that you have all of your events sent out to a dev environment first. Validated there and then moved to a production environment.
Similar to that, using branches in Amplitude is also quite helpful. You can have branches and work on branches with your developers. You're not impacting any of your data in the main branch, so it doesn't pollute anything. So you're branching out from that main branch, creating your new events. They're testing it out. They're making sure it's all valid and then merging it into your main branch.”
This is a snippet from Tracking Plan and Event Schema an Amplitude Tracking Plan Office Hours session with Ampliteers Jennifer Rudin and Anuj Sharma, who answer users’ burning data governance questions, covering when to use events or user properties, staging environments, and how to QA your setup.
Related Tips:
