Prooflytics
Platform10 min read

Enhanced Conversions for Google Ads: How First-Party Tracking Restores Attribution

Third-party cookie degradation causes Google Ads to undercount conversions, inflating CPL and misleading Smart Bidding. Enhanced Conversions replaces cookie-based tracking with hashed first-party signals from your own domain. Here is how it works and the four components you need to configure.

Data tracking and analytics code representing first-party conversion measurement

Enhanced Conversions for Google Ads: How First-Party Tracking Restores Attribution

When Google Ads stops seeing conversions that are actually happening, CPL rises, Smart Bidding misoptimizes, and ROAS reporting falls apart. The cause is almost always missing or broken first-party conversion tracking. Enhanced Conversions is Google's mechanism for restoring attribution accuracy when third-party cookies are blocked or unavailable: it replaces the cookie-dependent signal with a hashed identifier (email or phone number) that Google matches against logged-in accounts. This works even when ITP, ad blockers, or cookie deprecation has broken the standard conversion tag.

Key takeaways

  1. Enhanced Conversions recovers up to 25% of conversions lost to cookie blocking, ITP, and cross-device gaps -- restoring accurate CPL and ROAS without requiring consent for the match itself.
  2. The mechanism: a hashed email or phone number collected at conversion is sent to Google Ads, which matches it against logged-in Google accounts and assigns credit to the original click (gclid).
  3. Four components are required: Google Ads tag + Conversion Linker on the site, Enhanced Conversions enabled in the Google Ads UI or GTM, hashed data passed from the conversion page, and Consent Mode v2 compatibility.
  4. Smart Bidding improves directly when Enhanced Conversions is enabled: the algorithm receives more accurate conversion signals and can optimize tROAS/tCPA against real performance rather than partial data.
  5. Without Enhanced Conversions on a site with significant Safari or iOS traffic (where ITP limits first-party cookies to 7 days), Google Ads sees a systematically lower conversion rate than actually occurs -- leading to bids that undervalue the channel.

Why standard Google Ads conversion tracking loses data

Google Click ID (gclid): a unique identifier appended to the landing page URL when a user clicks a Google ad. Standard conversion tracking reads the gclid from a first-party cookie set by the Google Ads tag and attributes the subsequent conversion to the originating click.

The failure modes:

  • ITP (Intelligent Tracking Prevention) in Safari caps the lifespan of first-party cookies set by JavaScript to 7 days. A user who clicks an ad and converts after 7 days on Safari: no attribution.
  • Cookie blocking in Firefox (Enhanced Tracking Protection) and other browsers blocks the Google tag from setting the gclid cookie entirely in some configurations.
  • Cross-device journeys: a user clicks an ad on mobile, converts on desktop. The gclid cookie does not transfer across devices. No attribution.
  • Incognito mode: cookies cleared at session end. Any conversion that happens after reopening the browser is unattributed.

The net effect: Google Ads sees fewer conversions than actually occurred. CPL appears higher than reality. Smart Bidding receives a noisy, incomplete signal. Budget allocation decisions are made on partial data.

How Enhanced Conversions works

Enhanced Conversions: a Google Ads feature that supplements standard cookie-based conversion tracking with hashed first-party user data collected at the point of conversion.

The mechanism:

  1. User clicks a Google ad -- URL receives a gclid (Google Click ID)
  2. User reaches the conversion page (form submission, checkout, registration)
  3. The conversion page collects user-provided data (email address, phone number)
  4. The data is hashed using SHA-256 before being sent -- Google never receives the raw PII
  5. Google matches the hash against its logged-in user database
  6. If a match is found, Google attributes the conversion to the gclid from the original click

This recovers conversions that were lost in steps where the gclid cookie was unavailable: cross-device journeys, ITP-capped sessions, and incognito completions all become attributable as long as the user is logged in to a Google account (Gmail, YouTube, Android).

The ICP problem: CPL rising without a real performance decline

The operational problem this creates for performance marketing leads: Google Ads CPL increases quarter-over-quarter without a corresponding change in budget, bids, or campaign structure. The team investigates quality score, landing pages, and audience overlap. Nothing explains the increase. The actual cause is attribution degradation as Safari's market share grows and ITP becomes more aggressive.

If a site has 35-50% Safari traffic (typical for B2C consumer brands), a significant share of conversions on those sessions are invisible to Google Ads. The CPL increase is not a campaign problem -- it is a measurement problem. Enhanced Conversions is the fix.

By the Enhanced Conversions technical specification documented in the Prooflytics knowledge base (sourcing Google Ads first-party tracking documentation), the typical recovery rate for sites with significant ITP exposure is 15-25% of previously unattributed conversions. For accounts spending $20,000+ per month on Google Ads with heavy Safari traffic, this represents a material difference in measured ROAS and CPL.

