For operators

PlayerPal gives your players a loyalty Account that earns Points across the network, and gives you analytics on those players, without becoming a second copy of your player database. You never send PlayerPal a player's email, name or phone number, and PlayerPal is never in the path of login, wagering or payouts.

This page summarises what an Operator gets, with the status of each part. The labels mean: Available (built and tested in the platform), In development (being built; behaviour may change) and Planned (designed, not built yet).

What you get

Capability	What it means for you	Status
Linked players	Players connect their casino account to PlayerPal once, in a PlayerPal-hosted consent step	Available
Points across the network	Linked players earn Points from settled game rounds; PlayerPal calculates them	Available
Analytics on your players	KPIs about the players linked to you, through the KPI API	Available
Anonymous network comparison	How your players compare with the rest of the network, and with peer operators, without revealing any competitor	Available
Insights	Rule-based observations on your KPIs	Available
Operator portal	Browser workspace for your analytics	In development · demo
Spending Points on rewards	A player shop and redemption	In development

Your players stay yours

Available

• No personal data. PlayerPal never receives or stores a player's email, name or telephone number. The link step asks you for a signed assertion about your own player, not their details.
• Your own Alias. Each linked player gets an Alias that only you receive (pp_plr_opr_…). It is random, so it cannot be matched with the Alias another operator holds for the same person.
• Only your players. Every KPI and lookup is scoped to the players linked to you. Your scope comes from your credentials, never from a field in the request.
• The player is in control. A player can Unlink your casino at any time from their PlayerPal Account. Play at your casino continues; later Activity simply stops earning.

No impact on your platform

Available

PlayerPal is a sidecar, not a dependency. If PlayerPal is unreachable, your players still sign in, launch games, place bets, settle rounds and get paid. There is no PlayerPal call at login, game launch or settlement. Activity is sent afterwards in batches and retried until it is accepted.

PlayerPal does not handle your wallet, your casino login or your bonus engine. The player's casino account and the PlayerPal Account are separate.

Analytics and comparison

Available

The KPI API gives you three views:

View	What you see
Your performance	Linked players, new links, link funnel, active accounts, rounds, turnover, Points issued, ingest health
You vs the network	Your players' per-player figures against the rest of the network, as an index and a percentile band
Peer benchmarks	Where you sit among other operators: quartiles and your band, never names or ranks

Comparisons are protected by anonymity thresholds. Thin or dominated segments are suppressed rather than shown, so in early markets you will mostly see global figures. Some KPIs, such as retention, depend on data feeds that are still being added and show what they require instead of a zero. See Privacy thresholds and Metrics.

In development

The operator portal shows these analytics in a browser workspace, but its sign-in is not yet production authentication. Use the KPI API with your partner credentials for live access.

How the integration works

1. Link a player

   Your backend creates a link intent with a short-lived signed assertion. The player completes a PlayerPal-hosted consent step, and you exchange the result for your Alias and any provider Aliases you requested.

2. Pass the provider Alias at launch

   Put the provider Alias in your existing game launch payload. PlayerPal is not called.

3. Activity flows asynchronously

   The game provider sends settled rounds in batches. You can also send daily commercial facts through fact ingest.

4. Read your KPIs

   Call the KPI API with OAuth client credentials or signed requests.

Integration status

Part	Status
Link flow with signed operator assertion	Available
Per-partner credentials for linking and activity batches	In development
Fact ingest (commercial and attribution facts) with OAuth or signed requests	Available
KPI API with OAuth or signed requests	Available

Related

GuideQuickstart

The shortest path from credentials to a first linked player.

→GuideLink players

The link intent, consent step and Alias exchange.

→GuideSend activity

Batches, idempotency and retries.

→GuideKPI API

Read your KPIs, comparisons and benchmarks.

→GuideFact ingest

Send daily commercial and attribution facts.

→TrustPrivacy

What PlayerPal holds and who can see it.

→