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 design a fallback for missing or late data.
Insert a sports field
- Place the caret in the script and type {.
- Choose Sport events.
- Select the sport, for example Soccer.
- Select one or more available leagues and continue.
- Choose the field, such as Home score, Away score, team, date, or venue.
- Inspect the resulting token in Dynamic Properties.
The binding records the data provider, sport, league selection, field, and record source. The value shown during editing is only a preview of that structure.
Separate field selection from record selection
Choosing Away score answers “which column should be spoken?” Delivery must still answer “which match or event supplies that column?” The project therefore needs both:
- a token bound to the field;
- a Which record rule for the feed subject.
Configure the event record
Open Delivery and find the panel created for the selected league/feed. Configure candidate set, filters, exclusions, score or pick mode.
First eligible
Use a deterministic source order when that order already has business meaning.
Best
Score records and choose the candidate with the largest score.
Rotate
Cycle through all eligible records when variety matters more than score.
Random top-N
Randomize among the strongest candidates to avoid a single repeated winner.
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.
- Provide a safe line when no eligible event exists.
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 configured feeds beyond sports:
- SourceSelect the feed or entity family.
- ScopeChoose league, category, or list.
- FieldBind the value used by the creative.
- RuleChoose the winning record.
- FormatTurn raw data into approved spoken copy.
- FallbackHandle no-match and service failure.
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.
- No-match, delayed-feed, and malformed-value fallbacks are safe.
- Preview requests cover before, during, and after the event where relevant.
- Rights allow the data to be used in advertising output.