Prooflytics surfaces CPL anomalies in the daily briefing. When CPL rises without a corresponding change in impression share or click quality, the briefing flags Enhanced Conversions status as a diagnostic checkpoint: "Your CPL rose 30% -- verify that Enhanced Conversions and the Conversion Linker are configured and firing correctly."

Prooflytics

Stop stitching platform exports together

Every channel in one brief — plus the memory of what each one actually drove.

14 days free · no credit card

The four required components

Enhanced Conversions requires four components to be configured correctly. Missing any one of them silently breaks the attribution recovery:

Component 1: Google Ads tag with Conversion Linker

The Google Ads global site tag must be present on every page of the site, not just conversion pages. The Conversion Linker tag in GTM (or the linker parameter in the gtag.js implementation) writes the gclid to a first-party cookie and stores it in localStorage as a fallback. Without the Conversion Linker, the gclid is not persisted and no attribution is possible regardless of Enhanced Conversions status.

Verification: in GTM, check that a Conversion Linker tag fires on All Pages with no exceptions. In Google Ads, check the Tag Diagnostics report for Conversion Linker status.

Component 2: Enhanced Conversions enabled in Google Ads

Navigate to Google Ads > Tools > Conversions > [Conversion Action] > Edit settings > Enhanced conversions. Enable the feature and select the implementation method: automatic (recommended for basic setups), manual (GTM or code) for sites where the conversion form sends data server-side or in a non-standard structure.

Enhanced Conversions must be enabled at the conversion action level, not just at the account level. An account-level setting exists but does not automatically apply to all conversion actions.

Component 3: Hashed data from the conversion page

The conversion tag must receive hashed email or phone data at the moment of conversion. This can be implemented three ways:

  • GTM Auto-collection: GTM scans the page at conversion for form fields containing email-like strings and hashes them automatically. Works for most standard HTML forms without code changes.
  • Manual data layer push: the page fires a dataLayer event with email/phone data at conversion time; GTM reads the variable and hashes it before sending.
  • Enhanced Conversions API (server-side): conversion data with hashed identifiers is sent directly from the server to the Google Ads Conversion Measurement API. Most accurate, requires server-side implementation.

Verification: in the Tag Assistant Chrome extension, check the Enhanced Conversions event for a user_data object with SHA-256 hashed email field.

Component 4: Consent Mode v2 compatibility

Enhanced Conversions requires Consent Mode v2 to be configured if the site collects consent signals (GDPR scope, TCF v2 CMP). Consent Mode v2 introduces two new consent signals: ad_user_data (consent to send user data to Google for advertising) and ad_personalization (consent for personalized ads).

If ad_user_data consent is denied, Enhanced Conversions does not send hashed data for that user. Google's modeling (Conversion Modeling) fills in estimated conversions for non-consenting users based on aggregate patterns, but Enhanced Conversions precise attribution only applies to consented users.

For sites with significant EU traffic, Consent Mode v2 with a TCF v2-compatible CMP is a prerequisite for Enhanced Conversions to function correctly in GDPR scope.

01. Implementation checklist

In order from highest to lowest impact:

  1. Verify Conversion Linker is firing on all pages -- use Tag Assistant to confirm. This is the single most common gap: Enhanced Conversions is enabled but Conversion Linker is missing or excluded from certain page templates.

  2. Enable Enhanced Conversions on each conversion action -- do not rely on the account-level setting alone. Check each conversion action individually.

  3. Confirm hashed email data is being collected -- use Tag Assistant to verify user_data.sha256_email_address appears in the conversion event payload on a test form submission.

  4. Implement Consent Mode v2 if operating in GDPR jurisdictions -- verify that ad_user_data consent signal is being sent with the correct granted/denied value based on user choice.

  5. Check the Enhanced Conversions diagnostic in Google Ads -- 14 days after enabling, the Conversion Action detail page shows an "Enhanced Conversions" coverage percentage. A coverage above 30% indicates the feature is working; below 5% typically indicates a data collection problem.

02. Expected impact on reporting

After enabling Enhanced Conversions, Google Ads will show more conversions than before for the same campaign. This is not a performance improvement -- it is a measurement correction. CPL will decrease and ROAS will increase in the reporting UI because previously unattributed conversions are now being counted.

This has two practical implications:

Smart Bidding re-learning: Smart Bidding will enter a learning period (typically 7-14 days) as it recalibrates against the richer conversion signal. During this period, performance may fluctuate. Do not make bid strategy changes during the learning phase.

Historical benchmarking: comparing CPL or ROAS from before Enhanced Conversions to after is an apples-to-oranges comparison. The denominator changed. Establish new baselines after 30 days with Enhanced Conversions active rather than using pre-implementation data as the reference point.

