Enhanced conversions is a measurement feature in Google Ads that recovers conversions that ordinary tracking loses. When someone buys a product or fills out a form, the advertiser's website already holds identifying details the customer typed in, such as an email address or phone number. Enhanced conversions takes that first-party data, scrambles it with a one-way cryptographic function, and sends the scrambled version to Google. Google compares it against the same details held for signed-in account holders. When the two match, the conversion is tied back to the ad click or view that produced it, even when a browser cookie or click identifier went missing. The feature exists because the signals that measurement historically relied on, principally third-party cookies and device identifiers, have been degraded by browser restrictions, mobile operating system controls, and privacy law.

How the matching works

The mechanism rests on hashing, a mathematical operation that converts input text into a fixed-length string of characters. Google uses SHA256, a one-way algorithm, meaning the output cannot be reversed to recover the original email or number. The same input always produces the same output, which is the property that makes matching possible: two parties who independently hash the same email address arrive at the identical string without either revealing the address itself.

Before hashing, the data has to be normalized, because inconsistent formatting is the single most common cause of a collapsed match rate. Google's rules require removing leading and trailing whitespace, converting text to lowercase, and formatting phone numbers to the E.164 international standard with a country code. A quirk applies to Google's own mail domains: periods before the domain name in gmail.com and googlemail.com addresses are stripped, since Google treats them as insignificant. Only after normalization is the value passed through SHA256 and rendered as a hexadecimal string.

The hashed string travels to Google, which holds hashed identifiers for its logged-in users. A comparison runs across the two sets. Where a hash from the advertiser matches a hash from a signed-in Google account, the system attributes the conversion to the ad event associated with that account, whether a click or a video view. The advertiser never learns which specific users matched, and Google states it reports only privacy-safe, aggregated conversions. The raw customer data is not shared in either direction.

Where it sits in the flow

Enhanced conversions is a supplement, not a replacement. It layers on top of existing conversion tracking rather than substituting for it. Three implementation routes have historically existed. The Google tag, the base measurement snippet on a site, can capture identifiers from the conversion page directly. Google Tag Manager offers the same capture through a container interface. And the Google Ads API allows hashed data to be sent server to server, which carries a distinct advantage: first-party data can be transmitted up to 24 hours after the conversion event, letting an advertiser pull identifiers from a customer database or CRM rather than the live web page.

Two product variants developed along parallel tracks. Enhanced conversions for web measured on-site actions, such as purchases and form completions, capturing identifiers at the moment of conversion. Enhanced conversions for leads handled the offline case, where a form submission on the site is only the start and the actual sale closes later through a sales team. For leads, the advertiser uploads a lead identifier, typically the email field from the form, so that when the deal converts in the CRM, Google can match the closed lead back to the originating click. Google's documentation has stated that enhanced conversions for leads generally delivers higher accuracy than the web variant, because the lead identifier is a deliberate, controlled upload rather than an opportunistic page capture.

Origin and evolution

Google introduced enhanced conversions in May 2021, positioning it as a first-party answer to the erosion of third-party tracking. Enhanced conversions for leads followed in 2022, extending the same hashing approach from on-site measurement to offline CRM-based lead tracking. That split between two products, one for on-site purchases and form completions, the other for offline leads, then persisted for several years.

Google has cited performance figures to justify adoption. Early studies reported a median conversion-rate increase of 5 percent for Search and 17 percent on YouTube. A separate figure Google has quoted puts the average lift at 11 percent for Search conversions compared with standard conversion imports. These numbers describe measured conversions recovered rather than incremental sales generated, a distinction that matters for interpreting them: the feature surfaces activity that occurred but went unattributed, it does not by itself create new demand.

The most significant structural change arrived in 2026. On April 10, 2026, Google announced that the two enhanced conversions products would collapse into a single on/off setting, a change Google Ads finally collapses enhanced conversions into a single toggle documented in detail. The consolidation unfolded in two phases. From April 2026, Google Ads began accepting user-provided data from website tags, Data Manager, and API connections simultaneously, removing the previous requirement to designate a single implementation method. Rather than routing signals through one pathway, the platform now ingests hashed data from all connected sources at once and reconciles them internally. From June 2026, the interface distinction between the web and leads variants disappeared entirely, and the method selection screen was removed.

A related enforcement deadline landed alongside it. As Google kills 3 enhanced conversion methods, replaces all with single toggle reported, offline conversion imports and enhanced conversions for leads uploads were migrated to the Data Manager API and blocked in the legacy Google Ads API from June 15, 2026. Developer tokens that had sent no request between January and June 2026 were not allowlisted for continued legacy access. The change fits a documented pattern across Google's measurement products toward fewer integration points, unified schemas, and centralized pipelines that handle complexity internally.

Why it matters for marketers

Enhanced conversions sits at the center of how automated bidding now functions. Conversion events are among the strongest signals that bidding algorithms use to optimize campaigns, and Smart Bidding allocates budget based on the conversions it can see. When measurement undercounts, bidding starves. By recovering conversions that cookie loss would otherwise hide, the feature feeds more complete data into those systems, which is why Google frames it as unlocking more powerful bidding rather than merely improving reports.

