Besides production, you can run Trackingplan on other environments – like staging or development – to detect problems before a release.
Integrating your staging and testing environments and comparing them to your baseline allows you to see the differences between one release and the next, detecting broken events or schemas before releasing them.
To set it up, you’ll just need to modify this init according to your specifications and your own TP_ID and add it at the top of the <head> section of your site (instructions here), or include it as a new Google Tag Manager Script (instructions here).
As you can see, the installation process is the same as the one you carried out when installing Trackingplan. The only thing that changes here is the environment variable within the init provided above.
After this easy installation, you’ll be able to see Trackingplan’s results in real-time or through automated digests (e.g. reporting results on daily or weekly development cycles).
As a result, you can also cover the analytics service integrations in your existing release testing by simply integrating Trackingplan without changing your feature or testing code in any way. That way, any existing automated QA you have implemented, such as functional or non-functional regression testing (e.g. with Cypress), will stress your analytics under the watch of our system.
If you want to know more about how tracking can become a first-class citizen in your QA, you can read this blog post here.