Google Simplified Enhanced Conversions by Removing the Parts You Could Audit

Google Simplified Enhanced Conversions by Removing the Parts You Could Audit
One switch, every data source, and fewer places to check what is actually being sent.

Google announced this week that it's merging "enhanced conversions for web" and "enhanced conversions for leads" into a single unified feature. One toggle. On or off. Starting June 2026, the method selection screen disappears from your Google Ads account entirely.

The framing from Google is predictable: less setup friction, better conversion accuracy, more flexibility. On paper, consolidating two overlapping features into one sounds like reasonable housekeeping. Fewer menus, fewer places to misconfigure something. Fine.

But look past the interface cleanup and you'll find three distinct changes bundled together. Google removed the step where you chose your implementation method. It enabled automatic detection of user-provided data through your tags. And it started auto-migrating existing accounts without asking them to review the new behavior.

Three changes, presented as a simplification. From what I've seen with how these rollouts play out, the people who don't dig into the details are the ones who get surprised six months later.

Two Features, One Switch, Zero Method Selection

Previously, enhanced conversions for web and enhanced conversions for leads operated as separate features in Google Ads. You set them up independently, chose your implementation method (Google Tag, Tag Manager, Data Manager, or API), and could audit exactly how data flowed from your site to Google's attribution system.

The new version combines both into a single on/off switch. When June hits, you won't see a method selection screen at all. Instead, Google Ads simultaneously accepts user-provided data from all connected sources: website tags, Data Manager, and API integrations.

Google says this means "more accurate tracking with less setup friction." Which, sure. If you're running a straightforward e-commerce setup and you trust Google's handling of your customer data, this is probably a net positive.

The issue is that most performance advertisers didn't use the method selection screen because they wanted complexity. They used it because it gave them control over which data paths were active, and the ability to verify exactly what was being sent. That specificity made enhanced conversions auditable. You could point to the implementation and say: this is what we're sending, this is how, and we can demonstrate it to our compliance team.

It's roughly like replacing individual circuit breakers with a master switch. The lights still work. But when something trips, good luck figuring out which circuit caused it.

With simultaneous multi-source ingestion, that clarity gets muddier. Google pulls data from whatever sources happen to be connected, and your visibility into which source contributed to which conversion match becomes, honestly, pretty thin.

Auto-Detection Is Doing More Than Most Advertisers Realize

When you enable the new unified enhanced conversions, your Google tags can automatically detect user-provided data on your website. According to Google's documentation, the automatic detection method "inspects the page for strings that match a pattern for the configured data types."

Translation: the tag scans your pages for anything resembling an email address, phone number, or mailing address, hashes it, and sends it to Google for conversion matching.

This capability has been around for a while, but the consolidation changes how advertisers encounter it. Before, you actively chose automatic detection as your implementation method. Now it's part of the package when you flip the single toggle. The default path for most accounts leads through auto-detection whether or not the advertiser made a deliberate choice about it.

For e-commerce, this probably doesn't matter much. Your customers enter their email at checkout, the tag picks it up, conversions match better. Straightforward.

But if you run lead gen for financial services, healthcare, or any sector with data handling regulations, check what your tags are actually scanning. The auto-detection doesn't distinguish between a customer's email on a conversion page and a staff email address in your site footer. Any page where your Google tag fires becomes a potential data source, and the tag will grab whatever pattern-matches it finds.

This is the kind of thing that produces perfectly accurate conversion tracking while simultaneously creating a data pipeline your compliance team didn't approve of.

The toggle works. The question is whether you can explain to an auditor exactly how it works.

Existing Accounts Move Over Without a Review Step

If you previously accepted Google's customer data terms (and if you've been running enhanced conversions at all, you did), your account gets automatically migrated to the new unified setup. No confirmation screen. No review step. Google's documentation says "no action is required from existing users."

