IAB Releases AI Transparency Framework v2 for Marketing Automation

TL;DR

The Interactive Advertising Bureau released an updated AI Transparency and Disclosure Framework v2 on August 18, 2026 that tightens how advertisers describe AI involvement in ads, where labels must appear, and what proofs teams should log. If you run cross platform campaigns, align creative level labels with each platform's policy switches so the same disclosure intent flows from asset to delivery. The guidance dovetails with Google's July policy update and new EU transparency obligations, and it is designed to be implemented inside typical ad tech pipelines without breaking pacing. The practical outcome for marketing automation is a documented, repeatable disclosure workflow that touches creative, trafficking, and analytics.

What changed in IAB Framework v2

The headline is scope and specificity. Version 2 turns a general principle into concrete implementation guidance that most media and creative teams can operationalize in existing tools.

• A single taxonomy for AI involvement. V2 defines a simple ladder of involvement types, from AI assisted edits to fully synthetic imagery and audio. The ladder maps cleanly to creative review checklists and can be attached to asset metadata.
• Placement and prominence. V2 clarifies that disclosures must be visible and understandable where a typical user would notice them, which for video means the opening seconds and for static placements means inside the creative frame or immediately adjacent to it.
• Platform handoff. The framework treats platform label toggles as an extension of creative intent rather than a substitute. If your asset carries a visible disclosure, your corresponding ad placement should also set the platform's label where available so the two do not contradict each other.
• Proof and audit. Teams should capture a short event level trace indicating who applied the disclosure, on what creative and campaign, with what label text, and under which policy rationale. This can live in your data warehouse next to ad delivery logs.

The update was timed against two other changes that matter in day to day trafficking. Google documented a dedicated AI label setting for ads and assets in July 2026, and the European Commission announced transparency obligations on August 2, 2026 that many global brands will adopt as baseline. See Google's policy documentation and the Commission's notice for details.

Why this matters across platforms

Regulators and platforms are converging on simple expectations. If AI shaped a realistic ad experience, tell people clearly, and keep records of how you decided. The operational cost is low compared with the risk of removal or account holds when policies tighten under pressure.

Google Ads and YouTube

Google's July update added an AI label control for certain ad and asset types. The control does not replace creative level disclosures. It complements them so that the rendered ad and the platform metadata describe the same state. Teams should implement both. For policy coverage and examples, review the official page on updated AI labeling requirements in Google Ads.

TikTok and creator economy formats

TikTok's policy and seller guidance call out when AI generated scenes or voices must be labeled, especially when they depict realistic people or events. The safest pattern is a visible on screen disclosure in the first three seconds plus the platform toggle, with approvals logged to your ad ops system. That pattern also generalizes to Reels and Shorts.

EU transparency rules and global harmonization

If your media mix reaches the EU, the August 2 communication from the European Commission makes the harmonization decision simple. Adopt a global disclosure pattern that satisfies the stricter regions and apply exceptions only where a placement cannot render inline labels. This avoids duplicating creative versions by market.

A practical implementation model for cross channel teams

The fastest path is to treat disclosure as just another required field in your asset pipeline and to render labels inside the creative by template.

1. Extend your asset schema with a disclosure field. Examples: none, AI assisted edit, image generated, video generated, voice cloned. Require a rationale and approver.
2. Render a standard label element in your creative templates. For video, fade in at second zero and hold for at least three seconds. For static assets, reserve a footer strip or corner badge.
3. Map the disclosure field to platform level toggles. If the platform offers a label control, set it from the same field. Otherwise, rely on the creative label.
4. Log delivery side evidence. Join your disclosure field to impression logs so audits can show what users saw, what the platform recorded, and who approved the setting.

Below is a sample of minimal metadata you can attach to a creative record in your creative service or DAM.

{
  "creative_id": "crv_9472a",
  "campaign_id": "cmp_fall_launch_2026",
  "ai_disclosure": {
    "status": "image_generated",
    "label_text": "Made with AI",
    "approver": "qa_ops@brand.com",
    "rationale": "Background and product renders were synthesized",
    "applied_at": "2026-08-20T15:22:11Z"
  }
}

Where ButterGrow and OpenClaw fit

Disclosure is a coordination problem. You need the same label choice to follow the asset as it moves from creative to media to analytics. Using workflow orchestration lets you enforce that as a policy instead of a manual checklist.

• Use the AI marketing features to define a disclosure policy that blocks publishing when the disclosure field is empty or inconsistent. See what ButterGrow does in the product overview for how these checks integrate with assets and playbooks. the feature set
• Build a small approval flow that requires a reviewer to confirm the label text before publishing. You can get started in minutes using the onboarding flow and wire it to your asset store. get started in minutes
• If your creative templates live outside ButterGrow, add a post render check that inspects pixels for the label element to catch missing overlays. Keep the policy inside your orchestration so it runs in the same place as your trafficking jobs.

