In this guide
- Server-side events usually increase the conversions an ad platform sees, because they recover events lost in the browser.
- It does not change how a platform attributes (windows and models), only how much data it gets.
- Judge the change against store orders, not against yesterday's platform number.
You turn on server-side tracking, and a week later Meta shows more purchases and a better ROAS. Is the campaign better, or is the data different? Both can be true, and mixing them up leads to bad decisions. This page explains what changes, what does not, and how to read the new numbers. See also Meta Conversions API vs Pixel and cookieless advertising.
How much is your tracking missing?
Put in your own numbers. This is an estimate, not a promise.
Most stores do not know this number. Start with 20% and compare it with the orders in your store.
That is the signal Meta and Google are missing when they decide who to show your ads to. Server-side tracking sends it back.
3 things to remember
Scroll and the points stack up.
Server-side events usually increase the conversions an ad platform sees, because they recover events lost in the browser.
It does not change how a platform attributes (windows and models), only how much data it gets.
Judge the change against store orders, not against yesterday's platform number.
What changes
| Area | Before | After |
|---|---|---|
| Events seen | Only what the browser delivered | Browser events plus server events recovered |
| Attribution of a sale | Often missing for Safari and blocked visitors | More sales linked to the ad that brought them |
| Match quality | Low, few identifiers | Higher with hashed e-mail, phone and cookies |
| Platform ROAS | Understated | Closer to your store's truth |
What does not change
- Attribution windows. Meta, Google and TikTok still use their own click and view windows, such as 7-day click.
- Attribution models. Each platform still credits its own ads. They will still overlap, so adding platform numbers together double counts.
- The real orders. Your store has the same number of orders. Only the platforms' view moved.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
How to read the numbers
Take a baseline week
Platform purchases and store orders for the week before the change.
Take the first week after
The same two numbers.
Compute the gap
Platform purchases divided by store orders, before and after.
Expect the gap to shrink
A gap closer to one means the platform sees more of your reality.
Look at cost per purchase
It may fall because the platform now counts more purchases for the same spend.
Risks to watch
A fair way to judge campaigns
Use your own source of truth: orders, revenue and profit in your store or analytics. Compare campaigns by blended ROAS and by profit, not only by what each platform reports. Open Tracked's analytics shows spend, revenue, ROAS and profit by channel next to the tracking, which makes this comparison one screen. See ROAS vs POAS.
A worked example
A store has 1,000 orders a month and spends $10,000 on Meta. Before the change, Meta reports 520 purchases and a ROAS of 2.1. The store's own data shows that about 700 of the 1,000 orders came from Meta traffic. After a week of server-side events with hashed e-mail and a shared event ID, Meta reports 640 purchases and a ROAS of 2.6. Nothing about the ads changed. Meta simply sees more of what was already happening. The remaining gap, 640 against about 700, is the part that blockers, declined consent and cross-device buying still hide.
The mistake to avoid is to take the new 2.6 as proof that the campaigns improved and scale spend on it. Use the new number as a better estimate, and let profit and blended results guide budget changes. These figures are an illustration of the pattern, not a result you should expect: your own numbers depend on your traffic and set-up.
Terms you will see
- Attribution window
- The time after a click or view during which a platform credits a sale to an ad.
- View-through conversion
- A sale credited to an ad the person saw but did not click.
- Blended ROAS
- Total revenue divided by total ad spend across all channels.
- Incrementality
- The sales that happened because of the ad and would not have happened without it.
- Modelled conversion
- A conversion the platform estimates when it cannot observe it.
One more point for agencies: tell the client about the change before it happens. A client who sees purchases jump by a fifth after a tracking fix may think the ads suddenly improved, and a client who later sees them fall back may think the fix stopped working. A short note with the baseline numbers, the date of the change and the reason the numbers will move avoids both misunderstandings, and it shows that you are measuring carefully rather than chasing a good-looking chart.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Frequently asked questions
Will server-side tracking increase my ROAS?
The platform-reported ROAS often rises because more conversions are seen. Your real ROAS only improves if the platform then optimises better.
Why do I see more conversions after setting it up?
Events lost in the browser now arrive from the server, and match quality improves.
Does it change attribution windows?
No. Windows and models are set by each platform.
Can I trust platform numbers now?
They are closer to reality, but still modelled and overlapping. Check against store orders.
How long until the numbers settle?
About one to two weeks.
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 · 7 min read
