Why cross-vertical matters
The commercial logic was established in the iGaming Basics course and bears restating because it drives so much product investment.
Sportsbook acquires customers. It has mainstream cultural presence, it advertises through channels casino cannot use as effectively, and it reaches people who follow sport rather than people seeking gambling. Its revenue is volatile, because it moves with sporting results, and its acquisition costs are high.
Casino monetises. Its revenue is more predictable, because the house edge is built into every game rather than depending on how results fall, and revenue per customer is frequently substantially higher than the same customer generates in sportsbook. Flutter's annual report for 2025 shows both effects. In its international business, iGaming revenue in its existing brands rose 9% while their sportsbook revenue fell 6%, partly because of unfavourable sports results. In its US business, mainly FanDuel, iGaming earned $2,095 million from an average of 980,000 monthly players and sportsbook $4,633 million from 3,260,000, which on those figures is roughly $2,100 of revenue per average monthly player in iGaming against roughly $1,400 in sportsbook.
The operator that acquires through sportsbook and introduces those customers to casino captures both advantages. Many businesses that describe themselves as sports betting companies take a large share of their revenue from casino, and operators rarely publish profit by vertical, but they do credit cross-sell for casino growth: Flutter attributed part of its 2024 UK and Ireland iGaming growth to product improvements that "drove strong cross-sell rates", in the same 2025 annual report.
That structure has product implications, and it has responsible gambling implications that should be stated alongside rather than after.
The shared wallet
The foundation of cross-vertical product is a single balance usable everywhere, and it is more demanding than it appears.
A single number is trivial. The complexity is everything attached to it.
Bonus state. A bonus awarded in one vertical must have defined behaviour in the other. Does a sportsbook free bet contribute to casino wagering? Does casino play count towards a sportsbook bonus requirement? At what rate? These decisions must be coherent, must be communicated to the customer clearly, and must be enforced by the system rather than discovered in a dispute. In Britain part of the question is now settled by rule: since 19 January 2026 licensees must not include more than one type of gambling product (betting, casino, bingo and lottery) within an incentive, and wagering requirements are capped at ten times. An incentive whose credit the customer can use freely on any product is still permitted; one that requires play in both sportsbook and casino is not.
Wagering contribution. Different games and bet types contribute at different rates, and a cross-vertical bonus multiplies the combinations.
Limits. Deposit and loss limits should apply to the customer, not to a vertical, which requires enforcement above the vertical level. An operator whose limits apply per vertical has limits that do not limit.
Market rules. Some jurisdictions impose requirements that differ by vertical, including separate licensing, different display obligations and different permitted products. In Britain, for example, online casino, betting and bingo each have their own type of operating licence, and online slots carry game-design rules that betting does not. A shared wallet must accommodate that without leaking behaviour across the boundary.
Reporting. Regulatory reporting frequently distinguishes verticals, which means a unified wallet must still produce separated reporting. The Gambling Commission's industry statistics, built from operators' returns, split online yield by product: in April 2025 to March 2026 online casino games generated £5.7 billion, £4.8 billion of it from slots, remote betting £2.4 billion and remote bingo £147.8 million.
Bonus abuse surfaces. A shared wallet creates new routes to extract promotional value, since a bonus intended for one vertical may be cleared through the mechanics of another.
Operators without a shared wallet require customers to transfer between balances, which is friction at exactly the point the operator wants movement. It is also a clear signal to the customer that they are dealing with two products rather than one.
Bridges between verticals
Given a shared wallet, the question is how customers actually move.
The approaches that work share a property: they are contextually relevant rather than generic promotion.
Dead time. A customer who has placed a bet on a match starting in three hours has an interval in which they are engaged and have nothing to do. Surfacing casino content in that moment is relevant rather than intrusive.
Post-settlement. A customer whose bets have settled is at a natural decision point about what to do next.
Adjacent formats. Virtual sports, which are mathematically casino products presented as sports betting, and live casino game shows, which resemble entertainment more than traditional table games, both serve as intermediate steps for customers who would not choose a slot lobby directly.
Contextual placement. Casino content surfaced within the sportsbook interface at appropriate moments, rather than requiring the customer to navigate to a separate area.
Unified navigation. Making the other vertical visible and reachable without the transition feeling like leaving one product for another.
What works less well is generic promotional interruption: banners offering casino bonuses to sportsbook customers regardless of context, or push notifications unconnected to anything the customer is doing. These produce low conversion and measurable irritation.
The responsible gambling dimension
This is the part that a purely commercial treatment of cross-sell omits, and it should not be omitted.
Sports betting, in its traditional form, has a particular risk profile. A customer betting on weekend fixtures makes a decision, waits hours or days, and learns the outcome. The event frequency is low and the interval between stake and outcome is long. That matters because the Gambling Commission treats speed and intensity of play as features that raise the risk of harm.
Casino has the opposite profile. Event frequency is high, the interval between stake and outcome is seconds, and play is continuous. Britain's Gambling Commission banned online slot spins faster than 2.5 seconds, auto-play and features that speed up play from October 2021, on the evidence that these features increase the risk of harm. Its analysis of the Gambling Survey for Great Britain found that online slots and online casino games remained significantly associated with a problem gambling score of 8 or more after adjusting for how often and on how many activities people gambled, while online betting on sports and racing did not. In-play betting sits between the two, and the faster its markets, the closer it comes to casino.
Cross-selling a customer from the first to the second therefore changes the structural risk characteristics of what they are doing, regardless of how much they spend. The Commission also cites evidence that consumers are more at risk of harm when they gamble on multiple products rather than a single product, which was part of its case for the mixed-product ban. That is not an argument against cross-sell, which is legitimate and which many customers actively want. It is an argument that cross-sell warrants the same design consideration as any other feature affecting exposure.
The practical positions that follow are reasonably clear. Cross-sell should be suppressed entirely for customers under safer gambling restriction or displaying risk indicators, and that suppression must work across the bridges described above and not only in email campaigns. In Britain this is partly a licence condition: remote operators must prevent marketing and the take-up of new bonus offers where strong indicators of harm have been identified. It should not be targeted at moments of loss, since a customer whose bets have just settled badly is at a point where an optimiser would find good response rates for exactly the wrong reason. The monitoring that applies to casino play should apply from the moment a customer crosses, rather than being calibrated to their sportsbook history. And the effect of cross-sell on spend patterns should be measured, because a cross-sell programme increasing revenue predominantly through a small number of customers whose spend rose sharply is producing a result that needs examining rather than celebrating.
Lifecycle rather than session
A broader reframing that applies beyond cross-vertical work.
Most product measurement and most product decisions concern the session: did the customer convert, how long did they stay, what did they do. Lifecycle thinking asks a different question: what does this customer's whole relationship with us look like, and how does this decision affect it.
The two frequently disagree. A design that maximises a single session may reduce the likelihood of the next one. Aggressive promotional interruption converts in the moment and irritates over time. Removing friction from repeated deposits increases immediate spend and may produce a customer who leaves badly.
Lifecycle stages worth designing for distinctly.
New. The first session, covered in the journeys lesson, where orientation matters more than promotion and where introducing the tools is most readily accepted.
Establishing. The first weeks, where drop-off is usually steepest and where habits form. Product decisions here have disproportionate long-term effect.
Established. The mature relationship, where the customer knows the product and where the design questions concern depth, discovery breadth and keeping the experience fresh.
Changing. A customer whose behaviour shifts materially, in either direction, which warrants attention rather than a campaign. Increased activity may be enthusiasm or may be difficulty; decreased activity may be boredom or may be deliberate control.
Lapsing. Where reactivation is considered, and where the distinctions covered in the Customer Service and Operations Strategy courses apply: a customer who stopped because their gambling was becoming a problem should not be pursued.
Returning. A customer coming back after a break, which is a moment where limit-setting is well received and where assumptions based on their previous behaviour may no longer hold.
Measuring the relationship
The measurement implication is that session metrics are insufficient.
Cohort contribution over time, as established in the metrics lesson of iGaming Basics, is the fundamental measure. Retention curves by acquisition source and vertical show whether the cross-sell is producing durable customers or transient ones. Cross-vertical adoption rate and, more usefully, contribution difference between single and multi-vertical customers, quantifies whether the work is worth its investment. Spend pattern stability indicates whether customers are playing consistently or in a way that suggests escalation.
The caution throughout is the skew problem. A cross-sell programme can show excellent aggregate results driven almost entirely by a handful of customers whose spend increased dramatically, and that is a materially different finding from broad modest adoption. Distinguishing them requires looking at the distribution, which is a recurring theme across these courses because it is a recurring failure.
What good looks like
Cross-vertical product done well is coherent rather than aggressive. A single balance that behaves predictably. Bonuses whose cross-vertical rules are clear before the customer accepts them. Navigation where the other vertical is available without being pushed. Bridges placed where they are contextually relevant. Limits and monitoring that apply to the customer rather than to a product area. Suppression that works across every surface. And measurement that follows the relationship rather than the session.
The commercial return on that is real, and it comes from customers who genuinely wanted the second product rather than from customers who were pushed into it, which is also the version that does not generate the problems described above.
Poker, bingo and the other verticals
The lesson has treated cross-vertical as sportsbook and casino, which is the dominant case. The others behave differently and are worth noting.
Poker integrates awkwardly. It has its own client, its own tournament schedule, its own liquidity requirements and a player base with distinct expectations. Cross-sell from poker to casino tends to work more easily, since the audiences overlap in their comfort with gambling mechanics. Cross-sell into poker is harder, because the barrier is skill and social confidence rather than familiarity.
Bingo has a community dimension that other verticals lack, with chat rooms and hosts forming a real part of the proposition. Its players skew differently from casino and sportsbook, and the most natural cross-sell is towards casino slots, which bingo sites commonly offer alongside their rooms. The design consideration is that the community aspect is the product, and interventions that treat bingo as a slot lobby with a different game type reliably damage it.
Virtual sports sits between verticals by construction, presented as sports betting and mathematically a casino product. In Britain it is licensed as betting, under a separate virtual events betting licence. This makes it a genuine bridge, and it also means it should be treated as casino for risk purposes despite its presentation.
Lottery and instant win products are low-friction entry points that attract customers who would not choose either main vertical, and they can cross-sell in both directions.
The general design point is that each vertical has a distinct audience and a distinct product logic, and cross-vertical work that treats them as interchangeable surfaces of one product degrades what made each of them work.
The bonus problem across verticals
One recurring practical difficulty worth setting out, because it generates disputes and support volume.
A customer holding a bonus with a wagering requirement plays across verticals. The contribution rates differ: casino slots might contribute fully, table games partially, sportsbook bets at a rate depending on the odds, and some products not at all.
In Britain the mixed-product ban and the ten-times cap described above narrow this problem, but it remains in markets without them, and between game types within a single vertical. From the customer's perspective this is opaque. They are playing, their balance is moving, and their progress towards releasing the bonus is advancing at a rate they cannot easily predict.
The design responses are straightforward and uncommon. Show progress continuously, as a visible indicator of how much wagering remains. Show contribution rates at the point the customer selects a game or places a bet, not in a linked terms document. Warn before a non-contributing action, where a customer with an active bonus is about to do something that will not count. And prevent rather than penalise where a bonus term would be breached, since a system that allows a customer to breach a maximum stake and then voids their bonus has manufactured a dispute it could have avoided.
Operators that implement these should expect bonus dispute volume to fall, and, as noted in the Customer Service course, the size of that fall is the clearest test of how many such disputes were a presentation failure rather than a customer failure.
Designing for the returning customer
A lifecycle stage that receives almost no design attention and deserves some.
A customer returning after weeks or months away arrives with different needs from either a new customer or an active one. Their memory of the product is partial. Their saved payment method may have expired. Their preferences may have changed. And crucially, the reason they were away is unknown and matters.
Handling this well involves a few things.
Reorient without patronising. Surface what they played before, note what has changed, and make it easy to resume.
Check the practical state. Expired cards, outdated verification and lapsed preferences should be surfaced proactively rather than encountered as a failure at the point of deposit.
Offer the tools. A return after an absence is one of the moments where limit-setting is best received, because the customer is at a natural decision point about how they want to engage.
Do not assume continuity of behaviour. A customer's previous pattern may not describe them now, which matters for both recommendation and for risk monitoring. Treating a returning customer as picking up where they left off can produce both irrelevant recommendation and inappropriate assumptions about what is normal for them.
Consider why they were away. This cannot be known directly and can sometimes be inferred. A customer who set restrictive limits, took a time-out, or reduced activity following a safer gambling intervention before lapsing should not be treated as a reactivation opportunity, and the systems should prevent it rather than relying on someone remembering.
That final point connects to the reactivation discussion elsewhere in these courses. The commercial value of reactivation is genuine and the population it targets includes people whose absence was deliberate and protective. Distinguishing them is a design and data problem, and solving it is considerably better than either abandoning reactivation or pursuing everyone.
What this changes about roadmaps
A closing point about how lifecycle thinking affects prioritisation.
Product roadmaps in this sector are typically organised around features and surfaces: a new lobby, a bet builder improvement, a payment method, a redesign. Organised around lifecycle instead, the questions become different: what is the weakest stage of our customer relationship, and what would improve it.
That reframing usually surfaces different priorities. Many operators find their weakest stages are the first session, where new customers are handed a product designed for people who already understand it, and the return after absence, which is designed for not at all. Both are cheap to improve and neither generates a feature announcement.
It also changes how existing work is assessed. A discovery improvement is worth more if it helps new customers find something in their first session than if it marginally improves recommendations for established ones, and a roadmap organised by surface will not make that distinction.
The practical suggestion is to map the lifecycle explicitly, identify where customers are lost at each stage, and prioritise against that rather than against a list of features. It is the same discipline as the funnel work in the journeys lesson, extended from the first week to the whole relationship.