Google documented the enumerated values, the regional scope and a one-way write rule for its synthetic content attestation field on Tuesday, July 28, 2026, five days before European Union transparency obligations for AI-generated advertising become applicable, confirming that the same field now exists in both the Campaign Manager 360 API and the Display & Video 360 API.

The post appeared on the Google Ads Developer Blog under the byline of Trevor Mulchay of the Display & Video 360 API Team. It is brief, technical and, in one respect, more consequential than the release note that preceded it. According to the blog, updates launched in the previous week across both APIs added new optional fields that allow a creative or a creative asset to be labelled as having been created or edited with AI.

That much had already been reported. What the July 28 post supplies is the part the earlier announcement left out.

When the Display & Video 360 API gained the attestation field on July 23, neither the release note nor the accompanying blog specified enumerated values, described the behaviour of an unset field, or indicated whether the declaration could later be changed. Those questions sat in reference documentation rather than in the announcement. Five days later they have answers, and the answers carry operational weight for any team pushing creatives through automated pipelines.

One field, three states, two APIs

The field is named syntheticContentAttestationStatus. It accepts two values.

Setting it to IS_SYNTHETIC applies the label in the regions where local rules require one. Setting it to NOT_SYNTHETICrecords a confirmation that the content does not require a label. A third state exists by omission: the field can be left unset, and according to the blog, no label is applied when it is.

Three states, then, but they are not equivalent. Unset is a default. The other two are declarations, and one of them is a declaration that something is absent, which is a different thing from never having been asked.

The asymmetry becomes concrete in the rule that follows. Once the field is set for a resource, it cannot be unset. It can be updated, but only between IS_SYNTHETIC and NOT_SYNTHETIC. The unset state is available exactly once, at the beginning, and is unavailable afterwards.

For a single creative uploaded by hand, that constraint is trivial. For a creative management platform writing thousands of resources per day through a batch job, it is a schema decision that cannot be walked back. A pipeline that defaults the field to NOT_SYNTHETIC across an entire library commits every one of those resources to a permanent declaration, made by a machine, on behalf of an advertiser. A pipeline that leaves it unset preserves optionality but produces no record at all.

Where the label actually appears

The blog states that labels will be applied to ads with such assets serving in regions with local AI labelling regulations, and names three: the European Union, India, and New York state. That list is described as current as of the publication date, which implies it is expected to grow.

Each of those three regimes was drafted separately and defines its subject matter differently. PPC Land has documented how advertisers now navigate $5,000 New York penalties alongside 3 percent EU turnover fines, with New York's synthetic performer disclosure rules in force since June 9, 2026 and India's amended intermediary rules effective from February 20, 2026. India attaches no direct financial penalty and relies instead on the withdrawal of intermediary safe harbour.

The European deadline is the nearest one. Article 50 of Regulation (EU) 2024/1689 becomes applicable on August 2, 2026, five days after this post. The European Commission published implementation guidelines and a finalised Code of Practice on Transparency of AI-Generated Content on July 20, 2026, setting out the placement rules and penalty structurethat govern visible disclosure. Non-compliance reaches EUR 15,000,000 or 3 percent of total worldwide annual turnover, whichever is higher.

Google itself signed that code on July 24, 2026, two days after the date that confers a presumption of compliance. The signature binds the company as a provider of generative systems. It does not transfer the deployer-side labelling duty away from the advertiser.

Campaign Manager 360: the creative resource

In the Campaign Manager 360 API, the configuration lives in Creative resources. According to the blog, the field can be set at resource creation using creatives.insert, or updated on existing resources using creatives.patch and creatives.update.

That is a single attachment point. Campaign Manager 360 functions primarily as an ad server and attribution layer rather than a buying platform, and its creative model is correspondingly flatter. A creative is trafficked, assigned to placements, and served. The declaration attaches to the served unit.

The inclusion of both patch and update methods matters for teams with existing libraries. Creatives trafficked before July 2026 carry no attestation. Backfilling them requires a pass over the entire inventory, and each write in that pass consumes the one-time transition out of the unset state.

Display & Video 360: creatives and ad assets

The Display & Video 360 implementation is wider. The field appears on both Creative and AdAsset resources, and can be set at creation through four methods: advertisers.creatives.create, advertisers.adAssets.create, advertisers.adAssets.bulkCreate, and advertisers.adAssets.upload. Existing resources are amended through advertisers.creatives.patch and advertisers.adAssets.patch.

Two resources rather than one reflects how creatives are assembled in the platform. A single DV360 creative may draw on a video file, several image formats, a logo and text elements. A campaign might pair a photographed product shot with a generated background. Asset-level attestation captures that mixture. Creative-level attestation records a judgement about the finished unit as it serves.

The presence of bulkCreate and upload among the creation methods is the practically significant detail. Bulk asset creation is the path most large agencies use, and a field that could only be written through single-resource calls would have forced a second pass over every batch. It can be written inline instead.

Structured Data Files v10.1 and YouTube video assets

The third component is not yet available. According to the blog, Structured Data Files v10.1 is scheduled to launch in the coming weeks, and will allow labels to be added when YouTube videos are used as video assets in Ad files or as related videos in Line Item files. Further detail is deferred to the launch announcement for that version and its reference documentation.

