Analytics and Measurement

Google Tag Manager Setup, Server-Side Tagging and Consent Mode v2

Google Tag Manager (GTM) is where tags such as GA4, Google Ads, Meta Pixel, TikTok Pixel and Clarity live in one place, so marketing can add tags without waiting for a developer. Over a few years, that same convenience tends to produce a container everyone publishes to and no one fully understands. Half of our GTM work is setup; the other half is keeping the container in order.

Book a growth call Read the details

Illustrative view: diagram of tag management data flow.

Purpose and appearance

What do we use this service for?

Our goal with Google Tag Manager is simple: every conversion reaches GA4 and the ad platforms completely and exactly once. With server-side tagging we keep that data under your control, reduce the code running in the browser and give automated bidding a more reliable purchase signal.

Funnel stages it serves

Awareness
Consideration
Conversion
Loyalty

Data layer implementation: what your tags should rely on

Tying tags to a button's CSS class is quick but fragile. When the theme changes or the e-commerce platform renames a button, the purchase tag stops firing and nobody notices. Instead, we agree a data layer (dataLayer) specification with your developer that defines which fields are sent with which event, and we attach tags to those events.

On off-the-shelf platforms such as Shopify, or IdeaSoft, Ticimax and T-Soft in Türkiye, part of the data layer comes from a plugin or the theme. We check what actually arrives in preview mode and have the missing fields added. The product ID in particular has to carry the same value in GA4, the Meta catalog and Merchant Center.

GTM container audit: how we keep it organized

A container audit starts with an inventory of every tag, trigger and variable. After cleanup, these rules keep it readable:

A naming convention in the 'Platform - Event - Trigger' format, with a folder per platform
Publish rights for two people only; everyone else gets edit rights
A version note on every release explaining what changed
Changes prepared in a separate workspace, with the preview link shared for approval
Leftover Universal Analytics tags that no longer send data are deleted
Email and phone passed as hashed values for Google Ads enhanced conversions

Server-side GTM: when is server-side tagging worth it?

With server-side tagging, the browser doesn't send data directly to Google, Meta or TikTok. It sends it to a server container on your own subdomain (for example measure.yourdomain.com), which cleans the data, strips fields that aren't needed and forwards it to each platform. Less third-party code runs in the browser, which helps page speed, especially INP.

Running Meta Conversions API through the server container strengthens the purchase signal that Advantage+ Sales Campaigns learn from; the Pixel and server events must match on the same event_id. For Cloud Run, Google recommends at least two server instances to avoid data loss, and the preview server runs separately. Because it needs a Google Cloud project, we recommend server-side GTM for high-traffic sites sending data to more than one platform.

Consent Mode v2 setup in Google Tag Manager

Consent Mode v2 adds the ad_user_data and ad_personalization signals to ad_storage and analytics_storage. We map the choices in your cookie banner to these four signals and confirm in preview that the consent update fires before the page changes. Banner wording and the legal assessment (for example under KVKK, Türkiye's personal data protection law, or GDPR) stay with your legal counsel; we build the technical connection and monitor the signal that campaigns such as Performance Max receive.

Google Tag Manager: when do we recommend it?

We recommend it

Sites with tags embedded in theme files, where every change waits on a developer
E-commerce brands sending the same purchase data to more than one ad platform
High-traffic sites with page speed problems caused by third-party code

We don't recommend it

Server-side setup on low-traffic sites; the setup and maintenance effort may outweigh the gain
Building complex e-commerce measurement with click selectors alone, without a data layer

How we manage Google Tag Manager

Container inventoryWe list existing tags, triggers and variables and note what each one does.
Data layer specificationWe prepare a document with the developer that defines event names and fields.
Cleanup and renamingWe remove tags that don't work and apply the naming convention.
Preview testingWe run every scenario in Tag Assistant and verify it with each platform's testing tools.
Server container (if needed)We deploy the Cloud Run setup, the subdomain and the platform tags.

Google Tag Manager: metrics and requirements

Metrics we track

Tag firing accuracy
Pixel and CAPI match rate
Number of active tags
Consent rate
Order reconciliation gap

What you need to get started

Publish permission on the Google Tag Manager container
A developer or platform support to implement the data layer
A Google Cloud project and billing account for server-side setup
Access to add a DNS record for the subdomain

Official sources

The Brand Move Measurement Team

To learn more about Google Tag Manager or other measurement services, contact The Brand Move Measurement team today.

Explore further

Other Analytics and Measurement services

Analytics and Measurement overview

Google Analytics 4

A GA4 audit and setup: event plan, key events, ecommerce tracking and attribution settings, checked against real orders.

Explore

BigQuery

A data warehouse that joins raw GA4 event data with CRM, returns and ad cost to show real profit and lead quality.

Explore

Data Studio (Looker Studio)

A fast-loading Looker Studio (Data Studio) marketing dashboard with written metric definitions, so management and marketing read the same numbers.

Explore

Frequently asked questions

Google Tag Manager: frequently asked questions

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

With client-side tagging, each platform's code runs in the visitor's browser and sends data directly to that platform. With server-side tagging, the browser sends data to a server container on your own subdomain, which decides what is forwarded to each platform. The result is more control over the data and less code in the browser.

Does server-side tagging get around ad blockers and cookie consent?

No. If a visitor hasn't given consent, the server container has to respect that too, and Consent Mode signals are passed on unchanged. The real benefits are control over the data, not sending unnecessary fields to platforms and a lighter page.

Will Google Tag Manager slow down my site?

GTM's own code is light; slowdowns come from the tags inside it. Two Meta Pixels sending the same event, old heatmap scripts nobody looks at and chat tools loading on every page are what we see most. A cleanup alone often makes a noticeable difference.

Do we need a developer to set up Google Tag Manager?

For a reliable e-commerce setup, yes, at least once: the data layer has to be implemented in the site code or through your platform's plugin. After that, most tag changes can be made in GTM without developer time.

Can we share our GTM container with another agency?

Yes. We recommend each agency works in its own workspace while publish rights stay with you or a single owner. Version notes show which change came from whom, and a faulty release can be rolled back to the previous version.

Let's run a first Google Tag Manager review together.

In a free call we review your analytics property and tag setup, then show you in writing where data is missing or double-counted.

Book a growth call No sales pressure. Just findings.