Google Analytics

Google Analytics

Google Tag Manager for Google Ads and Google Analytics Tracking

Signup to our Newsletter

Accurate conversion tracking is the foundation of effective Google Ads management and reliable website analytics.

Google Tag Manager provides a central system for deploying and managing tracking across a website without requiring developers to hard-code every measurement tag individually. It can be used to implement Google Analytics 4, Google Ads conversion tracking, remarketing, enhanced conversions, Consent Mode and tags from many other advertising and analytics platforms.

Google has recently announced a significant change to this system. The Google tag and Google Tag Manager are being unified into a shared tagging platform.

This does not mean Google Ads and Google Analytics have become one reporting product. They remain separate destinations with different purposes, settings and conversion requirements. However, the underlying tagging infrastructure is becoming more centralised.

For advertisers, this should eventually mean:

Fewer separate scripts loading on a website.
More consistent settings across Google products.
A clearer view of where measurement data is being sent.
Easier debugging and version control.
Visual event creation for some conversion types.
Potentially faster transmission of measurement data.
A simpler route from basic Google tag installation to advanced Tag Manager functionality.

The technology may be becoming easier to manage, but measurement strategy still matters. A perfectly installed tag can still optimise advertising towards the wrong actions if conversions have not been defined properly.

What Is Google Tag Manager?

Google Tag Manager, commonly abbreviated to GTM, is a tag management system.

Instead of adding a separate piece of tracking code directly to the website every time a new platform or event needs to be measured, a business installs a Tag Manager container. Tags, triggers and variables can then be configured through the GTM interface.

The container acts as the delivery and control layer for website measurement.

It can be used to manage:

Google Analytics 4.
Google Ads conversion tracking.
Google Ads remarketing.
Enhanced conversions.
Consent Mode.
Floodlight tags.
Meta Pixel and Conversions API browser events.
LinkedIn Insight Tag.
Microsoft Advertising UET.
Call-tracking software.
Heatmaps and user-experience tools.
Custom HTML and JavaScript, where appropriate.

Tag Manager also provides workspaces, previews, debugging, user permissions and version history. This makes it much safer than repeatedly editing website code, particularly when several platforms and conversion events need to be managed.

What Has Google Recently Changed?

Google has announced that the Google tag and Google Tag Manager are being brought together into a more unified tagging system.

Under the new architecture, existing Google tags can be upgraded into fully capable Google Tag Manager containers. A website that currently uses only a basic Google tag will therefore gain access to Tag Manager capabilities such as interface-based configuration, debugging and version control.

Google has confirmed that the upgrade will not automatically change how existing Google tags behave on a website. Each connected Google destination will also retain its own tag and destination configuration.

The important distinction is:

Google tag and Google Tag Manager are being unified.
Google Ads and Google Analytics remain separate destinations.
Existing conversion events do not automatically become interchangeable.
Advertisers still need to decide what data should be sent to each platform.

Google is also introducing a simplified GTM interface. Container-wide settings will appear within a central Settings area, while triggers, variables, templates and folders will be grouped within an Advanced section.

Existing Tag Manager users may be invited to optimise their containers. Google says this optimisation will not be applied automatically. Users will be able to review the proposed changes before publishing them.

According to Google’s official announcement about the unified tagging platform, optimised containers will eventually be able to send data directly to Google destinations rather than loading additional gtag.js JavaScript for every destination. This may reduce latency and improve website performance.

Do I Need to Upgrade My Current Google Tag or GTM Script?

In most cases, no immediate script replacement is required.

Google states that existing Google tags will continue to behave as they do now. The upgrade gives them access to Google Tag Manager capabilities, but it does not require every website owner to remove the current script and install a completely different one.

The correct action depends on the current implementation.

If You Already Use Google Tag Manager

If the website already has a GTM container installed with an ID beginningGTM-, do not remove or replace the container snippet simply because Google has announced the unified system.

Google may display an optimisation banner inside the container. This will allow an authorised user to:

Review existing Google destination tags.
Move shared Google tag settings into the new Settings section.
Connect the container with relevant Google product accounts.
Preview the proposed configuration changes.
Publish the optimised version when it has been checked.

Google says the optimisation will not be published automatically.

Before accepting it:

Export or document the current container.
Create a clearly named workspace.
Review every proposed destination connection.
Check GA4 pageview and event behaviour.
Check Google Ads conversion and remarketing tags.
Check Consent Mode sequencing.
Preview the complete container.
Test the changes before publishing.

Do not delete existing conversion tags merely because the container has been optimised. Google says event tags will remain unchanged during the optimisation process.

If You Use a Direct Google Tag

If the website has a direct gtag.js installation rather than GTM, Google says it will be upgraded to gain Tag Manager capabilities without changing its existing in-page behaviour.

Therefore, you do not normally need to replace a working direct Google tag immediately.

You may later use the unified interface to:

Manage the tag through Tag Manager.
Add Google Ads or GA4 as destinations.
Create and debug events.
Use version control.
Review data flows.
Configure central settings.

