Half the Google Ads accounts I open in 2026 are still running tracking that was configured in 2023 and never touched again. That used to be survivable. This year it isn't, because Google shipped a cluster of changes that all push the same direction: first-party data, through modern pipes, with consent attached. Old setups don't throw errors when these land. They just report fewer conversions, and Smart Bidding quietly gets dumber.
Here's each change, who it hits, and exactly what to do.
| Setup from 2023 | What 2026 requires |
|---|---|
| Method picker per conversion action | One enhanced conversions toggle |
| UploadClickConversion via Ads API | Data Manager API uploads |
| A CMP that only shows buttons | ad_user_data actually granted |
| First click, linear, time decay | Data-driven or last click only |
What changed with enhanced conversions in June 2026?
Google collapsed enhanced conversions for web and enhanced conversions for leads into one on/off toggle, and the method picker (Google tag vs. GTM vs. API) is gone from the interface. Since April 2026, Google Ads accepts user-provided data from multiple paths at the same time: your website tag, Data Manager, and API connections. Google reconciles the hashed data on its side, so the same purchase arriving through two channels doesn't double-count. Search Engine Land and PPC Land both covered the rollout.
Who's affected: everyone using enhanced conversions. Existing setups migrated automatically if you'd accepted Google's customer data terms. No rebuild required.
The catch is what "on" actually means. The toggle turning green doesn't mean data is flowing. If your tag never captures an email or phone number on the thank-you page, the toggle sends nothing. I see this constantly: enhanced conversions enabled in 2024, checkout redesigned since, the CSS selector that scraped the email field long dead. No error anywhere. Just a slow match-rate bleed.
What to do:
- Open Google Ads, check the unified enhanced conversions setting at the account level. Confirm the Data Processing Terms are accepted.
- Check the conversion action's diagnostics and confirm user-provided data is actually being received, not just enabled.
- If you send data through more than one path (web tag plus a CRM upload, say), stop worrying about dedup. That's Google's job now, and multiple paths are a feature: when one gets blocked, the other still matches.
Did Google really block offline conversion uploads?
Mostly, yes. Per the Google Ads Developer Blog, starting June 15, 2026, offline conversion imports and enhanced conversions for leads uploads move to the Data Manager API. UploadClickConversion requests through the Google Ads API now fail for any developer token that hadn't already been uploading offline conversions between January and June 2026. New integrations can't start on the legacy path at all. Grandfathered tokens still work for now, but that's a bridge, not a destination.
Who's affected: anyone pushing CRM data into Google Ads. HubSpot and Salesforce pipelines, Zapier connectors, custom scripts a freelancer wrote in 2022. Lead-gen businesses feel this hardest, because offline conversions (the lead that became a sale two weeks later) are usually the only signal worth bidding on.
What to do:
- Inventory every path that uploads conversions from outside the browser: CRM integrations, automation tools, scheduled scripts.
- Ask each vendor one question: are you on the Data Manager API yet? If the answer is vague, plan your exit.
- For custom builds, migrate to the Data Manager API now and test with a real gclid plus hashed email before you shut the old path off.
- Visitor accepts banner — CMP records the choice and looks compliant
- Signals never passed — ad_user_data never flips to granted
- Tags send nothing — No conversion data and nothing modeled back
- Conversions vanish — PPC Land: one account lost 90% overnight
- Tag Assistant check — All four v2 signals flip on accept
Is Consent Mode v2 actually enforced for EEA and UK traffic now?
Yes. For EEA and UK traffic, Consent Mode v2 is a hard requirement for conversion measurement, not a best practice. It's been required since March 2024, but Google spent 2025 ratcheting: conversion modeling was cut off for non-compliant accounts, then personalization got restricted for accounts passing wrong or missing signals. By 2026 the enforcement is fully live, with policy warnings and potential serving restrictions for EU-targeted campaigns. There's no warning email before your numbers drop.
PPC Land documented an account in April 2026 that lost 90% of its measured conversions overnight. The consent banner looked fine. It collected choices, showed the right buttons. It just never passed the ad_user_data and ad_personalization signals to Google's tags. Cosmetically compliant, functionally broken. That's the trap: a CMP on the page is not the same as consent signals reaching Google, and the wiring between the two is where almost every failure lives.
What to do:
- Load your site with Tag Assistant. All four v2 signals, including
ad_user_dataandad_personalization, should flip from denied to granted when a visitor accepts. - Test the denied state too. With Consent Mode implemented properly, Google's tags send cookieless pings that feed conversion modeling. If your CMP hard-blocks gtag entirely on deny, you get nothing modeled back.
- Remember it's the visitor's location that matters, not where your business sits.
What happened to the old attribution models?
Nothing new in 2026, and that's the point: if you haven't looked since 2023, your reports changed meaning without you. Google removed first click, linear, time decay, and position-based attribution back in 2023, citing under 3% adoption. Only two models exist now: data-driven attribution and last click. Data-driven is the default for new conversion actions.
The 2026 implication is bigger than the model choice. Data-driven attribution is a machine-learned model trained on your account's conversion data, and every other change on this list feeds it or starves it. Broken enhanced conversions, a dead offline upload path, missing consent signals: each one shrinks the pool the model learns from, and Smart Bidding makes worse decisions on top of it. The attribution question in 2026 isn't "which model." It's whether the model has enough clean signal to be right.
What to do: set data-driven on anything with reasonable volume, keep last click as a comparison view, then spend your actual effort on the data feeding it.
Why does first-party server-side tracking absorb all of this?
Because every one of these changes rewards the same architecture: your own first-party pipeline feeding Google clean, consented data, instead of a pile of independent browser tags each hoping for the best.
If you haven't met the term: server-side tracking means your conversion events don't fire only from JavaScript in the visitor's browser. They also flow to a server container you own (Google Tag Manager's server-side version, running on your own subdomain, like track.yourstore.com), which cleans them up and forwards them to Google. The browser does less; a machine you control does more.
Map that against 2026's changes. The enhanced conversions consolidation explicitly rewards multiple simultaneous data paths, and a server container is exactly that: a reliable channel for hashed first-party data (email, phone) that keeps matching even when ad blockers and Safari's tracking prevention kill the browser tag, which they do daily. The offline-upload sunset is a pipe modernization, and a server-side setup gives you one owned pipe to update when Google moves endpoints, instead of six vendor integrations breaking on their own schedules. Consent Mode enforcement is easier to survive when consent is checked in one place, on your server, controlling exactly what gets forwarded per user choice, rather than trusting a dozen browser tags to each behave. And data-driven attribution simply works better fed more complete conversions, with cookies set from your own subdomain that outlive third-party ones.
One pipeline, your domain, your rules. Setups built this way shrugged off every change on this list; bolted-together ones lost something with each.
- Verify the unified EC toggle — On at account level, with the data processing terms accepted
- Read diagnostics, not the toggle — Confirm user-provided data is actually arriving, not just enabled
- Retest capture on the real page — A checkout redesign kills the selector that scraped the email, silently
- Move uploads to Data Manager — Legacy Ads API offline uploads blocked for new tokens since June 15, 2026
- Run a Tag Assistant consent check — All four v2 signals, in both the granted and the denied state
- Compare Ads to backend sales — A gap over 15-20% across the last 30 days means something above is broken
What exactly should I update this quarter?
The short version, in order:
- Verify the unified enhanced conversions toggle is on and diagnostics show user-provided data arriving.
- Confirm your email/phone capture still works on the actual conversion page. Redesigns kill selectors silently.
- List every offline conversion upload path and get each one onto the Data Manager API.
- Run a Tag Assistant consent check for EEA/UK traffic: all four v2 signals, both granted and denied states.
- Check attribution settings on each conversion action. Default to data-driven.
- Compare Google Ads conversions against your backend sales for the last 30 days. A gap over 15-20% means something above is already broken.
Frequently asked questions
Do I need to redo my enhanced conversions setup after the June 2026 change?
No. If you had enhanced conversions running and had accepted Google's customer data terms, you were migrated to the unified toggle automatically. Still open diagnostics and confirm user-provided data is being received; the migration preserved your config, not your data quality.
What replaces offline conversion imports in the Google Ads API?
The Data Manager API. As of June 15, 2026, new integrations can no longer start on the legacy Google Ads API endpoints for offline conversions or enhanced conversions for leads.
Will Google double-count conversions if I send data from both my website tag and an API?
No. Since April 2026, Google accepts user-provided data from website tags, Data Manager, and APIs simultaneously and deduplicates the hashed data on its side.
Is Consent Mode v2 required outside the EEA and UK?
Google's enforcement applies to EEA and UK traffic, wherever your business is based. Elsewhere it's not required by Google, though a clean consent setup helps with other privacy laws and keeps conversion modeling available.
Should I use data-driven or last click attribution in 2026?
Data-driven for any conversion action with reasonable volume; it's the default and it's what Smart Bidding is built around. Keep last click as a comparison view.
Does server-side tracking replace my Google Ads conversion tag?
It moves where the tag logic runs rather than eliminating it. Events route through a server container on your own subdomain, which forwards conversions and hashed first-party data to Google; a lightweight browser layer stays, and the server does the reliable delivery.
How do I know if my Consent Mode setup is actually working?
Test with Google Tag Assistant: the v2 signals (ad_user_data, ad_personalization) should show denied before consent and flip to granted after accepting. Then check the consent diagnostics inside Google Ads for warnings on your conversion actions.
