Turn a creative project into a decision system.
Delivery chooses the relevant data record, resolves dynamic content, selects a creative, and serves a frozen campaign release. Build and test the decision before publishing it.
When to use Delivery
Use Delivery when the audio response must be selected at request time rather than downloaded as one fixed file. Typical use cases include:
- Creative rotation — distribute impressions across alternatives.
- Sequencing — advance a known listener through a message order.
- Conditional messaging — choose copy from time, audience, or data.
- Nearest location — speak the best eligible POI for the listener.
- Your own data — speak the right product, store, or offer from a data collection.
- Live feeds — use the relevant sports or entity record.
- VAST delivery — publish a versioned advertising endpoint.
Prepare the project first
- Approve the creatives and names.
- Resolve required vocal synthesis and production settings.
- Confirm dynamic decision defaults and token formats.
- Review POI lists, data collections, and feed bindings.
- Identify the request parameters the integration will send.
- Decide what plays when a record or a spoken value is missing.
Delivery ribbon
The ribbon navigates the Delivery tab. Its groups are How your ad is chosen and Ad-server connection. The tab opens at Which record when that step is available.
| Panel | Question it answers |
|---|---|
| Which record | Which place, event, or data row supplies dynamic fields? Also lets you choose an optional source. |
| Which creative | Which message should this request receive? Shown when the project has more than one creative. |
| Parameters | Which additional values does the ad server send with the request? |
Publish, Share, and Feedback are top-bar dialogs available from every tab. Publish holds ad tags and version history. Share creates a review preview of a saved version or a snapshot of current work; it does not put content on air. Feedback holds the review conversation. Choose each tag's ad system and VAST version in Publish.
The decision order
- RequestRead listener context and request parameters.
- CandidatesLoad records from the selected source, when the project uses one.
- Which recordEvaluate computed fields, Include and Exclude rules, then pick a record or follow the explicit no-record choice.
- Which creativeRotate, sequence, run an A/B test, or evaluate conditions, using the selected record when needed.
- ServeResolve the creative's dynamic values and deliver a servable variant under the published release.
Configure Parameters
Parameters lists what the ad server must send with the ad request. Add a parameter only when the integration can reliably supply it.
Under Request parameters, each parameter has one expandable row. Enter the name your ad server sends. Add optional example values and a note; if a script criterion uses the parameter, its options and the value sent for each appear in the same row. Choose + Add request parameter for more values, such as a team, audience segment, or store ID. Rules read a declared value as request.parameters.<name>.
The page opens with How this works and Already handled for you, which say what the ad server sends and what Voxify resolves without a parameter.
Test before publishing
- Open Which record and choose Test to inspect the selected record and candidate reasons.
- Set the listener location, date & time, device, and request parameters your rules read.
- Open Test from Which creative to inspect the creative selected for that situation. For rotation, sequence, and A/B, this is one illustrative turn; a new listener starts at the first sequence position.
- Repeat for boundary cases and when no record survives.
- Listen to individual variants in Creatives using Criteria. This authoring preview does not run the Delivery rules.
Recipes, AI, and expressions
Recipes are ready-made conditions in Which creative. Configure with AI proposes a condition or a complete record rule from a description, and changes nothing until you apply the proposal. Show expression displays a rule as text. Regardless of how a rule was created, review and test it.
Save versus publish
Autosave updates the editable project. Publish creates a version and puts it on active ad tags. In the Publish dialog, add at least one tag, review Live now and Current project, then choose Publish. A further publish creates another immutable version, even when the editor has no changes. Later edits do not alter the version on air. Use History to inspect versions, make an earlier version live, or restore one to the editor.