Connect script values to data and rules.
Type a left brace to insert a data field, use Dynamic Properties to inspect the binding, and use custom criteria when the built-in catalog does not express the campaign decision.
Open the data token picker
- Place the caret where the value should be spoken.
- Type {.
- Choose a source family.
- Navigate to a category, list, league, or entity.
- Select the field.
- Inspect the resulting token and Dynamic Properties.
The token stores a structured binding, not only its visible label. Avoid copying only the rendered text when you intend to preserve the data source.
User context
User context contains request-level information about the listener and environment. Available dimensions depend on the configured services.
Location
Fields such as city or coordinates associated with the listener request.
Weather
Weather values resolved for the relevant listener context.
Request parameters
Campaign-defined fields such as audience, placement, or another supplied value.
For example, choose User context → Location → City to insert the listener city. Always provide fallback wording for requests without an accurate location.
Dynamic Properties
The properties panel is the control surface for the selected dynamic segment or token. Depending on type, it can show source, category, field, formatting, options, default, preview, list metadata, or expression configuration.
- Confirm the source and field, not only the visible example.
- Use the required spoken or raw format.
- Check option defaults.
- Do not assume a preview value will be saved as the runtime result.
Create a custom criterion
- Select the text and open Dynamic Content.
- Create a custom criterion.
- Name the decision in business language.
- Add a default and the required alternatives.
- Define or generate the expression for each non-default path.
- Validate, preview, and save.
Keep one criterion responsible for one business question. Compose several simple decisions instead of one expression that no campaign operator can explain.
Expression inputs
| Input family | Typical use | Example concept |
|---|---|---|
| User/request | Listener or request context. | Coordinates, audience, user ID, time. |
| Field/record | The candidate currently being evaluated. | POI coordinates, category, sports score. |
| Computed field | A reusable derived value. | Distance in kilometres. |
| Literal | A controlled threshold or label. | Maximum distance or named segment. |
Validate and preview
Validation distinguishes an invalid expression from a transport or service failure. A valid expression is not automatically a good campaign rule: test representative, boundary, and missing-data inputs.
- A matching example.
- A non-matching example.
- The exact threshold boundary.
- A missing optional field.
- An unexpected string, list, or numeric value.
- The default outcome.
Resolution order
- RequestReceive user and custom parameters.
- CandidatesLoad relevant feed or POI records.
- Record ruleFilter, score, and pick a record.
- FieldsResolve raw and computed values.
- Creative ruleSelect the message strategy.
- RenderResolve tokens and produce audio.