Server-side tracking
- Price
- from $2,000
- Timeline
- 1–3 weeks
- Experience
- 100+ projects · 10+ years · 9+ countries
We send conversions from the server: more accurate data, better ad optimization, fewer losses to ad blockers
- Google Tag Manager
- Google Analytics
Our usual stack. We bring in other tools when the task or the project calls for it.
Ad blockers and browser restrictions eat a noticeable share of conversion data, and ad algorithms learn from an incomplete picture. Server-side tracking sends events from your server instead of the visitor’s browser.
We set up a server-side Google Tag Manager container and the ad platforms’ server APIs, so lead and sales data arrives in full and respects cookie consent.
What we do
- A server-side Google Tag Manager container
- Google enhanced conversions
- CRM sales passed to the ad platforms
- Visitor consent respected in data processing
- Data reconciliation before and after
What you lose without server-side tracking
Ad algorithms learn from partial conversions and costs creep up
We send leads and sales to ad platforms from the server, where blockers and browser limits don't cut them. Algorithms get more signals to learn from.
Visitor data flows to third parties with no control
Events pass through your own server, and you decide which fields go further: strip IPs, hash phone and email, drop extra parameters before sending.
Payment happens on the bank's page and the purchase isn't recorded
We fire the purchase event from the payment provider's webhook, not the thank-you page. It's recorded even if the customer closes the tab after paying.
A return visit a week later counts as a new visitor
We set the visitor ID as a server-side cookie on your own domain. Browsers don't cut its lifetime the way they cap script cookies, so the journey doesn't break.
Deals close in the CRM and ad platforms never hear about it
We pass payments from the CRM to the server container and on to Google Ads and other platforms. Bidding adjusts to revenue, not just leads.
Who should move tracking server-side
A good fit if
- Ad spend is significant and every lost conversion hurts bidding
- A large share of your audience uses iPhones or ad blockers
- Payment happens on an external bank page or by invoice
- You have rules on which personal data may leave your systems
Not a fit if
- Basic goals aren't set up yet — start with standard web analytics
- A couple dozen leads a month — a quick check of your browser tracking is enough
Accurate data, no extra risk
No duplicates
We set up deduplication of browser and server events, so ad platforms never count the same lead twice.A server you control
The container runs on your domain and in your cloud: data doesn’t pass through middlemen and hosting costs stay transparent.Code changes included
Server-side events often need changes to the website and CRM. We make them ourselves, no extra vendor needed.
Express website audit
We review your site and within 3 business days send a PDF with up to 10 specific growth points, sorted by priority.
- Load speed and the mobile experience
- Structure, copy and the path to a lead
- Technical SEO and search visibility
- Forms, analytics and conversion tracking
For live websites only. No strings attached: you can make the fixes in-house.
How we work
- 01
Loss audit
1–2 daysWe compare leads and sales in your CRM with what analytics and ad platforms see and measure how many conversions go missing.
You get A gap report between your CRM, analytics and ad accounts - 02
Server infrastructure
1–3 daysWe deploy a server-side container on your domain and set it up to receive events from the site and the CRM.
You get A working server-side container on your subdomain - 03
Sending conversions
2–5 daysWe send leads and sales from the server to GA4, Google Ads, Meta Conversions API and other platforms, including offline CRM conversions.
You get Conversions reaching the ad platforms from the server - 04
Deduplication and checks
1–3 daysWe remove double counting between browser and server events and reconcile platform numbers with the CRM.
You get A reconciliation report showing how many conversions now get through - 05
Monitoring and handover
1–2 daysWe set up alerts for when events stop arriving and document the setup for your team.
You get Failure alerts and server-side tracking documentation
What server-side tracking needs
- Domain and DNS access for a tracking subdomain
- A cloud hosting account, or a decision on where the server lives
- Access to Google Tag Manager, analytics and ad accounts
- A backend developer contact or access to the site code
- Your cookie consent text and data processing policy
An express data-loss audit
We compare orders and leads in the CRM with what analytics and ad platforms see. In 3 working days we send 10 concrete growth points, free of charge.
Related articles
All news
Losing conversions
to ad blockers?
We’ll set up a server-side Tag Manager container on your domain and pass leads and sales to ad platforms with consent respected.
It depends on your audience: the more ad blockers and restrictive browsers, the bigger the difference. We compare before and after.
From $2,000. The total depends on how many ad and analytics platforms receive conversions, the website and CRM changes needed to send events from the server and the consent setup. The cloud server for the container is billed separately. We send an estimate after a call.
Yes, when consent is respected: server-side tracking only sends data for visitors who allowed processing.
You need a cloud server for the container, usually inexpensive. We’ll help choose an option.
If anything, positively: some scripts move from the browser to the server.