The change provides additional management capabilities around the existing installation. It is not an instruction to reinstall the tag on every website.

If You Have Separate GA4 and Google Ads Tags

Some older websites contain:

A direct GA4 Google tag.
A separate Google Ads Google tag.
Additional Google Ads event snippets.
A GTM container.
Plugins that install the same tags again.

This does not necessarily mean the website is broken, but it should be audited for duplication.

Google allows multiple destinations to share one Google tag configuration. However, combining tags can affect shared settings and may be difficult to reverse. Do not combine them without checking:

Which tag loads on which pages.
Whether both tags have the same consent behaviour.
Whether they use different cross-domain settings.
Which destinations are connected.
Whether events are already duplicated.
Whether different agencies or teams own the tags.
Whether the same tag ID is installed more than once.

A unified configuration can simplify management, but simplification should not come at the expense of reliable historical measurement.

If You Still Use an Old Universal Analytics Tag

Universal Analytics stopped processing standard property data and should not be treated as a current analytics implementation.

If the website only contains a Universal Analytics ID beginningUA-, it needs a GA4 property and a current Google tag or GTM implementation. This is a measurement migration rather than an upgrade caused by the latest Tag Manager announcement.

If You Use a WordPress Tracking Plugin

Check what the plugin installs before making any changes.

A WordPress website may have tracking deployed through:

A Google integration plugin.
A dedicated Tag Manager plugin.
Elementor custom code.
Theme header scripts.
A cookie-consent plugin.
WooCommerce integration.
Manually edited theme files.
Google Tag Manager itself.

Only one method should normally install the GTM container. Avoid adding a second container script while leaving the original installation active.

Does One Google Tag Now Track Google Ads and GA4?

A Google tag can already be connected to multiple destinations, including Google Ads and Google Analytics.

Google recommends that businesses using both products set up the Google tag in one platform and add the other platform as a destination. This can reduce duplicate installations and centralise common tag settings.

However, this does not mean that one basic pageview tag automatically provides complete Google Ads and GA4 conversion tracking.

The distinction between the shared infrastructure and the measurement destinations is important:

Component	Main purpose
Google Tag Manager container	Controls how tags, events, triggers, variables and settings are deployed
Google tag	Provides shared Google measurement configuration and connects to destinations
GA4 destination	Receives website and app analytics events
Google Ads destination	Receives advertising conversions, remarketing signals and enhanced conversion data
GA4 event	Records behaviour for analytics and reporting
Google Ads conversion action	Measures and potentially optimises advertising towards a defined outcome
Data layer	Supplies structured website and transaction information to the tracking system

A form submission might therefore activate:

A GA4 generate_lead event for analytics.
A Google Ads lead conversion for advertising measurement.
Enhanced conversion data for improved Google Ads matching.
A CRM process that later sends a Qualified Lead or Customer conversion back to Google Ads.

These events may use the same underlying website interaction, but they have different purposes and should be configured deliberately.

Google Tag Manager Versus the Google Tag

The Google tag is the core Google measurement technology used to send data to destinations such as Google Analytics and Google Ads.

Google Tag Manager is the management environment used to control tags, events, triggers, variables, consent states and other measurement logic.

Historically, a smaller business might install the Google tag directly through its website builder, while a more advanced advertiser would deploy it through GTM.

The recent unification reduces this separation. Google tags are gaining Tag Manager capabilities, and optimised Tag Manager containers will handle Google destinations more directly.

Nevertheless, Google Tag Manager remains valuable when a business needs:

Several conversion actions.
Custom form or button tracking.
Ecommerce tracking.
Dynamic conversion values.
Enhanced conversions.
Consent controls.
Cross-domain measurement.
Multiple advertising platforms.
Custom data-layer events.
Preview and debugging tools.
Version control and rollback.
Different tags for different website sections.
Agency and internal-team access controls.

A simple Google tag may be sufficient for basic pageview measurement. GTM becomes more useful as the website, advertising and measurement requirements become more complex.

How Google Tag Manager Works

A Tag Manager implementation has four main components.

Triggers

Triggers determine when a tag should activate.

Examples include:

Every pageview.
A specific thank-you page.
A successful form submission.
A telephone-link click.
A booking confirmation.
An ecommerce purchase.
A video interaction.
A custom data-layer event.
A consent-status update.

The quality of the trigger is critical. A trigger that activates when someone clicks a submit button may count failed form attempts as conversions. A trigger based on confirmed form success is usually more dependable.

Variables

Variables supply dynamic information to tags and triggers.

They may contain:

Page URLs.
Click text.
Form identifiers.
Product names.
Transaction values.
Currency.
Order IDs.
Customer types.
Consent states.
Hashed first-party customer information.
Data-layer values.

Variables allow one configuration to work across several pages, products or conversion values.

Data Layer

The data layer is a structured JavaScript object through which the website can communicate with Tag Manager.

For example, an ecommerce website can push a purchase event containing:

