On June 15, 2026, Google made a single cookie setting — ad_storage — the sole gate for whether a phone call gets credited back to the Google Ads campaign that produced it. Decline that consent, and the call still happens; Google Ads just never sees it, and Smart Bidding keeps optimizing blind to it (Invoca, 2026; OneTrust, 2026).
What actually changed on June 15
Before the update, two settings had to both allow tracking for advertising data to reach a linked Google Ads account: Google Signals and the ad_storage parameter inside Consent Mode. Google eliminated that dual-control model. Now ad_storage alone decides whether advertising data — including call data — flows to Ads, while Google Signals narrows to an Analytics-only job: matching sessions to signed-in Google users inside GA4 (OneTrust, 2026). It applies to every Google Ads account linked to Analytics, not a specific industry or account size.
Why phone calls specifically break
Click-to-call buttons, call extensions, and call-only ads all work the same way behind the scenes: a browser session gets tagged by an ad click, and if a call happens afterward, that tag is what lets Google Ads connect the two. Ad_storage is exactly the setting that governs that tag. A visitor who taps "decline" on a cookie banner can still pick up the phone and call the business off that same ad — the call is real, the lead is real — but Google Ads now has no signal linking it back to the campaign, so it doesn't show up as a conversion anywhere in the account (Invoca, 2026).
Three changes landing at once
| Change | Effective date | What it means for call tracking |
|---|---|---|
| ad_storage becomes sole gate for ad data | June 15, 2026 | Consent declines now cut calls out of attribution, not just clicks |
| Granular Ads reporting window shrinks | June 1, 2026 | History caps at 37 months instead of running indefinitely |
| Call-only ads phased out | No new ones since Feb 2026; existing ads stop Feb 2027 | A call-generating ad format goes away entirely |
None of these three needed the others to be a problem on its own. Landing in the same year, they compound: less attribution, a shorter lookback window to notice the drop, and one less ad format built specifically to generate calls (Invoca, 2026).
Who gets hit hardest
Invoca's analysis flags multi-location businesses, franchises, and regulated industries — healthcare, financial services, insurance — as carrying the most compounded risk, and accounts still running the older Consent Mode v1 see the attribution loss immediately, with no transition window (Invoca, 2026). Picture an independent insurance agency running one Google Ads account across branches in Spokane and Coeur d'Alene: a share of visitors in each market decline cookies, call the office anyway, and buy a policy. Nothing about that transaction failed. But the dashboard now shows fewer conversions than actually happened, unevenly across locations depending on how privacy-conscious each market's traffic happens to be — and Smart Bidding, reading only what it can see, starts shifting spend toward whichever branch's numbers look better for a reason that has nothing to do with which one is actually closing business.
What still works when Google's own tracking doesn't
The fix isn't inside Google Ads — it's downstream, at the moment the call actually connects. A phone system that logs every call as a structured record (who called, what number they dialed, what they needed) independent of a visitor's cookie choice gives a business its own source of truth, one that consent settings can't quietly erase. That's not a one-time patch for the June 2026 change specifically. Consent requirements only get stricter from here, and any attribution model built entirely on what Google's cookies are allowed to see will keep degrading regardless of what changes next.
- Check which Consent Mode version is live on your site — the older v1 loses call attribution immediately; the full four-parameter v2 has more room to adapt (OneTrust, 2026).
- Confirm you're not relying on call-only ads for volume — none have been allowed to launch since February 2026, and existing ones stop serving in February 2027 (Invoca, 2026).
- Compare any recent drop in Google Ads call conversions against the June 15 date, not against an assumed drop in actual call volume.
- Check whether your phone system records a call's source anywhere outside Google Ads — a place a cookie-consent decline can't touch.