In this guide
- Validate at four layers: the data layer, the container, the platform and your store.
- Write down what each event must contain, then test that, not only that the event fired.
- Automate where you can and keep a weekly routine for the rest.
Most tracking failures are silent. A theme update renames a field, a developer changes the thank-you page, a token expires, and the numbers drift for weeks before anyone notices. Validation is how you notice sooner. This page covers practical techniques at each layer and a short routine that fits into a week. It pairs with Google Tag Manager audit and Google Tag Manager errors.
1. Define what correct looks like
| Event | Must contain | Rules |
|---|---|---|
purchase | transaction_id, value, currency, items | Value is a number, currency is a 3-letter code, items not empty, ID unique |
generate_lead | Form name, source, event_id | Fires once per submission |
add_to_cart | Item ID, price, quantity | Quantity is at least 1 |
This table is your schema. Keep it with your container notes.
3 things to remember
Scroll and the points stack up.
Validate at four layers: the data layer, the container, the platform and your store.
Write down what each event must contain, then test that, not only that the event fired.
Automate where you can and keep a weekly routine for the rest.
2. Validate the data layer
- Open the browser console and read
dataLayerafter each action. - Check types: numbers as numbers, not text with currency symbols.
- Check that the ecommerce object is cleared between events.
- Check that values are present before the tag fires.
3. Validate the container
- Use Preview and read each tag's fields. In a server container, read the incoming event and each outgoing request.
- Add a small test trigger or variable that flags missing values, for example a purchase without a currency.
- Check the container version and the last publish date.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
4. Validate in the platform
- Meta: Test Events and Diagnostics. See event match quality.
- Google Ads: conversion status and diagnostics.
- GA4: DebugView and the real-time report.
- TikTok and others: their test event tools.
5. Validate against your store
The strongest check is simple: compare platform conversions and revenue with your store's orders and revenue for the same dates. A stable gap is fine. A gap that suddenly widens or narrows means something changed. Open Tracked's tracking score gives a quick set-up check (server running, your own subdomain, CDN, Custom Loader, Cookie Keeper and events arriving), and the analytics product lets you compare spend and revenue on first-party data.
Automate what you can
Alerts
Set alerts for a drop in events. Open Tracked offers monitoring alerts on Business (5) and Business+ (10).
Scheduled tests
A script or a monitoring tool that places a test order and checks events.
Dashboards
A daily chart of events by type, so a gap stands out.
A weekly routine
- Place one test order. Check Preview and each platform.
- Compare last week's platform conversions with store orders.
- Look at diagnostics warnings in Meta and Google Ads.
- Check the logs for repeated errors.
- Note anything that changed on the site.
A realistic example
A store notices on a Monday that Meta shows 40 percent fewer purchases than the week before, while the shop's orders are flat. The weekly routine pays off: a test order shows the browser event still fires but the server event fails, with a 401 response. The token was created by a former employee and was revoked when their account was closed. A new token from a business account fixes it within the hour. Without the routine, the failure would have run for weeks while campaigns optimised on half the data. The weekly check took ten minutes and saved a month of misdirected bidding.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Frequently asked questions
What is data validation in tracking?
Checking that events carry the right fields and values at each stage, from the page to the ad platform.
How often should I validate?
After every site or container change, and weekly for key events.
What is the best single check?
Comparing platform conversions with your store's orders.
Can I automate validation?
Partly: alerts on event drops, scheduled test orders and dashboards.
What does the Open Tracked tracking score check?
Whether the server is running, you have your own verified subdomain with a CDN, Custom Loader and Cookie Keeper are on, and events are arriving.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Blog · 5 min read