Transaction ID.
Order value.
Currency.
Product identifiers.
Product names.
Quantities.
Discounts.
Shipping.
Tax.

A lead-generation website might push a confirmed lead event containing:

Form type.
Service category.
Location.
Lead type.
Estimated value.
Logged-in or customer status.

The data layer is generally more dependable than asking GTM to infer every action from button text, page layout or CSS selectors.

Installing Google Tag Manager Correctly

A standard web container uses two installation snippets.

The primary JavaScript snippet is placed as high as possible within the website’s <head>. A secondary <noscript> iframe is placed immediately after the opening <body> tag.

Many content management systems, ecommerce platforms and website builders provide a native field or supported integration for the GTM container ID.

Common installation methods include:

Native CMS integration.
A carefully selected WordPress plugin.
Theme or child-theme installation.
A website-builder integration.
Direct developer implementation.
A consent-management platform integration.

Avoid installing the same GTM container through multiple methods. For example, adding it through both a WordPress plugin and Elementor custom code can cause duplicate events and unreliable reporting.

After installation, confirm that the container appears once on every required page and that preview mode can connect successfully.

How to Set Up the Google Analytics Base Tag and Pageviews

The first GA4 requirement is a website-wide Google tag connected to the correct GA4 web stream.

The terminology and layout may vary while Google rolls out the unified Tag Manager interface. Some containers will show a traditional Google tag within the Tags area. Optimised containers may show shared configuration and destinations inside Settings.

The measurement principle remains the same: the GA4 destination must load on every applicable page after the appropriate consent state has been established.

Step 1: Create or Select a GA4 Property

In Google Analytics:

Open Admin.
Select the correct account and property.
Under Property Settings, select Data streams.
Select an existing web stream or create a new one.
Confirm that the website URL and stream name are correct.
Copy the Measurement ID.

A GA4 Measurement ID normally begins with G-.

Step 2: Review Enhanced Measurement

Within the web stream, review Enhanced Measurement.

This can automatically collect certain events, including:

Page views.
Scrolls.
Outbound clicks.
Site searches.
Video engagement.
File downloads.
Form interactions.

Only enable the events that are appropriate for the website. If an interaction is already collected through Enhanced Measurement, do not recreate the same event in GTM without a specific reason.

Automatic form interactions should also be treated as behavioural events rather than assumed to be confirmed leads.

Step 3: Create the Google Tag in GTM

In a traditional GTM workspace:

Open Tags.
Select New.
Give the tag a descriptive name, such as Google Tag – GA4 – All Pages.
Select Tag Configuration.
Select Google tag.
Enter the GA4 Measurement ID beginning with G-.
Select the appropriate page-wide trigger.
Save the tag.

For a conventional implementation, the Google tag should load across all relevant pages. Depending on the container layout and consent setup, this may use an Initialisation or All Pages trigger.

Do not use Consent Initialisation for ordinary analytics configuration. That trigger is intended for tags responsible for establishing or updating consent states.

In an optimised unified container, add or confirm the GA4 destination within the Settings area and review its container-wide configuration. Google may manage the destination through the container rather than requiring the same legacy tag arrangement.

Step 4: Confirm Pageview Collection

The Google tag normally sends a page_view event when the GA4 configuration loads, unless automatic pageview sending has been disabled.

Do not add a separate GA4 pageview event tag until you have confirmed whether the base configuration already sends it. Otherwise, every page may be recorded twice.

For an ordinary multi-page website, one automatic pageview per successful page load is normally appropriate.

Single-page applications require additional handling because navigation can occur without a complete browser reload. Test whether GA4 Enhanced Measurement records virtual history changes correctly. If it does not, configure controlled virtual pageviews using history-change or data-layer triggers.

Step 5: Configure Consent

Ensure the consent platform establishes the default consent state before GA4 processes the page.

The GA4 destination should respect analytics_storage. Other consent parameters may also apply depending on advertising features, Google Signals, audiences and linked products.

Step 6: Preview and Test

Select Preview in GTM and connect Tag Assistant to the website.

Confirm that:

The correct GTM container loads.
The Google tag activates once.
The correct G- Measurement ID is used.
One page_view event is sent per ordinary page load.
Consent behaviour changes correctly after the visitor’s choice.
Internal tests appear in GA4 DebugView or Realtime.
No old GA4 plugin or direct script sends duplicate pageviews.

Step 7: Publish

When testing is complete:

Select Submit.
Give the version a descriptive name.
Document the GA4 property, Measurement ID and key changes.
Publish the container.

Allow time for data to appear in standard GA4 reports. Realtime and DebugView are more suitable for immediate technical testing.

For a broader introduction to reporting and behavioural analysis, see our Google Analytics guide.

Setting Up Google Analytics Events Through GTM

The base Google tag provides the GA4 connection and ordinary pageview measurement. Additional events record commercially or analytically useful interactions.

Recommended GA4 event names should be used where they accurately describe the action. Examples include:

