Server-side GTM container
We set up a server-side Google Tag Manager container on Google Cloud Run or a managed host such as Stape, on a first-party subdomain like data.yourdomain.com, sized for your traffic.
Server-Side Tracking That Recovers Lost Conversions
Our server-side tracking services move your tags from the browser to a server you control, so Google, Meta and GA4 receive conversions that pixels miss.
- Unicentro: GA4 purchase accuracy
- 80–95%GA4 purchase accuracyUnicentro
- Unicentro: Merchant Center listings
- 18,400+Merchant Center listingsUnicentro
- Carrum Health: data accuracy
- 95%data accuracyCarrum Health
Signs browser-only tracking is costing you conversions
Browser pixels lose data every time a visitor uses an ad blocker, Safari or a privacy setting. Server-side tracking helps when you see:
- Meta Events Manager shows a low Event Match Quality score or warns about missing events.
- Your backend or CRM records more orders or leads than Google Ads and Meta combined.
- Returning Safari and iPhone visitors look like new users because their cookies expire within days.
- Your site is slow because a dozen marketing pixels load on every page.
- Purchases are counted twice in Meta because the pixel and the API both send them without deduplication.
What's included in our server-side tracking services
Meta Conversions API
Purchases, leads and key funnel events go to Meta from the server, with hashed customer data and event IDs that deduplicate against the browser pixel, so nothing is counted twice.
Google enhanced conversions
We send hashed first-party data with Google Ads conversions, which improves match rates and gives Smart Bidding more of the conversions it would otherwise miss.
GA4 through the server
GA4 events route through your server container, which lets you set longer-lived first-party cookies, strip personal data before it leaves your systems and control what each vendor receives.
Other ad platforms
Where you advertise on them, we add the TikTok Events API, LinkedIn Conversions API, Snapchat and Pinterest server events from the same container.
Consent and data controls
Server-side tags follow the same consent signals as your browser tags through Consent Mode v2. We document what personal data is sent where, which your legal team will ask for.
QA, monitoring and handover
We compare server events against your backend orders, check deduplication in each platform and set up alerts for when event volume drops, then hand over documentation.
How server-side tracking setup works
- 1
Week 1
Tracking review
We audit your current pixels and conversions and agree which events move to the server.
- 2
Week 1–2
Infrastructure
We deploy the server container, set up the first-party subdomain and connect your web container.
- 3
Week 2–4
Platform connections
We build GA4, Meta CAPI, Google Ads and other platform tags with deduplication.
- 4
Week 4–5
QA and parallel run
Browser and server tracking run side by side while we compare counts against your backend.
- 5
Week 5–6
Launch and monitoring
We switch over, set up alerts and hand over documentation and hosting access.
Client result
Unicentro
Retail ecommerce · VTEX
- Challenge
- GA4 purchases were 40–50% off real orders, and Google Ads and Meta were optimizing on incomplete signals.
- What we did
- We rebuilt client-side and server-side GTM (hosted on Google Cloud Run), added Meta CAPI and Google Ads enhanced conversions, aligned VTEX purchase events with GA4, and fixed the Merchant Center feed.
- Result
- 80–95% GA4 purchase accuracy and 18,400+ products listed in Merchant Center.
Tools and platforms we connect
Server-side tracking sits between your site and your ad platforms. We connect:
- Server-side GTM
- Google Cloud Run
- Stape
- Google Analytics 4
- Meta Conversions API
- Google Ads enhanced conversions
- TikTok Events API
- LinkedIn Conversions API
- Consent Mode v2
- BigQuery
- Shopify
- VTEX
Who server-side tracking is for
- Brands spending $20,000+ a month on ads where a few percent of lost conversions changes how Smart Bidding and Meta's algorithm spend the budget.
- DTC and ecommerce stores with a large share of Safari and iPhone shoppers whose cookies expire quickly.
- Lead-gen and SaaS teams that want to send qualified leads and revenue from their CRM back to the ad platforms.
- Privacy-conscious businesses in healthcare, finance and other regulated industries that need control over what data leaves their systems.
Engagement and pricing
All prices are in USD and fixed before work starts. Server hosting is billed separately by Google Cloud or your host, and we estimate the monthly cost during scoping.
Server-side setup
4–6 weeks
Server container, first-party subdomain, GA4, Meta CAPI and Google enhanced conversions, QA and handover.
Setup plus monitoring
Monthly, cancel anytime
The full setup, then monthly checks, platform updates and new events as your campaigns change.
Frequently asked questions
What is server-side tracking?
Server-side tracking sends conversion and analytics data from a server you control instead of directly from the visitor's browser. Your site sends events to a server-side Google Tag Manager container on your own subdomain, and that server forwards them to GA4, Google Ads and Meta. It reduces data loss from ad blockers and cookie limits and gives you control over what each vendor receives.
Does server-side tracking get around cookie consent?
No, and it shouldn't. Server-side tracking still has to follow the visitor's consent choice. We pass consent signals to the server container through Consent Mode v2, so tags that need consent only fire when it's given. What changes is data quality and control, not your legal obligations.
How much does server-side GTM hosting cost?
Hosting is billed by traffic. Small sites can run on a managed host such as Stape for a modest monthly fee, while high-traffic sites on Google Cloud Run pay more for extra servers. We estimate your monthly cost during scoping from your traffic, so you know the number before we build anything.
Do we still need the Meta pixel if we use the Conversions API?
Yes, in most cases. Meta recommends running the pixel and the Conversions API together. The pixel captures browser signals, the API fills in what the browser misses, and a shared event ID lets Meta remove duplicates. Running both usually gives the best match quality and the most complete conversion data.
How many more conversions will server-side tracking recover?
It depends on your audience. Sites with many Safari, iPhone or ad-blocker users see the biggest gains, and sites that already have strong first-party data see less. We measure your current gap against backend orders or CRM leads during the review, so you get an estimate based on your own data rather than an industry average.
Does server-side tracking work with Shopify?
Yes. On Shopify we send events from Customer Events and order webhooks to the server container, then on to GA4, Google Ads and Meta. That covers purchases that browser pixels miss, including orders from shoppers with ad blockers. We set it up alongside Shopify's own channel apps so conversions aren't counted twice.
Related services
- GA4 & GTM Implementation servicesGA4 and Google Tag Manager set up from a written tracking plan, with a clean data layer, key events and QA, so every report starts from data your team can trust.
- Ecommerce Tracking & Analytics servicesEcommerce tracking for Shopify, WooCommerce, VTEX and headless stores: GA4 ecommerce events, purchases checked against real orders, accurate ad platform conversions and daily revenue dashboards.
- GA4 & GTM Audit servicesA full GA4 and Google Tag Manager audit that finds duplicate conversions, broken events and data leaks, then gives you a ranked fix list with the effort and impact of each item.
Not sure where your tracking stands?
In a free 30-minute review we look at your server-side tracking setup and tell you what to fix first.
Book a free tracking reviewLast updated