Bottom line

  • Enhanced Conversions recovers conversions lost to ITP, cookie blocking, and cross-device journeys by matching hashed email or phone data against Google accounts rather than relying on cookies.
  • Four components are required: Conversion Linker on all pages, Enhanced Conversions enabled per conversion action, hashed data from the conversion form, and Consent Mode v2 for GDPR scope.
  • After enabling, expect a 15-25% increase in reported conversions for sites with significant Safari traffic -- this is a measurement correction, not a performance change. Reset CPL/ROAS baselines after 30 days.
  • Smart Bidding improves directly from the richer signal; expect a 7-14 day learning period after enabling.
  • If CPL is rising without an obvious campaign cause, checking Enhanced Conversions configuration is the first diagnostic step.
  • You can read independent reviews of Prooflytics on G2 and compare it to alternatives in the marketing analytics category.

Frequently asked questions

What is Enhanced Conversions in Google Ads?+

Enhanced Conversions is a Google Ads feature that supplements standard cookie-based conversion tracking with hashed first-party user data. When a user converts on your site and provides their email or phone number, that data is hashed (SHA-256) and sent to Google Ads. Google matches the hash against logged-in accounts to attribute the conversion to the original ad click. This recovers conversions that would otherwise be lost due to ITP, cookie blocking, or cross-device journeys.

Does Enhanced Conversions violate GDPR or privacy regulations?+

Enhanced Conversions sends only hashed (SHA-256) data -- not raw email addresses or phone numbers. The hash is irreversible: Google cannot recover the original email from the hash. For GDPR compliance, Enhanced Conversions must be used in conjunction with Consent Mode v2: users who deny ad_user_data consent do not have their hashed data sent. This is the Google-recommended configuration for EU traffic.

How much will Enhanced Conversions improve my ROAS reporting?+

The improvement depends on your traffic composition. Sites with high Safari and iOS traffic (35-50%+) typically see 15-25% more conversions reported after enabling Enhanced Conversions, as ITP has been blocking attribution for those sessions. Sites with primarily Chrome and Android traffic will see smaller improvements (5-10%) as ITP is less of a factor. B2C consumer brands typically see larger recoveries than B2B brands due to audience demographics.

Is Enhanced Conversions the same as server-side tracking?+

No. Enhanced Conversions with hashed data is a client-side implementation (via Google tag or GTM) that sends hashed user data. It improves attribution by providing a stable identifier but the tracking still originates from the browser. Enhanced Conversions API is a server-side variant where the conversion data is sent directly from your server to Google's API -- this is more accurate and resistant to ad blockers, but requires server-side implementation. Both are distinct from the Google Ads Conversion Linker, which is a prerequisite for either approach.

What happens to Smart Bidding when Enhanced Conversions is enabled?+

Smart Bidding receives a richer and more accurate conversion signal, which improves its ability to optimize bids toward your target ROAS or CPA. The algorithm will enter a learning period (7-14 days) while it recalibrates against the improved signal. After the learning period stabilizes, campaigns that were previously underbidding due to incomplete conversion data typically show improved bid efficiency. Avoid changing bid strategies or targets during the learning period.

Prooflytics

Stop stitching platform exports together

Every channel in one brief — plus the memory of what each one actually drove.

14 days free · no credit card

Continue reading

Attribution· 13 min read

First-Party Data Attribution for EU Fintech: The Practical Setup Guide

EU fintech companies lose 30-60% of attribution signal when users decline cookie consent. This guide covers the exact first-party stack to fix it: server-side UTM capture, email-hash identity stitching, and cookieless pixel mode - without touching GDPR compliance.

Platform· 7 min read

Google Ads Bid Strategy Testing in 2026 Requires CRM Data, Not Just Campaign Metrics

Google Ads has shifted bid strategy validation toward conversion value by time and first-party CRM data. Testing on campaign metrics alone now produces false positives. Here is the operational setup teams need before running any bid experiment in 2026.

Platform· 10 min read

Google Ads Bid Strategy Testing Now Requires CRM Data: What Changed in 2026

Google Ads changed bid strategy validation requirements in 2026, shifting from surface-level metrics like ROAS and CPC toward conversion value by time window and first-party CRM data integration. Testing a new bid strategy without CRM data now risks false positives and budget waste -- the model validates against aggregated campaign metrics that can be disconnected from actual customer lifetime value.

Attribution· 11 min read

Free Trial Attribution for SaaS: How to Track the Full Funnel from Ad Click to Paid Subscriber

Standard ad platform attribution only sees the trial signup. To know which channels actually drive paid subscribers - not just signups - you need to bridge the pixel session, the trial user record, and the Stripe upgrade event into one continuous identity chain.