Measurement
MER vs ROAS: which number to manage to
MER vs ROAS comes down to scope: MER judges all ad spend against all revenue, while ROAS judges one channel's spend against…
Tracking & analytics · Server-side
Server-side tracking that sends ad platforms the sales they’re missing.
Browsers block and cut short more tracking every year, and ad platforms optimize on what they receive. We set up server-side tracking for stores: Meta’s Conversions API, Google’s enhanced conversions, TikTok and Pinterest server events, and server-side Google Tag Manager where it’s worth the hosting cost. Everything is deduplicated, consent-aware and checked against real orders.
200+ clients served 500+ projects delivered
Free tracking review
Tell us your stack and we will map server-side tracking.
Three fields and you are done. We review your current tracking and send what server-side would fix.
- Current tracking reviewed
- Data gaps listed
- A fixed-scope setup plan
Chat on WhatsApp
Prefer to talk first? Send us your store URL on WhatsApp.
Your PDF report comes by email. If you want to discuss going ahead after reading it, we’ll set up a video meeting. We use your details only for this audit.
Fit
Who it’s for
- Stores where Meta, Google or TikTok report far fewer purchases than the store records
- Brands spending enough on ads that missing conversions affect bidding
- Stores with a Pixel and Conversions API both running but no deduplication
- Teams considering server-side Tag Manager and wanting the trade-offs explained first
If GA4 and basic tags aren’t working yet, start with our tracking and analytics setup; server-side work builds on it.
Problems we fix
Why server-side tracking goes wrong.
- 01
Double-counted purchases
The browser pixel and the server send the same purchase without a shared event ID, so the platform counts it twice and bidding learns from inflated numbers.
- 02
Low match quality
Server events without hashed email, phone or click IDs can’t be matched to people, so they add little.
- 03
Consent ignored
Server events sent for visitors who declined tracking create legal risk and break the trust the consent banner promised.
- 04
Hosting nobody budgeted
Server-side Tag Manager runs on a server you pay for. Set up without a plan, it costs money without adding much.
- 05
Apps fighting each other
A platform app, a tracking app and a custom script all send purchases, each slightly differently.
- 06
No check against orders
Nobody compares what each platform receives with what the store actually sold, so problems last for months.
In 1:10 · animated
Before we change anything, we check five things.
A short animated walk-through of the first checks in our audit. No sound needed: everything is on screen, and the transcript is below.
What we check first in server-side tracking, an animated explainer of 1:10 with on-screen captions and controls to pause.
Read the transcript
- What we check first in server-side tracking Five checks, starting with double-counted purchases.
- 1. Are purchases counted twice? Meta, TikTok and Pinterest deduplicate browser and server events by a shared event ID. Without it, one sale can count as two. (Example store: pixel and server sent the same purchase with different IDs.)
- 2. Can server events be matched? Server events without hashed email, phone or click IDs can’t be matched to people, so they add little. (Example purchase event.)
- 3. Is consent respected? Server events sent for visitors who declined tracking create legal risk and break the banner’s promise. (Example setup.)
- 4. Who is sending purchases? A platform app, a tracking app and a custom script can all send the same purchase, each slightly differently. (Example store; one per platform is the goal.)
- 5. Is anyone checking against orders? We compare what each platform receives with what the store sold, every week, so problems don’t last months.
- Then we fix them, in that order. Want this checked on your tracking? The free growth audit covers all five, in writing.
Our approach
Server-side tracking, platform by platform.
Server-side tracking means your store or a server you control sends conversion events directly to ad platforms, instead of relying only on code in the visitor’s browser. Each platform has its own route: Meta’s Conversions API, Google’s enhanced conversions, TikTok’s Events API and Pinterest’s Conversions API.
We start with what the platforms already offer. Store platforms and official apps often include a server-side connection, and for many stores that’s enough once it’s configured properly. We check it sends purchases with values, includes the customer details each platform accepts, hashed, and shares event IDs with the browser pixel so duplicates are removed.
Where more control is needed, we set up server-side tagging in Google Tag Manager: one stream of events from your site to your own tagging server, which then forwards them to each platform. It gives you control over what each platform receives, but it has hosting costs and needs maintenance, so we price it out with you before building it.
Consent is wired through the whole chain. We connect your consent banner to Google consent mode and make sure server events respect each visitor’s choice, so the server route doesn’t become a way around consent.
Then we check the result against orders. Purchases in each platform are compared with store orders by day, duplicates are hunted down and match quality is reviewed, so you know the platforms are learning from real sales. That’s the foundation our Meta Ads and Google Ads work relies on.
Customer data is handled with care. Platforms accept hashed email addresses and phone numbers to match events to people, and we send only what each platform documents and what your privacy policy and consent allow. Nothing is sent in plain text, and nothing beyond what the match needs.
Maintenance is planned in. Platforms change their APIs, apps update and themes get replaced, so we set up a simple check that compares platform purchases with orders each week and flags a drop before it costs a month of bidding.
Server-side tracking doesn’t replace the browser pixel. Both run together, and deduplication by event ID makes sure each sale is counted once while the server catches what the browser misses. Meta’s Conversions API accepts an event time up to 7 days before the event is sent, so a delayed order can still be matched. Speed is judged against Google’s Core Web Vitals thresholds: main content within 2.5 seconds, a response to input within 200 milliseconds and layout shift of 0.1 or less.
How we use AI here
How we use AI in server-side tracking.
Server-side tracking is code and configuration. AI-assisted development makes it faster to build and test.
AI-assisted build
Server container tags, Conversions API payloads and custom templates are written with AI coding tools and reviewed line by line.
Payload checks
Scripts compare what the browser and server send for the same order, so duplicates and missing fields are found before ad platforms learn from them.
Ongoing monitoring
Alerts on event volumes and match quality catch silent breaks after theme or app changes.
Where it doesn’t help: consent. What you may send, and when, is a legal and policy decision, and the setup follows it.
What’s included
Deliverables, not promises.
Tracking audit
What each platform receives today, compared with store orders, plus every app and script that sends events.
Meta Conversions API
Server events with event IDs for deduplication, hashed customer data and match quality checked.
Google enhanced conversions
Hashed customer data with purchase conversions, linked to GA4 and consent mode.
TikTok and Pinterest server events
Events API and Conversions API set up with deduplication where those channels are in use.
Server-side Tag Manager (optional)
Tagging server, hosting and forwarding, scoped and priced before we build.
Consent across the chain
Consent mode and banner choices respected by browser and server events alike.
Reconciliation report
Platform purchases compared with store orders, with the remaining gaps explained.
How we run it
Four steps, in this order.
Measure the gap, close it, then prove it closed. Typical timing: the audit within 2 workdays, the build in about a week, and testing and handover within 2 weeks.
Step 1
Audit the gap
Purchases per platform compared with store orders, and every event source listed.
Step 2
Plan
Native integrations or server-side Tag Manager, consent handling and costs agreed.
Step 3
Implement
Server events, deduplication and hashed customer data set up, tested with real test orders.
Step 4
Reconcile
Platform numbers checked against orders after launch, and drift fixed.
Pricing
Starting prices, in US dollars.
The audit is free. Paid work starts at these prices, and your exact cost is fixed in writing before any work begins.
-
Free audit
Free no obligation
Tell us your stack and we will map server-side tracking.
Get my free audit -
Fixed scope
Server-side setup
From $600 one-off
Server container, events and destinations configured.
- Server container setup
- Key events mirrored server-side
- GA4, Meta CAPI, Google Ads connected
- Tested end to end
-
Tracking care
From $200 monthly
Monitoring and fixes as platforms change.
- Event health monitored
- Fixes after platform changes
- A short report
All prices are starting prices in US dollars. Custom work beyond these options is quoted after the audit.
By industry
What changes for your category.
Jewelry
High order values make every missing purchase expensive for bidding. We prioritize purchase events with accurate values and customer data for match quality.
Fashion & apparel
Returns are common in fashion. We send purchases with values and keep refund data in your reports, so bidding isn’t judged on revenue that comes back.
Luxury & high-ticket
Long consideration means buyers return on different devices. Customer data in server events helps platforms connect those visits to the purchase.
Sources
The documentation we work from.
Platform rules change. These are the official pages we check the work against, so you can check it too.
- Introduction to server-side tagging: Google Tag Manager’s server container
- Conversions API: Meta’s server events documentation
- About enhanced conversions: Google Ads’ hashed first-party data
- Get started with Events API: TikTok’s server events
- Set up consent mode: Google’s consent mode guide
- Event Quality Score: how Pinterest grades tag and Conversions API data
FAQ
Straight answers.
Can’t find yours? Ask on WhatsApp or by email and we’ll answer it.
Do we need server-side tracking?
If ad platforms report far fewer purchases than your store records, or you spend enough that missing conversions affect bidding, usually yes. A platform’s native server-side integration is often enough to start.
What is the difference between the Conversions API and server-side GTM?
The Conversions API is Meta’s way of receiving server events. Server-side Tag Manager is a server you run that can send events to Meta, Google, TikTok and others from one stream. One is a destination, the other is a route.
Will we get double counting?
Not if it’s set up properly. The browser pixel and the server send the same event ID, and the platform keeps one. We test that with real test orders.
Does server-side tracking get around consent?
It shouldn’t, and in our setups it doesn’t. Server events follow the same consent choices as browser tags.
How much does server-side Tag Manager cost to run?
It depends on traffic and the hosting provider. We estimate it from your traffic before building, so you can decide whether the extra control is worth it.
What is event match quality?
A score in Meta’s Events Manager showing how well your server events can be matched to Meta accounts. Better customer data, sent hashed, usually raises it. Pinterest has a similar Event Quality Score.
Can server-side tracking fix our attribution?
It fixes missing data, which is the first step. Attribution still depends on each platform’s model, so we judge channels on store orders and MER as well as on what the platforms report.
Do we still need the browser pixel?
Yes. Platforms recommend running browser and server events together. The pixel captures on-site behavior; the server fills the gaps. Deduplication keeps each sale counted once.
Which platforms do you support?
Meta, Google Ads and GA4, TikTok and Pinterest, on Shopify, WooCommerce and BigCommerce stores.
Related guides
Read before you decide.
E-commerce SEO
Affordable SEO services for small business: 5 best proven
Affordable SEO is a scoping decision, not a shopping decision. This guide shows what a small budget actually buys, what to buy…
E-commerce SEO
Email marketing cost: 5 best proven price drivers
Email marketing cost is five bills in one: the tool, the list, the sends, the flows and the people. This guide prices…
Free growth audit
Find out what’s holding your store back.
Tell us about your store. We’ll review your tracking, campaigns and SEO and send you a written audit with the top fixes, ranked by impact.
- Written audit as a PDF, delivered within 2 workdays (see a sample)
- A video meeting to go through it, if you want to discuss next steps
- Free and no obligation
- Read-only access or screenshots are enough