An iGaming CRM needs reliable player data, current eligibility controls, safe campaign and reward execution, and reporting you can reconcile. The product may supply those capabilities directly or through integrations. What matters is whether the complete system demonstrates them for your operation.
Use this checklist to brief a vendor or test a proposed setup. It connects each feature requirement to the data, owner and evidence needed for acceptance. It is a technical and operating framework, not a vendor ranking or a universal legal specification. Regulatory examples below were checked against primary sources on 17 October 2026.
What iGaming requires beyond a generic CRM feature list
A cross-industry engagement platform can process live events, segment audiences and apply supplied restrictions. An iGaming-focused platform can still fail if its integration is incomplete. "Generic" and "native" do not prove the outcome either way.
The difference is the operating requirement. A player may have transactions, unsettled bets, bonus state, channel preferences and restrictions that affect whether a campaign can act. Those facts must reach the right decision point, with clear ownership of updates and failures.
Model the player, events and actions separately
A useful player record identifies the person and the relevant brand/account context. Events describe changes: registration, deposit status, game round, bet settlement, consent change or exclusion. Actions describe what the CRM attempted: send, award, suppress, pause or alert.
Keep the source of truth explicit. The CRM does not need to become the wallet ledger, verification service or bonus engine. It needs trustworthy information from those systems and a reliable way to request and reconcile the actions it orchestrates.
Treat player restrictions as policy inputs
Do not use "compliance flag" as one undefined field. Specify the type, source, effective time, scope and permitted actions. Consent withdrawal, self-exclusion, a deposit limit and an at-risk review are different states; they do not automatically have identical effects across every channel and brand.
For example, the MGA's current player-protection guidance distinguishes the scope of some brand-specific exclusion requests from cases requiring exclusion across operated brands. It also requires effective self-exclusion and describes controls for limits. Your compliance owner must translate the applicable rules into an explicit system policy. (MGA Player Protection.)
Similarly, the UK Gambling Commission's guidance states that online gambling businesses must verify age and identity before gambling. That supports a requirement for current verification state; it does not make the CRM the verification provider. (UKGC age and ID guidance.)
Define the time requirement for each action
A report refreshed overnight and an in-session eligibility decision have different freshness requirements. Define the interval you need from source change to usable state, and from state to action. Measure that complete path under realistic load.
A fast CRM cannot compensate for a stale upstream feed. Equally, real-time ingestion is not proof that a queued message rechecks eligibility before dispatch.
Must UK online gambling operators verify a customer's age and identity before they gamble?
Yes. The UK Gambling Commission's age and ID guide, updated 13 April 2022 and checked 30 October 2026, says all online gambling businesses must ask players to prove their age and identity before they gamble.
Does a Malta self-exclusion request apply across all of an operator's brands?
Where there are sufficient indications of problem gambling, yes. The Malta Gaming Authority's player-protection page, checked 30 October 2026, says a self-exclusion request shall be applicable across all operated brands. Otherwise the operator may apply it to the requested brand only.
Does Malta Gaming Authority guidance require player limits to stay easily accessible?
Yes, for player limits. The Malta Gaming Authority's player-protection page, checked 30 October 2026, says operators must offer either deposit limits or wagering limits, and the ability to set limits must always remain available and easily accessible.
The iGaming CRM feature checklist
Use three columns in your own procurement record: requirement, owner and acceptance evidence. Mark documentation, demonstrated behaviour and contractual commitment separately. The examples below are proposed tests, not claims that a particular vendor has passed them.
Player data and identity
Require a documented identifier strategy, brand/account relationships and a rule for merging or separating records. Decide which history needs to remain available and how identity corrections propagate.
Demonstrate: one person with activity across two products, plus a corrected or duplicate account. Reconcile audience counts before and after the correction. Confirm that a merge does not duplicate rewards or erase restrictions.
Keep as evidence: field definitions, source ownership, reconciliation results and access rules. Use synthetic or appropriately protected records in evaluation.
Wallet, bonus and transaction events
Define the states the programme uses. An initiated deposit is not an approved deposit; a bet placement is not a settlement; an award request is not a fulfilled reward. Include currency, amount, status and correction handling where relevant.
Demonstrate: a qualifying event, a duplicate, a delayed event and a reversal. A proposed acceptance criterion might be one valid award for one eligible qualifying transaction, with a recorded outcome for every retry or correction. Agree the exact rule for your promotion before testing.
Keep as evidence: event and transaction identifiers, expected state changes, award acknowledgements and a cost reconciliation. The CRM and PAM responsibilities should be distinguishable.
Segmentation and lifecycle
Require the fields and event windows needed for your planned journeys. Specify whether eligibility is evaluated at entry, before each action, or both. Define how re-entry and conflicting journeys are handled.
Demonstrate: build an audience combining product activity, deposit state, lifecycle stage and current restrictions. Change one source attribute and show when the audience changes. Follow a player who ceases to qualify while waiting in a journey.
Keep as evidence: the segment definition, source query or comparison count, update timing and journey entry/exit record. The player lifecycle reference helps define stages; it is not a substitute for event definitions.
Messaging and channel coordination
Scope only the channels you intend to use, with contact limits and priorities across the programme. Define the difference between promotional and operational messages in your approved policy rather than using one label to bypass controls.
Demonstrate: email and another selected channel competing for the same player, an opt-out before send, a failed delivery and a retry. Show whether queued actions are cancelled or re-evaluated and how delivery status returns to the CRM.
Keep as evidence: template version, consent or eligibility decision, dispatch time, provider response and failure handling. A campaign dashboard showing "sent" is not by itself delivery evidence.
The ICO's current electronic-mail guidance describes consent requirements and a limited existing-customer exception, with opt-out conditions. It also notes that the guidance is under review following legislative changes. Treat it as a current source to check with your privacy owner, not a complete cross-market consent policy. (ICO electronic mail marketing.)
Player protection, permissions and audit
Define the restriction policy with the relevant compliance owner. Record which decisions must prevent an action when state is missing or stale. Include brand scope, channel scope, effective time and the escalation path for uncertain records.
Demonstrate: an exclusion arriving after journey entry, a more restrictive status during a queued action, and an interrupted restriction feed. Attempt an unauthorised edit or send. Inspect the final result in each channel or reward system, not just the CRM screen.
Keep as evidence: the applied policy version, source-state timestamp, decision, action outcome and audit record. Inspect applicable security reports, data-processing terms, retention and hosting scope separately; a vendor badge does not verify your configuration.
Reporting and incrementality
Require exports that connect eligible audience, treatment or holdout assignment, actions, outcomes and costs. Decide how to handle late settlements, refunds, currencies and player-tier changes.
Demonstrate: reproduce a campaign result outside the dashboard using agreed definitions. For a tier report, specify whether the tier means current tier or tier at the time of the campaign. For incremental measurement, inspect how the holdout is assigned and maintained.
Keep as evidence: metric definitions, calculation logic and reconciliation differences. Use the CRM KPI guide and ROI measurement guide to prepare the brief.
A compact acceptance run
Use a repeatable scenario set, with expected outcomes agreed beforehand:
| Scenario | Question the test must answer |
|---|---|
| Eligible player, normal event | Did the intended action occur once, with a usable record? |
| Duplicate or replayed event | Was duplicate contact or reward prevented according to the agreed rule? |
| Late event or reversal | Did state and reporting resolve correctly, without an unexplained new action? |
| Changed consent or exclusion | Did the current approved policy control the pending action? |
| Missing or stale critical data | Was the agreed safe failure behaviour applied and surfaced to an owner? |
| Source or delivery outage | Was recovery controlled, with no unintended replay or lost outcome? |
| Unauthorised user or assistant | Was the action prevented and the attempt recorded as appropriate? |
| Independent reconciliation | Can an analyst explain the audience, actions and financial result? |
These tests can be applied to direct user actions and AI-assisted workflows. An assistant generating a campaign does not remove the need for permission, approval and execution checks.
Do UK marketing emails need consent for iGaming operators?
Generally yes. ICO guidance (UK, under review, checked 30 October 2026) says you must not send marketing emails or texts to individuals without specific consent. The soft opt-in covers only an existing customer who bought, or negotiated to buy, a similar product or service.
Integration: what an iGaming CRM actually has to connect to
Draw the interfaces before evaluating connector logos. Your architecture may combine several roles in one provider, but every launch-critical responsibility needs an owner.
| Interface | Information or action | Acceptance focus |
|---|---|---|
| PAM and product systems | Player identity, account state, deposits, withdrawals, game or bet events | Completeness, identifiers, ordering, corrections and source reconciliation |
| Reward or bonus execution | Eligibility, award requests, acknowledgement, fulfilment and reversal | One intended outcome, caps and cost reconciliation |
| Analytics or warehouse | History and attributes in; campaign decisions and outcomes out | Definitions, export availability and reproducible reporting |
| Messaging providers and front end | Dispatch, rendering, delivery and interaction | Current eligibility, retries, visibility and provider feedback |
| Verification and restriction sources | KYC, jurisdiction and approved player-control states | Effective time, scope and controlled behaviour when unavailable |
| Consent or preference centre | Permissions, purpose, channel and withdrawals | Propagation, evidence and action-time enforcement |
What to put in each data contract
For each interface, define the record identifier, schema, source of truth, effective timestamp, update or event semantics, expected latency and owner. Add required fields, allowed values, currency and time-zone conventions, duplicate handling, retry behaviour and retention.
Distinguish the time a player acted from the time the event arrived. Define how backfills and historical corrections behave so they do not accidentally act like new campaign triggers.
What to ask about a PAM connector
Ask for the exact PAM, supported version, fields and events, deployment dependencies and responsibility for custom changes. "We integrate with PAMs" is not the same as a tested connection to your configuration.
Request a sample event trace and failure-recovery procedure. A connector already in use may reduce work, but still needs testing against your audience, reward and restriction requirements. A custom integration is not automatically unsuitable; it needs explicit scope, cost and ownership.
What must be ready for launch
Prioritise the interfaces used by the first journeys and all required player controls. A later analytics enhancement may be phased; a missing restriction feed cannot simply be treated as an optional feature if a launch action depends on it.
Record what remains untested, the temporary constraint and the owner. Do not mark a capability accepted because a roadmap promises it. For a platform switch, add the migration of identities, preferences, journey state and outstanding rewards to the migration plan.
Key numbers
Rules and limits quoted from primary sources, each checked on 30 October 2026. Confirm the current wording and your own licence conditions before relying on them.
| Fact | Source | Checked |
|---|---|---|
| GB (UKGC): all online gambling businesses must ask players to prove their age and identity before they gamble. | UK Gambling Commission: age and ID verification | 30 October 2026 |
| Malta (MGA): a self-exclusion request shall be applicable across all operated brands where there are sufficient indications of problem gambling; otherwise the operator may apply it to the requested brand only. | Malta Gaming Authority: player protection | 30 October 2026 |
| Malta (MGA): operators must offer either deposit limits or wagering limits, and the ability to set limits must always remain available and easily accessible. | Malta Gaming Authority: player protection | 30 October 2026 |
| UK (ICO guidance, under review): you must not send marketing emails or texts to individuals without specific consent. | ICO: electronic mail marketing | 30 October 2026 |
| UK (ICO guidance, under review): the soft opt-in applies only to an existing customer who bought or negotiated to buy a similar product or service, with an opt-out offered when details were first collected and in every message. | ICO: electronic mail marketing | 30 October 2026 |
Frequently asked questions
Can a generic CRM support iGaming?
It may, if the complete system can supply the required data, decisions and controls. Assess the integration and responsibility model. Neither a generalist product label nor an iGaming label proves readiness.
Does the CRM need its own bonus engine?
Not necessarily. The engine can be another system if the CRM can request the right action, receive the result and enforce the agreed eligibility and cost controls. Test duplicate requests, reversals and fulfilment failures.
Does every operator need a data warehouse?
Not as a separate compulsory purchase. The requirement is dependable data and reproducible reporting. Choose an architecture that supports those needs and your future exports.
What does "real time" mean in an integration brief?
Define it per flow: source change to usable CRM state, and decision to action. Measure the full path under realistic conditions, including the upstream feed and delivery provider.
Is player suppression a CRM or PAM responsibility?
The source system, decision layer and action endpoint all participate. Your approved policy determines the scope and action, while tests must prove that changed state reaches pending messages and rewards as required.
What evidence should a vendor provide before go-live?
A scoped data contract, named owners, results for critical normal and failure scenarios, reconciliation, operating procedures and agreed acceptance. Keep contractual commitments distinct from behaviours already demonstrated.
For the category decision, use iGaming CRM platforms compared. For help applying the requirements to a proposal and your own stack, see CRM technology advisory.
How to cite this page: EngageHut, "iGaming CRM features and integration checklist: what operators need to prove", engagehut.com, https://engagehut.com/insights/igaming-crm-features-integration-checklist/, updated 30 October 2026.
