Safer Google Ads setup, routing, and historical recovery
Google Ads integrations now separate Upload Targets, Traffic Rules, and the routing policy for unmatched calls, helping multi-account setups direct eligible calls to the intended account and conversion action.
What’s new
Choose strict routing with no default destination, or select a Default Destination for unmatched calls. Multi-account defaults require an ownership confirmation and are not used as failover after a rejected upload.
New and migrated integrations remain Paused until routing has been reviewed. The Overview shows readiness, Enhanced Conversions for Leads status, and recovery guidance.
Historical Call Recovery provides a frozen preview of eligible calls, routing results, and destination counts before you queue a scope.
Delivery reporting includes routing source and Traffic Rule context for each Upload Target.
How to use it
Open Integrations → Google Ads, choose an integration, and open Configuration.
Create or review Upload Targets and Traffic Rules.
Set the routing policy: No Default Destination, or Send Unmatched Calls to a Default Destination.
For earlier eligible calls, open Configuration → Historical Call Recovery, create a preview, review the frozen scope, then queue it.
Impact
Multi-account routing fails closed rather than silently sending unmatched or invalidly routed calls to another account.
Older calls require an explicit historical-recovery preview and confirmation.
