UK digital marketing · Google Ads from £150/month · you own the accounts01623 650333 · [email protected]
Free review

Server-Side Tracking with Google Tag Manager

dijitul marketing sets up server-side tracking for UK businesses, priced as a fixed quote after a short scoping call. We build a server-side Google Tag Manager container on your own first-party subdomain, route GA4, Google Ads and Meta events through it, and keep your consent banner in charge. The hosting account stays in your name.

Updated 2026-11-20 · by the dijitul marketing team · reviewed by , founder, building websites since 1996

Sound familiar?

  • GA4, Google Ads and Meta all report fewer conversions than your shop or CRM records.
  • Safari visitors look like new users every week, so returning-customer data is unreliable.
  • Your site loads a long list of vendor scripts in the browser and nobody knows what each one sends.
  • You have heard server-side tracking gets round cookie banners and want to know if that is true (it does not).
  • A previous set-up was left on a default run.app address and never moved to your own domain.
  • The Google Cloud bill for an old tagging server arrives on someone's personal card.

Key facts

  • Server-side tracking is priced as a fixed quote after scoping, because hosting, traffic and the number of platforms vary.
  • Google's Tag Manager documentation says a server container runs on a server you control, not in the visitor's browser.
  • Google's custom domain guide calls same-origin serving (for example www.example.com/metrics) best practice; a subdomain such as metrics.example.com also supports server-set cookies.
  • Google's custom domain guide says the default cloud provider domain does not support server-set cookies, only JavaScript cookies.
  • Apple's WebKit tracking prevention page says Safari deletes cookies created in JavaScript after 7 days, or caps them at 24 hours on a landing page reached through link decoration.
  • Server-side tagging does not remove the need for consent: the ICO says online advertising purposes are not exempt from PECR consent rules.
  • Hosting is a separate cost paid to the provider, such as Google Cloud or Stape, and varies with traffic.

What server-side tracking actually is

Normally every marketing tag runs in the visitor's browser. The browser sends data straight to Google, Meta and anyone else you have tagged. With server-side tagging, the browser sends one stream of events to a server you control, and that server decides what goes where.

Google's Tag Manager documentation describes server containers as using the same tags, triggers and variables as web containers. Incoming requests are turned into events by clients, and tags then forward those events to GA4, Google Ads, Meta or other platforms. Google's own wording is that only you have access to the data on the server until you choose to send it on. That is the real benefit: control over what each vendor receives.

dijitul marketing builds server-side set-ups for UK businesses as a fixed quote after scoping. Most clients start with a sound browser set-up first, so if yours is patchy we usually begin with conversion tracking and GA4 set-up.

Your own first-party domain

A tagging server is only worth having if it runs on your domain. Google's custom domain guide sets out three options:

  • Same origin, such as www.example.com/metrics. Google calls this best practice. It needs a CDN or load balancer to forward requests.
  • Subdomain, such as metrics.example.com. It also supports server-set cookies and only needs a DNS change.
  • Default domain, such as a run.app address. It is pre-configured but, per Google, does not support server-set cookies.

Google strongly recommends moving to your first-party domain before sending production traffic. We agree the option with whoever runs your DNS and hosting, and document every record we add.

What it helps with

Safari cookie limits. Apple's WebKit tracking prevention page says Safari's Intelligent Tracking Prevention deletes cookies created in JavaScript, and other script-writeable storage, after 7 days without interaction, and caps them at 24 hours on landing pages reached through link decoration (the tracking parameters added to ad clicks). Google's guide says server-set cookies are more durable than JavaScript cookies. One catch: WebKit also caps cookies set in HTTP responses to 7 days when it detects CNAME or third-party IP address cloaking, so how the subdomain is routed matters. We check this rather than assume it.

Ad blockers and browser losses. Requests to your own domain are less likely to be dropped than calls to well-known vendor domains. Some will still be blocked, and we do not promise a set uplift.

Data control. You can strip IP addresses, remove fields a vendor does not need, and send Meta its Conversions API events from the same stream.

What it does not fix: consent still applies

