Technology & Integration Glossary

What it means

A Customer Data Platform pulls player data out of the systems it's trapped in - the PAM, payment processor, game providers, CRM, and affiliate tracker - and stitches it into one live profile per player. Unlike a warehouse, which is built for historical analysis, a CDP is built for activation: it holds the current state of a player and pushes it, in near real time, to the tools that send offers, adjust the lobby, or trigger a retention message.

Why it matters for operators

Personalization and retention both fall apart without a single view of the player. If your bonus engine can't see what the payments system knows, you'll offer a reload bonus to someone who just charged back. A CDP is what lets AI-driven personalization and journey orchestration work on real, current data instead of a stale nightly export, and it sits next to (not instead of) a data warehouse.

Example

A player deposits, plays for ten minutes, then goes quiet. A CDP flags the drop against their usual pattern and triggers a personalized re-engagement message the same evening, rather than a generic email three days later.

What it means

A Data Warehouse is the single place where an operator's history lives: bets, deposits, bonuses, sessions, and marketing spend, cleaned and modelled so anyone can query them together. It's optimized for analytical questions across large time spans - "what's the 90-day LTV of players acquired through this affiliate" - rather than for the real-time activation a CDP handles. Most modern setups use a cloud warehouse (BigQuery, Snowflake, Redshift) fed by pipelines from each source system.

Why it matters for operators

Without a warehouse, basic numbers are guesses. Finance reports one revenue figure, marketing reports another, and nobody can reconcile GGR against player-level behaviour. A warehouse is the foundation that makes player lifetime value, churn, and cohort analysis answerable at all, and it's usually the first thing a serious data team builds.

Example

An operator wants to know whether high-bonus players retain better than low-bonus ones. With a warehouse it's a single query; without one, it's a two-week manual export project that arrives too late to matter.

What it means

Device fingerprinting assembles a stable identifier from attributes a browser or app exposes: canvas and WebGL rendering characteristics, installed fonts, audio stack behaviour, screen and timezone configuration, hardware concurrency, and dozens of smaller signals. Combined, these are distinctive enough to recognise the same device again. A good implementation survives incognito mode, cleared cookies and app reinstalls, because it doesn't depend on anything stored client-side.

Why it matters for operators

It's the single strongest link signal for multi-accounting and the backbone of most bonus abuse detection. It also carries the sharpest false-positive risk in the stack: shared household devices, internet cafés and office machines all produce genuine links between unrelated people. Treating a fingerprint match as proof rather than as one input is how operators end up explaining a voided withdrawal to a complaints body.

There's a compliance dimension too. Fingerprinting for fraud prevention is generally handled as a legitimate-interest processing activity in the EU and UK, but it isn't automatically exempt from transparency and minimisation duties, and regulator treatment varies. Document the purpose, limit retention, disclose the practice in the privacy notice, and take local advice per licensed market — "it's for fraud" is not a blanket answer.

Example

Two accounts opened eight weeks apart share a fingerprint. One belongs to a long-standing player, the other to a new registration that immediately claimed a welcome offer. The link triggers review rather than a block; the payment-instrument check decides the outcome.

What it means

Platform migration is the process of moving an operating gambling business from one platform to another: player accounts, wallet balances, KYC records, bonus states, game and transaction history, payment tokens and regulatory reporting. Unlike a fresh launch, everything has to survive the move — a player's balance, self-exclusion status and verification level must be identical on the new stack the morning after cutover.

Why it matters for operators

Migrations are where platform economics get honest. Operators usually migrate to escape revenue-share fees that no longer match their scale, to reach markets their current vendor won't certify for, or to regain product control. The costs are mostly hidden: months of parallel running, data mapping between incompatible schemas, re-integrating payments and content, and the churn spike if anything breaks on cutover weekend. Vendors know switching is painful, and that pain is priced into every contract renewal. Planning the exit path before signing — data export rights, wallet portability, notice periods — is the cheapest negotiation you'll ever do.

Example

A mid-size casino on a 12% revenue-share white label crosses 500,000 in monthly GGR. The same operation on a licensed turnkey deal would cost roughly half. The migration takes five months, including a six-week freeze on new features — and pays for itself inside the first year.

What it means

A Progressive Web App is a website built with modern browser features so it installs to the home screen, works offline, and can send push notifications — much like a native app, but delivered straight from the web. For iGaming, the draw is obvious: it sidesteps app-store gambling restrictions and review delays while still giving players an app-like feel.

