Open Tracked/Guides/Server side tracking post launch guide

Server side tracking post launch guide

Launching is the beginning. The first month decides whether the set-up stays reliable.

4 min read · Updated October 26, 2026

In this guide

The first 24 hours The first week The first month What to avoid while you measure Typical post-launch issues The ongoing routine A realistic example Frequently asked questions

Before you start

Check events in the first 24 hours, numbers against orders in the first week and cost effects in the first month.
Avoid big campaign or site changes while you measure.
Build a routine: one weekly check, one monthly review.

The launch day is exciting and not the hard part. The hard part is the following weeks, when small problems appear and nobody is looking. This post-launch guide lists what to check and when. It follows the setup checklist and leads into data validation techniques.

The first 24 hours

0 of 6 done

Open server Preview and place a real test orderCheck the logs for errorsCheck that each platform shows the event: Meta Test Events, Google Ads status, GA4 real timeCheck that the container version is publishedCheck that consent works: reject all, then accept allTake a screenshot of the working state

Check your setup

Check your tracking in one pass

This is an example. Run the check on your own site to see where yours stands.

The first week

0 of 6 done

Compare platform purchases with shop orders each dayCheck Meta deduplication and match qualityCheck that purchases are not counted twiceCheck the tracking score and power-up tests in Open TrackedRead the logs for repeated errorsTell the team what numbers to expect

The first month

0 of 6 done

Compare ratios with the baseline from before launchCheck cost per purchase and ROAS over four weeksReview monitoring alerts and fix noisy onesReview hosting usage against your planUpdate the documentation notePlan the next improvement: offline conversions, profit data, more platforms

The short version

3 things to remember

Scroll and the points stack up.

Check events in the first 24 hours, numbers against orders in the first week and cost effects in the first month.

Avoid big campaign or site changes while you measure.

Build a routine: one weekly check, one monthly review.

What to avoid while you measure

Large budget changes in the first two weeks.
New tracking changes without a note and a date.
Switching off the browser pixel before you have compared.
Reading a single day as a trend.

Typical post-launch issues

SymptomNumbers jump on day one

Likely causeEvents from both browser and server are counted.

FixCheck event IDs and deduplication.

SymptomNumbers fall on day two

Likely causeA duplicate source was removed, or a token expired.

FixCheck the logs and tokens.

SymptomA platform shows nothing

Likely causeThe tag failed.

FixRead the outgoing request in Preview.

SymptomHosting usage is higher than expected

Likely causeMore requests than planned.

FixReview events and the plan. See how much a server GTM costs.

The ongoing routine

When	What
Weekly	A test order and a platform-to-store comparison
Monthly	Diagnostics review, hosting usage, documentation
Quarterly	A short audit. See Google Tag Manager audit
After any site change	A test order

Open Tracked supports this with logs (3 days on Pro, 10 on Business), monitoring alerts (5 on Business, 10 on Business+) and a tracking score that shows whether the set-up is complete.

A realistic example

A store launches on a Tuesday. The first day looks perfect. On day three the Meta purchase count drops sharply, and the daily comparison catches it the same morning. The log shows a 401 response: the access token was created from a personal account that had been removed from the business the day before. The team creates a new token from a business account, and the count recovers. Without the daily comparison in the first week, the problem would have run for weeks. The post-launch routine is not bureaucracy. It is how the first small failure is found while it is still small.

Keep a simple log during the first month: the date, what changed, what you saw and what you decided. When a number moves, you can look at the log and see whether a change on the site, in the container or in a campaign came just before. Most puzzling movements have a boring explanation that the log makes obvious. After the first month the log can shrink to a line a week.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

Frequently asked questions

What should I check after launching server-side tracking?

Events in the first 24 hours, platform numbers against orders in the first week and cost effects over the first month.

When will I see results?

Counts change within days. Cost effects need several weeks of data.

What should I avoid during the first weeks?

Large budget changes and untracked changes to the set-up.

How often should I test?

Weekly with a real order, and after every site change.

Where do I see errors?

In server Preview and the logs.

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.

Start free More in Guides →

Written by

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?

Write to us Read the docs

Was this article helpful?