No date was attached. That leaves a gap for bulk operations teams, since Structured Data Files remain the primary interface for advertisers managing campaigns at volume through comma-separated files rather than REST calls.

The gap arrives during an unusually dense period of change in the format. Google announced on June 29, 2026 that Structured Data Files v9, v9.1 and v9.2 would sunset on January 28, 2027, after which requests specifying those version strings return a 400 error and accounts default to v10. Two months before that, on May 5, 2026, Partial Structured Data File Upload removed the requirement that every line item file carry more than 120 columns. A team migrating off v9 while waiting for v10.1 is managing two version transitions against one regulatory date.

Five weeks, five mechanisms

The July 28 post is the fifth distinct labelling mechanism Google has published for advertising products since late June, and they arrive in a recognisable sequence.

Google Ads API v24.2 introduced SyntheticContentInfo and SyntheticContentAttestation structures on June 24, 2026, splitting the declaration across two dimensions: whether an asset or ad is AI-generated, and whether generation ran fully automatically or passed through advertiser review. On July 9, an interface-level AI label setting rolled out across Google Ads, Display & Video 360, Campaign Manager 360, Merchant Center and Ads Editor. On July 22, the company's advertising policy documentation was revised so that AI disclosure labels would not breach the existing prohibition on text overlays in Search image assets. On July 23 came the Display & Video 360 API field itself.

A comparison with the Google Ads structure is worth drawing. Version 24.2 records two dimensions. The Marketing Platform field records one status. Whether that difference reflects a deliberate simplification or a documentation gap is not addressed in the July 28 post, but it means an advertiser running the same creative through Google Ads and through Display & Video 360 declares different amounts of information about the same asset.

What has not changed across any of the five is where responsibility sits. PPC Land reporting has documented that the 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 records a position. It does not underwrite one.

Why this matters for the marketing community

The immediate consequence for agencies and in-house programmatic teams is that AI disclosure has moved from an interface task to a data modelling problem, and the data model has a rule that most advertising fields do not.

Reversibility is the norm in campaign configuration. Budgets change, targeting changes, creatives are paused and reactivated. A field that permits exactly one exit from its default state behaves more like an audit record than a setting, and it needs to be treated as one. Teams that write it automatically at upload are choosing a default that will apply to every future resource. Teams that write it manually are accepting a per-creative decision at a volume that scales with campaign output.

The three-region list creates a second problem, and it is a routing problem rather than a labelling one. An advertiser with a single global creative library and campaigns running in more than three markets is setting one status per resource while facing three separate legal definitions of what triggers disclosure. New York's rule concerns synthetic performers. India's concerns synthetic content on intermediary platforms. The European rule concerns deep fakes and AI-generated text on matters of public interest, with Commission guidance treating persuasive commercial content as outside the lighter regime available to artistic work. One boolean-style field cannot express three different tests. It expresses whether the advertiser believes a label is warranted, and the platform applies it where local rules exist.

For measurement and ad operations teams, the Campaign Manager 360 side is the one most likely to be overlooked. Attention through July has concentrated on Google Ads and Display & Video 360. Campaign Manager 360 sits underneath both as the serving and attribution layer for a large share of enterprise display activity, and its creative library often predates the campaigns currently running. A backfill there is a larger job than a forward-looking default.

Finally, the deferred Structured Data Files support draws a line between two classes of advertiser. Teams working through the REST API can declare attestation from July 23 and July 28 respectively. Teams working through bulk files, which tends to mean the largest buyers with the most creative volume, wait for v10.1 with no published date. The regulatory deadline does not wait with them.

Timeline

Summary

Who: Google's Display & Video 360 API Team, with the post signed by Trevor Mulchay, addressing developers, agencies, in-house programmatic teams and creative management platforms building integrations against Campaign Manager 360 and Display & Video 360.

What: Documentation of the syntheticContentAttestationStatus field now present in both APIs. The field accepts IS_SYNTHETIC, which applies a label in regions with local AI labelling rules, and NOT_SYNTHETIC, which records that no label is required. Leaving the field unset applies no label. Once set, the field cannot return to the unset state and may only be switched between the two values. In Campaign Manager 360 it sits on Creative resources, written through creatives.insert, creatives.patchand creatives.update. In Display & Video 360 it sits on Creative and AdAsset resources, written through advertisers.creatives.create, advertisers.adAssets.create, advertisers.adAssets.bulkCreate, advertisers.adAssets.upload, advertisers.creatives.patch and advertisers.adAssets.patch.

When: The post was published on Tuesday, July 28, 2026, on the Google Ads Developer Blog, describing updates launched across both APIs during the preceding week. Structured Data Files v10.1, which will carry label support for YouTube video assets, is scheduled for the coming weeks with no announced date.

Where: The APIs operate globally. Labels are applied to ads carrying declared assets when those ads serve in regions with local AI labelling regulations, which as of the publication date are the European Union, India and New York state. Support runs through Campaign Manager 360 API support and the Google Discord channels for the Display & Video 360 API and Structured Data Files.

Why: Transparency obligations under Article 50 of the European Union's AI Act become applicable on August 2, 2026, five days after the post, with penalties reaching EUR 15,000,000 or 3 percent of worldwide annual turnover. Parallel regimes in India and New York took effect earlier in 2026. The field gives automated creative pipelines a programmatic route to record a disclosure position that the advertiser, rather than the platform, is responsible for holding.