Meta final-week political ad block: finish video early
Meta blocks new political, electoral and social issue ads in the final week of the US campaign. Submit every video cut, with AI disclosure, before then.

Meta says it will block new political, electoral and social issue ads during the final week of the US election campaign. Ads that had at least one impression before the restriction period may keep running. So every cut you want to run has to be finished, disclosed and live, with at least one impression, before that week starts.
Rules below are from Meta's 2026 midterms post, read 2026-09-30. Sume's side comes from its Timeline and bulk runs docs. This is not legal advice.
What does Meta require for these ads?
Political advertisers must complete an authorization process and include a "paid for by" disclaimer; ads are stored in the Ad Library for seven years. Advertisers must also disclose when they use AI to create or alter ads about elections, politics or social issues. When disclosed, Meta adds information to both the ad and its Ad Library entry.
What does a production calendar look like?
Count back from the first day of the restricted week, not from election day.
| Step | What to finish | Why |
|---|---|---|
| Last day before the block | Ads submitted and delivering | New ads are blocked after this |
| Days before that | Review and approval | Leave time for rejections and edits |
| Before review | AI disclosure answered, authorization done | Required for political ads |
| Earliest | All variants rendered | Nothing new can be added later |
How can I render many variants before the deadline?
Timeline 1.0 has an unbilled compile preflight, POST /v1/timeline-1.0/plan, that returns duration, segment count and the estimated cost before anything is reserved. A render is $0.10 per output minute. Renders are async by default, so a batch can run overnight. For many variants, a bulk run queues up to 100 Format runs server-side with a concurrency of 1 to 16; see Format bulk runs.
What should I record for the AI disclosure?
For each cut, note whether AI created or altered it, and keep the Sume job ids next to the file names. That way the answer you give in the disclosure toggle matches how the video was made. The platform-by-platform view is in the disclosure checklist.
Sources
Related posts
- Google Ads election ads: the altered or synthetic checkbox
- TikTok political ads policy: paid ads banned, with one exception
- AI generated video disclosure checklist: TikTok, YouTube, Instagram
- Meta ads bulk upload: push AI videos to your ad account
- Sume Format bulk runs: queue up to 100 renders in one request
More in Use cases
- Midjourney inpainting via API: mask_url on GPT Image 2.5
Midjourney's edit model now changes only selected pixels. Sume lists no Midjourney model; its masked inpainting runs on GPT Image 2.5 through mask_url.
- Midjourney --tile seamless pattern API: what Sume accepts
Midjourney fixed --tile seams for V8.1 and V8.2 on Sep 24, 2026. Sume's image API has no tile flag; here is what a pattern request can set instead.
- New York synthetic performer ad law and AI avatar ads
NY S8420A requires a conspicuous disclosure of synthetic performers in ads. What it covers, what it exempts, and how to burn a line onto an avatar ad.
- Pinterest Performance+ creative: feed it asset variations
Pinterest's new Performance+ creative model selects at the asset level. Make distinct hook and image variations in one Sume bulk run and upload the keepers.
Written by Sume