Google Ads Call Recording Opt-In July 2026: The Agency Playbook for the Smart Bidding Signal Swap

What’s actually changing on July 1

Per Google Ads Help documentation on the call recording setting, on July 1, 2026 the call recording setting defaults to On for eligible accounts in the US and Canada that haven’t previously made a selection. The carve-outs are clear:

• Accounts that previously opted out stay opted out.
• Accounts identified as operating in healthcare or specific financial services are skipped by default and must accept Call Ads Supplemental Terms to opt in.
• Eligibility requires Google Forwarding Numbers (GFNs), call reporting enabled, and calls originating from call ads, call assets, or website-originated flows. Location-asset calls are not in scope for recording-based qualification.

That last point matters more than the headline. If your client’s calls don’t route through GFNs — which is common for accounts running heavy third-party tracking through CallRail’s dynamic number insertion, Invoca’s call tracking, or similar — the default flip is a non-event for that traffic. The first agency task is mapping which accounts and which call sources are actually in scope.

Why the “disclosure burns billable seconds” framing is wrong

A common framing of this change argues that Google’s recording disclosure adds 4–6 seconds to the call, compressing the qualifying window and pushing calls under buyer duration thresholds (typically 60–120 seconds depending on vertical and buyer).

That framing doesn’t hold up under operational reality:

• The buyer-side billable counter doesn’t start at call answer. It starts when the call connects to the buyer, after IVR routing and qualification. Google’s recording disclosure fires at the start of the call, before the buyer connect — it sits inside the IVR window, not inside the billable window.
• Operators don’t control when Google’s disclosure fires. It’s platform-injected, pre-IVR. There’s no setting to move it after the qualifying question, so any “re-sequence your IVR” advice is impossible to execute against Google’s disclosure.
• Many accounts already had recording on. For those operators, nothing about the audio flow changes on July 1.

There’s a smaller, real version of the friction concern: a longer pre-IVR experience can cause some callers to drop off before they reach the IVR or the buyer. That’s a connect-rate question, not a duration-math question, and it’s worth measuring — but it doesn’t structurally compress buyer payouts the way the duration framing implies.

The actual operator impact: a Smart Bidding signal swap

The substantive change is what recording enables downstream. Once recording is on, Google can use AI-qualified call leads as the call conversion signal instead of (or alongside) raw call duration. Search Engine Land’s coverage of Google’s AI-powered call conversions notes that the system uses Gemini to evaluate recorded conversations rather than simple duration thresholds.

The old signal: a call over X seconds counts as a conversion. The new signal: the system evaluates the recorded conversation for evidence of business intent and counts the call accordingly.

For Smart Bidding, that’s a meaningful shift. Bidding strategies optimize against whatever the conversion action defines, and the qualified-call population is not the same population as the over-X-seconds population. Expect:

• Reported call conversions to move. Direction depends on the account. Some accounts will see lower volume because long-but-noisy calls stop counting. Others will see higher volume because shorter, high-intent calls start counting that previously fell under threshold.
• CPA and ROAS to drift during the relearn. When the conversion action’s underlying definition changes, Smart Bidding effectively retrains on a new target. Google’s own guidance on Smart Bidding learning periods suggests roughly two weeks is a reasonable expectation, though it varies by volume.
• Campaign rankings to reshuffle. Campaigns that were strong on duration-based scoring may look different under qualification-based scoring, and vice versa. That’s a feature, not a bug — but it surfaces in performance reporting before the strategic case has been made internally.
• Buyer-side scoring divergence. Lead buyers running their own AI scoring on returns may also recalibrate. If buyer-side payout logic moves at the same time Google’s signal moves, attribution gets messy.

None of that is catastrophic. It’s a measurement upgrade that requires deliberate handling.

The agency playbook for Q2 and Q3

Treat this as a measurement transition, not a deadline scramble. Four moves, sequenced across June and July.

Move 1 (this month): Audit eligibility and current state

Build a working sheet across managed accounts capturing:

• Account ID and vertical
• Current call recording state (On / Off / Unselected)
• Vertical classification (healthcare / financial services / other) and whether the account is auto-carved-out
• GFN coverage and call reporting status
• Which call sources are in scope (call ads, call assets, website, location)
• Who owns the IVR and call tracking stack (Google native, CallRail, Invoca, other)

This audit alone surfaces accounts where the default flip is irrelevant and accounts where it materially changes the conversion signal.

Move 2 (June): Make the recording decision intentional per account

For accounts where the flip would otherwise auto-apply, decide before June 30 whether you want recording on. The right answer depends on:

• Whether AI-qualified call leads improve the conversion signal versus duration
• Whether legal, compliance, and the client’s operations team are aligned on recording handling, retention, and access
• Whether the account operates in a state with two-party consent rules that need additional internal review (the FCC’s guidance on recording telephone conversations is a useful baseline)
• Whether buyer-side contracts have any clauses around recording, AI evaluation, or data handling

If the answer to any of those is unresolved, opting out before June 30 and reopening the question deliberately is more defensible than letting the default ride.

Move 3 (late June): Prepare the conversion-action plan

If you’re keeping recording on and want AI-qualified call leads as the primary signal, decide before the flip how you’ll handle the conversion action:

• Will AI-qualified call leads replace the duration-based call conversion, run alongside it, or be set up as a secondary action?
• Are bidding strategies set to optimize toward the new action, or are you holding the old action as the primary while you observe?
• What’s the rollback path if the relearn produces unacceptable CPA or volume swings in the first two weeks?

A conservative path: keep the existing duration-based call conversion as primary through July, observe AI-qualified call leads as a secondary action, and switch primary signals only after you’ve seen the qualified-call population behave consistently.

Move 4 (July onward): Watch the right metrics, not the obvious ones

The metrics that matter through July and August aren’t the headline call conversion totals. They’re:

• Connect rate to buyer / handoff — to catch any pre-IVR caller drop-off if the recorded-call experience is new for the account
• Qualified-call volume versus historical duration-based call volume, indexed
• CPA and CVR by campaign during the Smart Bidding relearn window
• Downstream outcomes (booked appointments, sales, buyer payouts) versus platform-reported conversions, to confirm the new signal correlates with revenue

Set a 30-day review. If platform conversions and downstream outcomes diverge meaningfully, the AI qualification isn’t yet calibrated to that account’s intent profile and the duration-based action is the safer primary signal until it is.

What this isn’t

• It isn’t a TCPA story. Disclosure handling, consent capture, and lead-buyer compliance are governed by separate frameworks; this change doesn’t move them.
• It isn’t a buyer-payout story driven by disclosure timing. The disclosure plays before buyer connect; it isn’t sitting inside the billable window.
• It isn’t a one-size-fits-all flip. Sensitive verticals are carved out by default, GFN-less accounts are unaffected for that traffic, and previously opted-out accounts stay opted out.

How Elevarus thinks about it

For agencies managing call-driven Search across mixed portfolios, the work between now and August is mostly measurement hygiene: confirm eligibility per account, decide recording intentionally, set up AI-qualified call leads as a tracked-but-not-yet-primary action, and let the data accumulate before swapping the Smart Bidding target. The accounts that handle this well will end Q3 with a stronger conversion signal and cleaner downstream attribution. The accounts that ignore it will end Q3 wondering why their bidding rankings moved.

If you’re an agency with mixed-vertical call-driven accounts and you’d like a second set of eyes on the audit and conversion-action plan before July 1, book a strategy call and we’ll walk through it.