Server-side tracking setup with server-side GTM for US businesses
I handle server-side tracking setup with server-side GTM for US businesses whose ad platforms keep reporting fewer conversions than actually happened. Your server container runs on your own subdomain, key tags move off the browser, and I check the numbers against your real orders and leads.
Typical turnaround: within a week
Sound familiar?
Your ad platform's conversion numbers are consistently lower than what you know actually happened
iOS and Safari users seem to disappear from your reporting entirely
Ad blockers are silently killing a chunk of your tracked conversions
Here's what changes
Conversion data that survives browser privacy features and ad blockers
More complete conversion data going back to Google and Meta for their bidding to work with
A clearer picture of what's actually working, not just what got through the browser
How it works
Set up the server container
Deploy a server-side GTM container on your own subdomain, separate from the client-side one.
Migrate tags server-side
Move key conversion tags to fire from the server instead of the browser, where browser blockers have less to block.
Validate the data match
Confirm server-side numbers reconcile with what you know actually happened before calling it live.
Hiring for server-side tracking setup? Here is what it should actually include
Server-side tracking with server-side GTM means your visitor's browser sends one stream of data to a tagging server that you control, and that server forwards what each platform needs, instead of every tag firing straight from the browser to Google, Meta and everyone else. Done well, you get more control over your data, sturdier first-party cookies, and fewer conversions lost to blocked scripts. Done badly, it reports the same numbers as before, or double counts them.
It is not magic, and anyone who promises a fixed percentage of recovered conversions is guessing. Ad blockers and browser privacy features do cut off some client-side tracking, but how much depends heavily on your audience, and published estimates vary widely. What server-side changes is where your tags run and who sets the cookies. What it does not change is consent: if a visitor declines tracking, a server does not make it acceptable to track them anyway. It also cannot recover a conversion that never reached your site or your server. Safari treats server-set cookies differently depending on how the server is hosted, so I test instead of assuming.
A proper setup has a few parts. I deploy a server-side GTM container in a Google Cloud project or another host you choose, point a subdomain of your own site at it, and connect your web container so it sends data to the server. Then I move the key conversion tags (Google Ads, GA4, and Meta's Conversions API where it applies) to fire from the server. The step most people skip is the last one: comparing what the server reports against your actual orders or leads, and fixing mismatches before calling it done.
Before you hire anyone for this, me included, ask whether they will tell you when server-side is not worth it for your volume, whether you get documentation of what moved and why, and who owns the hosting account afterward. Hosting is billed by the host you pick, separate from my work, and the account should be yours.
Who server-side tracking is for, and who should skip it
This fits ecommerce brands and lead-generation businesses that spend real money on Google Ads or Meta, already have working browser-side tracking, and still see their ad platforms reporting fewer purchases or leads than their own orders or CRM show. It also fits businesses that want to send cleaner conversion data back to ad platforms and keep more control over where customer data goes.
It is not the right first step if your basic tracking is broken. If tags double fire, triggers are wrong, or GA4 and Google Ads disagree for simple reasons, moving that mess to a server just moves the mess. Start with conversion tracking and come back. It is also probably not worth it for a small account with modest ad spend, where the added moving parts outweigh the data you would recover. And if your leads mostly arrive as phone calls, call tracking through CallRail will usually move the needle more.
You also need to be able to make a one-time DNS change for the subdomain, and some platforms need a developer for a small site change. If neither is possible, tell me upfront and I will say so honestly.
Real results, not theory
What You Get:
Server-side GTM container deployed on your own subdomain
Key conversion tags migrated server-side
Data validation against known real-world numbers
Documentation of what moved server-side and why
Checks for data discrepancies after launch
The Tracking Accuracy Guarantee
If the numbers this delivers don't match across your ad platform and GA4, I'll fix it for free until they do. No time limit, no extra charge.
Frequently asked questions
What is server-side tracking with server-side GTM?
It is a Google Tag Manager server container that receives data from your website and then sends it on to GA4, Google Ads, Meta and other platforms, instead of each tag firing from the visitor's browser. The server runs in your own Google Cloud project or another environment you choose, and ideally on a subdomain of your own site.
Does server-side tracking get around ad blockers and iOS privacy features?
Partly, and the amount depends on your audience. Moving tags to a server reduces exposure to blocked browser scripts, and a custom domain lets the server set first-party cookies. It does not override a visitor's consent choice, and Safari can still limit some cookies. I do not promise a recovery percentage, I measure it against your real orders.
What access do you need to set up server-side tracking?
Publish-level access to your Google Tag Manager container, edit access to GA4 and Google Ads, access to the Google Cloud project or hosting account for the server, and the ability to add a DNS record for your subdomain. Some ecommerce platforms also need a developer for one small change. I will list exactly what applies before I start.
How is server-side tracking different from your conversion tracking service?
Conversion tracking is about making sure the right actions are counted correctly in GTM, GA4 and Google Ads. Server-side tracking is an extra layer on top that changes where those tags run. If your basic tracking is wrong, fix that first, because a server only forwards what it receives.
How long does server-side tracking setup take?
Most setups are done within a week once I have access. The server container, subdomain and tag migration are quick. Anything that depends on DNS changes or a developer on your side can add time, and I validate the numbers against your real orders or leads before calling it live.
Do I actually need server-side tracking?
Not always. It tends to pay off for accounts with meaningful ad spend, a clear gap between platform conversions and real orders, and working browser-side tracking already. For a small account or one with broken basics, it usually adds cost and complexity without much return. I will tell you honestly which case you are in.
Guides on this topic
- How to Share Google Tag Manager AccessShare Google Tag Manager access in four steps, plus which of the five permission levels to actually give someone and why it matters.
- What Is a Google Ads Conversion?A conversion is a specific action you've told Google Ads to count as valuable, not a click or a visit. Here's what counts and how to set one up.
- Smart Bidding Learning Phase: 50 ConversionsGoogle's Smart Bidding guidance is shifting from weeks to a conversion count. Here's what that actually means for low-volume accounts.
- How to Share Google Analytics 4 (GA4) AccessShare GA4 access in four steps, what each of the five roles can do, and the difference between account and property level access.
Related services
I'm Filip Steiner - your Google Ads & Conversion Tracking Specialist
Over the past 5 years, I've managed 100+ ad accounts across the US, from local services to ecommerce.
My background in analytics and conversion tracking helps me turn ad chaos into profitable systems.
I don't just run ads. I build measurement systems that show you exactly where every dollar goes, and what it returns.