This is consistent with how Google has handled similar transitions recently. We wrote about how Consent Mode V2 enforcement quietly ate nine months of EU conversion data earlier this month. Same pattern: Google makes a change that's technically an improvement, frames it as a compliance or simplification update, and existing users get moved over by default.

The opt-out is still available at the conversion action level, which matters. But opting out requires you to know the change happened. And Google isn't blasting this through Ads Manager with a red banner. It's in the help docs. It's in trade press coverage. If you're a media buyer who doesn't read Search Engine Land, you might just notice your conversion numbers shift slightly and chalk it up to normal fluctuation.

The Offline Conversion Angle Most Coverage Missed

Separately but worth connecting: Google also announced improvements to offline conversion imports rolling out April through May 2026. Phase 1 enables attribution for some expired GCLIDs and historical clicks. Phase 2 makes it easier for manager accounts to import conversions on behalf of client accounts.

These are genuinely useful improvements. Expired GCLID recovery alone helps agencies and large accounts that historically lost conversion data due to timing gaps. Fewer EXPIRED_EVENT errors means more complete attribution, and that's real money for anyone running lead gen at scale.

But pair these with the enhanced conversions consolidation and a broader pattern emerges: Google is ingesting more conversion data, from more sources, through more automatic pathways, with fewer manual checkpoints in between. Each change is individually defensible. The cumulative direction is toward a system where Google handles the entire conversion pipeline and the advertiser's job is to flip a switch and trust the output.

By the end of 2026, I'd estimate fewer than 30% of active Google Ads accounts will maintain any manual documentation of their conversion implementation. The rest will be running on Google's defaults with no baseline for what "normal" looked like before the migration.

For most small and mid-size advertisers, that trade probably works. The data gets better. The setup gets easier. But I think it's worth being honest about what you're giving up when you accept the convenience: the ability to independently verify how your conversion data is being collected, processed, and attributed. That's not nothing, especially if you ever need to explain your data pipeline to someone outside your marketing team.

Three Things Worth Checking Before June

If you're running enhanced conversions or planning to, I'd spend about 30 minutes on this before the June migration flips your account over.

Audit your auto-detection scope. Open Google Tag Manager, navigate to your enhanced conversions configuration, and check what data types are set to automatic detection. If "automatic" is selected, verify the tag only fires on pages where customer data capture is intentional. Exclude staff pages, internal tools, and staging environments from the trigger. About 15 minutes with a GTM workspace audit.

Screenshot your current method configuration. Before June removes the method selection screen, document your setup for each conversion action. Note whether you're on Google Tag, GTM, Data Manager, or API. If your conversion numbers shift after migration, you'll want a reference point for diagnosing what changed. Without the old interface, reconstructing your previous setup from memory becomes a headache you don't need.

Review your data processing terms. If you accepted them when you first enabled enhanced conversions, you probably don't remember the scope. With the new system pulling data from all connected sources simultaneously, those terms now cover a broader data surface than when you originally agreed. Find them at Settings > Measurement > Enhanced Conversions. Ten minutes of reading. Worth it if you're in a regulated industry, and probably still worth it if you're not.

Simpler for Google, Convenient for You, and Those Aren't the Same Thing

Google's track record with "simplification" follows a pretty consistent arc at this point. Broad match replaces exact match as the default. Smart Bidding absorbs manual controls. Audience targeting becomes a suggestion the algorithm mostly ignores. And now enhanced conversions goes from a configurable implementation to a single toggle.

Each change individually makes the product easier to use. Stacked together, they make it progressively harder to see inside the machine. I don't think that's some coordinated conspiracy, honestly. It's just how platform incentives work. Google benefits when more data flows through its systems with less friction, so every product update trends in that direction.

I don't expect this change to break anyone's account. For most advertisers, the conversion matching probably gets marginally better. The risk isn't in the data quality today. It's in the slow erosion of your ability to verify data quality yourself, and that's a harder thing to notice. You won't feel it until the moment you actually need to audit something and realize the implementation you used to rely on has been quietly abstracted into a process you can only toggle on or off.