Server side tracking

incentX ezcards Variabl Orbx LCN

Trusted by B2B brands like yours

Conversions counted on your server, even when browsers block the pixel.

Server side tracking moves your tags from the visitor's browser to a server container on your own domain. Google Ads, Google Analytics and Meta then keep getting accurate conversion data when browsers block cookies and scripts.

We do it for B2B SaaS companies, consultancies and professional services firms as part of our Marketing analytics services. The Meta Conversions API and the other platform APIs are set up alongside consent mode. Here GTM means Google Tag Manager.

The ad platforms bid on the conversions they can see. A browser-only setup hides a growing share of them.

Book a free strategy call

20 minutes. No pitch deck. Leave with your top 3 growth priorities.

Man in glasses and a green shirt working on a laptop at a desk in a bright office
Deals by source: paid search, 3 deals.
Report card: leads by channel. Paid search 42%, organic search 22%, LinkedIn 26%, referral 10%
Pipeline by source: $412K open pipeline. Organic search $148K, LinkedIn $112K, email $86K, paid search $66K. Open deals in your CRM, by first-touch source.

Monthly report: leads by source, what worked, what we'd do next

The CRM has 30 leads from Google Ads. Google Ads can see 18 of them.

Safari caps cookies at seven days, ad blockers strip the pixel on a growing share of B2B visitors and consent banners switch tags off before they fire. Every one of those is a conversion the ad platform never learns about.

The campaigns look worse than they are, the bidding learns from a partial picture and the budget moves to whatever the browser happens to let through.

Sound familiar?

"Isn't this just a way around consent?"

No. A server container obeys the same consent signals as a browser tag, and consent mode still decides what gets sent. What changes is where the tags run and how much the browser can interfere once a visitor has agreed.

Our Consent mode page covers that side, and we set both up together.

"We don't have the infrastructure or the people to run a server."

You do not need to. The server container runs on Google Cloud or on a managed tagging host for a modest monthly fee, and we set it up, monitor it and keep it patched.

Your team keeps working in the web container they already know.

What's included

Server side tracking services: what's included

Every deliverable exists to give the ad platforms the full count of conversions and to show you, in your own accounts, which campaigns produced them.

Server side tagging container on your own domain

A server container in your Google Tag Manager account, hosted on Google Cloud or a managed provider and served from a subdomain you own, such as data.yourcompany.com.

Events arrive there as first-party requests and the server decides what each platform receives.

GTM server side tracking for Google Ads and GA4

The web container sends one stream of events to the server.

The server container, which ships with Google Analytics 4 clients built in, passes them to GA4 and fires the Google Ads conversion tags with enhanced conversions where the platform supports them.

Fewer scripts load in the browser and every request to Google comes from your server.

Meta Conversions API and other platform APIs

Lead and purchase events sent to Meta through the Conversions API, deduplicated against the browser pixel so each conversion counts once.

The same pattern covers the LinkedIn Conversions API and others as you need them.

Match quality depends on the customer data you send, so we hash and send what consent allows.

Data filtering before anything leaves

The server container validates each event, strips personally identifiable information the platforms should not receive and adds the variables they need.

You decide what each vendor gets. That is a privacy control a browser tag cannot offer.

Consent mode and documentation

Consent mode connected across the web and server containers, so a declined visitor is modeled and an accepted one is measured.

A written setup document covers every client, tag and transformation, so your team or a future developer can maintain it.

Monthly reporting

A one-page report every month: leads by source, what changed and what's next.

Results

The growth B2B teams get when one team runs the whole funnel

Server side tracking runs on the same system: one web container, one server container on your domain and conversion events that match the CRM.

"They have a brilliant workflow and we always know exactly where things are with them."

Simon McSorley

CEO, Crew Talent Advisory

Want numbers like these in your own report?

Book a free 20-minute strategy call. We compare the conversions your ad platforms can see with the leads in your CRM first, so the call is about your growth.

Book a free strategy call

20 minutes. No pitch deck. Leave with your top 3 growth priorities.

icon calendar glass

Our process

Our 3-step server side tracking process

The Momentum Framework applied to server side tagging: map what the browser is losing, build the server container, improve on the data each month.

momentum step map

Map

