Skip to main content

Hello!

 

I know the best practice is to define the nomenclature of events, then create the dashboard and then the devs sending the events to production.

 

However, I see that, as long as an event is not triggered in production, it doesn't appear anywhere. It is the moment when one of the testers triggers each and all of the events proposed when they start appearing in Amplitude.

 

Therefore the process we currently follow is the opposite to the best practice: we define the nomenclature of events + send them to production + create the dashboard.

 

Is there any way to follow the process as in the best practice? Am I missing anything?

 

Thanks in advance :) 

What I think works best is that you send the events to a separate “test” amplitude project, and create the charts/dashboards for that project. Then when the events go to production, you can switch the charts/dashboards over to that project.

Reply


Terms & ConditionsCookie settings