Server-side conversion events: why your adverts under-report and how to fix it
Browser tracking misses a growing share of purchases: blockers, privacy settings, closed tabs. Sending the purchase from your server as well fills the gap — if it is done with consent and without double-counting.
4 min read
In short: a server-side conversion event is a purchase report sent from your store’s server to the ad platform (Meta Conversions API, TikTok Events API, Snap Conversions API, Google Data Manager API), in addition to the browser pixel. It recovers purchases the browser never reported. Done properly, it uses hashed customer data, the order number to avoid double-counting, and only fires when the visitor consented. Wameed supports it as an optional setting on every plan.
The problem it solves
A browser pixel depends on the visitor’s browser cooperating. It does not always:
- Ad blockers and privacy browsers stop scripts from loading.
- Privacy settings on phones and browsers limit what tracking can see.
- Closed tabs and slow pages — the visitor pays and leaves before the pixel reports.
The result is that your adverts produce orders that the platform never sees. It then under-reports results and, worse, optimises on incomplete data.
What “server-side” means
Instead of relying only on the browser, the store’s server tells the platform directly: “order 10482 was paid, for this value, by a customer with this (hashed) e-mail.” The platform matches it to the advert that produced it.
It is an addition to the pixel, not a replacement. Running both is recommended, because each catches what the other misses.
The platforms
| Platform | Server interface |
|---|---|
| Meta | Conversions API |
| TikTok | Events API |
| Snapchat | Conversions API |
| Data Manager API |
Google Tag Manager on its own has no server feed. Using it does not give you server-side events; you need the platform’s own interface.
How to keep it safe and accurate
Three rules matter.
1. Hash the personal data
Identifiers such as e-mail and phone are sent asone-way hashes, so the platform can match a person without receiving their raw details. Wameed sends hashed customer data.
2. De-duplicate
If the browser and the server both report the same purchase, the platform must know they are one. The solution is a sharedevent ID. Wameed uses theorder number as the de-duplication ID, so the same purchase is counted once.
3. Respect consent
Server-side events are still tracking. They should fire only when the visitor consented, and Wameed gates them by consent. A visitor who declined the banner is not reported.
Seead pixels andcustomer data and the PDPL.
When it is worth turning on
- You spend meaningfully on Meta, TikTok or Snapchat and the platform’s numbers look lower than your orders.
- Many of your visitors use iPhones or privacy browsers.
- You want the platform to optimise on more of your real purchases.
If you spend little, start with the pixel and a good analytics setup. Server-side is not magic; it is plumbing.
How to check it works
- Place a test order.
- In each platform’s event manager, confirm thepurchase arrives once, not twice, and is marked as received from both the browser and the server.
- Check the value, currency and the order number.
- Compare ten real orders against what the platform shows after a few days.
Frequently asked questions
Does server-side tracking get around consent?
No, and it should not. It is gated by the same consent as the pixel. A visitor who declines is not reported.
Do I need a developer?
No. In Wameed it is a setting where you enter each platform’s credentials. A developer helps only for custom setups.
Will it double-count purchases?
It should not. The order number is used as the de-duplication ID. If you see doubles, check that the same event ID is used by both the browser and the server.
Is it the same as Google Tag Manager server-side?
No. Wameed sends events directly to each platform’s interface. Google Tag Manager on its own does not send a server feed.
- #أحداث التحويل
- #Conversions API
- #تتبع الإعلانات
- #قياس الإعلانات
- #server-side tracking
- #Meta Conversions API
- #TikTok Events API
Share this article
Ask about your own shop
Thirty minutes on your products, your tax setup and your hardware — not a slide deck.
Keep reading
4 min read
Selling from the shop and the store at once: the operating model that works
Two channels do not double your work if they share a catalogue, stock, customers and books. They do if they do not. Here is the model, role by role.
4 min read
Your online store in Ramadan and White Friday: prepare two weeks ahead
Peak days do not forgive improvisation. Stock, hours, delivery capacity, margins, messaging and speed all need a decision two weeks before — and a plan for what happens when volume doubles.
4 min read
Online store launch checklist: 25 things to tick before your first advert
Launching a store and then discovering the delivery fee is missing is an expensive way to test. Twenty-five checks, grouped by what they protect, take one afternoon and save weeks.

