Google released version 24.2 of the Google Ads API on June 24, 2026, adding synthetic content labeling structures aligned with the EU AI Act, a new multi-party approval mechanism for sensitive account operations, granular network segmentation for Performance Max placement reporting, and two new campaign experiment types - changes that together represent the most compliance-focused minor release in the v24 cycle.

A minor release with a compliance-sized footprint

Minor API releases are usually incremental. Version 24.2 is different. Published on June 24, 2026, on the Google Ads Developer Blog by Anash P. Oommen of the Google Ads API Team, it arrives at a moment when a hard regulatory deadline - the EU AI Act's transparency obligations under Article 50, taking effect August 2, 2026 - is fewer than six weeks away. The timing is not incidental.

According to Google, v24.2 is a drop-in upgrade for v24.1, meaning existing integrations require no structural renegotiation. Developers need only download the latest version of their client library and update any client code to access the new capabilities. All updated client libraries and code examples were published alongside the June 24 announcement. Google also hosted a live walkthrough of the release on June 25 through its "Google Ads API Release Highlights" event on Discord and an Ads Developers YouTube Live session, recorded for those who could not attend.

The release is accompanied by parallel minor version updates to three older supported versions: v23.3, v22.2, and v21.2. Those older-version updates carry a narrow but important scope - additional support for multi-party approvals and synthetic content labeling, two of the headline features in v24.2. The fact that Google backported these specific features across supported versions signals that both are being treated as infrastructure requirements rather than optional enhancements.

Multi-party approvals: a second set of eyes on sensitive actions

The most operationally significant security change in v24.2 is the introduction of multi-party approval support. According to Google, the feature - abbreviated as MPA - secures sensitive account actions by requiring a second administrator to approve certain changes before they take effect. The specific actions covered include user invitations and user access level updates.

This is a meaningful gap in the previous model. Before MPA, a single authenticated administrator could invite a new user or escalate access permissions unilaterally, with no structural check from a second human reviewer. For agencies managing client accounts, for large enterprise accounts with multiple team members, and for any organization concerned about the kinds of unauthorized access escalations that have become more common as account hijacking grows more sophisticated, the absence of a two-step approval path was a documented risk. PPC Land documented in May 2026 that Google was already moving toward passkey enforcement for sensitive Google Ads account actions from July 15, 2026, a parallel track addressing the same threat surface through authentication rather than approval workflows.

MPA at the API level gives developers and integrators a programmatic path to build and test against this security model. The fact that it was also backported to v23.3, v22.2, and v21.2 means teams running older supported versions do not need to migrate to v24.2 solely to gain access to multi-party approval infrastructure.

Synthetic content labeling and the EU AI Act race

Perhaps the most technically layered addition in v24.2 is the exposure of SyntheticContentInfo and SyntheticContentAttestation structures on both Asset and Ad resources. These two structures allow advertisers and their API integrations to programmatically label ad creatives as AI-generated.

The labeling model operates on two distinct attestation dimensions. First, both the advertiser and Google systems can attest whether the assets and ads are AI-generated or not. Second, the attestation covers whether the content was generated fully automatically or with advertiser review. That distinction - fully automated versus human-in-the-loop - maps directly to the transparency requirements that the EU AI Act is introducing. According to the Google Ads Developer Blog, if teams are "preparing for the EU AI Act taking effect on August 2, 2026," this feature is the relevant integration point.

The EU AI Act context is substantial. Brussels negotiations over the Digital Omnibus package collapsed in May 2026 without producing a delay, leaving the August 2 date intact for Article 50 transparency obligations. A provisional agreement reached on May 7, 2026, between the European Council and Parliament did introduce some grace periods for certain categories under the Digital Omnibus VII - generative AI systems already on the market before August 2, 2026, gained until December 2, 2026, to ensure their outputs are machine-readable and detectable. But the underlying obligation to label synthetic content did not disappear; the window to comply simply shifted slightly. IAB's disclosure framework, published in January 2026, had already identified a 37-point gap between what advertisers believe about consumer sentiment toward AI ads and what consumers actually report - making transparency infrastructure a business issue as much as a regulatory one.