For background on provenance standards, see how platforms are accelerating C2PA adoption and why that matters for brand safety and trust. That analysis covers how content credentials flow across tools and where provenance can augment simple on screen labels. Platforms accelerating C2PA adoption in marketing

A short comparison: creative label only vs platform toggle only vs both

The table below shows how each pattern performs against the expectations set by IAB v2 and common platform policies.

Pattern	User clarity	Platform compliance	Auditability	Cross channel consistency
Creative label only	High if placed prominently	Medium when the platform expects a metadata flag	Medium, proof depends on creative archive	Medium, relies on creative versioning
Platform toggle only	Low when the label is not visible in the frame	High where the platform supports AI labels	Medium, depends on platform logs only	Low, varies by platform support
Both creative label and platform toggle	High in frame plus metadata alignment	High on platforms with label controls	High, two data sources plus human approval	High, same field drives both sides

The combined approach reduces false negatives in moderation systems and makes human review simpler when regulators request evidence.

Common edge cases and how to handle them

Edge cases are where most policy tickets originate. Solve them once in your templates and job runners to avoid repeated work.

• Partially synthetic scenes. If a background plate is generated but models and product footage are real, use image generated and make sure product integrity is not compromised by the overlay.
• Synthetic voiceover on live footage. Treat voice cloned as AI involvement even if the visuals are simple edits. Add a visible caption in the open and keep a longer label in the description where allowed.
• Dynamic creative optimization. If your system swaps in generated variants at render time, force the disclosure field to the highest involvement level across the components, and log the generator version in case of future questions.
• Social formats with limited text fields. When a platform cannot display an inline badge, use the first three seconds plus a caption. If neither is available, consider excluding that placement for generated assets.

Rollout plan for the next 14 days

You can implement a compliant disclosure pipeline without disrupting live spend. Treat this like any other policy change in ad ops.

Step 1Inventory assets and set a baseline

Export a list of active creatives and annotate the disclosure field based on what the team knows today. Prioritize high reach campaigns and video units. Add a place to record the label text and the approver.

Step 2Update templates and rendering

Add a reusable overlay component for video and static formats. Set the default to appear automatically when the disclosure field is not none. Ensure the element meets size and contrast recommendations for readability on mobile and CTV.

Step 3Map to platform switches

Create a mapping table from your disclosure field to each platform's toggle. For Google Ads, wire the new AI label control where supported. For TikTok and short form video, use the platform's disclosure and seller guidance as a template.

Step 4Add policy checks to workflows

Insert pre flight validations in your orchestration that block publishing when the disclosure field is missing or when a platform toggle is required but not set. Capture a human readable error that points the trafficker to the fix location.

Step 5Turn on audit logging

Store the disclosure choice, label text, approver, and render timestamp with campaign and creative IDs. Use a nightly job to reconcile creative intent, platform settings, and delivery logs for a random sample of impressions.

Step 6Run a compliance fire drill

Pick three top campaigns and simulate a regulator or platform policy review. Show how you decided the disclosure level, where the label appears, and the approval trail. Use the drill to update your checklists.

Long tail questions you should be able to answer

Treat these as prompts for runbooks or internal documentation so your team is ready when review queues get tight.

• How to implement AI disclosure labels in ads across video, display, and social without duplicating creative versions.
• IAB AI transparency framework v2 checklist that maps to your asset schema, trafficking controls, and audit logs.
• EU AI transparency rules for advertisers and how they influence your global default.

Measurement, QA, and change control

Disclosure work touches templates, metadata, and ad server settings. That earns a place in your change control calendar and QA plan.

• Add a pre publish screenshot capture for video and static that verifies the label element renders correctly on representative placements.
• Track delivery metrics for any creative where labels were newly added and watch for material changes in CTR or view rate. Most teams will see minimal impact when labels are placed correctly.
• Document an exception process for creative that cannot carry an inline label due to legal or brand constraints. Those exceptions should be rare and short lived.

How ButterGrow customers can move faster

Teams using ButterGrow already have orchestration, templates, and policy checks in one place. You can centralize disclosure logic, enforce it before creatives go live, and keep evidence for audits next to your other delivery traces.

• Review the product capabilities to understand how policy checks, creative rendering, and approvals connect inside the product.
• If you want a guided setup, follow the onboarding flow to wire your asset store and ad accounts, then add the disclosure field to your creative schema.
• If you have questions about scope, exemptions, or how proofs are stored, see answers to common questions and reach out through your account team if you need an enterprise review.

If you want a policy aware disclosure pipeline that spans creative, ad ops, and analytics, ButterGrow's platform can enforce labels, set platform toggles, and log evidence with minimal engineering time. Start with ButterGrow and connect your accounts, then enable the disclosure policy in settings to see it in action. get started in minutes

References

• IAB announces AI Transparency and Disclosure Framework v2 - Official release with summary of changes and implementation intent.
• European Commission news on transparency obligations for AI - Background on new EU expectations that influence global disclosure baselines.