Google Ads API Exposes AI Max Migration Dates
Google Ads API v25.1 adds campaign fields for ACA and broad-match auto-migration timing, making AI Max transition tracking programmatic.
The News
Google updated the Google Ads API release notes for v25.1 on August 19, 2026, adding campaign fields for aca_migration_date_time and broad_match_migration_date_time. The affected surface is programmatic Google Ads campaign management. These fields let advertisers track upcoming auto-migration to AI Max for campaigns using automatically created assets or campaign-level broad match settings.
The OPTYX Analysis
This is a search ads and commerce discovery signal because Google is turning a platform migration into an addressable API state. The mechanism is migration observability, where automated account tooling can identify which campaigns are queued for AI Max behavior before the transition happens. Strategically, Google is normalizing broader automation in Search campaigns while giving enterprise advertisers just enough metadata to govern timing, exception handling, and reporting continuity. The change matters because campaign semantics, query expansion, and asset generation controls are shifting from manual configuration toward platform-managed matching.
Enterprise Impact
The exposed operator is the paid search operations team, martech engineer, agency platform owner, or performance governance lead managing large Google Ads accounts. The vulnerability is untracked campaign conversion when ACA or broad-match campaigns move into AI Max without alerting, budget labeling, experiment baselines, or stakeholder signoff. Required move is a migration field audit across API pulls, dashboards, change logs, naming conventions, bid strategy cohorts, and QA workflows so Search automation changes are detected before performance comparisons become polluted.
Locked Recommendations
This signal has triggered a material consequence alert. Strategic recommendations are locked pending analyst clearance.