What is mutable now and what becomes mutable in v25

The implementation in v24.2 comes with an explicit sequencing constraint. According to Google, the interface for mutating advertiser attestation fields is being introduced early - visible in v22 and later - but two specific fields remain immutable in these early versions: synthetic_content_info.advertiser_attestation.status and synthetic_content_info.advertiser_attestation.source.

If a developer attempts a mutate request on either field in v24.2 or earlier, one of two errors will return: "The field attempted to be mutated is immutable" or "Field cannot be set." Both fields will become fully mutable starting in v25. Google's explicit recommendation is to use the current visibility window to build and test internal logic now, so systems are ready for full write capabilities when v25 launches. This staged approach avoids the risk of teams scrambling to implement attestation workflows at the last minute - a pattern that has complicated compliance timelines on previous API feature rollouts.

The backport of synthetic content labeling to v22.2 and v21.2 gives teams on those older versions a path to begin building against the structures without migrating their entire integration to v24.2.

Performance Max placement segmentation by ad network type

Performance Max placement reporting has expanded incrementally since Google introduced the performance_max_placement_view resource in API v18 in October 2024. Version 24.2 adds a new segmentation dimension: ad_network_type. According to Google, developers can now segment performance_max_placement_view reporting by this field, giving granular visibility into where PMax ads are serving across Search, Display, and partner networks.

PPC Land has tracked this trajectory across multiple releases - from the channel-level reporting introduced in API v23 in January 2026, which enabled breakdowns by Search, YouTube, Display, Gmail, Maps, and Discover, to the alpha-stage network toggle spotted in May 2026 that would let advertisers switch the Search Partner Network and Google Display Network on or off individually within Performance Max campaigns. The network-type segmentation in v24.2 is a programmatic reporting addition, not a control surface - it allows developers to see which network a given placement belongs to, rather than switch it off.

Why does this matter for practitioners? Performance Max campaigns allocate budget automatically across a broad inventory pool. Without network-type segmentation in the placement view, identifying whether a campaign is delivering disproportionately on lower-performing partner networks versus Google's owned inventory required either inference from aggregate data or expensive workarounds. The new segment makes that distinction available natively through the API query layer.

Microsoft Advertising extended similar transparency to its own Performance Max in May 2026, adding conversion data, clicks, and spend at the placement level - going beyond the impression-only placement data most cross-channel campaign types had offered. The competitive pressure toward placement-level transparency is visible across platforms, and v24.2's network segmentation is Google's latest response to that pressure at the API level.

Alongside the placement segmentation, v24.2 introduces the ability to create secure YouTube data links associated with a specific brand channel directly through the Google Ads API. According to Google, these links enable richer video asset integrations. The addition gives developers and large accounts a programmatic path to establish channel-level video connections that previously required manual UI steps. For teams managing substantial YouTube advertising at scale - particularly those coordinating video assets across multiple campaigns through API-driven workflows - removing that manual dependency is a meaningful reduction in operational friction.

Landing page text generation as an automation type

A third reporting and asset enhancement in v24.2 is the introduction of LANDING_PAGE_TEXT_GENERATION as a new AssetAutomationType. This value lets advertisers opt into automatic text asset generation derived directly from their landing page content. The opt-in framing is notable. Google is not applying this automation by default; it requires explicit activation through the API. That design choice preserves advertiser control over whether landing page content feeds into automated creative assembly - a consideration that matters for brands with strict message approval processes or regulated industries where creative must be reviewed before publication.

New experiment types: Campaign Mix and PMax text customization

Version 24.2 expands the experiments framework with two new experiment types that address different testing scenarios.

