The most expensive AI disclosure problem rarely begins with a label. It begins when nobody can answer a simple upload question: was this final asset generated, meaningfully edited, or merely cleaned up?
That question now appears inside the advertising workflow. In July 2026, Google began rolling out AI-label controls across Google Ads, Display & Video 360, Campaign Manager 360, Merchant Center and Ads Editor. Assets designated as AI-created or edited can surface disclosure through “How this ad was made” or “About this Ad”; some campaigns targeting the European Union, India and New York can also receive visible overlays. Google is equally clear that using the setting does not, by itself, guarantee regulatory compliance.
For global brands buying production from China, the commercial implication is concrete: the final video file is no longer the whole handover. Production must also deliver enough provenance, transformation and release information for media, legal and regional teams to make the next decision without reconstructing the edit history.
What Google changed—and what the update does not decide
Google’s July 9, 2026 policy update confirms three operational choices. Advertisers may place text or visual labels directly inside AI-generated or AI-modified image and video ads; they may use a platform AI-label control; and Google may automatically label certain assets made with its own AI tools.
The DV360 implementation guidance makes the workflow more specific: an uploaded creative can be designated as AI-created or edited, asset-library items can be reviewed, and Google-generated assets can carry machine-readable SynthID and C2PA information. But the same guidance warns that the platform setting is not a legal safe harbor.
This matters because “AI was used” is too broad to be a production specification. Google notes that requirements differ by region and content type. The EU AI Act’s Article 50 also distinguishes machine-readable marking from audience-facing disclosure, and it treats assistive standard editing differently when it does not substantially alter the input or its meaning. The right production response is therefore traceability plus a decision route—not a blanket watermark on everything.
A global master can still fail at the last mile
Consider a product campaign built from live-action product footage, an AI-expanded location, a synthetic voice and a replaced background performer. The agency supplies a 30-second master, a 15-second vertical cut and six language versions. The output count looks healthy, yet four delivery questions remain:
- Which shots only received cleanup, and which changed a person, place, event or product behavior?
- Did the final export preserve machine-readable provenance, and was it still present after transcoding?
- Does each market-platform combination require an in-platform declaration, a visible disclosure, or both?
- Who checked that labels, captions, product claims and calls to action do not collide in the served format?
Aspect ratio and language describe files. Market, platform and disclosure status describe deployable assets. Procurement should count the latter.
The ONCE STAMP handover card
ONCE recommends a STAMP card for every commercial release that includes meaningful AI generation or alteration. It is not a compliance certificate. It is a compact factual record that allows brand, production, legal and media teams to make their respective decisions from the same source.
S — Source
List the source and licensed scope of live footage, product images, likenesses, voices, music, fonts, references and third-party assets. Re-generating an asset does not cure an unclear right.
T — Transformation
Describe what the system actually changed. Separate full generation, object replacement, outpainting, background replacement, digital doubles, voice cloning and translated speech from restoration, denoising and routine color work. For video, record this by shot or time range rather than applying one vague note to the entire film.
A — Audience
Identify target countries, languages, platforms, ad types and sensitive audiences. Realistic people, health or financial claims, children, politics and public-interest contexts deserve a higher human-review route than a simple product-background extension.
M — Marking
State whether each release uses an account-level declaration, visible in-asset text or symbol, audio disclosure, or a combination. Record language, duration, safe area and placement. If the platform adds an overlay, include the final preview in approval so the label does not obscure a feature, caption or CTA.
P — Proof
Archive the approved file, a durable version identifier, any C2PA or Content Credentials verification, the platform preview, approver, date and scope. The C2PA specification can make provenance records tamper-evident; it does not prove that a product claim, price or likeness permission is true.
Change the denominator from exports to deployable releases
A source asset can become many independent deliverables after resizing, compression, caption replacement and re-encoding. Each final file may need a new provenance and disclosure check. A more useful internal comparison is:
Fully loaded cost per deployable release = (creative and production + source and rights review + AI-change logging + market/platform disclosure design + versioning + final verification + approval archive) ÷ releases accepted for their intended conditions.
This is a management model, not an industry price benchmark or legal formula. Its purpose is to expose late-stage work. Twenty inexpensive generations do not equal twenty usable assets if only six have a known source, approved disclosure route and valid usage scope.
Route the work by transformation risk
Assistive edit route
Use this for denoising, color work and ordinary cleanup that does not change the communication meaning. Keep a light version record and confirm the actual market and platform requirement.
Material generation route
Use this for fully generated environments, actions or voices, or edits that could change what the audience believes happened. Determine account disclosure, visible labeling and safe-area requirements before final exports.
High-risk human route
Use this for realistic digital doubles, medical or financial claims, children, political content and images likely to be mistaken for evidence of a real event. Production supplies complete facts and version records; accountable brand, legal or specialist reviewers make the final decision. Separate market releases may be more reliable than forcing one master everywhere.
Six questions for the next production brief
- Which countries, platforms and ad types will receive the work?
- Which shots, voices or people will be generated or materially altered?
- Who decides disclosure, and who approves claims and likeness rights?
- Will the vendor deliver shot-level change notes and a release-level STAMP card?
- Who rechecks labels and provenance after caption swaps, transcoding or recuts?
- Are platform-rendered overlays included in final visual QA?
If these questions have no owner, “exported” should not be treated as “ready to run.” ONCE’s AIGC commercial production workflow starts with the job of each shot, the live-action truth anchors, the intended channels and the planned version set—then carries those decisions into delivery.
Sources and scope
- Google Advertising Policies Help, “Updates to AI labeling requirements (July 2026),” posted July 9, 2026.
- Google Display & Video 360 Help, “Use AI content label settings and disclosures in Display & Video 360.”
- European Commission AI Act Service Desk, Article 50.
- C2PA, Content Credentials Specification 2.2.
- IAB, AI Transparency & Disclosure Framework.
This article separates verified platform capabilities from ONCE’s production analysis and from decisions that remain market-specific. Interfaces and regional obligations can change; final release decisions should be checked against the actual account, target market, asset and contract.
