Classify, freeze, and publish an approved release.
The final Delivery step describes the ad for downstream systems, selects technical formats, freezes the current decision configuration, and controls whether that release is live.
Classify the ad product
Use the IAB Ad Product taxonomy to describe what the creative advertises. Choose manual classification when the category is known and approved; use auto-detect as a suggestion that still requires review.
- Select the most specific accurate category.
- Do not classify by audience when the taxonomy describes the advertised product.
- Revisit classification after a material offer or product change.
- Record any buyer or platform-specific category requirement.
Choose an export profile
Available profiles include common downstream presets such as:
- Generic IAB — standards-oriented baseline.
- Google DV360 — destination-oriented defaults.
- The Trade Desk — destination-oriented defaults.
- AdsWizz — audio advertising delivery defaults.
A profile is a starting point. Compare its VAST and audio choices with the current insertion order or publisher specification.
VAST and audio formats
Choose a supported VAST version such as 4.2, 4.1, or 4.0 and one or more required audio renditions. The format catalog includes MP3 and PCM/WAV combinations with different sample rates, bit depths, or bitrates.
Review the draft state
A project that has not been published is a draft. Before publishing, verify:
- creative and record decision rules;
- request parameters and fallbacks;
- taxonomy and export profile;
- VAST version and audio formats;
- licences, compliance review, and campaign approval;
- preview results for representative requests.
Preview a release
- Save current project configuration.
- Open Versions or the available preview action.
- Generate or open the preview tag.
- Request default, targeted, no-match, and boundary scenarios.
- Confirm media URL, format, duration, tracking behavior, and audio.
- Record the tested project state and expected release version.
Publish
- Confirm that your role is authorized to publish.
- Review the final configuration summary.
- Publish to create a new immutable release.
- Wait for the release result; do not repeat the action while it is pending.
- Verify that the new version appears in history with the expected status.
- Run a post-publish smoke request before sending traffic.
Versions
Version history provides immutable campaign snapshots. Use it to identify what was live at a particular time and to separate a working draft from the active release.
| Control | Meaning | Operator action |
|---|---|---|
| Preview | Exercise a release without changing its configuration. | Test representative parameters and inspect output. |
| Enable | Allow the selected published release to serve. | Use only after smoke testing. |
| Disable | Stop serving the release without rewriting it. | Use for incident containment or campaign stop. |
| Publish new version | Freeze the current approved draft. | Use after any material creative, rule, taxonomy, or format change. |
If status, taxonomy, or versions appear empty
Do not immediately conclude that nothing has been published. Reload once, confirm account/project and role, then check whether other Delivery panels load. If the state remains unexpectedly empty, stop the publish workflow and contact support with project name, time, and visible panel state.
Post-publish checklist
- Version — the expected immutable release exists.
- Status — enabled/live state matches the campaign plan.
- VAST — requested version parses at the destination.
- Media — every required rendition is reachable and playable.
- Decisioning — targeted and fallback requests select correctly.
- Monitoring — owner and stop procedure are known.