Weeks 1 to 3

Measure the gap. We compare conversions in Google Ads, Meta and GA4 to leads in the CRM for the last 90 days.

You see how many conversions the browser is losing and whether a server container is worth the hosting cost.

Container and consent plan. One page that lists every event, which platform receives it, what data it carries and how consent mode applies. Your team approves it before anything is provisioned.

momentum step build

Build

Weeks 4 to 12

Provisioning. A server container created in your Tag Manager account and deployed on Google Cloud or a managed host, served from a subdomain on your domain with its own SSL certificate.

Event routing. The web container is pointed at the server URL.

GA4, Google Ads and the Meta Conversions API are configured in the server container with deduplication against the browser pixel.

Everything is tested in preview mode on every page type.

Verification. For the first month we compare server-side conversions to CRM leads every week. Gaps get traced to their cause and fixed, and the setup document gets updated.

momentum step improve

Improve

Week 13 on

Report and maintain. Each month brings one page of conversions by platform and the browser-to-server gap. The server stays patched and monitored, and new platforms get added through the same container.

Why us

Work with the person who does the server side tracking work

why growth chart

1-to-1 with a marketing expert

No middleman, on every plan

A marketing expert leads your server side tracking program, working with professionals and experts in their fields.

Our team sent a counseling practice's booking confirmations through Tag Manager and a server container into Google Analytics and Google Ads, so that every booking counted as a conversion.

The account booked four new clients from Google Ads in the first week.

We rebuilt the purchase tracking for a software publisher through Tag Manager, part of the work behind a Google Ads return that more than doubled.

We hold Google Ads Search certification, which matters because the conversions the server sends are what the bidding learns from.

You work 1-to-1 with a marketing expert, with no middleman. They measure your gap, plan the containers and provision the server. Developers join when the work calls for them.

Google Partner Cloudways Agency Partner Silver G2 Users Love Us

Built on repeat business.

Leaders who changed jobs or brought marketing in-house have hired us again, one of them after three years away.

New tools, minus the hype.

New AI tools launch every week. We test them across client accounts and bring you the few that pay off.

See which spend brings in leads.

Each vendor reports on its own channel, so nobody ties spend to revenue. You get one monthly page of leads by source.

Pricing

Server side tracking pricing

A server side tracking setup is quoted as a fixed price before we start.

What moves the price is the number of domains, the number of platforms receiving events and whether the Meta Conversions API or other APIs need deduplication against existing pixels.

Ongoing work sits in the Growth plan, from $2,000 a month in USD, which covers the containers alongside the campaigns they measure and the monthly report.

Teams with their own developer who want a plan, a review and help when stuck use Advisory, from $200 a month.

Hosting for the server container is paid by you to Google Cloud or the managed provider, in an account you own, and the ad platforms' conversion APIs are free to use. Ad spend is paid by you to the platforms, and we never take a percentage.

Advisory

From

$200

/mo

You do the work. We guide it.

Includes

One 60-minute strategy session a month

A monthly written review of your campaigns

Month to month from day one

Hands-on help when you need it, priced by the job

Growth

From

$2,000

/mo

We do the work.

Includes

Everything in Advisory

Ads, website and CRM work

Graphic design, video editing and content creation

A one-page report every month

Scale

Custom quote

Our most complete plan.

Includes

Everything in Growth

A dedicated copywriter, graphic designer and video editor

More channels and more output

A fixed price, agreed before we start

You own every account and login from day one. We never bill by the hour or take a percentage of ad spend. Flexible terms. We agree the term with you before we start, based on the work you need. One-off projects, like a new website or audit, get a fixed quote up front.

Book your server side tracking call in two steps

Choose any open time on the calendar. You talk 1-to-1 with a marketing expert, with no middleman.

20 minutes. No pitch deck. Leave with your top 3 growth priorities.

Step 1 of 2: Pick a time

  1. Pick a time
  2. Your details
This field is for validation purposes and should be left unchanged.

Free 20-minute strategy call

Zoom

Next: your name, email and what we should look at first

Get your invite

We email a calendar invite with the Zoom link, then remind you a day and an hour before.

We review before we meet

We compare the conversions your ad platforms can see with the leads in your CRM, starting where you want us to focus.

