How much does server-side tracking cost?

Three paths. GTM Server-Side via Google Cloud Run runs $120 to $500 per month depending on traffic. Stape (managed) starts at $20 per month and scales to $300+ for high-traffic sites. Self-hosted costs zero in subscription but requires engineering time (20 to 40 hours setup, 5 hours per month maintenance).

GTM Server-Side vs Stape vs self-hosted: which is best?

Stape if you want the easiest setup and a managed solution. GTM Server-Side via Google Cloud if you have engineering capacity. Self-hosted only if you have strong DevOps capacity. For most B2B SaaS spending $5K to $50K per month on ads, Stape is the right pick.

Tool Comparison · 8 min read

Server-Side Tracking Guide for B2B SaaS (Recover 30-50% of Lost Conversions)

Q: What is server-side tracking?

Server-side tracking means your backend (not the user browser) sends conversion data directly to ad platforms via Conversions API. Unlike client-side pixels which can be blocked by iOS, Safari, or ad blockers, server-side events bypass those blocks. Recovers 30 to 50 percent of missed conversions.

Q: Do I need server-side tracking for B2B SaaS?

If you spend over $5K per month on paid ads, yes. Below that threshold, the data recovery is real but the implementation effort outweighs the benefit. Above $20K per month in ad spend, server-side is non-negotiable: you are losing $6K to $10K per month in attribution clarity without it.

iOS 14.5+, Safari, and ad blockers kill 30 to 50% of your client-side conversions. Server-side tracking recovers most of that data. Here is the full setup, including pricing for GTM Server-Side, Stape, and self-hosted options.

By Ayoub Kaddouri · Published 18 May 2026 · B2B SaaS attribution implemented across 12+ clients

The Short Answer

Client-side pixels lose 30 to 50% of conversions on iOS, Safari, and to ad blockers. That is data you pay for in ad spend but cannot measure.

Server-side tracking sends conversion events from your backend directly to ad platforms via Conversions API. Recovers 60 to 80% of the lost data.

Three paths: GTM Server-Side ($120-500/mo), Stape ($20-300/mo), or self-hosted (free + dev time). Pick by team capacity.

Why Client-Side Tracking Is Broken

Open your Meta Ads Manager. Compare the conversion count there to the conversion count in your CRM for the same time window. There is almost certainly a gap. For most B2B SaaS clients I audit, that gap is 30 to 50 percent.

The causes:

iOS 14.5+ (April 2021): App Tracking Transparency blocks cross-domain tracking unless the user opts in. They do not.
Safari Intelligent Tracking Prevention: Caps cookie lifespan at 7 days. Many B2B journeys are 30+ days.
Ad blockers: B2B audiences are technical and more likely to use blockers (15-25% of users).
Browser fingerprinting protections: Brave, Firefox Tracking Protection, newer Chrome versions.

Net result: your pixel reports 1,000 conversions. Your CRM has 1,500. The 500 missing conversions are real revenue you cannot attribute.

How Server-Side Tracking Fixes It

User converts on your site.
Your backend captures the event with the identifiers it has (email, phone, IP).
Your backend hashes those identifiers and sends them to Meta CAPI, Google CAPI, LinkedIn CAPI, TikTok CAPI directly.
Ad platforms match the hashed identifiers to ad-exposed users and credit the conversion.

Three Implementation Paths

1. Stape (managed, recommended for most)

Stape is hosted GTM Server-Side. Point your Google Tag Manager Server container at Stape, set up the connections to ad platforms, done.

Cost: $20 to $300 per month.

Setup time: 4 to 8 hours for a marketer who has used GTM.

Best for: 80% of B2B SaaS.

2. GTM Server-Side on Google Cloud Run

Same product but hosted on your own Google Cloud project. More control, potentially lower cost at very high traffic.

Cost: $120 to $500 per month.

Setup time: 8 to 20 hours including Cloud Run configuration.

Best for: Companies with strong DevOps and existing Google Cloud usage.

3. Self-hosted via RudderStack or Segment

Use an open-source CDP to handle the server-side event dispatch. RudderStack is open-source; Segment is paid SaaS.

Cost: Zero subscription for RudderStack self-hosted, $120+/month for Segment.

Setup time: 20 to 40 hours.

My pick for most B2B SaaS in 2026

Stape. Best balance of cost, setup time, and reliability for B2B SaaS spending $5K to $50K per month on ads.

The single biggest mistake I see: companies skipping server-side because they already have a pixel. The pixel is the problem, not the solution.

The Setup in 5 Steps

Audit your current event tracking. List every conversion event your client-side pixel currently fires.
Set up a GTM Server-Side container. Either on Stape or Google Cloud Run.
Configure Conversions API connections. For each ad platform, generate a CAPI access token and add it to GTM Server.
Wire your backend to send events. When a conversion happens, your backend posts the event to your GTM Server endpoint.
Validate parity. Run client-side and server-side in parallel for 30 days. Expect server-side to report 30 to 50% more.

Frequently Asked Questions

What is server-side tracking?

Server-side tracking means your backend sends conversion data directly to ad platforms via Conversions API. Bypasses iOS, Safari, and ad-blocker blocks. Recovers 30 to 50% of missed conversions.

Do I need server-side tracking for B2B SaaS?

If you spend over $5K per month on paid ads, yes. Above $20K per month in ad spend, non-negotiable.

How much does it cost?

GTM Server-Side: $120-500/mo. Stape: $20-300/mo. Self-hosted: free in subscription but 20-40 hours of engineering time.

Which is best?

Stape for most B2B SaaS spending $5K-$50K/month on ads. GTM Server-Side if you have engineering capacity. Self-hosted only with strong DevOps.

Want me to audit your attribution stack?

30 minutes. I look at your setup, where data is leaking, and what to change.

Book a Free Attribution Audit