In this guide
- Monitor in layers: server uptime, event volume, errors, platform diagnostics and purchases against orders.
- Set alerts for drops and failures. Open Tracked offers monitoring alerts on Business (5) and Business+ (10).
- Add a weekly test order. Nothing beats a real purchase.
Most tracking failures are not dramatic. A token expires. A theme update renames a field. A deployment removes a tag. Numbers drift for days or weeks until someone notices a strange report. Monitoring shrinks that time. This page gives a layered approach you can set up in an afternoon. It continues from data validation techniques, post-launch guide and Google Tag Manager audit.
What to watch
| Layer | What to check | How |
|---|---|---|
| Server | Is the tagging server up? | An uptime check on https://your-subdomain/healthy |
| Events | Are events arriving at normal volume? | Logs and request counts by day; an alert on a sharp drop |
| Tags | Are tags failing? | Server Preview and the logs; errors by tag |
| Tokens | Are access tokens valid? | A calendar reminder and a test event; alerts from platforms |
| Platforms | Do platforms show warnings? | Meta Diagnostics, Google Ads diagnostics, GA4 data checks |
| Business | Do platform purchases track store orders? | A weekly ratio |
3 things to remember
Scroll and the points stack up.
Monitor in layers: server uptime, event volume, errors, platform diagnostics and purchases against orders.
Set alerts for drops and failures. Open Tracked offers monitoring alerts on Business (5) and Business+ (10).
Add a weekly test order. Nothing beats a real purchase.
Alerts
Set alerts you will actually act on. Too many, and people ignore them. A good starter set: the server health check fails, event volume drops by more than a set share against the same weekday last week, the number of failed requests rises, a platform sends a diagnostic warning. Open Tracked's monitoring on the Business plan includes up to 5 alerts and up to 10 on Business+. Pick the ones for your most important flows.
A synthetic test order
Once a week, or daily for large stores, place a test order and check that it appears in Preview, in each platform's test tool and in your analytics. Automate it with a scheduled script or a browser testing tool if you can. A human check is fine to begin with.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
Logs
Logs show what the server received and answered. Open Tracked keeps logs for 3 days on Pro and 10 days on Business, with export from Business+. Use them to answer "did the request arrive?". Review them after any change, and when numbers move.
A response routine
Confirm the problem
Is it real, and since when?
Check recent changes
Site, container, hosting, consent banner, tokens.
Find the layer
Server, events, tag, platform.
Fix and test
With a test order.
Record what happened
In your change log, with the cause.
Make monitoring part of the job
- Assign an owner for alerts.
- Review alert settings quarterly.
- Include a monitoring section in every client handover.
A realistic example
A store sets up an uptime check on its tagging subdomain, an alert for a drop of more than 30 percent in daily events and a weekly test order. Three weeks later the alert fires on a Tuesday morning: event volume fell by half overnight. The logs show requests arriving but the purchase tag failing with an authentication error. The Meta token had been revoked when an agency user left the business account. A new business token fixes it before lunch. Without monitoring, the failure would have run until the monthly report. The set-up took an hour and paid for itself the first time it fired.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Frequently asked questions
How do I monitor website tracking?
Check server uptime, event volume, errors, platform diagnostics and the ratio of platform purchases to store orders, and set alerts for drops.
What alerts should I set?
Server health, a drop in event volume, a rise in failures and platform warnings.
Does Open Tracked offer monitoring?
Yes. The Business plan includes up to 5 alerts and Business+ up to 10.
How often should I place a test order?
Weekly at minimum, daily for large stores.
Where do I see what the server received?
In the logs: 3 days on Pro and 10 days on Business.
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...
Guides · 6 min read
