Home / Server-side tracking
Server-side tracking · GA4 · Google Ads · Meta CAPI
Server-side tracking: which setup to choose without overpaying
GA4 shows fewer transactions than your store, and Meta is losing purchases? Server-side tracking usually fixes that. I compare three setups: Stape Gateway for Google tags, a full server-side GTM container and Meta Conversions API. I also tell you plainly when you need none of them.
- Stape hosting from $10* per month
- Stape partner discount when I set up the account
- The account and data stay with you
- 11+ years in analytics, 150+ companies
The short answer
This is how I choose for clients
- Simple business: Stape Gateway for Google tags plus Meta CAPI. Hosting from about $20* per month.
- Higher traffic and budget: a full server-side GTM container. Stape hosting from $20* per month.
- High cookie acceptance and little Safari traffic: you often do not need server-side at all.
9 questions, instant result, no email required
The problem
Why GA4, Google Ads and Meta see fewer conversions than your store
Browser tags send data straight to Google and Meta, and some of it gets lost on the way. Your campaigns then learn from incomplete data, so you pay more for every conversion.
Server-side tracking means sending data first to a server on your own subdomain (for example sst.yourdomain.com) and only then to GA4, Google Ads or Meta. To the browser, this is traffic within your own website.
Where data gets lost
- Ad blockers block Google and Meta scripts, especially among tech-savvy audiences.
- Safari and iOS limit cookies set by scripts to 7 days. A customer returning after two weeks counts as new.
- The browser Meta Pixel misses purchases, so Ads Manager shows fewer transactions than your store.
- Smart Bidding and Advantage+ optimise on what they see. Missing conversions mean worse algorithm decisions.
Comparison
Stape Gateway, server-side GTM or Meta CAPI? The differences in one table
All three setups move data sending to your subdomain. They differ in which platforms they support, whether they let you change data on the way and what they cost each month.
| Stape Gateway | Server-side GTM | Meta CAPI | |
|---|---|---|---|
| What it covers | Google tags only: GA4 and Google Ads | GA4, Google Ads plus Meta, TikTok, Microsoft Ads, BigQuery | Meta: Facebook and Instagram |
| What you need | Your existing web GTM container and a subdomain | A web GTM container, a server container and a subdomain | The Meta Pixel, a correct dataLayer and a subdomain |
| Changing data on the way | No, it forwards what the browser sends | Yes: removing personal data, server-side consent, margin, CRM data | Not with Meta CAPI Gateway, yes in an sGTM container |
| Complexity | Low | Medium to high | Medium |
| Stape hosting per month | $10* per domain (up to 2M requests) | from $20* (Pro plan, 500k requests) | $10* per pixel (Meta CAPI Gateway, 10M events) or included in the sGTM container |
| Implementation, my price excl. VAT | from €225 | from €375 | from €225 |
| Who it is for | Smaller companies advertising on Google | Higher traffic and budget, several platforms, CRM or store data | Anyone paying for Facebook and Instagram ads |
* Stape’s price as the hosting provider, not mine. As of October 2026, paid directly to Stape. I set up Stape accounts through the partner programme, which can get you a partner discount on hosting.
How I choose
Simple business: Gateway plus Meta CAPI. Larger business: full server-side GTM
The choice depends on your traffic and ad budget. For simple businesses, Gateway with Meta CAPI delivers the main gain at the lowest cost. For larger ones, control over the data matters, and only a server container gives you that.
Stape Gateway + Meta CAPI
- lower traffic and ad budget
- ads on Google Ads and Facebook
- no need to change data before sending
- nobody in the company will maintain a server
Stape Gateway or full sGTM for GA4 and Google Ads Meta CAPI (Conversions API) implementation
Full server-side GTM
- high traffic and a large ad budget
- several platforms: Google, Meta, TikTok, Microsoft Ads
- CRM or store data, for example margin instead of revenue
- consent handling and personal data removal on the server
Honestly
When you do not need server-side tracking
You often do not need a server-side setup if all three conditions below apply. Your browser data is then almost complete and the cost of a server will not pay off.
I check this for free in your GA4, Meta and consent banner data. If server-side does not make sense for you, I tell you so.
- 95% or more of visitors accept cookies in your consent banner (CMP).
- Your customers do not block ads on a large scale. Developers with an ad blocker on every site are a different story.
- You get almost no Safari and iOS traffic, meaning Apple devices that shorten cookie lifetimes.
Prerequisite
A server will not fix bad browser data
Server-side tracking forwards whatever it receives from the website. If your dataLayer sends the wrong order value or has no transaction ID, the server sends the same errors to Google and Meta.
None of the server-side setups include fixing the dataLayer. Your website must send correct data from the browser first. I check this at the start. dataLayer fixes are quoted separately, see GTM and dataLayer.
Before you decide
Three things the hosting vendor will not tell you
- Server-side costs money every month. Hosting is an ongoing expense, not a one-off purchase. That is why I pick the cheapest plan that covers your traffic.
- It does not bypass consent. Your cookie banner and Consent Mode v2 still apply. Server-side improves data quality from people who gave consent.
- When the server is down, there is no data. That is why I choose hosting with monitoring and test the setup before publishing.
How I work
From a free consultation to a before-and-after report
From you I mainly need access and one subdomain. You get the DNS record instructions by email.
Free consultation
I look at your GA4, Meta and consent banner data. I tell you whether server-side makes sense for you and which setup to choose.
dataLayer check and fixed price
I verify the data sent from the browser. Before we start you get a fixed price and scope.
Stape account and subdomain
I create the account through the partner programme. You add the DNS records following my instructions.
Implementation, testing and report
I compare data before and after the implementation with your store or CRM. The account and container stay with you.
Questions about server-side tracking
Is server-side tracking GDPR-compliant?
Yes, if it is configured correctly. The server respects consent from your banner and Consent Mode v2, and in a full server-side GTM setup you can also remove personal data before it reaches Google or Meta.
Do I still need cookie consent if data is sent from a server?
Yes. Server-side does not bypass consent. It changes the route data takes to the platforms, not the legal basis for collecting it.
How much does hosting cost and who pays for it?
Stape Gateway costs $10* per month per domain, Meta CAPI Gateway $10* per pixel, and full server-side GTM on Stape from $20* per month. You pay Stape directly. When I set up the account, you may get a partner discount.
Will my current GTM stop working?
No. Your web GTM container stays. I only change where the tags send data.
Can I start with Gateway and move to full server-side GTM later?
Yes. The subdomain and the corrected dataLayer carry over unchanged. When more platforms come in or you need to change data, we move to a server container.
Does the implementation include fixing the dataLayer?
No. That is a separate stage, quoted individually. Without correct browser data, the server cannot fix it.
How do I know whether I need server-side at all?
I check it for free in GA4, Meta and your consent banner data. With cookie acceptance above 95%, an audience without ad blockers and little Safari traffic, you often do not need it.
Not sure which setup to choose?
Answer 9 questions in the calculator or book a free consultation. I reply personally within 24 hours, with no obligation.