Tech for Retail 2025 Workshop: From SEO to GEO – Gaining Visibility in the Era of Generative Engines

Back to blog

Setting up Google Tag Manager and Google Analytics 4 without duplicates

SEO

Discover Incremys

The 360° Next Gen SEO Platform

Request a demo
Last updated on

1/11/2026

Chapter 01

Example H2
Example H3
Example H4
Example H5
Example H6

This page is for marketing managers, SEO leads and analysts who connect Google Analytics 4 to their website through Google Tag Manager. It shows how to make Google Tag Manager and Google Analytics work together: the Google tag, GA4 events, enhanced measurement, key events and, above all, removing the duplicates that distort page views, sessions and events.

 

The basics (container, tags, triggers, variables) are covered in our guide to Google Tag Manager; here, you choose your deployment method and your checks.

 

Connecting Google Tag Manager to Google Analytics 4 (GA4): a Reliable Tag-Management Setup

 

In a sound setup, Google Analytics 4 receives and reports the data, while GTM decides when each tag fires. You deploy from one interface, with versions, preview and rollback.

 

If your team still confuses "it's in GA4" with "it's deployed in GTM", our comparison GTM or GA4: who does what clarifies the roles.

 

Define a Measurement Plan for Acquisition, Key Events and GEO/SEO ROI

 

Before you connect anything, formalise a measurement plan built around the decisions you need to make. It covers three families of signals:

 

  • Acquisition: SEO, SEA, referral and tagged campaigns.
  • Engagement: useful clicks, scroll depth and downloads.
  • Key events: demo or quote requests, and the micro-actions that lead to them.

 

Avoid piling on events "just to track everything": a few stable business actions, enriched with consistent parameters (form_name, content_type, cta_location), are enough to identify the content that converts.

 

Prerequisites Before Linking GTM to GA4: Property, Data Stream and Governance

 

Before opening GTM, check three prerequisites:

 

  • The GA4 property and its web stream: the G-… measurement ID is found in Admin > Data streams.
  • The installed container: its ID follows the GTM-… format; if it is missing, follow our guide to install GTM on your website.
  • A single source of implementation: no hard-coded GA4 code, no plugin already sending data.

 

Choose the Google Tag and Keep the IDs Distinct

 

Distinguishing G-… from GTM-… prevents implementing the wrong ID or sending data to the wrong property. For the base tag, GTM offers, at the time of writing, the "Google Tag" tag type: it replaced the former GA4 Configuration tag in September 2023 and relies on the Google tag (unified gtag.js, 2022).

 

High-Risk Scenarios: iFrames, Cross-Domain Journeys and Redirects That Distort Attribution

 

Three situations commonly create gaps between real acquisition and measured acquisition:

 

  • iFrames: depending on how it is embedded, the iframe prevents context sharing (domain, cookies) and breaks the session.
  • Cross-domain: a poorly configured journey across several domains generates self-referrals.
  • Redirects: a redirect that drops UTMs shifts the visit into "direct" or "referral".

 

As soon as journeys become dynamic (SPAs, funnels, embedded forms), a site-side data layer becomes the most stable foundation: GTM reads business events from it instead of fragile DOM elements.

 

Create a GA4 Tag in GTM: Step-by-Step Setup to Connect GTM to GA4

 

The basic web process runs in five steps, each with its own check:

 

StepTag or triggerCheck
Retrieve the measurement IDNone: G-… in Admin > Data streamsRight web stream, right property
Create the base tagTags > New > Google TagG-… ID pasted, no legacy ID
Attach the triggerAll Pages, as early as possibleOnly one Google tag per page
Add business eventsGA4 Event tags on stable triggersNon-empty parameters in DebugView
TestPreview mode via Tag AssistantA single page_view received in DebugView
PublishNamed and described versionData visible in GA4 after publishing

 

Until the container is published, no data is collected. The Google tag already sends page_view: do not add an event tag for the page view.

 

"All Pages" Trigger and Naming: Reducing Duplicates from the Start

 

GA4 uses an event-based model: an event name plus parameters. Four rules keep collection clean and readable:

 

  • Firing: the base tag on all pages, as early as possible, subject to your consent strategy.
  • Inventory: source code, plugins and legacy tags reviewed before deployment.
  • Naming: short, unambiguous event names and a shared parameter dictionary.
  • UTMs: shared source, medium and campaign conventions, without variations that fragment attribution.

 

Events in GA4: Automatic Collection, Enhanced Measurement and GA4 Events via GTM

 

Once the Google tag is live, GA4 collects page views. Everything else is split between enhanced measurement and your GTM tags.

 

What GA4 Collects by Default and What Enhanced Measurement Covers

 

Enhanced measurement, enabled at web stream level, automatically adds scrolls, outbound clicks and file downloads. Anything business-related needs dedicated instrumentation in GTM. The following table helps you choose the source of each signal:

 

