Google released the July 2026 update to the Display & Video 360 API on Thursday, July 23, 2026, adding a synthetic content attestation field to Creative and AdAsset resources ten days before European Union transparency obligations for AI-generated content become applicable, alongside advertiser-level creative defaults and a reach forecasting beta restricted to allowlisted partners.

The announcement was posted to the Google Ads Developer Blog by Trevor Mulchay of the Display & Video 360 API Team, the same author who has signed most DV360 developer notices over the past two years. Three changes were listed. Each one touches a different part of the campaign construction process, and only one of them is available to every partner on day one.

The update carries no version bump. It arrives as an incremental release against API v4, which reached general availability on March 27, 2025 and became the only supported major version after v3 sunset on October 7, 2025.

The attestation field

The first item is a new field named syntheticContentAttestationStatus, added to both the Creative and the AdAsset resources. According to the Ads Developer Blog, the field allows a developer to specify whether a creative or an ad asset contains content that was "created or edited with AI." Google's own documentation on labeling AI content in ads is referenced as the explanatory material.

Placing the field on two resources rather than one is the technically interesting choice. A creative in Display & Video 360 is frequently assembled from multiple underlying assets: a video file, several image formats, a logo, text elements. A campaign might use a photographed product shot alongside a generated background. Attestation at the asset level permits that granularity. Attestation at the creative level records a judgement about the finished unit as served.

Neither the blog post nor the accompanying release notes reference specifies enumerated values for the field, the behaviour when the field is left unset, or whether Display & Video 360 validates the declaration against provenance signals already embedded in the file. Those questions sit in the API reference rather than the announcement.

The field has a close relative on the Google Ads side. On June 24, 2026, Google Ads API v24.2 introduced SyntheticContentInfo and SyntheticContentAttestation structures, splitting the declaration across two dimensions: whether an asset or ad is AI-generated, and whether the generation ran fully automatically or passed through advertiser review. That second distinction, automated output versus human-in-the-loop, maps onto how the European rules treat responsibility. Whether the Display & Video 360 field replicates that two-dimension structure or collapses it into a single status is not stated in the announcement.

Two weeks after the Google Ads release, on July 9, 2026, Google published a changelog entry introducing an interface-level AI label setting. That setting rolled out across five products: Google Ads, Display & Video 360, Campaign Manager 360, Merchant Center and Ads Editor, with a bulksheet column in Display & Video 360 among the controls. The July 23 API field is the programmatic counterpart to that manual control. A media agency running thousands of creatives through automated pipelines does not want a bulksheet. It wants a field.

What has not changed is where responsibility lands. PPC Land reporting has documented that Google's labeling architecture places the compliance obligation on the advertiser rather than on the platform carrying the ad, with the company stating that use of its label settings does not guarantee compliance with any specific regulation. A field in an API does not alter that allocation. It changes who types the value and how many times.

Ten days to Article 50

The date sequence around this release is tight. Transparency obligations under Article 50 of the European Union's AI Act, formally Regulation (EU) 2024/1689, become applicable on August 2, 2026. The July 23 announcement therefore lands ten days before the rules bind.

On July 20, 2026, the European Commission published implementation guidelines as Communication C(2026) 5054 final together with a finalised Code of Practice on Transparency of AI-Generated Content, fixing the technical detail ahead of the compliance date. Adherence to the Code is voluntary. The underlying obligations are not, and non-compliance carries penalties reaching 3 percent of global annual turnover.

The deadline survived an attempt to move it. Negotiations in Brussels over the Digital Omnibus package collapsed in May 2026 without producing a delay, although a provisional agreement gave generative systems already on the market until December 2, 2026 to bring machine-readable marking into conformity. The European regime is also not the only one in play. Google's own policy documentation names the European Union, India and New York as jurisdictions requiring disclosure when advertising creative contains certain AI-generated or edited assets.

That regulatory pressure explains the shape of the past month at Google. On July 22, 2026, one day before the API update, the company's advertising policy documentation was revised so that AI disclosure labels would not violate the existing prohibition on text overlays in Search image assets. Policy carve-out, interface setting, Google Ads API structures, and now a Display & Video 360 API field: four separate mechanisms, published across roughly five weeks, all pointing at the same August date.

