In this guide
- Measure the gap between platform and store numbers before and after.
- Change one thing at a time and keep campaigns steady while you measure.
- Report what you can show and what you cannot. Honesty builds trust.
Everyone wants to know whether server-side tracking was worth it. The honest way to answer is a clean comparison, not a claim. This page shows how to set up a before-and-after, what to measure, what can distort the result and how to report. It uses ideas from attribution with server-side tracking and data validation.
Choose the metrics
| Metric | Why |
|---|---|
| Orders in the shop | The reference that does not change with tracking |
| Purchases and revenue in each ad platform | Shows how much the platform sees |
| Platform-to-store ratio | Purchases in the platform divided by shop orders from that channel |
| Event match quality (Meta) | Shows data quality |
| Cost per purchase in the platform | A downstream effect, which takes weeks |
| Duplicate rate | Should be close to zero |
Works with your stack
Grab a logo and throw it. These are the tools Open Tracked already talks to.
Run the comparison
Take a baseline
At least two full weeks of platform and store numbers before the change.
Freeze other changes
No new campaigns, big budget shifts or site changes where possible.
Make the change
Server-side events with a shared event ID.
Wait
Two weeks of data after the change, avoiding sales events.
Compare ratios
Platform-to-store ratio before and after.
What can distort the result
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.
Calculate the value
A fair estimate: the extra purchases the platform now sees, times average order value, is the revenue that was invisible. The business value is not that revenue itself, but the improvement in optimisation and decisions that comes from seeing it. You can estimate this by comparing cost per purchase or ROAS over a longer period, with the caution that many things change. Present the gap closure as the hard evidence and the cost improvement as a likely benefit.
Report honestly
- Show before and after on one page.
- State the assumptions and the period.
- Separate what is measured (gap closure) from what is estimated (value).
- Say what has not improved yet.
Add profit
A better picture of revenue is useful. A better picture of profit is better. Open Tracked's POAS Data Feed (Pro) sends profit to GA4 and Google Ads, and its analytics shows profit by channel. See profit on ad spend.
A realistic example
A store records two weeks of baseline: 1,100 shop orders from paid social and 640 purchases in Meta, a ratio of 58 percent. It launches server-side events with a shared event ID and keeps campaigns unchanged. Two weeks later, the shop shows 1,150 orders and Meta shows 830 purchases, a ratio of 72 percent. Deduplication is checked and Meta marks the overlapping events as deduplicated. The team reports that the platform now sees an extra 14 points of its orders, and that cost per purchase in Meta fell by a few percent over the month, while noting that other factors could have contributed. That honest report is more convincing than a bold claim, because the client can check every number.
Check your tracking in one pass
This is an example. Run the check on your own site to see where yours stands.
Frequently asked questions
How do I prove server-side tracking works?
Compare the ratio of platform purchases to shop orders before and after, with deduplication checked and other changes frozen.
How long should I measure?
Two weeks before and two weeks after, avoiding sales events.
Will ROAS improve?
Reported ROAS often rises as the platform sees more purchases. Judge real improvement by profit and cost per purchase over time.
What if the gap does not close?
Check deduplication, matching data and consent. Some gaps remain because of declined consent and other devices.
Can I show value in dollars?
You can show invisible revenue and estimate the benefit. Be clear which is which.
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...
Integrations · 6 min read
