Amazon DVA+ rolls out from late October: get your video assets ready
Amazon says DVA+ begins rolling out in late October and advertisers approve creatives before launch. A checklist for preparing holiday video assets with Sume.

Amazon's Ads Agent page, read on 2026-10-01, says DVA+ rolls out beginning late October and that advertisers approve creatives before launch. It does not publish video specs or prices for DVA+, so the useful work this month is to have a library of approved, correctly finished product clips ready, not to guess at a spec. Sume can produce and finish that library by API.
What does Amazon say, and what is missing?
| Item | On the page |
|---|---|
| DVA+ | Rolls out beginning late October |
| Creative tools | Make TV-quality video and display images from existing product pages |
| Availability of Full-Funnel Campaigns | All US advertisers |
| Approval | Advertisers approve creatives before launch |
| Video specs, length and pricing | Not given on the page |
What should I prepare now?
Build the library so that any spec Amazon publishes later is a small change, not a rebuild.
- Make one hero clip per top SKU with a catalog Format, queued as a bulk run.
- Cut each hero into a short, medium and long version with
POST /v1/video-trimat $0.02 per job. - Add an end card and fades with a timeline render at $0.10 per output minute.
- Add captions with
POST /v1/video-captions, $0.20 per job for videos up to 60 seconds, after you pick the winners. - Keep the media.sume.com URL and the run id for every approved clip, so you can find it again.
How do I cut three lengths from one hero?
The trim endpoint makes a new file for each window, and the source is never changed. Use a different Idempotency-Key for each length.
for L in 6 15 30; do
curl -sS -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: hero-001-cut-$L" \
-d "{\"video_url\": \"https://media.sume.com/artifacts/artf_demo/hero.mp4\", \"start\": 0, \"duration\": $L}"
echo
doneHow do I keep the approved clips organised?
Amazon says advertisers approve creatives before launch, so the unit of work is an approved clip, not a draft. Name each Idempotency-Key after the SKU and the version, for example hero-sku42-v1, and write the key, the run id and the media.sume.com URL to one row of your own sheet. A durable URL on media.sume.com stays public, so the same file can be handed to an agency or an ad console later.
Do the review pass before you cut lengths. A flaw in the hero is then fixed once and not three times.
What are the limits?
- The three lengths are examples, not Amazon requirements. Use the lengths Amazon publishes when it does.
- The source must be on media.sume.com; import it first with
POST /v1/media-imports. - The late-October date is Amazon's statement about a rollout, so your account may see DVA+ later.
- Sume does not upload into Amazon Ads or approve anything for you; Amazon's review stays yours.
Sources
Related posts
More in Use cases
- Storyboard animatic from stills with a Sume timeline
Check pacing and shot order before paying for video: render storyboard stills as a silent Timeline 1.0 animatic, with an unbilled plan call first.
- AI Act marking exemption for B2B and industrial output: how narrow
The Commission FAQ says a narrow Article 50(2) marking exemption is envisaged for B2B or industrial outputs, with conditions in the guidelines. What it lists.
- AI Act Article 50 fines: up to EUR 15M or 3%, and who enforces it
The Commission's Article 50 FAQ says fines can reach 15 million euros or 3% of worldwide turnover, enforced mainly by national market surveillance authorities.
- AI Act Article 50 for non-EU providers: output used in the EU
The Commission FAQ says providers outside the EU are subject to the AI Act if their system's output is used in the EU. How it defines provider and deployer.
Written by Sume