The second item in the update is quieter and purely operational. The Advertiser resource now supports default business name and logo values. According to Google, once those values are set, they will automatically be used when creating or updating Demand Gen and YouTube responsive ads that do not carry a specified business name and logo of their own.

Both fields are mandatory inputs for the formats concerned. Demand Gen ad specifications require a business name capped at 25 characters and a square logo at a 1:1 ratio, with a 144 by 144 pixel minimum and 1200 by 1200 recommended, as documented in PPC Land's Demand Gen ad specs reference. Every ad created through the API previously had to carry both values explicitly.

For a partner managing a single brand, that is redundancy. For a partner managing hundreds of advertisers through one integration, it is a persistent source of mismatch: a logo updated in one place and not another, a business name entered inconsistently across ad groups. Moving the values up to the advertiser level converts them from per-ad payload into inherited configuration, with the per-ad value retained as an override.

The change only became meaningful once Demand Gen was fully addressable through the API. Full Demand Gen resource support began rolling out on June 10, 2026 and reached all partners by June 24, covering LineItem, AdGroup and AdGroupAd types with complete get, create, delete and patch operations. That rollout followed a closed beta that opened on April 14, 2026. Before it, creating a Demand Gen ad programmatically was not possible at all.

The API documentation still carries a banner promoting the Demand Gen guide as the starting point for building and running such a campaign. Demand Gen itself arrived in Display & Video 360 in October 2024, and the API has been catching up with the interface ever since, adding asset creation and retrieval for YouTube and Demand Gen ads in the October 2025 release.

Reach forecasting, behind a gate

The third item is the most restricted. Google launched beta support for generating reach forecasts and retrieving relevant metadata through the API. The feature is available only to allowlisted partners. According to the announcement, partners will be able to apply for access at a later date.

No application mechanism exists at publication. No date for one was given. For the majority of developers reading the release notes, the item is an advance notice rather than a capability.

The significance lies in what is being exposed. Reach forecasting has lived inside the Display & Video 360 planner interface for years and has accumulated considerable functionality there. Google added programmatic deals to the forecasting tool in February 2022, producing deduplicated reach estimates spanning open auction, YouTube and deal inventory. Planning support for efficient reach auction line items, combining in-stream, in-feed and Shorts formats, followed in September 2024. In April 2026, the platform gained reach overlap dimensions and moved inventory availability reporting into instant reporting, compressing the delay between a targeting hypothesis and a feasibility check.

None of that was scriptable. Media planners generated forecasts by hand, in a browser, one scenario at a time. Exposing forecasts through the API would allow a planning system to iterate across budget levels, frequency caps and audience combinations automatically, then write the winning configuration straight into line items through the same interface.

That prospect is also why the allowlist is unsurprising. Forecast generation is computationally expensive relative to a resource read, and an unrestricted endpoint invites parameter sweeps at a scale no planner would attempt manually.

The measurement basis underneath is itself in transition. Under the platform roadmap Google published on June 10, 2026, several planning surfaces switch from cookie-based audience reach to impression volume, including the forecasted audience summary in campaign construction and the custom affinity audience estimator, while user reach forecasting in the planner itself was stated to remain unchanged. Partners building against a forecasting endpoint will be building against numbers whose definition has recently moved.

What developers have to update

Google's instruction to developers is unchanged from previous releases: consult the release notes for the complete feature list, and update the client library to the latest version before using any of the new capabilities. Support questions are directed to the Google Advertising and Measurement Community Discord server, the channel Google expanded to cover the DV360 API, Structured Data Files and the Bid Manager API in March 2026.

The client library landscape shows where that instruction bites unevenly. Google's Samples and Libraries documentation, last updated on July 16, 2026, lists six client libraries with full documentation: .NET, Java, JavaScript, Objective-C for REST, PHP and Python covering v1 and v2. Three further libraries are described as early-stage: Go, plus Node.js and Ruby, both marked alpha.

