Delivery: files, dashboard & API

Campaign variants land as run-group files — poll GET /campaigns/{id} or the Campaigns pane. No hosted CDN feed on platform.

Last updated August 12, 2026

Each variant is a member of the campaign run group. When a member succeeds, its deliverable is a Files library object (same as chat OUTPUTS).

How to fetch

  • Campaigns pane — Campaigns: per-SKU tiles + download when a file exists.
  • REST — GET /campaigns/{campaignId} returns the run-group projection plus SKU-keyed variant status/outputs. campaignId = runGroupId.
  • Run groups — GET /run-groups/{id} is the same driver; Files GET /files/{id} for bytes.
  • MCP — get_campaign.

Retired: GET /api/v1/dco/campaigns/{id}/manifest, public cdn.wavemakr.com/dco/… URLs, VAST tags, dco.variant.updated webhooks, activation kits. Those return 410 or were never mounted on platform-api.

Trafficking today

Download files (or copy file URLs from the library) into your ad account. There is no hosted supplemental video_link / image_link feed writer on the platform DCO path. Re-engage when creatives need to change — see Sync.

Caps

24 variants per engage. For a larger catalog, slice rowIds and run sequential engages; each is its own campaign/run-group.