generate_lead
sign_up
login
search
view_item
add_to_cart
begin_checkout
purchase
refund

To create a GA4 event in GTM:

Open Tags.
Select New.
Select the relevant Google Analytics event tag type.
Choose the Google tag or GA4 destination.
Enter the event name.
Add useful event parameters.
Select a dependable trigger.
Save and preview the tag.
Confirm the event and parameters in GA4 DebugView.
Publish the container.

For example, a successful lead form might send:

Event name: generate_lead
form_name: contact_form
service: google_ads_management
lead_type: consultation_request

Do not include names, email addresses, telephone numbers or other directly identifying information in GA4 event parameters.

How to Set Up Google Ads Conversion Tracking Through GTM

Google Ads conversion tracking measures actions generated after advertising interactions.

The recommended setup begins inside Google Ads, where the conversion action and its commercial settings are defined. GTM then controls when the conversion event is sent.

Common website conversions include:

Lead-form submissions.
Quote requests.
Telephone calls.
Appointment bookings.
Trial registrations.
Online purchases.
Subscription activations.
Account creations.

Step 1: Create the Conversion Action in Google Ads

In Google Ads:

Open Goals.
Select Conversions and then Summary.
Create a new conversion action.
Select Website as the source.
Enter and scan the website domain if requested.
Select the most appropriate conversion category.
Choose to create the conversion directly using the Google tag.
Select the manual setup option if GTM will control the event.

Google may also offer an integrated Set up in Google Tag Manager option. This can import suggested Google Ads Conversion Tracking tags into a selected GTM workspace. The imported tags still require triggers and variables to be reviewed before publication.

Step 2: Configure the Conversion Settings

Review the following settings carefully:

Conversion name: Use a specific commercial name such as Website Lead – Contact Form.
Goal and action optimisation: Decide whether the action should be Primary for bidding or Secondary for observation.
Value: Use a fixed value, dynamic value or no value depending on the action.
Count: Use One for most leads and Every for ecommerce transactions.
Conversion windows: Select appropriate click-through, engaged-view and view-through windows.
Attribution: Review the available attribution setting.
Enhanced conversions: Enable where appropriate and implement the required first-party data collection.

A conversion should not be made Primary simply because it is measurable. Primary conversions normally influence automated bidding and should represent outcomes the business genuinely wants more of.

Step 3: Obtain the Conversion ID and Label

After creating the conversion, open its tag setup or implementation instructions.

Select the Google Tag Manager option to obtain:

The Google Ads Conversion ID, normally beginning AW-.
The conversion label unique to that conversion action.

The Conversion ID identifies the Google Ads destination. The label identifies the individual action, such as a lead or purchase.

Step 4: Create the Google Ads Conversion Tag in GTM

In GTM:

Open Tags.
Select New.
Name the tag clearly, such as Google Ads Conversion – Website Lead.
Select Tag Configuration.
Select Google Ads Conversion Tracking.
Enter the Conversion ID.
Enter the Conversion Label.
Add the conversion value if applicable.
Add the currency code if a value is supplied.
Add the unique transaction ID for ecommerce.
Select the confirmed conversion trigger.
Save the tag.

For a purchase, the value, currency and transaction ID should normally come from the website’s data layer rather than being typed as fixed values.

Step 5: Select a Dependable Trigger

Suitable triggers include:

A unique confirmation-page view.
A successful form-submission data-layer event.
A booking-confirmed event.
A completed purchase event.
A successful account-registration event.

Avoid relying solely on a submit-button click. The user may click the button when required fields are missing, the form may fail, or the CRM may reject the submission.

Where a thank-you page is used, make sure:

It is unique to the conversion.
It cannot be reached through ordinary navigation.
Refreshes do not create repeat conversions where this would be inappropriate.
Query parameters do not break the URL condition.
The trigger does not match unrelated pages.

Step 6: Add Dynamic Ecommerce Information

For purchases, create GTM variables for:

Transaction value.
Currency.
Transaction ID.

Map these variables to the Google Ads conversion tag.

A unique transaction ID helps Google Ads deduplicate repeated purchase events. It should come from the ecommerce or payment system and remain consistent for the same order.

Step 7: Check the Google Tag and Conversion Linker

The relevant Google destination or Google tag must be configured correctly in the container.

Existing legacy GTM implementations may also use a Conversion Linker tag on all pages. The Conversion Linker helps preserve advertising click information in first-party cookies for conversion measurement.

Do not remove a working Conversion Linker simply because the container has been offered the unified upgrade. Review Google’s proposed optimisation and Tag Diagnostics first.

Step 8: Configure Enhanced Conversions

Where enhanced conversions are appropriate:

Enable enhanced conversions for the conversion action in Google Ads.
Identify where consented email or telephone data becomes available.
Create a user-provided data configuration in GTM.
Map the relevant data-layer or website variables.
Ensure the data is correctly normalised.
Fire the user-provided data event when the information is available.
Test the setup using Tag Assistant and Google Ads diagnostics.

