In-play (Live) Betting in iGaming: Definition, How It Works and Why It Drives Modern Sportsbook Revenue
In-play (also called live) betting lets customers place bets while a sporting event is in progress, with prices updated continuously based on the evolving state of play. It has become the dominant betting mode at most major sportsbooks, often generating more turnover and more GGR…
TL;DR
In-play (also called live) betting lets customers place bets while a sporting event is in progress, with prices updated continuously based on the evolving state of play. It has become the dominant betting mode at most major sportsbooks, often generating more turnover and more GGR than pre-match. The trading complexity is significant: prices must update in seconds, liability changes constantly, and customer behaviour shifts as the event unfolds. Operators that run in-play well outperform those still treating it as an extension of pre-match.
How it works
When an event starts, the pre-match market closes (or remains open with adjusted prices) and the in-play market opens. The sportsbook's pricing engine continuously updates odds based on:
- Current state of play (score, time elapsed, possession, momentum).
- Live data feeds from the event venue (player statistics, key events, injuries).
- Trading platform algorithms that translate state changes into probability updates.
- Liability adjustments based on bets placed since the event started.
Customers see updated prices and place bets that the engine accepts or rejects (typically within milliseconds) based on liability, customer profile and price sanity checks. Cash-out is heavily integrated with in-play, since customers want the option to exit positions as state changes.
Why it matters in iGaming
In-play has fundamentally changed sportsbook economics. Pre-match was a fixed-deadline product: customers place bets before kick-off, then watch passively. In-play turns the event into a continuous betting experience: customers stay engaged for 90 minutes (football), three to five hours (cricket, tennis matches), or an entire game day (NFL, NBA). This generates dramatically more turnover per customer per event.
Different teams care about in-play differently:
- Trading runs in-play as a continuous pricing operation, often with dedicated traders for major events.
- Risk monitors liability concentration during running events with much shorter cycles than pre-match.
- Product treats in-play UX (responsive design, fast settlement, integrated cash-out) as a major competitive differentiator.
- Marketing tracks in-play share of activity as an engagement signal.
In-play also exposes operational quality differences across operators more clearly than pre-match. A sportsbook that takes 5 seconds to update prices after a goal is operationally weaker than one that updates in 200 milliseconds. A sportsbook that suspends in-play markets too aggressively loses customer engagement; one that suspends too rarely takes losses on outdated prices. The trading discipline behind in-play is one of the harder challenges in iGaming operations.
Common mistakes and how operators get in-play wrong
Slow price updates after key events. A goal, a red card, an injury changes probabilities instantly. Pricing engines that update too slowly take bets at outdated prices, which produces sharp losses. Sub-second update latency is now standard for major events.
Over-aggressive market suspension. Suspending in-play markets too often (after every minor event) frustrates customers and reduces engagement. Suspending too rarely takes losses on stale prices. Calibrating suspension policy is an ongoing trading discipline.
Treating in-play overround like pre-match. In-play margins typically run wider than pre-match because pricing must compensate for state-update latency and customer behaviour. Operators that apply pre-match overrounds to in-play often underperform on realised hold.
Not separating in-play and pre-match analytics. The two products have different margin profiles, different customer mixes and different operational requirements. Aggregating their analytics hides the structural differences and produces wrong conclusions about either.
Cash-out integration weak. In-play customers expect to cash out positions during running events. Sportsbooks where cash-out lags behind in-play price updates by seconds frustrate customers and lose engagement to faster competitors.
Inadequate data feeds. In-play pricing depends on real-time event data. Operators using cheap or unreliable feeds get inaccurate state information and price wrong as a result. Premium data costs more but pays back through better trading performance.
Healthy patterns and what good looks like
In-play practices observed in mature sportsbooks:
- Sub-second price update latency on major events with reliable real-time data feeds.
- Clear suspension policy calibrated to event types and risk tolerance, with documented criteria.
- Cash-out fully integrated with in-play and updating at the same cadence as price changes.
- Separate trading desk staffing for high-stakes events with dedicated coverage.
- Customer-segmented in-play limits and acceptance rules.
- Analytics that distinguish in-play from pre-match across all reporting layers.
How Gamblitude handles in-play
In Gamblitude, in-play and pre-match are first-class separate dimensions in all sportsbook analytics. Realised hold, customer mix, bet acceptance, cash-out behaviour and liability are tracked separately for each mode. Trading teams see in-play-specific dashboards with the cadence appropriate to fast-moving events. Insight Radar surfaces in-play anomalies (acceptance rate drops, liability spikes, margin drift) often within minutes of them developing, enabling intervention during running events rather than post-mortem after settlement.
FAQ
Multiple reasons. In-play overrounds are typically wider because pricing must compensate for state-update latency. Customer behaviour favours the book (faster decisions with less reflection). Cash-out margins compound on in-play activity. Volatility produces more results in the book's favour over time. Together these factors structurally raise in-play hold compared to pre-match.
For major events, sub-second is the standard. State changes (goals, points scored, key plays) need to flow through the data feed to the pricing engine to the customer-facing odds in well under a second to avoid sharp customers betting at outdated prices. Niche events with thinner liquidity can tolerate slower updates.
Standard practice is to suspend during fast-developing situations (goalmouth scrambles, penalty shootouts, key plays) where prices cannot reliably update fast enough. The exact criteria vary by sport, league and operator risk tolerance. Documented suspension policy prevents inconsistent decisions from individual traders.
In-play customers place more bets, with smaller average stake, faster decisions and stronger emotional engagement with the event. Cash-out usage is heavily concentrated in in-play. Recreational customers favour in-play; sharp customers split more evenly between modes depending on the value they perceive.
From a customer-facing UX perspective, yes; the transition should be seamless. From a trading and analytics perspective, no; they have different margin profiles, customer mixes and operational requirements. Operators that conflate them in internal reporting lose visibility into both.
Further reading
Found a mistake or want a term added to the iGaming Glossary? Let us know.
Browse the complete glossary or see how governed definitions work across dashboards, reports, alerts and AI answers.