Server-side tracking is sometimes sold as a way round cookie banners. It is not. Under PECR, storing or reading information on a visitor's device needs consent unless an exception applies, and that includes cookies your tagging server sets. Any personal data you then forward is also covered by UK GDPR.

The ICO's guidance on storage and access technologies says online advertising purposes are not exempt from consent and never have been. The Data (Use and Access) Act 2025 added a statistical purposes exception, but the ICO says it applies only where the sole purpose is collecting statistics about use of your service, users must be given an easy way to object, and it does not cover advertising.

So we pass Consent Mode signals through to the server container and configure each tag to respect them. If a visitor declines advertising cookies, the server does not quietly send their data to Meta anyway.

Hosting options and costs

The tagging server has to run somewhere, and that cost is paid by you to the hosting provider, separate from our fee. The main options we use:

  • Google Cloud Run, in a Google Cloud project you own. Google's Cloud Run set-up guide estimates roughly $45 (US dollars) a month per server for 1 vCPU and 0.5GB memory, recommends at least two instances in production to reduce the risk of data loss, and says Cloud Run scales with load. A separate preview server is also needed for debugging. Google also warns that request logging can add significant charges above 1 million requests a month, so we review logging settings.
  • Stape, a managed hosting service for server-side Tag Manager. Its plans are priced by request volume on its own pricing page, and costs vary with your traffic.

We set up a billing alert so there are no surprises, and the account is always in your name, not ours. When we scope the job we estimate your request volume from GA4 so you can compare the providers' own pricing before committing.

What you get

  • A scoping note: which platforms, which events, expected traffic and hosting options with their pricing pages
  • A server-side Google Tag Manager container linked to your web container
  • Hosting on Google Cloud Run or Stape, set up in an account you own, with a billing alert
  • A first-party subdomain or same-origin path, with the DNS or CDN changes documented
  • GA4, Google Ads and Meta Conversions API tags in the server container
  • Consent Mode signals passed through so server tags follow each visitor's choice
  • Testing in server container preview mode and a written handover

How it works and what it costs

Google Ads management from £150 a month, social media management from £125 a month and email marketing from £95 a month, all + VAT. Ad spend is separate and paid to the platform. No long contracts.

  1. Free review

    We look at your current ads, social, email and analytics, or your plans if you are starting out, and tell you plainly what we would change.

  2. Plan and price

    You get a written plan with targets, budgets and a fixed monthly fee before anything starts.

  3. Set up properly

    Tracking and consent first, then campaigns, audiences, content calendars or email flows, all in accounts you own.

  4. Run and improve

    We manage it every week: search terms, bids, creative, posts and tests, cutting what does not pay and doing more of what does.

  5. Report in plain English

    A monthly report on leads, sales and cost per result, not vanity numbers, with what we will do next.

Frequently asked questions

How much does server-side tracking cost?

dijitul marketing prices server-side tracking as a fixed quote after scoping, because the number of platforms, events and domain set-up varies. Hosting is a separate monthly cost paid directly to Google Cloud or Stape, and depends on your traffic.

Does server-side tracking mean we no longer need a cookie banner?

No. PECR consent rules apply to cookies set by your tagging server too, and the ICO says advertising purposes are not exempt. Server-side tagging gives you control over data, not a way round consent.

Will server-side tracking recover all our lost conversions?

No set-up recovers everything. It can reduce losses from ad blockers and short cookie lifetimes, but visitors who decline consent should not be tracked for advertising. We measure before and after so you can see the real change.

What is the difference between a subdomain and same-origin set-up?

A subdomain such as metrics.example.com needs only a DNS change. Same origin, such as example.com/metrics, routes through your CDN or load balancer. Google calls same origin best practice; both support server-set cookies.

Do we need server-side tracking for Meta Conversions API?

Not always. Shopify and WooCommerce have their own Meta integrations, and Meta offers a Conversions API Gateway. Server-side Tag Manager makes most sense when you want one stream feeding several platforms.

Who owns the server and the data?

You do. The Google Cloud project or Stape account, the Tag Manager containers and the domain all sit in your name, with dijitul given user access. If you stop working with us, everything keeps running.

Related

Get a free marketing review

We'll look at your ads, social, email and tracking, and tell you plainly what we'd change. No obligation.

Call usFree review