Do not send ordinary personal information as GA4 parameters. Enhanced conversions use a specific controlled process for matching first-party customer data.

Step 9: Test the Conversion

Use GTM Preview and Tag Assistant to complete a test conversion.

Confirm that:

The tag does not fire before successful completion.
The tag fires once after successful completion.
The Conversion ID is correct.
The Conversion Label is correct.
The value and currency are correct.
The transaction ID is present and unique.
Consent settings are respected.
Enhanced conversion data is detected where enabled.
Reloading the confirmation page does not inflate results.
The Google Ads conversion status begins receiving activity.

Step 10: Publish and Monitor

Publish the container with a clear version name and description.

Continue monitoring:

Google Ads Tag Diagnostics.
Conversion action status.
Conversion volumes.
Values and revenue.
Differences between website records and Google Ads.
Duplicate or unexplained conversions.
Primary and secondary goal settings.

Our Google Ads conversion tracking guide explains how conversion actions, primary goals and bidding signals should be structured.

How to Set Up Google Ads Remarketing Through GTM

Google Ads refers to remarketing audiences as data segments. These allow advertisers to reach people who previously visited or interacted with the website.

There are two main forms:

Standard remarketing: Creates audiences using page visits and general website activity.
Dynamic remarketing: Sends product, service or listing identifiers that can be matched with a feed to personalise advertising.

A standard implementation may now be handled through the Google tag and its Google Ads destination. Older or unoptimised GTM containers may use a dedicated Google Ads Remarketing tag.

Do not install both methods without checking whether this duplicates the same destination activity.

Step 1: Configure the Audience Source in Google Ads

In Google Ads:

Open Tools.
Open Shared library.
Select Audience manager.
Select Audience sources.
Locate the Google tag card.
Select Set up tag, or edit the existing source.
Choose the data the source should collect.

For ordinary remarketing, select the option to collect standard website data.

For dynamic remarketing, select the option to collect specific attributes or parameters and choose the relevant business type.

Business types can include:

Retail.
Travel.
Hotels and rentals.
Flights.
Property.
Jobs.
Local deals.
Education.
Custom.

The exact parameters required depend on the business type.

Step 2: Connect Google Ads as a Destination

In the unified Google tag or optimised GTM interface, confirm that the correct Google Ads account is connected as a destination.

The destination ID normally begins with AW-.

If the website-wide Google tag is correctly connected to Google Ads and the audience source collects standard data, it may already provide the website coverage required for general remarketing. Do not automatically add another all-pages remarketing tag.

Step 3: Use a Dedicated Remarketing Tag Where Required

If the container still uses the traditional GTM setup and Google Ads instructions provide a remarketing configuration:

Open Tags in GTM.
Select New.
Name the tag Google Ads Remarketing – All Pages.
Select Google Ads Remarketing.
Enter the Google Ads Conversion ID.
Leave custom parameters empty for ordinary remarketing.
Select the appropriate All Pages trigger.
Save the tag.

Before publishing, check whether the same AW- destination is already activated through an all-pages Google tag. If it is, adding a separate remarketing tag may be unnecessary.

Step 4: Configure Consent

Remarketing is an advertising use case and should respect the relevant consent parameters, including:

ad_storage
ad_user_data
ad_personalization

The consent platform should establish the default state before the advertising destination processes the page and update the state after the visitor makes a choice.

Audience size will be lower where users do not grant the required consent. This is expected and should not be bypassed by firing remarketing tags before the consent state is known.

Step 5: Create Website Visitor Segments

After the source is active, create useful audience segments inside Audience Manager.

Examples include:

All website visitors.
Visitors to a service category.
Product viewers.
Basket abandoners.
Checkout starters who did not purchase.
Lead-form visitors who did not submit.
Existing customers.
Visitors within a specific membership duration.

Audience exclusions are as important as inclusions. For example, a lead-generation campaign may exclude recent converters, while an ecommerce campaign may treat existing customers differently from new prospects.

Step 6: Test Standard Remarketing

Use Tag Assistant and Audience Source diagnostics to confirm:

The correct Google Ads destination receives page activity.
The destination is not being loaded twice.
Page URLs are available for segment rules.
Consent settings are respected.
Audience source activity appears in Google Ads.
Segment sizes begin populating.

Audiences require enough eligible users before they can serve. A technically correct tag does not guarantee that every segment will immediately meet Google’s minimum size requirements.

How to Set Up Dynamic Remarketing Through GTM

Dynamic remarketing requires more than an all-pages Google tag.

The website must send information about the products, services, destinations, properties or listings viewed by the visitor. This activity must correspond with identifiers in an associated feed.

A retail implementation may send events for:

Product views.
Search results.
Category views.
Basket additions.
Checkout.
Purchases.

The event data may include:

Product or item ID.
Page type.
Product value.
Business type.
Feed identifier.
Transaction information.

The product IDs sent from the website must match the IDs in Merchant Center or the relevant business-data feed. Even a small formatting difference can prevent Google from matching the website activity with the correct advert content.