The first is Campaign Mix Experiments, which uses a new workflow supporting the COMPARE_CAMPAIGNS experiment type. This is equivalent to the "Custom mixed campaign types" option in the Google Ads interface. According to Google, it allows assigning existing campaigns across up to 5 experiment arms to compare multiple variables and campaign types within a single experiment. That up-to-5-arm structure is significant - it moves beyond simple A/B testing into more complex multi-variable comparisons that have historically required either multiple sequential experiments or custom external tracking setups. The Campaign Mix workflow also supports creating custom Performance Max experiments.

The second new type is PMAX_TEXT_CUSTOMIZATION_FINAL_URL_EXPANSION. This experiment type lets developers split traffic within a single Performance Max campaign to test the impact of two related features: text customization (formerly known as automatically created assets) and final URL expansion. Until now, testing whether these automation features add or reduce value required constructing comparisons manually or relying on aggregate before-after analysis. The new experiment type provides a proper controlled split within the same campaign, which produces cleaner causal comparisons.

PPC Land covered the May 2026 v24.1 release's significant expansion of the Experiments framework, which introduced direct experiment statistics retrieval and support for AI Max, Video, Demand Gen, and Performance Max experiment types alongside the ability to retrieve per-arm performance metrics in a single API call. The v24.2 additions build on that infrastructure, extending the experiment type roster rather than restructuring how experiments are queried.

Documentation changes and release note format

According to Google, the release notes format has been overhauled in v24.2. Breaking changes are now listed separately from non-breaking feature updates. A dedicated "Feature deprecations and unversioned changes guide" has also been introduced to help developers track feature sunsets. The separation of breaking from non-breaking changes is a practical improvement for development teams managing multi-version integrations. Previously, identifying which changes required active code modification before upgrading required reading through the full notes and distinguishing severity manually.

Context: where v24.2 sits in the monthly cadence

Google shifted to monthly Google Ads API releases in January 2026, after announcing the change on September 4, 2025. Under that schedule, major versions last one year from launch, and minor versions are non-breaking additive releases. V24 launched April 22, 2026. V24.1 followed May 13, 2026. V24.2 on June 24, 2026, is the second minor update in the cycle. V25 is scheduled to arrive in July 2026, at which point the advertiser attestation fields introduced in v24.2 will become fully mutable.

V24 itself introduced CartDataSalesView for product-sold reporting at the item level, nine new lead generation conversion type enumerations, and VTC optimization for Demand Gen and App campaigns. V24.1 added mobile device platform segmentation for campaign and customer-level reports, static image support for Demand Gen campaigns on the Google Display Network, passkey field detection, and the expanded Experiments framework covering AI Max, Video, Demand Gen, and Performance Max. V24.2 closes the minor version cycle on the v24 branch with security hardening, regulatory compliance infrastructure, and reporting granularity.

For advertising technology vendors, the combination of MPA and synthetic content labeling in a single release - both of which were also backported to three older versions simultaneously - reflects a degree of urgency that typical minor releases do not carry. Developers using v22 or later can begin building against the synthetic content structures immediately. The question of whether EU AI Act enforcement and Google's own attestation model will become fully synchronized by August 2, 2026, depends on how quickly teams complete their integrations and whether v25 arrives on schedule to unlock the mutable attestation fields.

