Google Ads API Version 24.1 Now Available

Why It Matters

The enhancements give marketers finer‑grained control over creative assets and experiment design, driving more efficient spend and better performance insights. Developers and agencies gain new data points that can be leveraged for automated optimization and compliance reporting.

Key Takeaways

• v24.1 adds classic_display_images field for DemandGen ads
• Passkey_enabled flag now visible in CustomerUserAccess resource
• New experiment types include ADOPT_AI_MAX and PMAX_REPLACEMENT_SHOPPING
• Mobile_device_platform segment enables iOS/Android reporting
• ZEFR integration adds third‑party viewability for video ads

Pulse Analysis

Google’s release cadence for the Ads API has become almost monthly, reflecting the platform’s push toward hyper‑automation. Version 24.1 arrives just weeks after the April 24 launch, underscoring Google’s commitment to delivering incremental functionality that developers can immediately embed in bidding scripts, reporting dashboards, and creative management tools. By exposing classic_display_images, advertisers can serve custom static assets without the overhead of responsive formats, a move that simplifies asset pipelines for demand‑generation campaigns.

The addition of the passkey_enabled flag signals Google’s broader security strategy, allowing agencies to verify whether users have adopted password‑less authentication. Meanwhile, the expanded experiment taxonomy—ADOPT_AI_MAX, ADOPT_BROAD_MATCH_KEYWORDS, OPTIMIZE_ASSETS, and PMAX_REPLACEMENT_SHOPPING—gives marketers a richer sandbox for testing AI‑driven bidding and asset optimization. Coupled with new experiment metrics, advertisers can now quantify lift across clicks, conversions, and cost efficiency with statistical confidence intervals, turning hypothesis testing into a data‑driven routine.

From a measurement perspective, the mobile_device_platform segment and vertical ads listing fields enrich cross‑device attribution, helping brands allocate budgets between iOS and Android ecosystems more precisely. The ZEFR partnership introduces third‑party viewability data directly into the API, enabling video advertisers to incorporate viewability thresholds into automated bidding rules. Collectively, these updates lower the barrier for sophisticated, programmatic campaign management and set the stage for deeper AI integration in future API versions.