TL;DR Summary of Google Ads API Version 24.2 Released with AI Transparency and Reporting Enhancements
Optimixed’s Overview: Key Innovations and Security Upgrades in Google Ads API v24.2
Enhanced Security with Multi-Party Approvals
Google Ads API version 24.2 introduces multi-party approval (MPA) to strengthen security around critical account operations like user invitations and access level changes. This requires a second administrator’s approval, reducing the risk of unauthorized modifications.
AI Transparency and Synthetic Content Labeling
With the rise of AI-generated advertising assets, Google has implemented new structures (SyntheticContentInfo and SyntheticContentAttestation) that allow advertisers to programmatically label AI-generated ads and assets. This feature supports compliance preparations for the upcoming EU AI Act effective August 2026 and allows both Google and advertisers to attest to the origin and review status of synthetic content.
Advanced Reporting and Video Asset Integration
- Performance Max Placement Segmentation: Enables segmentation of PMax campaign reports by ad network type to identify ad placements across Search, Display, and partner networks.
- YouTube Brand Channel Links: Facilitates creation of secure data links to specific YouTube brand channels, enriching video asset integrations within campaigns.
- Landing Page Text Automation: Introduces opt-in functionality for automatic text asset generation directly from landing pages to streamline creative assets.
New Experiment Types for Campaign Optimization
The update brings Campaign Mix Experiments allowing comparison of multiple existing campaigns across up to five experiment arms, plus Performance Max Feature Testing to split traffic and measure the impact of text customization and final URL expansions within a single campaign.
Improved Documentation and Upgrade Support
Google revamped its release notes format to clearly separate breaking changes from non-breaking updates and included a guide for feature deprecations and unversioned changes. This aims to simplify upgrade paths for developers planning integrations with future API versions, especially as v25 approaches with write capabilities for synthetic content attestations.