Why it matters for operators

Apple's and Google's stores limit or complicate real-money gambling apps in many regions, so a PWA is often the most practical way to put an installable product on a player's phone. It also ships updates instantly, with no store approval in the loop. The trade-off is tighter performance budgets — a PWA still has to hit a fast Time to Interactive on mid-range phones to convert.

Example

An operator blocked from the App Store in a given market can offer a PWA players add to their home screen in two taps, getting an app icon and push notifications without a native build.

What it means

Provably fair systems publish a cryptographic commitment (a hash) to a round's outcome before bets are placed, usually combining a server seed, a client seed and a nonce. After the round, the player can recompute the hash and confirm the result was locked in before they bet — meaning the operator couldn't have adjusted it in response to the wagers. The technique emerged in early Bitcoin casinos and dice sites, where players had no regulator to appeal to, and became the trust mechanism behind crash games like Aviator.

Why it matters for operators

In markets where licensing carries little weight with players, provably fair verification is a conversion tool: it answers "is this rigged?" with math instead of a logo. In regulated markets it complements rather than replaces RNG certification — regulators still want lab reports, not just hashes. Operators offering crypto-origin content should understand the seed mechanics well enough to handle player disputes, because "check the hash yourself" only builds trust if support can walk a player through it.

Example

A crash game shows the hashed server seed before takeoff. After the round crashes at 2.47x, a player pastes the revealed seed into the game's verifier and reproduces the multiplier — confirming the crash point existed before anyone bet.

What it means

A Random Number Generator is the algorithm that decides game outcomes: which symbols land on a slot spin, which card comes off the deck, where a crash multiplier stops. Online casinos use pseudo-RNGs — deterministic algorithms seeded with entropy — that pass statistical randomness tests. Before a game goes live in a regulated market, an accredited lab (GLI, BMM, eCOGRA, iTech Labs) certifies that its RNG output is unpredictable and that the realized RTP matches the published figure.

Why it matters for operators

RNG certification is a licensing requirement in every serious jurisdiction — UKGC, MGA and Brazil's SPA all require certified games, and running uncertified content is a fast way to lose a licence. It's also the trust backbone of the product: disputes about "rigged" outcomes are settled by pointing at the certificate and the game logs. When sourcing content through an aggregator, the operator still carries the obligation to confirm each title's certification covers the market it's offered in.

Example

An operator entering a regulated market submits its game catalogue for approval. Three titles from a new studio lack certificates for that jurisdiction — they stay switched off in the lobby config until the lab report lands, while the rest of the portfolio goes live.

What it means

A Remote Game Server hosts a game's core logic — the math model, the random number generator, win evaluation and the regulatory audit trail — on the studio's or aggregator's infrastructure rather than inside the casino platform. When a player spins, the operator's frontend calls the RGS over an API, the RGS resolves the round, and the result comes back along with the wallet transaction. One certified game build can then serve hundreds of operator sites without being re-deployed into each one.

Why it matters for operators

The RGS model is what makes modern content distribution work. Studios certify a game once per jurisdiction on their own RGS, and every integrated operator inherits that certification instead of hosting and re-certifying game code themselves. It also concentrates the integration question: what you actually connect to is either a studio's RGS or a game aggregator that fronts dozens of them through a single API. The trade-off is dependency — if a studio's RGS has latency or an outage, every operator running its games feels it at the same time.

Example

An operator adds a new studio through its aggregator. No game files are installed anywhere: the platform registers the studio's game list, players' bets route to the studio's RGS, and settled results post back to the operator's wallet — with the round history stored on both sides for dispute handling.

What it means

Time to Interactive is the point at which a page has loaded enough that taps, scrolls, and button presses respond reliably, not just when pixels appear. A page can look ready while the main thread is still busy and ignoring input — that gap is what TTI captures. On mobile iGaming, a TTI under three seconds is the rough line between a player who plays and one who bounces.

Why it matters for operators

Most iGaming traffic is mobile, often on mid-range phones and patchy networks, so slow TTI directly costs deposits and retention. It's shaped by JavaScript weight, third-party scripts, and how much work the device does before the lobby responds. Tuning it is a core part of a mobile-first build and sits alongside Google's Core Web Vitals as a metric worth tracking per release.

Example

Two casinos with identical games but a one-second TTI gap will see measurably different bounce and conversion rates, because the slower lobby feels broken on the first tap.