Google Ads Tracking 2026: What Changed in Consent Mode, Enhanced Conversions and GTM

If you manage Google Ads, you received a lot of emails from Google in 2026. Each change looks small on its own. Together, though, they shift where tracking errors happen and which settings really matter. This article sorts the most important changes of the year by what they mean for your conversion tracking. All details come from Google's own help pages and release notes, as of mid-October 2026.

If you want to understand the setup from the ground up, start with our guide on how to set up Google Ads conversions. This article is about what is new.

1. Enhanced conversions: one toggle instead of two variants

The biggest simplification of the year concerns enhanced conversions. According to the Google Ads help center, the change came in three steps:

• April 2026: Google Ads accepts user-provided data simultaneously from the website tag, Data Manager and API connections. You no longer have to choose a single path.
• June 2026: Enhanced conversions for web and for leads are combined into a single on/off setting. Choosing an implementation method is no longer needed. Anyone who had already accepted the customer data terms was migrated automatically.
• June 15, 2026: Offline conversion imports and uploads for enhanced conversions for leads only run through the Data Manager API. They are blocked in the Google Ads API.

What this means for you: For website conversions things get simpler. The actual work stays the same, though: at the moment of conversion, the Google tag needs the hashed user data such as email or phone number. If diagnostics in Google Ads report that hardly any user data arrives, the new toggle will not help either.

If you send leads from your CRM back to Google Ads, you need to check whether your tool already uses the Data Manager API. That concerns offline conversions, a topic we cover with our sister product LeadMetrics.

2. Consent Mode becomes the single control for advertising data from GA4

The second big change is less visible but has more consequences. Until mid-2026, two places in Google Analytics governed whether advertising identifiers were collected: the Google Signals setting and the Consent Mode settings. According to the Google Analytics help center, Google Consent Mode v2 has been the single control for this since around June 15, 2026.

Google Signals now only governs whether Analytics data is linked to signed-in users for behavioral reporting. For data that flows to Google Ads through a linked property, the settings in Google Ads apply.

Google has announced two further steps, but has not dated them yet:

• ad_personalization is to exclusively control whether linked data is used for personalization in Google Ads.
• Automatically collected IP addresses are to be sent encrypted to the linked Google Ads account.

What this means for you: If you relied on "Google Signals off" to hold back advertising data, that safety net is gone. What matters now is that your cookie banner sets the Consent Mode default to "denied" and only sends the update after active consent. A banner that stores consent but never informs the Google tag costs you conversions. A default of "granted" is a data protection problem in the EEA.

3. The Google tag gateway is generally available

The Google tag gateway for advertisers serves Google tags through your own domain. According to the Tag Manager release notes it rolled out step by step in 2026:

• January 5: Google Cloud in beta with a one-click workflow
• January 29: Akamai
• May 14: Akamai and Fastly with automatically created routing rules
• June 1: Google Cloud generally available
• June 3: Amazon CloudFront via a guided flow in Tag Assistant

What this means for you: Google now offers itself what server-side vendors used to sell as a first-party proxy. Requests through your own domain are slowed down less often by ad blockers. The gateway does not change the consent requirement, though. Consent signals are evaluated exactly as before. And you need access to a CDN or cloud infrastructure, which many smaller websites on site builders do not have.

4. Google Ads collects more website events automatically

On February 4, according to the release notes, Google introduced broader collection of website event data by Google Ads with less manual setup. Google itself points out that you may see more network requests to Google domains as a result.

What this means for you: More automatically collected events are no substitute for clearly defined conversion actions. Check which actions count as primary in your account so that Smart Bidding optimizes for what really is a lead or purchase for you. And remember that these additional requests are subject to your consent settings too.

5. Tag Manager has changed noticeably

For everyone working with Google Tag Manager, a few release notes were particularly relevant in 2026:

• July 9, container restrictions: A container's behavior now depends on its ID, not on how it is loaded. GTM containers are unrestricted, containers with a G- or AW- ID only run Google-provided tags and variables. Google emailed affected admins.
• June 22, server-to-server conversions: When a gclid is present, Google joins server-side data with browser signals such as cookies to attribute conversions that were previously undercounted.
• September 17, AI summaries: When publishing, Tag Manager suggests the version name and description automatically.
• October 8, gtag('config') standardization: All gtm.js snippets now initialize when the container loads, regardless of gtag('config') commands. Config commands appear in the data layer as gtag.config events. Google explicitly warns that wildcard custom event triggers may fire unexpectedly as a result.
• October 12, direct sending: Containers can send data directly to Google measurement products without additionally loading gtag.js. Settings and diagnostics are then attached to so-called destination tags in the container.

What this means for you: The October 8 change has the most potential for errors. If you built triggers on "all custom events" or with regex on event names, check in preview mode now whether tags suddenly fire more often than intended. Duplicate conversions are the typical result.

What the changes show together

Google makes individual things simpler, such as the toggle for enhanced conversions. At the same time the overall system does not get smaller: more automatic events, new loading paths, new container rules and, with the tag gateway, another infrastructure option. If you use Tag Manager heavily and have a team for it, you get more possibilities. If you only want to measure cleanly whether ads lead to leads and purchases, you have to track more changes than you would like.

Three things remain equally important regardless of all changes:

1. Consent first: default "denied", update only after active consent, and a banner that actually talks to the Google tag.
2. User data at the right moment: enhanced conversions only work if email or phone number is available at the conversion event.
3. One source per conversion: no parallel counting via Ads tag and GA4 import.

How LeadSignal handles this

LeadSignal connects Google Ads in the browser via the Google tag. As soon as a Google Ads integration is set up, the script sets the Consent Mode defaults to "denied" and sends an update after consent in the built-in cookie banner. The advertising signals follow the Marketing category, analytics_storage follows the Statistics category. LeadSignal detects form fields for email, phone and name automatically and passes them as user data for enhanced conversions to the Google tag with conversion events.

You do not need a Tag Manager container for this, and the same setup also serves Meta, LinkedIn and TikTok. The page on the Google Ads integration shows what that looks like in practice.