Connect script values to data without inventing what to say.

Type a left brace to insert a data token, choose how that occurrence should be spoken, and use the Criteria menu to hear it with a real value.

Open the data token picker

1. Place the caret where the value should be spoken.
2. Type {.
3. Choose a source under User context, Events, POI, or DATA.
4. Navigate to a context concept, competition, list, or collection.
5. Select the field and, when offered, its spoken form.
6. 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 describes the listener's local date, place, or weather for the request. It is different from a custom request parameter: parameters can drive a rule, while a User Context token inserts one of the supported spoken facts below.

For example, choose User context → Location → City. A supplied city, region, or country takes priority; otherwise valid latitude and longitude can resolve the place. When the place cannot be worked out for a request, the rule in When a value is missing applies.

Preview with Criteria

What the editor shows and plays inside a token is decided by the Criteria menu in the Creatives tab, and by nothing else. Delivery rules have no part in it.

• User context sets the listener used for location, date, and weather tokens. Choose Current location, Pick on map… to click or search a place and confirm with Use this point, or one of the places listed as Recently used.
• A POI list or data collection has its own entry with its first five records. Choose the record to hear.
• A sport feed has an entry for one round of matches, each shown with its date and its score or status.

Without a choice, tokens preview your current location, the first record of a list, and the first match of the round. The choice is for listening only and is never published.

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, spoken form, options, preview, list metadata, or expression configuration.

• Confirm the source and field, not only the visible example.
• Choose the spoken form that fits the surrounding sentence.
• Treat a blank format row as potentially mixed: several occurrences of that field may currently use different forms.
• Remember that the chosen format belongs to each token occurrence. A grouped row can update all occurrences it represents.
• Do not assume a preview value will become the runtime result.
• Weather tokens speak a temperature in degrees. Temperature bands such as cold, mild, or hot belong to targeting criteria and rules, where Temperature unit switches the bands between °C and °F.

When a value is missing

A token speaks the real value for the request, in the format chosen on the token. When that value is missing at request time, the creative is not served for that request, and Which creative chooses again from the creatives that remain.

Preview values are not delivered

The text shown inside a token while editing is the preview chosen from Criteria. It helps with grammar and timing, and it is never used as the spoken value for a listener.

Repair an older format

An older project can contain a spoken format that is no longer supported. Dynamic Properties names the retired format and offers a button such as Use Relative. Review and click that replacement explicitly; opening or saving the project alone does not re-approve or rewrite the token.

Create a custom criterion

1. Select the text, right-click, and choose Dynamic Content → Create → Custom….
2. In Name, enter the parameter the ad server sends on the ad request, for example team.
3. For each value, enter the value sent on the left and what the ad says on the right.
4. Use + Add value for more values, and write the default for every other case.
5. Choose each value from Criteria to hear it in the sentence.

Keep one criterion responsible for one business question. The criterion's name is the request parameter, so it needs no entry of its own in Delivery › Parameters.

Expression inputs

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

1. RequestReceive listener and custom parameters.
2. CandidatesLoad relevant feed, POI, or collection records.
3. Record ruleInclude, exclude, and select a record.
4. FieldsResolve canonical and computed values.
5. Creative ruleSelect the message strategy.
6. SpeakResolve every token of that creative; choose another creative when a value is missing.