SignalEnhanced measurementEvent via GTM
Page viewSent by the Google tagUnnecessary, a source of duplicates
ScrollCovered, without business contextUseful for reading a key section
Outbound clicks, downloadsCovered automaticallyUseful for adding business parameters
Strategic CTA clickNot coveredGA4 Event tag on an identified click
Qualified lead, funnel stepNot covereddataLayer event pushed by the site
Form actually submittedNot covered as a business successEssential, on a success event

 

Check that no signal is sent twice, by the stream and by GTM.

 

Create Custom Events via Tag Manager: a Robust Method and Useful Parameters

 

The maintainable method links three building blocks, so that a text or CSS change does not break measurement:

 

  • a stable trigger: ID, URL condition or data layer event;
  • a GA4 Event tag: event name and parameters;
  • variables: URL, clicked text or data layer values, to add context.

 

For common B2B interactions, choose parameters that support analysis by page and intent:

 

  • CTA: cta_text, cta_location, page_path, content_type.
  • Form: form_name, form_step, lead_type where relevant, and a genuine success signal.
  • Scroll: an engagement signal on a key section, never a pseudo-conversion.

 

A common pitfall is tracking a "submission" on a click even when the form fails. Instead, trigger on an event pushed on success, for example lead_submit with form_name and plan: it feeds GA4 and, if needed, Google Ads.

 

Key Events and Acquisition: GA4, Google Ads and De-duplication

 

A key event is only worth something if the source event is accurate: a real success, fired once, attributed to the right channel.

 

Turn an Event into a Key Event: Primary or Micro-action

 

In GA4, you mark certain events as key events, the name that replaced "conversions" in 2024. In B2B, the primary key event remains the lead (demo, quote, meeting). Micro-actions diagnose the funnel: lots of CTA clicks but few submissions point to friction.

 

For Google Ads, choose a single route per action: import the GA4 key event, or fire a Google Ads tag via GTM. The GA4-side setup is detailed in our guide to defining key events in Google Analytics.

 

De-duplicate a "Hard-coded + GTM" Implementation

 

The classic risk is a hard-coded GA4 tag (gtag.js, CMS plugin, theme) coexisting with the Google tag deployed by GTM. Each symptom has its cause and its fix:

 

SymptomLikely causeFix
Double page_view on every loadHard-coded gtag.js and Google tag via GTMRemove the hard-coded gtag, keep GTM only
Inflated sessionsCMS plugin and GTM each send dataDisable sending by the plugin
Duplicated eventsEnhanced measurement and GTM tag on the same signalKeep a single source per signal
Overstated key eventTwo triggers for the same actionA single trigger, on success
Action counted twice in Google AdsGA4 import and Google Ads tag in parallelA single route per action

 

Check each fix in Preview mode: one page load must produce a single page_view request per measurement ID.

 

Diagnose Attribution Issues: Direct, Referral, Self-referrals and Cross-domain

 

When a key event shows up as "direct" or "referral", look at the journey first, and only then at GA4:

 

  • Cross-domain: declare every domain in the journey (website, payment, booking) in the cross-domain configuration.
  • Redirects: check that UTMs survive every hop.
  • Self-referrals and iframes: look for your own domain as a source and for broken sessions.
  • GA4: last, check filters and referral exclusions.

 

E-commerce: Implement GA4 via GTM, Validate It and Interpret the Reports

 

In e-commerce, GTM fires the standard GA4 events (view_item, add_to_cart, purchase) from a stable data layer: ID, name, price, quantity, currency. Their structure is described in our guide to the data layer in GTM. Before relying on the reports, make a full purchase and check:

 

  • no duplicates, especially on the confirmation page;
  • consistent currency;
  • amounts present on every event;
  • how taxes and fees are handled for your model.

 

Testing and Debugging: Validate GTM, GA4 and Key Events Before Going Live

 

Preview mode protects GA4 from polluted data: it shows which tags fire, on which event and with which variables. The complete workflow is in our guide to testing GTM before publishing.

 

Tag Assistant and DebugView: What to Check Depending on the Symptom

 

Tag Assistant (tagassistant.google.com) opens GTM Preview mode; DebugView, in GA4 Admin, shows reception and parameters. Preview mode can set debug_mode, which helps you read your test visits. The discontinued Tag Assistant Legacy extension cannot read GA4.

 

SymptomWhere to lookLikely cause
Tag fired, nothing in DebugViewNetwork requests, measurement IDWrong property, browser blocking or filter
Action performed, no tag firedTrigger in Tag AssistantTrigger condition, not GA4
Event received twiceSource code, network requestsHard-coded and GTM implementation
Empty parameter in DebugViewVariables in Tag AssistantMisdefined variable or missing data

 