We share what we found

Your priorities are yours to use, whether or not you work with us.

What is server side tracking?

Server side tracking is a way of collecting website data on a server you control, rather than in the visitor's browser, and sending it from there to Google Analytics, Google Ads, Meta and your other platforms.

A server side tracking consultant sets up that server, routes the events through it and keeps it running.

Server side tagging uses two containers. The web container still sits on your site, and it sends one stream of events to a URL on your own domain. The server container lives on a cloud server at that URL, usually Google Cloud or a managed tagging host.

It receives each event, validates it, removes anything the platforms should not see and sends it on.

Because the request to your domain is first-party, the browser treats it like any other call to your site. Cookies set by the server last longer than cookies set by a script. Ad blockers have less to block, and the page loads faster because fewer scripts and HTTP requests run in the user's browser.

For B2B, the stakes sit in the conversion data. Consumer sites lose a share of purchase events to browser restrictions and can live with it, because the volume is high. A B2B site might get thirty leads a month.

Losing a third of them from the ad platform's view changes how the bidding behaves and which campaigns look worth funding.

Our parent Marketing analytics page covers the full program. This page is the server side tracking part. The web container that feeds it is covered on our Google Tag Manager page, and the ad accounts that depend on it under Google Ads, Meta Ads and Retargeting.

Chart: browser tags versus server-side tags. In the browser the Meta tag is blocked; through a server container GA4, Google Ads and Meta all receive the conversion. Chart: browser tags versus server-side tags. In the browser the Meta tag is blocked; through a server container GA4, Google Ads and Meta all receive the conversion.

Client-side versus server side tagging

Client-side tagging runs every vendor's script in the browser and sends data straight from the user's browser to each vendor. It is simple to set up and free to run, and it gives each vendor whatever its script collects.

Server side tagging runs the scripts on your server, sends one request from the browser and lets you decide what each vendor receives. It costs a little to host and requires technical knowledge to set up.

For a B2B company running paid campaigns, the control and the recovered conversions usually pay for the hosting many times over.

What GTM server side tracking looks like in practice

A visitor fills in a demo form. The web container fires one GA4 event to data.yourcompany.com. The server container receives it, confirms consent was granted and hashes the email address.

It then sends a lead event to GA4, a conversion to Google Ads with enhanced conversions and a lead event to Meta through the Conversions API with an event ID that matches the pixel. Each platform counts one lead.

The CRM records the same lead with its source, and the monthly report matches across all four.

The Meta Conversions API

The Meta Conversions API sends events from your server to Meta rather than from the pixel in the browser. It is free to use. You need a Meta pixel or dataset ID and an access token, and each event should carry the same event ID as the browser pixel so Meta can deduplicate.

Match quality depends on the customer information you send, such as a hashed email. A server container that captures the form data properly makes retargeting and conversion campaigns more accurate.

Privacy, consent and what the law requires

Server side tracking does not remove the need for consent. Under GDPR and similar laws a visitor who declines still has to be respected, and consent mode is how the containers know.

What server side tracking adds is control. You can strip IP addresses and personal data before anything reaches a vendor, keep data on infrastructure you own and manage consent consistently across domains. Done properly, it improves compliance rather than working around it.

What the best server side tracking setups have in common

They run on a subdomain the business owns, under a Google Cloud or hosting account in the business's name. They send one event stream from the web container and let the server fan it out. They deduplicate every platform against its browser pixel.

They document every client and tag, so the setup survives a change of agency. And they get checked against the CRM every month, because a server that quietly stops sending is worse than a pixel that was never installed.

How to get started with server side tagging

Measure the gap first. Compare the conversions each ad platform reports with the leads in your CRM for the last quarter. If the platforms see most of them, a clean web container and consent mode may be enough.

If they are missing a meaningful share, provision the server container, route the events and test every page type in preview mode before you publish. Then keep comparing against the CRM, because the first month shows where the remaining gaps are.

Is server side tracking right for your business?

It fits when you spend on Google Ads, Meta or LinkedIn and the platforms report noticeably fewer conversions than your CRM records, or when privacy requirements mean you need control over what each vendor receives.

It's a good fit if:

Your ad platforms report fewer conversions than your CRM has leads from the same campaigns