Of the six documented libraries, only three carry Display & Video 360 API code examples. Java, PHP and Python have sample repositories. .NET, JavaScript and Objective-C for REST do not. Neither do any of the three early-stage libraries.

A team working in Python can consult a worked example when wiring an attestation field into a creative upload. A team working in Node.js is reading the REST reference and an alpha library, with no platform-specific sample to check its interpretation against. That gap has existed for some time, but it acquires a different weight when the field being implemented carries a regulatory deadline ten days out.

Version churn as background noise

This release lands amid a period of unusually dense change in the Display & Video 360 developer surface. Bulk operations teams are working through the deprecation of Structured Data Files v9, v9.1 and v9.2, announced on June 29, 2026 with a sunset date of January 28, 2027, after which requests specifying the retired version strings return a 400 error. Two months earlier, on May 5, 2026, Google introduced Partial Structured Data File Upload, relieving the requirement that every line item file carry more than 120 columns.

The July 2025 update, by contrast, was largely housekeeping: targeting parity between v3 and v4, YouTube inventory control settings, and the removal of SDF v6. Regulatory obligations have since become a recurring feature of these releases rather than an occasional one. In August 2025, Google made EU political advertising declarations mandatorythrough the containsEuPoliticalAds field, enforced from September 8 of that year under Regulation 2024/900.

Why this matters for the marketing industry

The practical consequence of the attestation field is that AI disclosure stops being a task performed in an interface and becomes a value carried in a data structure. Agencies, in-house programmatic teams and creative management platforms that push assets into Display & Video 360 through automated pipelines can now set the declaration at the point of upload, rather than returning to the platform afterwards to tick a box per creative.

That is a workflow improvement and a documentation problem at the same time. A value written through an API is a record. Where an advertiser declares that a creative contains no AI-generated content and a regulator later disagrees, the declaration exists, timestamped, in Google's systems. The field does not distribute liability; it documents a position that the advertiser has already been made responsible for holding.

The advertiser-level defaults address a narrower irritation, but one that scales badly. Brand identity fields duplicated across every ad in an account are a maintenance cost that grows linearly with campaign volume, and Demand Gen campaigns generate a large number of ad variants by design.

Reach forecasting is the item with the largest potential effect on how media planning is done, and the one furthest from general availability. Until an application process opens, the capability changes nothing for most partners. When it does open, the question worth watching is whether forecast access is priced, rate-limited, or tied to spend thresholds, since none of those parameters appear in the announcement.

For everyone else, the immediate item on the list is the one with a date attached. The field exists. The deadline is August 2.

Timeline

Summary

Who: Google's Display & Video 360 API Team, with the announcement signed by Trevor Mulchay, addressing developers, agencies, in-house programmatic teams and marketing technology vendors building integrations against the platform.

What: The July 2026 update to the Display & Video 360 API introduces three changes. A syntheticContentAttestationStatusfield is added to the Creative and AdAsset resources, allowing a declaration of whether the content was created or edited with AI. The Advertiser resource gains default business name and logo values that are applied automatically to Demand Gen and YouTube responsive ads lacking their own. Beta support for generating reach forecasts and retrieving related metadata launches for allowlisted partners only, with an application process promised at an unspecified later date.

When: The announcement was published on Thursday, July 23, 2026, through the Google Ads Developer Blog. The attestation field arrives ten days before Article 50 transparency obligations under the EU AI Act become applicable on August 2, 2026. The supporting Samples and Libraries documentation was last updated on July 16, 2026.

Where: The changes apply to the Display & Video 360 API globally. Nine client libraries are listed in Google's documentation, six with full documentation and three at early stage, of which only Java, PHP and Python carry Display & Video 360 code samples. Developer support runs through the Google Advertising and Measurement Community Discord server.

Why: Disclosure requirements for AI-generated advertising content take effect in the European Union on August 2, 2026, with parallel regimes in India and New York, and the attestation field gives automated creative pipelines a programmatic route to record that declaration. The advertiser-level defaults reduce duplicated brand identity data across Demand Gen and YouTube responsive ads following the June 2026 completion of Demand Gen API support. Reach forecast access remains gated while the capability is tested with a limited partner set.