Use live records without losing editorial control.

Sports and other data feeds can supply a value from a selected event or entity. Bind the field in the script, define which record wins in Delivery, and cover the case where no event or value is available.

Insert a sports field

1. Place the caret in the script and type {.
2. Under Events, choose the sport events feed.
3. Select the sport, for example Soccer.
4. Select one or more competitions and choose Continue.
5. Choose a speakable field, such as a team, event date, venue, or Score when available.
6. For a field with several spoken forms, choose the form that fits the sentence, then inspect the token in Dynamic Properties.

The binding records the sport, the competitions, and the field. The available sports and competitions come from the configured catalog; choosing a competition does not guarantee a current live score for every event. The value shown during editing is a preview: open Criteria and point at the feed to choose among the matches of one round, each listed with its date and its score or status. Without a choice, the round's first match is previewed.

Spoken formatting belongs to the token occurrence. The same event date can therefore appear once as a weekday and elsewhere as an exact spoken date. A venue uses the same location forms as User Context and POI locations.

Separate field selection from record selection

Choosing Score answers “which field should be spoken?” A form such as Away score controls how that field is read. Delivery must still answer “which match or event supplies the value?” The project therefore needs both:

• a token bound to the field;
• a Which record rule for the feed.

Configure the event record

Open Delivery and find the feed's panel in Which record. The feed may contain upcoming, live, and completed events. Define Include and Exclude, then choose a strategy card. To follow only matches still to be played, click Only matches still to be played in Include. The cards shown depend on the feed.

Plan for data timing

Sports meaning changes before, during, and after an event. A field can be technically present but editorially wrong for the current phase.

• Filter by relevant date, status, season, and league.
• Do not speak a live score from a stale snapshot.
• Distinguish scheduled, in-progress, postponed, cancelled, and completed events.
• Use explicit formatting for time zones and dates.
• Under When no record survives, choose a default creative or no ad.
• Use Which creative › Conditional on the match status to play a different creative before, during, and after the match.

Use computed fields

Computed fields can convert or combine feed values before a rule uses them. Examples include normalized kickoff time, score difference, time until event, or a reusable eligibility flag.

Name computed fields by business meaning and keep the raw provider field available for troubleshooting.

Other data feeds

The same pattern applies to other feeds when they have been configured for the account. For your own list of products, stores, or offers, use a data collection; the Data workspace does not currently offer creation of a new connected feed.

1. SourceSelect the feed or entity family.
2. ScopeChoose league, category, or list.
3. FieldBind the value used by the creative.
4. RuleChoose the winning record.
5. FormatTurn the canonical value into approved spoken copy.
6. FailureCheck the no-record case and a missing field separately.

Data governance

Feed QA checklist

• Provider, sport/category, league/scope, and field are correct.
• Record rules exclude irrelevant and stale candidates.
• Date, number, and name formatting sound natural.
• The no-record choice and the creative for a missing value are deliberate.
• Test covers before, during, and after the event where relevant.
• Rights allow the data to be used in advertising output.