A typical setup includes:

Configure dynamic remarketing in the Google Ads audience source.
Select the appropriate business type.
Create or connect the required product or business-data feed.
Ask the website to push the relevant event data into the data layer.
Create GTM data-layer variables for the required parameters.
Configure the Google Ads remarketing event or relevant Google destination event.
Trigger it only on the appropriate product, basket or purchase event.
Preview each stage of the customer journey.
Check that product IDs match the feed.
Review Google Ads diagnostics for missing or invalid parameters.

Dynamic remarketing should not be confused with GA4 audience sharing. GA4 audiences can be linked with Google Ads, but Google’s current guidance states that GA4 web properties do not replace the dedicated Google Ads dynamic remarketing setup.

Should Google Ads Import Conversions From GA4?

Google Ads can import GA4 key events as conversion actions. This is convenient, especially when GA4 events are already implemented correctly.

However, for important Google Ads website conversions, we generally prefer native Google Ads conversion tracking.

A direct Google Ads conversion tag can provide:

More direct measurement.
Google Ads-specific settings.
Enhanced conversions.
Advertising attribution capabilities.
Faster availability of some conversion data.
Clearer separation between analytics reporting and bidding signals.

GA4 events remain valuable for analysing website behaviour and comparing acquisition channels. The same confirmed action can be sent to GA4 and Google Ads, provided the resulting conversion actions are managed carefully.

If a direct Google Ads conversion and a GA4-imported version of the same action are both present, do not normally set both as primary conversions for bidding. Doing so can duplicate the business outcome in the Conversions column and distort automated bidding.

A practical structure is:

Direct Google Ads conversion: primary.
Corresponding GA4-imported event: secondary or excluded from account-default goals.
GA4 event: retained for analytics and cross-channel reporting.

The correct arrangement depends on the account, attribution requirements and existing historical data.

Enhanced Conversions for Google Ads

Enhanced conversions supplement ordinary conversion tracking with consented first-party customer data, such as an email address or telephone number.

The data is normalised and securely hashed before being transmitted to Google. Google can use it to improve the matching of conversions with advertising interactions when ordinary browser identifiers are unavailable or incomplete.

Enhanced conversions can be configured through GTM using:

Automatic detection, where suitable.
CSS selectors or JavaScript variables.
Data-layer variables.
Custom JavaScript.
A structured user-provided data variable.

A deliberate data-layer implementation is normally preferable for complex websites because it gives the business greater control over which fields are collected and when they become available.

Enhanced conversions should only use data collected lawfully and for which the organisation has an appropriate legal basis. Sensitive personal information must not be transmitted.

See our complete guide to Google Ads enhanced conversions for the implementation options and privacy considerations.

Website Conversions Versus Offline Conversions

Google Tag Manager primarily measures activity occurring within the website or browser.

It can record that somebody submitted a form, called the business or purchased through the website. It cannot independently determine whether a lead later became qualified, attended an appointment, accepted a quotation or generated revenue inside a CRM.

These later outcomes require an offline or CRM-based conversion connection.

A lead-generation measurement system might record:

Website Lead.
Qualified Lead.
Sales Opportunity.
Customer.
Revenue.

The website lead can be recorded through GTM. The later stages are normally sent from the CRM using a native integration, Google Ads Data Manager, an automation platform or the Google Ads API.

Our offline conversion tracking guide explains how to connect advertising clicks with later lead quality, customers and revenue.

GTM and offline conversion tracking therefore solve different parts of the measurement problem:

GTM manages website-side collection.
The CRM records commercial progression.
An integration returns selected outcomes to Google Ads.
Google Ads uses the resulting data for reporting and bidding.

Consent Mode and UK GDPR Privacy Requirements

Google Tag Manager does not remove the need for lawful consent and privacy controls.

UK and European websites may need to obtain consent before accessing or storing non-essential advertising and analytics identifiers. The exact requirements depend on the organisation, data use, jurisdiction and applicable legal advice.

Google Consent Mode communicates a user’s consent choices to Google tags.

The current consent parameters include:

analytics_storage
ad_storage
ad_user_data
ad_personalization
functionality_storage
personalization_storage
security_storage

A Consent Management Platform should normally establish the default consent state before measurement tags are allowed to process the page. It should then update the state after the visitor makes a choice.

Consent Mode can operate in two broad configurations:

Basic Consent Mode: Google measurement tags are blocked until consent is granted.
Advanced Consent Mode: Google tags can load with denied consent and send restricted, cookieless signals where permitted by the implementation and Google’s controls.

Advanced Consent Mode does not remove the business’s legal responsibilities. A technical capability should not be treated as a substitute for assessing the applicable privacy requirements.

Follow Google’s current Consent Mode implementation guidance and ensure the configuration accurately reflects the choices presented by the website’s consent banner.

What Is Visual Tagging?

Visual tagging is a new feature being introduced within Google’s unified tagging platform.