The broader context is signal loss. Browser restrictions, mobile operating system controls, and regulation have progressively removed the identifiers that measurement depended on. First-party data collected directly from customers is one of the few durable inputs left, and enhanced conversions is Google's primary route for putting that data to work inside Google Ads. The feature also connects to targeting: the hashed data used for matching can enrich Customer Match audiences, extending its value beyond measurement into audience building.

Limitations and criticism

The privacy framing that surrounds enhanced conversions is contested. Google describes the hashed data as sent in a privacy-safe way, but the Federal Trade Commission has directly challenged the premise that hashing protects anonymity. In a technology blog post on July 24, 2024, FTC staff wrote that hashes are not anonymous and can still be used to identify users. According to the FTC, all user identifiers carry the capability to identify and track people over time, and the opacity of an identifier cannot excuse improper use. The agency noted this reaffirmed a position it first took in 2012, pointing to enforcement cases including a 2022 action against BetterHelp, where the complaint alleged that a recipient could undo the hashing to reveal shared email addresses.

Practical constraints also apply. Match rates depend on customers being signed in to a Google account and on the advertiser capturing clean, complete identifiers, which not every conversion produces. Consent is a hard gate: both account-level and action-level activation require acceptance of Google's Data Processing Terms, and advertisers who decline cannot use the feature at all. In the European Economic Area, consent signals must accompany the data, adding a compliance layer that can suppress volume where users withhold permission. And because the reported lift figures describe recovered measured conversions rather than incremental outcomes, they cannot be read as a direct estimate of the advertising's causal effect.

Disambiguation

Enhanced conversions is frequently confused with adjacent measurement concepts.

Conversion tracking is the base layer: the standard tags that record a conversion happened. Enhanced conversions supplements that layer with hashed identifiers, it does not stand alone.

Consent Mode governs whether tags fire at all, adjusting behavior based on user consent choices and modeling conversions for users who decline. It operates on the consent question, not on identity matching.

Customer Match is an audience-targeting feature that uploads hashed customer lists to reach or exclude those users in campaigns. It shares the hashing mechanism but serves targeting rather than conversion measurement, though enhanced conversions data can feed it.

Conversions API, the cross-platform pattern standardized by the IAB Tech Lab as ECAPI 1.0 in 2026, is a server-side channel for sending events. Enhanced conversions is a Google-specific feature that can use an API path, whereas Conversions API describes the general server-to-server approach used across Meta, Microsoft, and others.

Recent developments

Beyond the 2026 toggle consolidation, Google has continued to build out the surrounding infrastructure. The launch of the Data Manager API centralized first-party data uploads, with the same SHA256 hashing and normalization requirements, and became the mandated path as legacy routes closed. In November 2025, Google Analytics refocused its user-provided data feature on advertising conversions, explicitly prioritizing enhanced conversions and Customer Match while removing reporting identity. More recently, Google introduced a Data Strength Uplift metric to quantify the contribution of first-party data in Google Ads, extending the same direction of travel toward measuring and centralizing advertiser-owned data rather than exposing integration complexity to advertisers.

Timeline

  • 2012 - FTC's then-Chief Technologist publishes a blog concluding that hashing does not make data anonymous, establishing the agency's long-held position.
  • May 2021 - Google introduces enhanced conversions in Google Ads.
  • 2022 - Enhanced conversions for leads launches, extending the feature to offline CRM-based lead tracking.
  • July 24, 2024 - FTC reaffirms in a technology blog post that hashed identifiers are not anonymous and remain capable of identifying users.
  • November 5, 2025 - Google Analytics refocuses its user-provided data feature on advertising conversions, prioritizing enhanced conversions and Customer Match.
  • April 10, 2026 - Google announces the consolidation of enhanced conversions for web and leads into a single toggle; phase one accepts data from all sources simultaneously.
  • June 2026 - The interface distinction between web and leads variants is removed; method selection disappears.
  • June 15, 2026 - Offline conversions import and enhanced conversions for leads uploads migrate to the Data Manager API and are blocked in the legacy Google Ads API.

Summary

Who - Google operates the feature within Google Ads; advertisers implement it using first-party data collected from their own customers, with matching performed against Google's signed-in account holders.

What - A conversion measurement feature that supplements standard tracking tags by sending SHA256-hashed first-party customer data, such as email addresses and phone numbers, to Google for matching against logged-in users.

When - Introduced in May 2021, extended to leads in 2022, and consolidated into a single toggle across April and June 2026, with legacy upload paths blocked from June 15, 2026.

Where - Inside Google Ads and its connected infrastructure, including the Google tag, Google Tag Manager, the Google Ads API, and the Data Manager API, affecting campaigns globally with additional consent requirements in the European Economic Area.

Why - Third-party cookies and device identifiers have been degraded by browser restrictions, mobile controls, and privacy regulation, leaving first-party data as one of the few durable inputs for accurate conversion measurement and the automated bidding that depends on it.