Back to all comparisons

Signal vs GTM Server-Side

Still loading gtag.js? There’s a better way.

GTM Server-Side was a step forward from client-side tagging, but it still requires 80 KB+ of gtag.js in the browser, still depends on vendor JavaScript for identity, and runs on shared Google Cloud infrastructure. Signal replaces all of that — with a single 5.2 KB collector, server-generated vendor identities, and single-tenant infrastructure you control.

Head-to-head comparison

How Datafly Signal and GTM Server-Side compare across the capabilities that matter most to your marketing team.

Browser footprint

Datafly Signal

5.2 KB single script

GTM Server-Side

80 KB+ (gtag.js + vendor tags)

Tag replacement

Datafly Signal

Complete — zero vendor JavaScript

GTM Server-Side

Partial — still requires client-side vendor tags for identity

First-party setup

Datafly Signal

True first-party on your subdomain

GTM Server-Side

CNAME proxy (detectable by browsers)

Attribution window

Datafly Signal

400 days (server-set cookies)

GTM Server-Side

7 days in Safari (client-set cookies)

Session continuity

Datafly Signal

Sessions computed server-side, stable across the 400-day window

GTM Server-Side

session_number resets + first_visit re-fires after 7 days in Safari

Vendor identity

Datafly Signal

Generated server-side automatically

GTM Server-Side

Requires vendor JavaScript in the browser

Data governance

Datafly Signal

Company-wide rules + per-destination rules

GTM Server-Side

Basic event filtering only

PII protection

Datafly Signal

Automatic hashing, masking, and stripping

GTM Server-Side

Manual configuration required

Consent enforcement

Datafly Signal

Built into the platform

GTM Server-Side

Requires separate Consent Mode setup

Infrastructure

Datafly Signal

Single-tenant — your data only

GTM Server-Side

Shared Google Cloud

Delivery guarantee

Datafly Signal

Automatic retry with zero data loss

GTM Server-Side

If the request fails, the data is lost

Cost structure

Datafly Signal

Flat licence, all integrations included

GTM Server-Side

Free container, plus always-on servers and the engineers to run them

The key differences

GTM Server-Side was a step in the right direction. But it left significant gaps that affect your data quality, attribution accuracy, and total cost of ownership.

GTM Server-Side still requires vendor JavaScript

GTM Server-Side moves tag execution to a server container, but it still loads gtag.js (80 KB+) in the browser. And for vendor identity — generating _ga, _fbp, _ttp cookies — it still needs the vendor’s own JavaScript running client-side. Signal replaces all vendor JavaScript. The 5.2 KB collector is the only script on your site. Vendor identities are generated server-side and set as first-party cookies.

Safari deletes your attribution data after a week away

Safari deletes JavaScript cookies after 7 days if the visitor doesn’t come back. Since GTM Server-Side uses client-side JavaScript to set cookies, every Safari customer who takes more than a week to return is lost to attribution. Signal sets cookies from your own server on your own domain, giving you 400 days of customer recognition across every browser.

Your data flows through Google’s infrastructure

GTM Server-Side runs on Google Cloud. Every event transits Google’s shared infrastructure before reaching your vendors. Signal runs on single-tenant infrastructure — dedicated to your organisation. Your data never touches shared systems, and you can deploy in your own cloud or VPC.

No guaranteed delivery

When GTM Server-Side sends events to vendor APIs and the request fails, the data is lost. There’s no retry mechanism, no queuing, no fallback. Signal guarantees delivery with automatic retry and dead letter queuing — every event reaches its destination, even during vendor outages.

Hidden costs add up

GTM Server-Side is free to download, but it needs always-on servers, an engineer or agency to build and maintain a template for every vendor, and more of both as your traffic and destinations grow. Datafly Signal is one licence with every integration included and maintained by Datafly. The full breakdown is below.

Free to download. Not free to run.

The GTM server-side container costs nothing. Running it does: servers that are always on, people to build and look after it, and a bill that grows with your traffic and your list of vendors.

It costs to run

A server container needs servers. Google’s own guidance is to keep at least two or three running at all times so an outage doesn’t lose data, at around $30–$50 each a month, and to budget for the most your traffic can scale to: ten or more servers on a busy day. Network traffic, logging, monitoring and a separate preview server for debugging all add to the bill.

It needs someone to look after it

This is the cost that never makes it into the business case. Someone has to build it: configure the servers, set up the custom domain and TLS so cookies are first-party, and write or adapt a server-side template for every vendor. Then someone has to keep it running: capacity planning, monitoring and alerts, updating templates whenever a vendor changes its API, and tracking down events that went missing without an error. Whether that is an in-house engineer or an agency retainer, it is a recurring cost, and usually the largest one.

It gets expensive as you grow