Instead of manually creating selectors and triggers, an advertiser can navigate through the website and select an element or action to define an event. Google handles some of the underlying technical configuration.

The feature is initially available in beta for Google Ads purchase conversions and is expected to expand to more use cases.

Visual tagging may make straightforward event setup more accessible, but it should still be tested carefully.

A visual tool may identify that a button was clicked. It may not understand whether:

The form was successfully submitted.
The payment was approved.
The booking was confirmed.
The order value was correct.
The event had already been sent.
The action represented a commercially valuable conversion.

For important lead and revenue events, successful back-end confirmation or structured data-layer signals remain preferable to superficial click tracking.

Common Google Tag Manager Tracking Mistakes

Most serious tracking problems are caused by implementation and measurement design rather than the Tag Manager platform itself.

Counting Button Clicks as Completed Leads

A submit-button click can occur even when a form contains validation errors or fails to reach the CRM.

Use a confirmed success event, form callback, data-layer event or genuine thank-you page.

Tracking the Same Action More Than Once

Duplicates can arise when tracking is installed through:

Website code.
A WordPress plugin.
Google Tag Manager.
A GA4 import.
An advertising-platform plugin.
An ecommerce integration.

Map every event and installation method before adding another tag.

Treating Every Event as a Primary Conversion

Page views, button clicks, scrolls and form starts can be useful diagnostic events. They should not necessarily be used as bidding goals.

Google Ads automated bidding will optimise towards whatever actions are designated as primary. The Google Ads account therefore needs commercially meaningful conversion goals, not simply a large number of easily generated events.

Firing Purchases Without Transaction IDs

Without a unique order ID, a confirmation page refresh can produce duplicate purchases and inflated revenue.

Using Fixed Values for Unequal Transactions

An ecommerce purchase tag should receive the genuine order value. Lead-generation businesses may use estimated values, but those values should be based on qualification rates, close rates and commercial value rather than arbitrary numbers.

Ignoring Consent Sequencing

If consent defaults are established after GA4 or Google Ads tags have already fired, the implementation may not reflect the user’s actual choice.

Publishing Without Testing

Every GTM change should be previewed and tested before publication. The container version should include a clear name and description so it can be audited or restored later.

Sending Personal Information to GA4

Names, email addresses, telephone numbers and other personally identifiable information must not be sent as ordinary GA4 event parameters or included in page URLs.

Enhanced conversions use a specific controlled process. That does not make personal data suitable for general analytics events.

How to Test a GTM Implementation

Testing should cover both technical activation and reporting outcomes.

Useful tools include:

GTM Preview mode.
Google Tag Assistant.
GA4 DebugView.
Google Ads Tag Diagnostics.
Browser developer tools.
Network-request inspection.
Consent Management Platform diagnostics.
CRM and ecommerce transaction records.

A practical test should confirm:

The correct container loads once.
Consent defaults are applied before measurement.
Consent updates reflect the selected choice.
The Google destination settings load correctly.
GA4 receives the expected event name and parameters.
Google Ads receives the correct conversion ID and label.
Enhanced conversion data is detected where applicable.
Values and currencies are correct.
Transaction IDs are unique.
Failed forms do not produce conversions.
Successful forms do produce conversions.
Duplicate events are not generated.
Cross-domain journeys retain the required attribution.
Events appear in the relevant platform diagnostics.
Published results reconcile with the underlying website, CRM or sales system.

Testing one successful transaction is not sufficient. Test refreshes, failed submissions, declined payments, returning visitors, different consent choices, mobile devices and relevant browser restrictions.

A Recommended Measurement Architecture

A strong implementation separates behavioural analytics from advertising optimisation and commercial outcomes.

For Lead-Generation Websites

Use GTM to record:

Page and landing-page activity.
Confirmed form submissions.
Appointment bookings.
Relevant telephone calls.
GA4 engagement events.
Google Ads website conversions.
Enhanced conversion data.

Use the CRM to record:

Lead source and campaign details.
Click identifiers.
Qualified Lead status.
Sales Opportunities.
Customers.
Revenue.

Send the later commercial outcomes back to Google Ads using the simplest dependable integration available.

For Ecommerce Websites

Use GTM and the data layer to record:

Product views.
Add-to-basket actions.
Checkout starts.
Purchases.
Transaction values.
Currency.
Order IDs.
Product-level data.

Reconcile the recorded purchases and revenue against the ecommerce or payment platform. Where a payment completes outside the normal website journey, a server-side or post-purchase integration may be needed. Our guide to connecting Stripe with Google Analytics explains some of these additional considerations.

Does the New Unified Google Tag Replace Tracking Strategy?

No.

Google’s unification should make the technical infrastructure easier to deploy and manage. It does not decide:

Which actions represent genuine conversions.
Which conversions should guide bidding.
Whether a lead is qualified.
How much a conversion is worth.
Whether two tags are counting the same action.
Whether CRM outcomes should be imported.
Whether consent has been collected lawfully.
Whether platform-reported revenue matches actual sales.

