When to use it
Use a managed publication when the destination needs VAST rather than a raw hosted MP4. The publication step does not make an incompatible file compatible: the source must first pass inspection and produce a ready rendition for the destination profile. The current certification boundary is unchanged:- Google Ad Manager is the first end-to-end canary destination.
- Managed FreeWheel ingestion is not certified yet.
- A seller policy can narrow a certified destination profile, but cannot widen an unknown platform limit.
Publication flow
1
Obtain a ready rendition job
Scope3 prepares the canary job against the selected storefront and
destination profile. The job must be ready, and its source must remain
approved or promoted.
2
Publish the immutable rendition
Call
publish_rendition_vast with the advertiser, job, storefront,
publication expiry, and the approved HTTPS impression-tracking contract.
Supply a stable idempotency key and reuse it only for an identical retry.3
Give the returned URL to the ad server
The response contains
vastUrl, an HTTPS URL suitable for the destination
canary. The VAST document and its media set do not change in place.4
Revoke or rotate deliberately
Call
revoke_rendition_vast to disable the VAST URL and every embedded
media capability together. To replace a live publication, publish a new
immutable version with rotatePublicationUid and a new idempotency key.Delivery and security guarantees
- The public URL reveals no bucket, object name, or storage credential.
- Publication, tracking, and media authority all expire; the shortest valid authority is the effective delivery lifetime.
- Revoked, expired, incomplete, or no-longer-ready publications return
404without disclosing which check failed. - VAST responses are digest-verified and served with
no-storecaching. - Publication and revocation require buyer write authority and are scoped to the authenticated customer, advertiser, storefront, and rendition job.