GA4, GTM, and the data layerVerified at every stepWithout writing any code
An event that won't go away, a purchase value of zero, a product ID that changes format. The tagging plan breaks silently, and the error isn't noticed until weeks later, when the numbers don't add up.
That’s what makes it dangerous. The site works perfectly—customers make purchases, and no one reports any issues. Meanwhile, the purchase event is recorded with a zero amount, and you’re managing your advertising budgets based on inaccurate data. The problem isn’t discovered until the end of the month, when it’s too late to recover the lost data.
The script tracks the process and verifies that at each step, the expected event is triggered exactly once.
Product ID, amount, currency, quantity. An event that starts with an empty value is just as serious as a missing event.
What happens before and after the user makes a choice. A tag that is set despite a refusal is a compliance issue.
The tagging plan is reviewed just like everything else—not just once a year during an audit.
“With Mr Suricate, we’ve automated label verification, secured our data, and gained the reliability we need to make strategic decisions without errors. Plus, it’s fun!”
Xavier ValetHead of Data Analytics, HelloWork
GO FURTHER
Fifteen types of tests, four categories. Each one answers a different question about your application.
Is there a term you don't understand? The automated testing glossary defines it.
YOUR QUESTIONS
The most common questions we get about tagging control.
This is a scenario that simulates a user journey and checks, at each step, the events pushed to the site's data layer. It verifies the presence of the event, its name, and the content of its parameters.
Yes. The check focuses on what your site actually sends to the data layer, which is the source of the data received by GTM and then GA4. This is the right level to check: we verify the data being sent, not how it appears in the destination tool.
Yes, and that's one of the most useful scenarios. The script can block cookies, then verify that no tracking tags are being sent, and do the opposite after acceptance. This serves as a check for both compliance and data quality.
With every production deployment, just as with regression testing. A tagging plan most often fails due to a change to the site that had nothing to do with the measurement—and thus fell outside the data team’s scope of attention.
No. The flow is built just like any other scenario, and event handlers are added to the relevant steps. The preliminary work is editorial rather than technical: you need to know which event should be triggered and with what values.
A 30-minute demo of your own app. You'll see one of your workflows automated in real time, without writing any code.