The strongest measurement systems begin with the business outcome and work backwards.

For an ecommerce business, that may be completed revenue, margin or new-customer value. For a lead-generation business, it may be Qualified Leads, Sales Opportunities and customers rather than every submitted form.

Tag Manager is the implementation layer. It cannot compensate for weak conversion definitions or unreliable commercial data.

Google Tag Manager Audit Checklist

A structured audit should review:

GTM ownership and administrator access.
Container installation and duplication.
Published and unpublished workspaces.
Google destination connections.
GA4 stream IDs.
Google Ads conversion IDs and labels.
Triggers and firing conditions.
Data-layer structure.
Ecommerce parameters.
Transaction IDs.
Conversion values and currency.
Primary and secondary Google Ads conversions.
GA4-imported conversions.
Enhanced conversion coverage.
Consent defaults and updates.
Cross-domain configuration.
Internal and developer traffic.
Referral exclusions or unwanted referrals.
Personally identifiable information.
Custom HTML tags.
Obsolete tags and unused variables.
Preview and diagnostic errors.
Website, GA4, Google Ads and CRM reconciliation.
Container naming, documentation and version history.

Removing obsolete or duplicated tracking can be just as important as adding new tags.

Frequently Asked Questions

Have Google Analytics and Google Ads Tags Been Merged?

Not exactly.

Google is unifying the Google tag and Google Tag Manager infrastructure. A Google tag can send data to destinations such as GA4 and Google Ads, but those products remain separate and retain their own measurement settings, events and conversion requirements.

Do I Need to Replace My Existing Google Tag Script?

Usually, no.

Google says existing Google tags will retain their current in-page behaviour. Existing GTM containers may receive an optional optimisation process, but proposed changes must be reviewed and published by an authorised user.

Audit and test the existing implementation before changing or removing any scripts.

Is Google Tag Manager Still Needed?

For very simple measurement, a directly installed Google tag may be sufficient.

GTM remains valuable for custom events, ecommerce, enhanced conversions, multiple platforms, consent management, debugging, version control and more advanced measurement requirements. The new architecture effectively makes Tag Manager capabilities available more broadly.

Will Google Automatically Change an Existing GTM Container?

Google says existing GTM container optimisation will be optional. Users will be able to initiate the optimisation process and preview proposed changes before publishing them.

Do not publish an upgrade without checking the proposed settings, destinations and event behaviour.

Can the Same Event Be Sent to GA4 and Google Ads?

Yes. A confirmed lead or purchase can be sent to both destinations.

However, the GA4 event and Google Ads conversion should be configured for their respective purposes. Avoid counting both a direct Google Ads conversion and an imported copy of the same GA4 event as primary bidding conversions.

Do I Need a Separate Google Ads Remarketing Tag?

Not always.

If the website-wide Google tag is connected to the correct Google Ads destination and the audience source is configured for standard website data, the shared Google tag may already provide the required general remarketing coverage.

A separate legacy remarketing tag may still appear in existing GTM implementations. Check the destination, audience source and Tag Diagnostics before adding or removing one.

Does GTM Improve Google Ads Performance?

GTM does not improve campaigns by itself.

It can improve the accuracy, completeness and maintainability of conversion tracking. Better conversion data can then support more reliable reporting, budget allocation and automated bidding.

Does GTM Track Offline Sales?

Not by itself.

GTM measures website-side activity. Later CRM, telephone, in-store or payment outcomes require an appropriate offline conversion connection, native CRM integration, Data Manager connection, automation or API implementation.

Should I Remove My Existing Google Tags?

No. Do not remove or combine tags solely because Google has announced the new unified architecture.

First audit the current implementation, identify every destination and conversion action, review Google’s proposed container optimisation and test the resulting setup before publishing changes.

Conclusion

Google Tag Manager provides a central and flexible way to implement Google Analytics, Google Ads conversion tracking, remarketing, enhanced conversions, Consent Mode and other marketing technologies.

Google’s decision to unify the Google tag and Google Tag Manager should simplify the tagging architecture. Basic Google tag users will gain access to Tag Manager features, while existing GTM users will be able to optimise their containers for more centralised settings and potentially faster data transmission.

The update does not turn Google Ads and Google Analytics into one measurement product. GA4 remains the behavioural analytics destination, while Google Ads remains the advertising measurement and optimisation destination.

Existing scripts do not normally need to be replaced immediately. Businesses should audit their current implementation, review any optional container optimisation and test all destination, event, conversion, remarketing and consent behaviour before publishing changes.

The best implementation uses the shared infrastructure without confusing the roles of each platform.

It sends behavioural events to GA4, accurate advertising conversions to Google Ads, consent signals to the relevant Google services and later commercial outcomes from the CRM or sales system. It also prevents duplication, protects personal information and tests every important event against the source of truth.

When these components are designed correctly, Google Tag Manager becomes more than a convenient way to install scripts. It becomes the website measurement layer connecting advertising investment with user behaviour, audiences, leads, customers and revenue.