Who this is for
Operators whose retention team has outgrown the CRM hooks that came with the platform, groups running several brands that want one view of a player, and CTOs replacing a CRM that fires offers at people it should not. Buy a CRM module separately when you need real-time triggers and per-market rules that your platform's built-in tool cannot express. For a first brand, take the CRM hooks inside the platform and choose a specialist CRM once there is a player base to segment.
This page is about the software. Running campaigns every day, writing the copy and owning the retention numbers is a staffed service, scoped and priced separately under managed services.
What the module does
- Segments. Built from behaviour, not only demographics: deposit pattern, verticals played, game types, sports bet on, verification status, market. They update as events arrive, not overnight.
- Triggers. Any account event can start an action: registration, first deposit, a failed deposit, a withdrawal request, a limit change, inactivity.
- Journeys. Onboarding, reactivation and VIP sequences, each with entry and exit rules, waits and control groups, built per market.
- Channels. Email, SMS, push, on-site messages and the player inbox, with frequency caps across all of them.
- Bonus hand-off. The CRM chooses who receives an offer and when. The bonus engine decides whether that market allows it and enforces the terms.
- Suppression. Excluded, cooling-off and opted-out players drop out of every segment, checked again at the moment of sending.
Consent and marketing rules the CRM must enforce
The costly CRM mistake is a message sent to someone who should have been suppressed. The rules below come from law, a test-lab standard and the licences on this site. The right-hand column is what to test in a demo.
| Rule | Where it comes from | What the CRM must do |
|---|---|---|
| Excluded players must not be targeted by marketing | GLI-19 v3.0, the interactive gaming systems standard; national registers in Finland and Cyprus | Receive exclusions as events and check them at send time, not when the segment was built |
| Email and SMS marketing need prior consent; existing customers may get offers for similar products if they can refuse in every message, free and easily | EU ePrivacy Directive, Article 13 | Store consent per channel with a timestamp; put an opt-out in every message |
| A player may object to direct marketing, including profiling for it; their data then may not be processed for marketing | GDPR, Article 21(2) and (3) | Remove the player from marketing segments and scoring, not only from the email list |
| No welcome, deposit, free-play or VIP offers; no telephone direct marketing; retention bonuses only, at 5× wagering | Finland, from 1 July 2027 | Run Finland on its own journey set with no acquisition steps, no VIP tier and no phone channel |
| No promotion mixing betting with casino, bingo or lottery; wagering capped at 10× | Great Britain, Gambling Commission, since 19 January 2026 | Split sport-to-casino cross-sell into single-product offers for that market |
The Finnish and British rules remove the two journeys most CRM stacks are built around: the welcome sequence and the cross-sell from sport to casino. A CRM that cannot hold a separate journey set per market will either break those rules or force you to run a second CRM instance.
Module or platform
| Your situation | Specialist CRM as a module | CRM hooks inside a platform |
|---|---|---|
| First brand, no player base yet | Not yet. There is nothing to segment | Yes. Use the platform's welcome and bonus tools, export events for later |
| Established brand, retention team in place | Yes. This is where real-time triggers and journey testing matter | Only if the built-in tool already triggers in real time |
| Several brands or markets on one licence group | Yes, with one player view and journeys per market | Rarely; built-in tools tend to run per brand |
| Entering Finland or Great Britain | Yes, if it can hold a separate rule set per market | Yes, if the platform's bonus and CRM tools are already market-aware |
The platform route is set out on the casino engine and online casino software pages.
What integration with an existing stack requires
Specialist CRMs publish their integration requirements, and they look alike. Fast Track's integration guide, for example, states that its CRM "runs entirely off a real-time data feed". The operator publishes registrations, logins and payments as they happen. The CRM calls operator-hosted endpoints for user details, marketing consents and blocks or exclusions. That gives a checklist for any vendor:
- An event feed from the PAM. Registration, login, deposit, withdrawal, verification change, limit change, exclusion, bet and game-round events, published in real time. See player account management.
- One owner for consent and exclusion. The PAM holds both; the CRM reads them. If both systems store consent, they will disagree within a month.
- A bonus API. The CRM requests a bonus by template; the bonus engine grants or refuses it under that market's rules. The CRM never writes to the balance.
- Player identity across brands. A rule for matching the same person across brands and verticals, so one exclusion suppresses all of them.
- Channel providers. Email, SMS and push providers connected with delivery and opt-out callbacks flowing back.
- Reporting back. Campaign cost and bonus cost into BI and reporting, so retention is measured against what it costs.
How CRM integrations break
- Segments rebuilt overnight. A player excludes at 22:00 and gets the morning campaign at 09:00. Suppression must run at send time.
- The CRM grants bonuses directly. It bypasses the market rules in the bonus engine, and a Finnish player receives a deposit offer.
- Responsible-gambling suppression needs a developer. Then it is changed late or not at all. Compliance staff should be able to edit it.
- One journey for all markets. Fine on an offshore licence; it breaks the day the first European licence goes live.
Questions to put to any CRM vendor, including us
- Exclude a test player now: how long until they drop out of a live campaign?
- Where is consent stored, and what happens when the PAM and the CRM disagree?
- Can one brand run different journey sets per market without a second instance?
- How does a CRM offer reach the bonus engine, and what happens when the engine refuses it?
- Which events does the CRM need from our PAM, and in what format?
- How is the player matched across brands and verticals?
Frequently asked
What is the difference between a CRM and a PAM?
The PAM holds the player's state: identity, balance, limits, consent, exclusion. The CRM consumes events from it and decides what to send. A CRM without a clean event feed from the PAM is guessing.
Can I use a general CRM such as Salesforce or HubSpot?
For B2B sales, yes. For players, only with heavy custom work, because general CRMs do not receive game-round and wallet events, do not know about bonus wagering and have no exclusion logic of their own.
What does iGaming CRM software cost?
There is no public price list. One integrator's 2026 buyer guide puts purpose-built CRM SaaS at USD 1,500 to 15,000 a month, priced on active players, and CRM bundled in a platform at no extra cost or USD 500 to 5,000 a month as an add-on. Treat those as one firm's market range, not a quote.
Does the CRM run campaigns by itself?
It runs the journeys you build. Somebody still has to build them, test them, write the copy and read the results. That team is a separate decision from the software.
Is a VIP programme allowed everywhere?
No. Finland prohibits loyalty and VIP schemes from 1 July 2027 and allows only modest retention bonuses. The offshore licences on this site leave bonusing to the operator.