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 simulate 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.
- 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 all dynamic tokens and defaults.
- Review POI lists and feed bindings.
- Identify the request parameters the integration will send.
- Decide the safe behavior when data is missing.
Delivery ribbon
| Panel | Question it answers |
|---|---|
| Which creative | Which message or treatment should this request receive? |
| Which record | Which POI, event, or feed entity supplies dynamic fields? |
| Parameters | Which request inputs are accepted and how can they be simulated? |
| Classification | How is the ad described for standards and downstream platforms? |
| Versions | Which immutable configuration was published, and is it enabled? |
The decision order
- RequestRead user and campaign parameters.
- CandidatesLoad records for detected subjects.
- Which recordFilter, score, and choose each record.
- ResolveCompute fields and dynamic values.
- Which creativeRotate, sequence, or evaluate conditions.
- ServeRender or retrieve the release outcome.
Configure Parameters
Parameters document the inputs used by decisioning and give the simulator concrete values. Add custom parameters only when the integration can reliably supply them.
- Use a stable
user_idfor sequence or user-level rotation semantics. - Use clear names such as
audience,placement, orcampaign_region. - Define the expected type: scalar, list, number, boolean, or coordinates.
- Test missing, empty, malformed, and unexpected values.
Simulate before publishing
- Open Parameters and enter representative request values.
- Use Pick on Map where listener coordinates matter.
- Evaluate Which record and inspect eligible/winning candidates.
- Inspect resolved fields and the creative condition.
- Preview the selected creative and dynamic values.
- Repeat for fallback and boundary cases.
Recipes, AI, and manual control
Recipes provide reusable business patterns. Configure with AI can propose an expression or rule from an instruction. Manual mode exposes the final deterministic configuration. Regardless of how it was created, review and simulate the saved rule.
Save versus publish
Autosave updates the editable project. Publish creates an immutable release for live delivery. Later edits do not retroactively alter an existing release; publish a new version after completing review.