Timeline

  • October 16, 2024 - Google introduces performance_max_placement_view reporting in Google Ads API v18, providing initial visibility into where Performance Max ads run
  • September 4, 2025 - Google announces monthly Google Ads API release cadence beginning January 2026, increasing major versions from three to four per year; PPC Land coverage
  • January 2026 - Google Ads API v23 introduces channel-level reporting for Performance Max across Search, YouTube, Display, Gmail, Maps, and Discover; PPC Land coverage
  • January 15, 2026 - IAB publishes AI Transparency and Disclosure Framework; research reveals a 37-point gap between advertiser and consumer sentiment on AI-generated advertising; PPC Land coverage
  • February 6, 2026 - Google acknowledges developer token application backlog and introduces Explorer Access tier for the Google Ads API; PPC Land coverage
  • March 18, 2026 - European Parliament committees vote 101-9 to propose fixed AI Act compliance dates; PPC Land coverage
  • April 22, 2026 - Google Ads API v24 launches with CartDataSalesView, nine lead gen conversion types, and VTC optimization for Demand Gen; PPC Land coverage
  • May 3, 2026 - Brussels overnight negotiations fail to amend the EU AI Act; August 2, 2026, deadline holds; PPC Land coverage
  • May 7, 2026 - EU Council and Parliament reach provisional Digital Omnibus VII agreement; generative AI systems already on market before August 2 gain until December 2, 2026 to comply with synthetic content detection requirements; PPC Land coverage
  • May 7, 2026 - Microsoft Advertising expands Performance Max placement reports to include conversion data, clicks, and spend; PPC Land coverage
  • May 13, 2026 - Google Ads API v24.1 releases; introduces mobile device platform segmentation, passkey detection field, static Demand Gen image support, and expanded Experiments framework; PPC Land coverage
  • May 31, 2026 - Google's passkey requirement for sensitive Google Ads account actions confirmed for July 15, 2026 enforcement; PPC Land coverage
  • June 24, 2026 - Google releases Google Ads API v24.2 with multi-party approvals, synthetic content labeling structures, Performance Max placement segmentation by ad network type, Campaign Mix and PMax text customization experiment types, and an overhauled release notes format; minor versions v23.3, v22.2, and v21.2 released simultaneously with MPA and synthetic content labeling support
  • July 2026 - Google Ads API v25 scheduled to launch; advertiser attestation fields in SyntheticContentInfo will become fully mutable
  • August 2, 2026 - EU AI Act Article 50 transparency obligations take effect for interactive AI systems and providers of AI-generated content

Summary

Who: Google's Ads API Team, led by Anash P. Oommen, released v24.2 alongside minor updates to v23.3, v22.2, and v21.2. The release affects developers, marketing technology vendors, and agencies building API integrations for Google Ads accounts globally.

What: Google Ads API v24.2 introduces four major additions: multi-party approval support for sensitive account actions; SyntheticContentInfo and SyntheticContentAttestation structures for programmatic AI-generated content labeling on Asset and Ad resources; Performance Max placement view segmentation by ad_network_type across Search, Display, and partner networks; and two new experiment types - COMPARE_CAMPAIGNS for Campaign Mix testing across up to 5 arms, and PMAX_TEXT_CUSTOMIZATION_FINAL_URL_EXPANSION for in-campaign PMax feature testing. The release also adds YouTube Brand Channel Link creation and a LANDING_PAGE_TEXT_GENERATION AssetAutomationType, alongside an overhauled release notes format separating breaking from non-breaking changes.

When: The announcement was published June 24, 2026, on the Google Ads Developer Blog. Minor versions v23.3, v22.2, and v21.2 were released simultaneously. Synthetic content labeling fields will become fully mutable in v25, expected in July 2026. The EU AI Act Article 50 deadline driving the transparency feature is August 2, 2026.

Where: The changes apply globally to all Google Ads API integrations. The release announcement was published on the Google Ads Developer Blog. A live walkthrough took place on June 25 via the Google Ads API Discord server and the Ads Developers YouTube channel.

Why: V24.2 addresses two converging pressures. The EU AI Act's August 2, 2026, deadline for AI-generated content transparency creates a concrete compliance requirement for advertisers using AI creatives at scale. At the same time, the growing complexity of account access management - and the documented rise in account hijacking - has pushed Google toward structural security additions like multi-party approvals. The Performance Max placement segmentation and experiment additions continue the API team's incremental effort to give programmatic advertisers better visibility and testing infrastructure inside an automated campaign type that has historically provided limited transparency.