A large share of your visitors use Safari, Firefox or ad blockers

You run Meta or LinkedIn campaigns and the pixel match rates are poor

Your legal or security team wants control over what data leaves the site

It's not the right fit if:

Your web container is a mess and the events do not fire properly yet. Start with Google Tag Manager.

The data reaches the platforms but the Google Analytics property counts it wrong. Start with Google Analytics consulting.

You do not know where the conversions are going missing. Start with a Tracking audit.

Your main concern is the consent banner and what it switches off. Start with Consent mode.

You run one channel with a handful of leads a month. The hosting cost is hard to justify, and we will say so on the call.

FAQs

Server side tracking questions, answered in plain English

What is GTM server side tracking?

GTM server side tracking is Google Tag Manager running in a server container on your own domain, which receives events from your website and forwards them to your platforms. The web container you already have sends one stream of events to the server.

The server container handles GA4, Google Ads, Meta and the rest. Google documents the setup and provides the server container; you provide the hosting.

What is the difference between client-side and server-side tracking?

Client-side tracking runs vendor scripts in the visitor's browser and sends data straight to each vendor. Server-side tracking sends one request to your server, which processes the data and sends it on.

The server version is more resilient to browser restrictions and ad blockers, loads fewer scripts on the page and lets you filter what each vendor receives. It costs a little to host and takes more to set up.

Is server side tracking legal?

Yes, when it respects consent and the privacy laws that apply to your visitors. Moving tags to a server does not change what consent you need.

It gives you more control over what data is collected and shared, which makes compliance with GDPR and CCPA easier to prove. We set it up with consent mode so declined visitors are modeled and never tracked.

Can you give me an example of server side tracking?

A booking confirmation sent through a server container so Google Ads counts the booking as a conversion. A counseling practice's booking tool fired a confirmation event into the web container, and the server container passed it to Google Analytics and Google Ads as a conversion.

Four new clients booked from Google Ads in the first week after it went live, and every one of them showed up in the ad account.

How do I set up server-side tagging in Google Tag Manager?

Create a server container in your Tag Manager account, deploy it to Google Cloud or a managed host, point it at a subdomain on your domain and route your web container's events to that URL. Then configure clients and tags in the server container for GA4, Google Ads and any conversion APIs, test in preview mode and publish.

The steps are documented by Google. The judgment is in what to send, what to strip and how to deduplicate, which is where most do-it-yourself setups go wrong.

What is the Meta Conversions API, and is it free?

The Meta Conversions API sends conversion events to Meta from your server rather than from the browser pixel, and it is free to use.

You need a dataset ID and an access token from your Meta business account, and each event should share an event ID with the pixel so Meta deduplicates. A server container can send those events without custom code.

Which server side tracking tool is best?

For most B2B companies, a Google Tag Manager server container on Google Cloud or a managed tagging host is the right choice, because it works with the tools you already run. Managed hosts simplify the deployment for a monthly fee.

Dedicated customer data platforms do more and cost far more, and few B2B teams need them. Pick the setup your team can maintain.

How much does server side tracking cost?

Our server side tracking setup is quoted as a fixed price, and ongoing work sits in the Growth plan from $2,000 a month in USD. Hosting runs from a few tens of dollars a month on a managed provider to more on Google Cloud at high traffic.

Across the market, agency setups range from a couple of thousand dollars to tens of thousands for enterprise programs. Advisory starts from $200 a month for teams with their own developer.

Who will I work with day to day?

You choose, depending on your goals and budget. You work 1-to-1 with a marketing expert who leads your account and your strategy on every plan, with no middleman. On Advisory, they guide your own team. On Growth, we do the work, with professionals and experts in ads, web, CRM, design and video joining as it needs them.

On Scale, you get a dedicated copywriter, graphic designer and video editor. We'll help you pick the plan that fits.

Find out where your server side tracking budget should go first

Tell us where to focus. We compare the conversions your ad platforms can see with the leads in your CRM before we meet. What we find is yours to use, whether or not you work with us.

Book a free strategy call

20 minutes. No pitch deck. Leave with your top 3 growth priorities.

Server side tracking is part of our Marketing analytics services.

icon calendar glass