Every new vendor is another template to build and maintain. Every traffic peak needs more servers, and when the container is overloaded or a vendor API fails, those events are lost, because nothing queues or retries them. Consent, identity and data governance each become projects of their own. The free container turns into an always-on service with a growing team behind it.

How Datafly Signal is different

Datafly Signal is one licence with all 260+ integrations included, and Datafly maintains them as vendor APIs change, so there are no templates to write or update. Identity, consent enforcement, bot filtering and queued, retried delivery are part of the platform rather than projects. It runs in a dedicated environment Datafly manages, or in your own cloud (AWS, GCP or Azure) if you prefer to host it. For pricing, request a demo.

To be fair to GTM: if you send data to one or two vendors and have engineers with time to run servers, a self-managed container can be the economical choice. The sums change as you add destinations, traffic and the people needed to keep it all working.

Is it time to move beyond GTM Server-Side?

If any of these sound familiar, Signal can solve the problem immediately.

Your Safari attribution is broken

If you’re losing customer journeys to Safari’s 7-day cookies, Signal’s 400-day server-set cookies solve this immediately.

Ad blockers hide 20–40% of your data

If your conversion data doesn’t match reality and ROAS calculations are unreliable, Signal’s first-party collection recovers the traffic that ad blockers hide.

Page speed impacts your conversions

If Core Web Vitals scores are suffering under the weight of vendor scripts, Signal eliminates them entirely — 5.2 KB replaces 800 KB+.

You need data governance before delivery

If you’re concerned about PII reaching vendors or need consent-aware data routing, Signal handles this automatically before any data leaves your infrastructure.

Frequently asked questions

Is Datafly Signal a replacement for GTM server-side or does it complement it?
Signal is a full replacement. GTM server-side still requires vendor JavaScript (gtag.js, Meta Pixel, etc.) in the browser to generate the events it forwards. Signal replaces the entire client-side tag layer with a single 5.2KB first-party collector, then delivers events directly to vendor APIs server-side. There is no gtag.js, no Meta Pixel, and no vendor script on the page.
How long does migration from GTM server-side to Datafly Signal typically take?
A typical production migration is two to three weeks for a mid-size site: one week to stand up the Datafly Signal cluster in the customer VPC and mirror existing tags, one week of parallel-run validation comparing event counts with GTM, and a final week for cut-over and decommissioning of the GTM container.
Does Datafly Signal support Google Consent Mode v2?
Yes. Signal enforces consent twice — once on the browser before events leave the page, and again on the server before delivery to each vendor. Consent decisions map cleanly onto Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) and are propagated to every destination that supports them.
Can I run GTM server-side and Datafly Signal in parallel during migration?
Yes, and we recommend it. A parallel run for one to two weeks lets you compare event counts side-by-side, confirm data quality, and ensure attribution is matching before you decommission the GTM container. Datafly Signal uses its own first-party subdomain so it does not conflict with an existing GTM deployment.
What happens to my existing GTM templates when I move to Datafly Signal?
GTM tag templates translate into Datafly Signal integration blueprints — pre-built configurations for each vendor (GA4, Meta CAPI, TikTok, LinkedIn, etc.). 260+ blueprints ship with the platform, so in most cases you will not need to rebuild tag logic from scratch. Custom GTM templates can be ported to Signal pipeline transformations in YAML.
How much does Google Tag Manager server-side cost?
The container is free, but running it isn’t. Google recommends at least two or three always-on servers for production, at around $30 to $50 each a month, scaling up with traffic, plus network traffic, logging and a preview server. The larger cost is people: building a server-side template for each vendor, setting up the custom domain, and monitoring and updating it all as vendor APIs change. Datafly Signal is one licence with all 260+ integrations included and maintained by Datafly; request a demo for pricing.
Is Datafly Signal a first-party vendor, or does my data go through Datafly servers?
Signal is deployed inside your own VPC on AWS, GCP, or Azure. Your data never touches Datafly-controlled infrastructure. We provide the Helm charts, you own the deployment.

Browser JavaScript footprint

Less code in the browser means faster pages, less ad-blocker surface area, and fewer tracking failures. Indicative figures.

Datafly Signal collector5.2 KB
Typical sGTM + 6 vendor pixels78.0 KB
Multi-product vendor suites + connectors95.0 KB
Per-connector pricing platforms + integrations52.0 KB

How long before your attribution data dies?

Customer cookies set client-side die fast. Server-set first-party cookies last for the customer’s full purchase cycle.

Safari (JavaScript cookies)7 days without a visit
Chrome (3rd-party cookies)90 days, then expiring
Datafly Signal (server-set 1st-party cookies)400 days

Server-set cookies from your own domain skip Safari’s 7-day limit, because your server sets them, not a vendor’s script.

Ready to move beyond GTM Server-Side?

See exactly how Signal compares to your current GTM setup — with your real data and integrations.