In-Play Odds Feed vs Pre-Match: What Changes at Kick-Off
The technical requirements of an in-play odds feed are fundamentally different from pre-match. Operators who underestimate this discover it during their first major live event. WSGaming explains exactly what changes at kick-off.
Pre-Match: Low Frequency, High Precision
Before an event starts, a pre-match odds feed updates on a relatively low-frequency schedule. Prices move as sharp money flows in, team news breaks, and market consensus shifts. These updates might occur every 30 seconds to several minutes for a match announced a week ahead, accelerating to every few seconds in the final hours.
The technical requirements are manageable: moderate update frequency, no suspension urgency, no event-triggered update requirement. Most odds feed provider infrastructure handles pre-match reliably because it is low-intensity relative to live delivery.
In-Play: Event-Triggered, Sub-100ms Required
At kick-off, technical requirements change completely. A live football match generates odds update triggers every 5–15 seconds from normal play, and within milliseconds of major events — goals, cards, VAR reviews. The live odds feed must:
- Process each game event through the pricing engine within milliseconds of receipt
- Suspend relevant markets immediately when a definitive event occurs
- Push updated odds to all operator platforms before any bettor can act on stale information
- Reinstate markets once the event is confirmed and markets repriced
The total pipeline latency requirement — from official data source to player’s screen — is under 100ms for a production-grade feed. Pre-match delivery has no such urgency.
Many odds feed providers use the same infrastructure for pre-match and in-play delivery. This creates resource contention during peak events — a Saturday with 15 simultaneous in-play Premier League and Asian league matches can saturate shared infrastructure. Ask directly: does your in-play infrastructure scale independently of pre-match?
What Changes at Kick-Off: A Comparison
| Dimension | Pre-Match Feed | In-Play Feed |
|---|---|---|
| Update frequency | Minutes to seconds | Seconds to milliseconds |
| Trigger type | Scheduled + sharp money flow | Event-triggered (goals, cards, etc.) |
| Suspension requirement | Rare and non-urgent | Immediate — same-frame required |
| Infrastructure load | Low baseline | 10–100x higher during live matches |
| Latency requirement | Seconds acceptable | Sub-100ms mandatory |
The Questions to Ask Your Provider
“Does your in-play infrastructure scale independently of pre-match?” If the answer is no or vague, peak in-play performance will degrade when multiple live matches run simultaneously. WSGaming’s odds feed solution operates on dedicated in-play processing infrastructure that scales horizontally for peak event periods.
Key Takeaways
- Pre-match feeds update on low-frequency schedules — seconds of latency is acceptable
- In-play feeds require event-triggered updates with sub-100ms end-to-end delivery
- Suspension must fire in the same frame as the triggering event — separate calls add dangerous latency
- Shared pre-match/in-play infrastructure creates contention during peak Saturday schedules
- Ask providers explicitly whether in-play infrastructure scales independently — the answer is revealing
See WSGaming’s In-Play Odds Feed Under Live Load
Our team demonstrates live in-play performance during a running event — real latency, real suspension timing.
Book In-Play DemoView Odds Feed Solution