Overview
A Creative in v2 is a creative manifest — a structured bundle containing uploaded assets (images, video, HTML, VAST tags), an optional brief, brand info auto-resolved from the campaign’s advertiser, and a target ADCP format. Manifests are nested under campaigns and propagate to media buys at execution time.New in v2: creatives are no longer stored at the advertiser level and referenced by campaigns. They are created directly under a campaign at
/api/v2/buyer/campaigns/:campaignId/creatives/.... The model is also fully manifest-aligned with the AdCP creative manifest spec.Field-name exception: Creative manifests use snake_case field names (
creative_id, campaign_id, format_id, template_id, brand_domain, target_format_ids) because they are passed through verbatim to the ADCP wire-format. This is an intentional exception to v2’s general camelCase convention — see the migration guide for context.Why this changed
V1 treated creatives as advertiser-level assets reused across campaigns. V2 tightens the model so:- Each campaign sees exactly the formats its selected products require (
creativeFormats.required) - Asset uploads happen in a single multipart request with the manifest metadata
- Format and template auto-detection runs against the campaign’s product mix
- Tracking macros and brand info are resolved from the campaign + advertiser context
Key fields
| Field | Type | Notes |
|---|---|---|
creative_id | string | Manifest ID |
campaign_id | string | Owning campaign |
name | string | Human-readable name |
message | string | Optional creative brief / direction text |
template_id | string | Creative template (display_image, display_html, video_standard, vendor tags, etc.) |
format_id | object | { agent_url, id } — legacy (v1 named-format) format reference. Mutually exclusive with format_kind. |
format_kind | string | Canonical (AdCP 3.1) format selector — a bare enum (image, video_vast, video_hosted, …) with no agent_url. Video/audio duration rides in params (duration_ms_exact / duration_ms_range), not on format_id. See the glossary. |
target_format_ids | array | Formats from campaign products this manifest can serve |
brand_domain | string | Auto-resolved from the campaign’s advertiser |
assets | array | Uploaded assets (id, type, MIME, public URL, source) |
preview_url | string | URL to processed HTML preview hosted on GCS |
tracking | object | Auto-generated impression and click tracker URLs |
sync_status | object | { synced, agent_count, last_synced_at } across sales agents |
frequencyCaps | array | Buyer-defined caps on this creative |
Asset types
V2 assets cover the full ADCP type spectrum:| Type | Purpose |
|---|---|
IMAGE | JPEG, PNG, GIF, WebP, SVG |
VIDEO | MP4, WebM, QuickTime |
AUDIO | MP3, WAV, OGG |
HTML | Inline content or hosted URL |
JAVASCRIPT / CSS | Companion script and style assets |
VAST | VAST tag (URL or inline XML) — renamed from v1’s VIDEO_VAST |
URL | Clickthrough, tracker pixel, or VAST URL with explicit url_type |
FONT / LOGO / DOCUMENT / TEXT | Supporting assets |
url_type: CLICKTHROUGH, TRACKER_PIXEL, TRACKER_SCRIPT, or VAST. Webhook assets enable server-side dynamic content rendering (DCO) with HMAC or API-key signing.
Lifecycle
Discover required formats
GET /api/v2/buyer/campaigns/:campaignId/creatives/templates returns available templates and the deduplicated campaign_format_ids from selected products. Each product’s required formats are also broken out under campaign_products. The full registry of formats across agents is available at GET /api/v2/buyer/formats.Create the manifest
POST a multipart request with files + JSON metadata. Scope3 auto-classifies assets, processes HTML to rewrite local references to CDN URLs, inserts ADCP macros, and generates a preview.
Validate coverage
GET /api/v2/buyer/campaigns/:id returns creativeFormats: { required, covered, missing }. Upload more manifests until missing is empty.Propagate to media buys
On campaign execute, the manifests sync to each sales agent for the formats they support. Sync status is reflected in
sync_status on each manifest.Conversational creative sessions
Creative sessions are the agent-native path for buyers who want to generate, compare, refine, validate, and save creatives without handling manifest details directly. The intended user flow is:- Idea — the buyer describes the channel, audience, goal, and source assets.
- Draft gallery — a creative adapter returns multiple draft variants for human review.
- Refine — the buyer gives natural-language feedback like “make the book more prominent” or “less busy.”
- Evaluate — draft checks are advisory; final hard/blocking checks stop finalization.
- Finalize — the approved leaf is saved as a campaign creative manifest.
POST /api/v2/buyer/campaigns/:campaignId/creative-sessions to start a session. The response is designed for MCPUI and includes the draft variants[], asset_store, renderer_capabilities, rendering_model, staged evaluator badges, and format_renders[] once a final is approved.
Creative sessions are review workflows. They do not replace campaign creative manifests. Finalization is the transition point where a selected draft/refinement becomes a normal campaign creative with
creative_id, format_id, assets, preview, and sync status.Asset lifecycle
Creative production uses three related but distinct asset layers:| Layer | What it is | Stored as | How to use it |
|---|---|---|---|
| Source asset | Buyer-supplied input such as a book cover, product photo, logo, DAM URL, catalog image, audio file, or reference image | source_asset and asset_store.assets[] inside the creative session | Treat as raw input. Preserve locked assets exactly; track role, provenance, rights, checksum, dimensions, and render crop/mask metadata when available. |
| Draft variant | A generated or composited creative direction for review | variants[] with preview URL, quality, status, lineage, and evaluator checks | Use for exploration. Drafts may be discarded, branched, or refined. They are not campaign creatives until finalized. |
| Final creative | The approved execution saved to the campaign | Creative manifest under /campaigns/:campaignId/creatives | Use for delivery. It carries the final render, linked assets, text assets, ADCP format ID, tracking, preview, and sync status. |
- Set
locked_asset: true,can_transform: false,role: "product"(or the closest role), and specificpreservation_notes. - Keep provenance separate from rights.
source: "upload"orsource: "dam"says where the asset came from;rights.statussays whether it is cleared. rights.status: "unknown"is a non-blocking review warning for final approval.restrictedorexpiredblocks finalization.- If the source image includes studio background or whitespace, provide
render_crop,subject_bounds, or a transparent cutout/mask when available. Cropping is a preservation-safe fallback; a real cutout produces cleaner final compositions.
Seller-specific versions
The campaign’s selected products determine which seller formats need coverage. Use the creative template/format endpoints before and after finalization:GET /api/v2/buyer/campaigns/:campaignId/creatives/templatesshows required campaign formats and available templates.- Start a creative session against the best matching creative adapter and target format.
- Finalize the chosen direction into a creative manifest.
- Re-check
creativeFormatsonGET /api/v2/buyer/campaigns/:campaignId. - If
creativeFormats.missingstill contains seller formats, generate or adapt seller-specific manifests for those formats.
format_renders[] is the review surface for publisher/format previews. It helps a buyer inspect what the final creative looks or sounds like in a particular canonical renderer. The actual delivery object remains the saved creative manifest and its synced seller-specific format coverage.
Performance loop
Creative work does not end at finalization. The full performance cycle is:- Create or update campaign goals — use
performanceConfigon the campaign when optimizing toward events or metrics. - Launch with format coverage — execute only after required creative formats are covered.
- Collect delivery and outcome data — use reporting plus conversion/measurement ingestion (
log_event, measurement data sync, or measurement records depending on integration). - Compare creative performance — inspect performance by campaign, media buy, package, and creative where reporting dimensions are available.
- Iterate — duplicate or start a new creative session from the winning direction, then refine the creative based on observed performance and seller feedback.
The Anjali/The Shift prototype exercises the creative build, preview, evaluator, and finalization loop. A complete performance cycle also needs live delivery, measurement ingestion, reporting by creative, and an optimization decision that feeds a new creative iteration.
Evaluator strategy
Creative evaluators answer different questions at different moments. Treat them as a selected set of checks, not a single score.| Evaluator type | Question it answers | Typical stage |
|---|---|---|
| Core readiness | Is there a renderable preview and valid manifest structure? | Draft, final |
| Asset fidelity | Did locked assets stay intact, and are rights/provenance usable? | Draft, final |
| Brand/brief | Does the direction fit the campaign brief and brand guidance? | Draft, final |
| Format/seller | Does this execution satisfy the selected seller or publisher format? | Final |
| Policy/safety | Is there policy, claims, legal, or safety risk? | Final |
| Performance | Did it actually work after delivery? | Postflight |
- source assets and lock/rights metadata
- modality and renderer type
- campaign brief and brand guidance
- selected seller formats and publisher policies
- available adapter/seller evaluator capabilities
- postflight reporting and measurement data
Common operations
Create a creative manifest (multipart)
The endpoint accepts ametadata JSON field plus files[] form fields:
Creative creation is a single multipart request: a JSON
metadata field plus zero or more files parts (-F "files=@..."). The server accepts up to the configured MAX_FILE_COUNT files per request and pairs each file with the matching assets[].filename in the metadata.List manifests
search, includeFrequencyCaps. Pagination: take, skip.
Get / update / delete
Render an ADCP preview
preview_creative tool to render at native format dimensions. Useful for validation before publisher submission.
Format coverage on the campaign
When youGET /api/v2/buyer/campaigns/:id, the response includes:
missing is the prompt to upload more creatives. Coverage is computed against the formats every selected product needs.
Tracking macros
When the format supports it, Scope3 auto-injects:- An impression tracker URL as a
TRACKER_PIXELURL asset - A click tracker URL that wraps the original clickthrough — the original is preserved in the
rurlquery parameter
{CAMPAIGN_ID}, {DEVICE_TYPE}, {COUNTRY}, etc.) are filled at impression time. The tracking.supported_macros array on the manifest response lists which macros the format supports.
Format catalog
To inspect formats required by the campaign’s selected products:| Endpoint | Purpose |
|---|---|
GET /api/v2/buyer/campaigns/:campaignId/creatives/templates | List the deduplicated format IDs required by every product in the campaign and the available templates. |
GET /api/v2/buyer/formats | Cross-agent format registry (all formats discovered from sales agents). |
GET /api/v2/buyer/formats/:agentUrl/:formatId | Format details for a specific format on a specific agent. |
Propagation to media buys
At campaign execute, the manifest is synced to each sales agent that supports itsformat_id. The same manifest can serve multiple media buys; later updates re-sync. Use sync_status to confirm publishers have received the latest version.
Creative transport modes
Interchange chooses the creative transport mode per sales agent:- Creative library sync — sellers that advertise a creative library through
creative.has_creative_library: truereceive manifests throughsync_creatives, and packages reference them withcreative_assignments. - Inline creative delivery — sellers that advertise
creative.has_creative_library: falsereceive the creative manifest inline on each package that needs it.
creative.has_creative_library is null or absent), Interchange falls back to the seller’s advertised tools and uses sync_creatives when available.
If sync_creatives fails and the seller allows inline creatives, Interchange falls back to inline package delivery for that seller. If the seller is library-only and sync_creatives fails, the media-buy create or update request fails synchronously instead of silently continuing.
Related concepts
Campaign
Owning campaign — formats come from its products
Brand
Brand info auto-resolved from the advertiser