At every version you publish, and again during the monthly check, apply this list:

 

  • name the GTM version and describe the changes;
  • confirm no equivalent tag is hard-coded;
  • test a full journey, from acquisition to key event;
  • validate parameters: not empty and in the right format.

 

Compliance: GDPR, Cookies and Consent in a GTM + GA4 Setup

 

Consent and privacy determine the completeness of your data as much as your compliance.

 

Consent and Signal Loss: Correctly Interpreting Incomplete Data

 

Some visitors refuse certain tags: read these gaps as trends, not absolute values. GTM enforces firing rules based on user choices, separating necessary, measurement and advertising tags. It sets no cookies by itself, and Consent Mode v2 is configured once in the container, as explained in our article on cookies and consent in GTM.

 

Privacy and Governance: What You Can Actually Control

 

GA4 does not store IP addresses: there is no anonymisation setting to add to the tag. Keep instrumentation (GTM and its tags) aligned with GA4 configuration (retention, key events, attribution). Over time, quality depends on four practices:

 

  • separate environments, staging and production;
  • limited publishing permissions;
  • named and described versions;
  • a regular audit of obsolete tags, for a lean container.

 

GEO and SEO: Making Use of Analytics Once Collection Is Reliable

 

Clean collection first serves your editorial priorities, through two cross-analyses.

 

Link Content to Outcomes: Landing Pages, Engagement and Key Events

 

Connect SEO landing pages, engagement and key events. Pages that drive traffic but convert poorly signal an intent problem; those that convert well but lack visibility, an editorial opportunity. For GEO, referral traffic from AI assistants can be read in GA4 like any other source, provided collection is clean.

 

Link Search Console to GA4: Interpret Queries, Pages and Key Events Without Bias

 

Google Search Console measures visibility in Google (impressions, clicks, positions), GA4 on-site behaviour. Differences between them are normal (consent, ad blockers, redirects, delays). Combine them to connect a query and a page to a business KPI: see our article on Search Console and Google Analytics.

 

Depending on Your Situation

 

Depending on where you are, here is the resource to open next:

 

  • Your events need dynamic values: data layer variables, constants and lookup tables are chosen according to use, as our guide to GTM variables shows.
  • Your campaigns land in "direct": shared conventions restore the source, see our guide to the UTM tag.
  • Your collection is reliable: our guide Google Analytics for SEO details the reports that matter for search.
  • You are unsure what to track: our selection of KPIs in Google Analytics helps keep the measurement plan to the essentials.

 

Once your key events are reliable, you can bring them together with Google Search Console data in the Incremys Performance Reporting module, connected to both sources via API.

 

FAQ: Tag Management, GA4 and Connecting GTM to Analytics

 

How Do You Connect GTM to GA4 Without Creating Duplicate Tracking?

 

A single Google tag must send data to your measurement ID, with no gtag.js or plugin running in parallel. Deploy it via GTM on all pages, test in Preview mode, then publish. Then check in DebugView that one page produces only one page_view.

 

Should You Keep the Hard-coded gtag If You Use GTM?

 

No, the hard-coded gtag must be removed as soon as GTM deploys the Google tag. Running both in parallel doubles page views and events and distorts key events. Inventory the source code, plugins and theme, then check in Preview mode that only one request is sent per page.

 

How Do You Create a GA4 Tag in GTM and Which Trigger Should You Choose?

 

Create a Google Tag with your G-… ID and attach it to the "All Pages" trigger, as early as possible, subject to your consent strategy. Then add GA4 Event tags for business actions. Test in Preview mode, then publish a named version.

 

What Is a GA4 Key Event?

 

A key event is a GA4 event you mark as important for your business, such as a demo request or a purchase. This name replaced "conversions" in 2024. It is only worth something if the source event represents a real success, fired only once.

 

What Is the Difference Between Automatic Events, Enhanced Measurement and Custom Events?

 

Automatic events come from the Google tag, such as page_view. Enhanced measurement adds, at web stream level, scrolls, outbound clicks and file downloads. Custom events are the ones you define for your business, such as lead_submit, usually via GTM and the data layer.

 

How Do You Track a Form, a CTA Click or a Download in GA4?

 

Each interaction is tracked with a stable trigger and a GA4 Event tag. For a CTA, trigger on a click identified by an ID or attribute; for a form, on the genuine success (confirmation or data layer event). For a download, first check whether enhanced measurement already covers it.

 

Why Do Key Events Show as Direct or Referral, and How Do You Fix Attribution?

 

A key event shows as direct or referral when the journey loses its source. Common causes are UTMs lost during a redirect, incomplete cross-domain setup, self-referrals and iframes. Fix the journey first (links, domains, redirects), then the referral exclusions in GA4.

Discover other items

See all

Next-Gen GEO/SEO starts here

Complete the form so we can contact you.

The new generation of SEO
is on!

Thank you for your request, we will get back to you as soon as possible.

Oops! Something went wrong while submitting the form.