Server-side tracking and CAPI
so ad platforms see the conversions that are real
A browser pixel alone misses a growing share of conversions to ad blockers, iOS tracking limits and cookie consent. We set up server-side tracking and a Conversions API feed that catches what the pixel misses, deduplicated correctly so a sale is not counted twice.
Why the pixel alone undercounts
Server-side tracking sends conversion events, a purchase, a lead, a signup, to an ad platform directly from your server. That is instead of relying only on a browser pixel firing on the user’s device.
The point is coverage. A growing share of browsers block third-party pixels by default. iOS limits what Safari reports. Cookie consent choices reduce what a pixel is allowed to send. A server-side event, sent from your backend when the actual conversion happens, is not subject to any of that.
When the gap between platforms and reality matters
You need this once ad spend is meaningful, and the platform’s reported conversions clearly undercount what your own order or CRM data shows. A gap of 10 to 30% between ad platform numbers and actual sales is common, and usually traceable to exactly this.
It is also worth doing before scaling spend on Meta or Google. Both platforms reward advertisers whose conversion signal is more complete, often with better campaign optimization, not just more accurate reporting.
You do not need this if ad spend is minimal, or a campaign is still in early testing. The pixel’s directional signal is enough on its own at that stage. The investment pays off once you optimize spend on conversion data that needs to be trustworthy.
How dedup actually gets done right
We audit the existing pixel setup first: what events fire, what data they carry, and where the obvious gaps are. Only then do we add a server-side layer on top.
Server events get sent with the same event ID as the corresponding browser pixel event. That is what lets the platform deduplicate the two into one conversion, instead of counting it twice, a mistake we catch often in audits of other agencies’ work.
Customer data sent for matching, email, phone, gets hashed before it leaves our systems, per each platform’s own requirements. Nothing goes over in plain text.
Consent gating happens before any send. Server-side events respect the same consent choice a user made on the browser. We verify everything against the platform’s test event tool before calling a setup live, not after spend starts flowing through it.
This is the layer we get wrong least often, and right most often, across our own media buying work.
Where server-side tracking goes wrong
The single most common mistake in server-side tracking is sending events without deduplication against the browser pixel. That inflates conversion counts, and actively misleads optimization rather than improving it. We treat deduplication as a required step, not optional.
The other thing to watch is data minimization. Sending more customer data than a platform’s matching actually needs increases privacy exposure for no real benefit. We send what each platform’s documentation specifies, and nothing extra.
Ownership and lock-in are not meaningful concerns here. The implementation lives in your own backend code, and sends to the ad platform’s public API. There is nothing proprietary to get locked into.
Attribution windows are another detail worth getting right early. A server event sent with the wrong attribution window can tell the ad platform a conversion happened further from the ad click than it did. That skews optimization in the opposite direction from the problem server-side tracking is meant to fix.
We configure windows to match your actual sales cycle, not a platform default built for a generic e-commerce checkout that may not resemble your business at all.
Price and timeline
| Scope | Price | Timeline |
|---|---|---|
| One platform, key events | from $800 | 3 to 7 days |
| Meta + Google, full deduplication | from $1,800 | 1 to 2 weeks |
Related
Built as part of setup and integrations and analytics. Pairs with product analytics setup for the product side of the picture. See the media buying results this kind of tracking supports in AI-assisted Meta ads media buying. Tell us which platform’s numbers you do not trust yet: get in touch.
FAQ
How much does server-side tracking cost?
A setup covering Meta Conversions API for one or two key events, purchase and lead, starts at $800. A fuller setup across Meta and Google with full deduplication and a server-side tag manager runs $1,500 to $3,000.
How long does it take?
3 days to 2 weeks. The technical setup itself is usually quick. Most of the time goes to verifying events actually match what the browser pixel reports, and that nothing double-counts.
Do we still need the browser pixel?
Yes. Server-side tracking supplements the pixel, it does not replace it. Running both with correct deduplication gives the ad platform the fullest, most accurate picture, which is the whole point.
Does this work with cookie consent requirements?
Yes, events are gated on the user's actual consent choice. We do not send tracking data before consent is given, and we configure what gets sent based on which categories a user accepted.
Which platforms do you support?
Meta Conversions API most often, plus Google's Enhanced Conversions and server-side Google Tag Manager, and TikTok's Events API where relevant. We set up what matches where you actually spend ad budget.