Where to set the AI label: Ads Editor, DV360, CM360, SA360, more
Google's AI label setting exists in Ads, Ads Editor, Search Ads 360, DV360, CM360 and Merchant Center. How a Sume-made clip moves through them.

Google offers the AI label setting in six places: Google Ads, Google Ads Editor, Search Ads 360, Display & Video 360, Campaign Manager 360 and Merchant Center. Google's AI content label page says you can add labels directly to your creatives or use the AI label setting in several Google platforms, and links an instructional article for each one.
The Shorts ads asset page gives the reason in one line: AI regulations in the European Union, India and New York require that ads with certain AI-generated or edited assets include disclosures or labels.
Pick the surface by the job
The pages do not rank the tools, so this table maps each to the kind of work it usually fits, which is a planning aid, not a Google statement.
| Surface | Typical use of the clip | Where the Sume file arrives |
|---|---|---|
| Google Ads | Video campaigns, Demand Gen, Performance Max, Shorts ads | Asset library or campaign creation |
| Google Ads Editor | Bulk edits to many assets | Assets you already uploaded |
| Search Ads 360 | Search-led cross-engine management | Per Google's linked article |
| Display & Video 360 | Programmatic video | Creative upload |
| Campaign Manager 360 | Ad serving and trafficking | Creative upload |
| Merchant Center | Product feeds and shopping video links | Product data |
A shared workflow for a Sume clip
Whichever surface you use, the clip is made first and labeled second. Generate it with Sume video generation, cut it with video trim, and conform it with a timeline if you need a new aspect ratio; then upload the final MP4. Sume does not push the file or the label into Google's tools; the label is a setting in each Google product.
That separation is useful. You can keep one record per final MP4 (job ids for the steps that produced it, and the decision on 'created with AI' or 'edited with AI') and reuse it in all six places, so the label is consistent across Ads, Editor and the 360 tools.
Steps
- Make the final MP4 and record how it was produced.
- Decide the label once per asset.
- Open the product you traffic in and find its AI label setting in Google's article for that product.
- Apply the same decision everywhere the asset appears.
- Re-check the status after Google processes the upload.
Why one record beats six settings
The failure mode with several tools is drift: an asset is labeled as AI in Google Ads, but the same MP4 is uploaded unlabeled to a 360 tool by a different team. Viewers and regulators do not care which console a team used. A one-page record per asset, with the decision and the reason, prevents the mismatch.
Include in the record what was generated and what was only cut, so that when counsel asks whether a trimmed, captioned clip counts as 'edited with AI', the facts are on hand. Google's page does not list which operations count, so that is a question to settle before the campaign, not during it.
Caveat
Google says that using the setting does not guarantee legal compliance, and that it may add labels itself where required. If an asset shows a label you did not set, it may not be possible to remove it.
Sources
Related posts
More in Integrations
- Amazon Seller Assistant plugin for Claude: add listing media
Amazon's Seller Assistant plugin (beta with Claude) reads your listings and sales. Pair it with Sume's hosted MCP server to make the missing images and clips.
- Gemini wrote your UrlFetchApp call for Sume: a review list
Gemini in the Apps Script editor is in beta. Before you run generated code against Sume, check it against this list of headers, keys, retries and status.
- AgentCore Gateway Sume MCP target: pick authorization code or API key
AgentCore Gateway offers three OAuth grant types for an MCP target. Sume's hosted MCP issues only the authorization code grant, so the choices narrow to two.
- Bubble's agent can build API Connector calls: give it Sume's spec
Bubble's Agent can create API Connector calls on its own. Hand it Sume's OpenAPI JSON, the single-header rule and a free GET /v1/me to initialize.
Written by Sume