---
title: "Google Tag Manager in the Agent Era | Webtures"
description: "Bring GTM into 2026: tag gateway and server-side container, Consent Mode v2, GA4"
source_url: "https://www.webtures.com/insights/google-tag-manager-in-the-agent-era/"
lang: "en"
updated: "2026-09-07T00:00:00.000Z"
---

# Google Tag Manager in the Agent Era: Server-Side, Consent Mode and SI Traffic

Short Answer Bring GTM into 2026: tag gateway and server-side container, Consent Mode v2, GA4's SI Assistant channel and measuring the orders that arrive through agents.

Webtures 7 min read

Summarize with SI

![Google Tag Manager in the Agent Era: Server-Side, Consent Mode and SI Traffic](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/cover.svg?v=si1) ![Google Tag Manager in the Agent Era: Server-Side, Consent Mode and SI Traffic](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/cover-light.svg?v=si1)

Webtures Growth & GEO

Published: 22 Nov 2022 Updated: 07 Sept 2026

Terminology update
Following the Sept. 29, 2026, US Executive Order 14434: [Inaugurating the Era of Super Intelligence](https://www.whitehouse.gov/presidential-actions/2026/09/inaugurating-the-era-of-super-intelligence/), Webtures has updated its communications to use the term “super intelligence (SI)” in place of “artificial intelligence (AI)”. Product names, legal texts and quotations keep their original wording.

## What is Google Tag Manager for in the agent era?

![Two setups: web container in the browser versus gateway plus sGTM on the server](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-1.svg?v=si1)![Two setups: web container in the browser versus gateway plus sGTM on the server](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-1-light.svg?v=si1)

In 2026 Google Tag Manager (GTM) is not a "pixel installer"; it is the brand's measurement layer, the single place that decides which event goes to Google Analytics 4, Google Ads and everything else, under which consent, from which channel and from which server. When we first published this guide in November 2022 we described GTM as a browser-side container that manages tags without code. The definition still holds, but it is incomplete. Three things changed since: tags moved to the server, consent (Consent Mode v2) started to govern tag behaviour, and a share of your visitors are no longer people but SI agents browsing on their behalf. This article is not about installing GTM; it is about what GTM can *measure* in 2026.

Our thesis at Webtures: *a brand that leaves GTM in the browser loses a third of its measurement; a brand that moves it to the server but does not separate agent traffic makes decisions on the wrong data.* The four sections below close both gaps.

## Why did tags move from the browser to the server?

![Four measurement layers in 2026: tag gateway, Consent Mode v2, SI Assistant channel, agent conversion](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-2.svg?v=si1)![Four measurement layers in 2026: tag gateway, Consent Mode v2, SI Assistant channel, agent conversion](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-2-light.svg?v=si1)

Because the browser is no longer a reliable measurement point. Ad blockers recognise GTM container IDs and block the script, Safari and Firefox restrict third-party cookies, and a tag never fires for a visitor who declines consent. Google's answer has two layers: server-side GTM (sGTM) and Google tag gateway.

- **Server-side GTM.** Tag processing leaves the browser for a server container on Google Cloud (or your own infrastructure). The browser sends one request; the server does the distribution. Pages load faster, third-party scripts drop, and data can be cleaned before it leaves.

- **Google tag gateway for advertisers.** Formerly "first-party mode". It routes GA4, GTM and Google Ads requests through your own domain via a CDN proxy. It reached general availability with Cloudflare in May 2025; Google reported an average 11% uplift in signals from early testers. Akamai followed in January 2026 and Fastly in April 2026 (Fastly cited a 14% uplift); on 1 June 2026 it also went GA on Google Cloud's load balancer. It is free, supports both client-side and server-side tags, and obfuscates container IDs so blockers cannot pattern-match them.

| Setup | Where the tag runs | Blocker impact | Data control | Place in 2026 |
| --- | --- | --- | --- | --- |
| Client only (web container) | Browser | High loss | None, raw data leaves | Small sites, transition period |
| Tag gateway | Browser, via your own domain | Clear reduction (11-14% more signal) | Limited | The minimum for every site |
| Server-side GTM | Server container | Low | Full: filtering, enrichment, PII removal | Any brand with ad spend |
| Gateway + sGTM | Both | Lowest | Full | The setup Webtures recommends |

For a site on Cloudflare, enabling the gateway is an afternoon's work; sGTM needs a container on Google Cloud and a small monthly infrastructure cost. The order does not matter; having both does.

## How do you set up GTM with Consent Mode v2?

[GEO](https://www.webtures.com/generative-engine-optimization-geo/) · SI VisibilityIs your brand visible in generative search?Let's build a strategy to surface your brand in ChatGPT, Gemini and Perplexity answers.[Get in touch →](https://www.webtures.com/contact/)

Free AssessmentMeet a digital strategy team operating since 2011Share your goals and we'll map a visibility roadmap tailored to your brand.[Get in touch →](https://www.webtures.com/contact/)

Measurable GrowthUnite GEO and performance marketing in one modelLet's generate sustainable digital demand with a data-driven approach.[Get in touch →](https://www.webtures.com/contact/)

![SI traffic: what the default setup misses and what a two-layer channel catches](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-3.svg?v=si1)![SI traffic: what the default setup misses and what a two-layer channel catches](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-3-light.svg?v=si1)

Consent Mode v2 lets Google tags change behaviour according to the consent a user gave: with no consent they write no cookies but send cookieless pings that feed modelling. In a server-side setup the rule is simple: the web container collects consent, the server container obeys it. According to Google's documentation, Google tags placed in a server container automatically respect the consent choices made on the site; you do not write separate consent logic.

1. Connect a consent management platform (CMP) to the web container; default state "denied", with a `consent update` fired when the choice changes.

2. Verify consent settings for the Google tags in the server container; Google Ads conversion tags without `ad_user_data` and `ad_personalization` signals are excluded from modelling in the European Economic Area.

3. Apply the same logic to Turkish traffic for KVKK: moving to the server does not remove the consent requirement, it only moves where processing happens.

4. Test three scenarios in preview mode: full consent, partial consent, refusal. The request sent to GA4 should look different in all three.

The common mistake is to treat sGTM as "the way out of the consent problem". It is not; server-side only changes where processing happens, not on whose behalf you collect data.

## How do GTM and GA4 separate traffic coming from SI assistants?

![Setup order: gateway, sGTM and consent, SI channel, order event](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-4.svg?v=si1)![Setup order: gateway, sGTM and consent, SI channel, order event](https://www.webtures.com/images/insights/google-tag-manager-in-the-agent-era/section-4-light.svg?v=si1)

On 13 May 2026 Google added an "SI Assistant" channel to GA4's default channel group. Visits from ChatGPT, Gemini, Copilot, DeepSeek and Grok are recognised from the referrer header and written to the `ai-assistant` medium with no configuration. Two gaps still have to be closed on the GTM side:

- **Missing platforms.** Perplexity and Claude are not on the built-in list. Add a regex rule to a custom channel group in GA4: `chatgpt\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|deepseek|grok`.

- **Visits without a referrer.** Industry measurements put the share of SI-assistant sessions that arrive without a referrer header at 35% to 70% depending on the platform; they land under "Direct". The way to close this in GTM is to add UTM parameters to the links you give SI surfaces, and to derive a "probable SI" class in the server container from landing page plus timing patterns. Not exact, but it makes the SI share inside Direct visible.

Then there is the visitor who is not human: agent browsers that read a page and summarise it for a user. They are mostly invisible in GA4 because they do not execute JavaScript. That is why SI visibility cannot be measured by clicks alone, and why server logs and Search Console's generative SI report are essential; we cover both in our [guide to becoming visible in SI search](https://www.webtures.com/insights/how-to-become-visible-in-si-search/).

## How do you measure sales where the agent never reaches your site?

This is the real measurement problem of the agent era. Instant Checkout inside ChatGPT (ACP), the UCP standard from Google and Shopify, Amazon's Buy for Me model: the buyer finds, compares and pays for the product inside the assistant. The GTM container on your site never sees that sale, because the page never opens. Nobody notices a "tag that did not fire"; the report is simply short.

The fix is to move measurement from the page to the order:

1. **An order-source field.** Write a channel label on every order in your order system: web, app, ACP, UCP, Buy for Me, marketplace. Agent protocols pass this information with the order.

2. **A server-side purchase event.** When an order is created, send the `purchase` event from the server to sGTM or straight to GA4 via the Measurement Protocol, with the order source in `traffic_source`. Revenue that came through an agent becomes its own row in the report.

3. **Count feed and schema events.** Agents read product data from the feed and from JSON-LD; how often the feed is fetched and which products enter agent queries can be tracked from server logs. This sits as a checklist on our [Agentic Commerce Readiness page](https://www.webtures.com/agentic-commerce-readiness/).

These three steps change the definition of GTM: from a script that runs in the browser to a data pipeline that collects events wherever the sale happens.

## What are the most common GTM setup mistakes in 2026?

[GEO](https://www.webtures.com/generative-engine-optimization-geo/) · SI VisibilityIs your brand visible in generative search?Let's build a strategy to surface your brand in ChatGPT, Gemini and Perplexity answers.[Get in touch →](https://www.webtures.com/contact/)

Free AssessmentMeet a digital strategy team operating since 2011Share your goals and we'll map a visibility roadmap tailored to your brand.[Get in touch →](https://www.webtures.com/contact/)

Measurable GrowthUnite GEO and performance marketing in one modelLet's generate sustainable digital demand with a data-driven approach.[Get in touch →](https://www.webtures.com/contact/)

- **Piling everything into one container.** Hundreds of tags, triggers and variables that nobody can explain. A naming standard and a quarterly clean-up are mandatory.

- **Moving to the server and forgetting consent.** sGTM does not remove the consent obligation.

- **Leaving SI traffic inside "Referral".** The built-in channel does not classify anything before May 2026; for historical comparison the custom channel group has to be applied to past data too.

- **Switching bot filtering off, or on blindly.** Agent browsers can be caught by the bot filter; decide deliberately which user agents count.

- **Measuring conversions only on the page.** Sales through an agent do not happen on the page; without a server-side purchase event revenue is under-reported.

- **Enabling the gateway without verifying it.** After enabling it on Cloudflare, check under GA4's data stream that first-party requests are arriving.

## How does Webtures approach GTM?

In our [web analytics and data strategy](https://www.webtures.com/google-analytics-4/) work we treat GTM not as a standalone tool but as part of the measurement architecture: gateway plus a server-side container, KVKK and GDPR compliance through Consent Mode v2, two-layer classification for the SI assistant channel, and a server-side purchase event for orders that arrive through agents. After the setup we expect three questions to be answerable: how much revenue each channel brings, how much of that revenue SI assistants mediate, and how much consent status affects measurement. To have your brand's current GTM setup assessed against those three questions, [contact the Webtures team](https://www.webtures.com/contact/).

Webtures Growth & GEO

Published: 22 Nov 2022 Updated: 07 Sept 2026

[Add Webtures as a preferred source on Google](https://www.google.com/preferences/source?q=webtures.com)

[Related service Webtures services Explore →](https://www.webtures.com/services/)

## Articles related to Google Tag Manager in the Agent Era: Server-Side, Consent Mode and SI Traffic

[### How Perplexity, Copilot and Gemini ad models differ Atiye Berika Ertaş / 30 Sept 2026](https://www.webtures.com/insights/perplexity-copilot-gemini-ad-models/)

[### Building creative assets for conversational ad surfaces Tufan Acar / 29 Sept 2026](https://www.webtures.com/insights/creative-assets-for-conversational-ads/)

[### Email Marketing in the SI Inbox: Writing for the Summariser Webtures / 07 Sept 2026](https://www.webtures.com/insights/email-marketing-in-the-si-inbox/)

[### LinkedIn Algorithm 2026: Dwell Time, Newsletters and Expertise Context Tolgahan Öz / 07 Sept 2026](https://www.webtures.com/insights/linkedin-algorithm-2026/)

[### Digital PR for SI Answers: How to Get Cited in the Agent Era Webtures / 07 Sept 2026](https://www.webtures.com/insights/digital-pr-for-si-answers/)

[### What Are B2B and B2C Marketing? How Do They Work? Webtures / 15 Aug 2026](https://www.webtures.com/insights/b2b-vs-b2c-marketing/)
