Symplify
Symplify supplies first-party CRM and marketing-automation software for online casino and sportsbook operators. The product covers recipient profiles, segmentation, automated journeys, and communication across configured digital and offline channels; it is not a PAM, wallet, payment system, or gambling operation.
Page updated
Symplify Technologies AB is the legal company behind the brand and is registered in Pennsylvania for CRM services. The contracting entity may vary by region.
Buyer decision brief
Use this summary to decide whether the offer belongs on your shortlist and which terms need a written answer.
Fit and use case
Editorial fitCasino and sportsbook operators that want one CRM and journey layer with several ingestion options and can actively govern player identifiers, database boundaries, suppression state, communication providers, and retention.
Primary offer: Symplify iGaming CRM
Primary offer delivery
- Software license
Integration boundary: An operator chooses an identifier and database model, then supplies recipient and transaction data through Event Hub or Kafka, REST APIs, scheduled files, manual imports, or optional DataDocs and DataHub features.
Critical contract questions
Start with unresolved terms, negotiated terms, and dependencies that need a named owner.
Resolve before shortlist
No usable standard answer is available on the public terms.
- License and add-on pricingNot disclosed
- Symplify iGaming CRM · Commercial terms
Fix in the signed order
The answer changes by operator, market, package, or negotiated order.
7 of 9 shown- Other jurisdiction controlsSet in contract
- Symplify iGaming CRM · Market and approvals
- Database and account boundariesSet in contract
- Symplify iGaming CRM · Contract and supplier
- Supplier and licensed scopeSet in contract
- Symplify iGaming CRM · Contract and supplier
- Player-state and communication decisionsSet in contract
- Symplify iGaming CRM · Operating responsibilities
- Retention and data rightsSet in contract
- Symplify iGaming CRM · Operating responsibilities
- Chosen ingestion routeSet in contract
- Symplify iGaming CRM · Implementation
- Suppression and channel setupSet in contract
- Symplify iGaming CRM · Implementation
Next buyer step
Ask Symplify to resolve “License and add-on pricing” before moving Symplify iGaming CRM to a commercial shortlist. Then compare the answer with the complete product record below.
Confirm every selected term in the proposal and signed order. No price, market approval, availability, or contracting entity is implied unless it is stated above.
What this provider offers
1 offering- OfferingSymplify iGaming CRMTypeCRM · Multi ProductOwnership and packagingFirst Party · StandaloneDeliverySoftware LicenseCompare in
- Casino CRM & Retention Platforms · Technology Owner
Symplify iGaming CRM
Multi ProductFirst PartyAvailability: StandaloneSymplify supplies first-party CRM and marketing-automation software for online casino and sportsbook operators. The product covers recipient profiles, segmentation, automated journeys, and communication across configured digital and offline channels; it is not a PAM, wallet, payment system, or gambling operation.
Data paths differ materially: event messages and Kafka support high-volume or event-driven use, REST APIs provide near-real-time recipient updates, daily scheduled files handle batch imports, and add-on DataDocs or DataHub functions process transactional data. A generic 'real-time' promise does not establish the latency or data scope of a proposed deployment.
Opt-out, blocking, and self-exclusion controls have important boundaries. Opt-out state is tied to a specific Symplify database, DataHub rules can return blocked or self-excluded contacts in segment results before suppressing communication, and a Journey can be configured to ignore opt-out for selected messages. The operator must govern those settings across every brand, database, journey, and channel.
Products
Integration: An operator chooses an identifier and database model, then supplies recipient and transaction data through Event Hub or Kafka, REST APIs, scheduled files, manual imports, or optional DataDocs and DataHub features. Journeys can start from stored data or ad hoc API requests. The chosen path determines latency, reconciliation, deletion, and the operator work required to keep consent, block, and self-exclusion state aligned.
Key facts
- Symplify Technologies AB is the legal company behind the brand
- Symplify Technologies AB, DBA Symplify, is registered for CRM services to operators and PAMs operating in Pennsylvania
- Symplify provides an iGaming CRM for casino and sportsbook operators with player segmentation, journey automation, personalization, and multichannel communication
- Event Hub and Kafka, REST API, daily scheduled files, manual imports, DataDocs, and DataHub are separate integration paths with different latency and data behavior
- DataHub segment results can include blocked or self-excluded recipients before communication suppression, opt-out state is database-specific, and Journeys expose an ignore-opt-out option for selected messages
- Contact and message retention is license-linked and automatically purged under configured rules, while DataDocs has no automatic retention and must be updated or deleted by the customer
- Symplify Technologies AB controls its own website and digital-channel data; controller, processor, hosting, subprocessor, transfer, and model-training terms for operator player data are deployment-specific
Delivery options
Software License
Delivery modelCRM and multichannel journey software connected to an operator's PAM, data sources, sites, apps, and selected delivery providers.
Included
- + Recipient profiles, attributes, transactional-data options, and segmentation
- + Journey and campaign orchestration
- + Configured communication channels and content workflows
- + REST, event-stream, and file-based integration options
- + Opt-out, retention, and anonymization configuration tools
Not included
- ! A PAM, gaming wallet, sportsbook, or casino engine
- ! A gambling license or operator market authorization
- ! Deposit, withdrawal, payment, or merchant-of-record service
- ! Operator bonus eligibility, funding, wallet posting, or reversal execution
- ! Automatic inclusion of every channel, add-on, carrier, or third-party account
- ! A universal controller and processor allocation or regulatory-compliance guarantee
Procurement record
Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.
Known is usable now. Contract specific changes by order or market. Not disclosed has no usable standard term. Unknown remains unresolved. Outside provider scope is handled by the operator or another supplier.
Contract and supplier
- Supplier and licensed scopeContract specific
- The order must name Symplify Technologies AB or another counterparty, invoice issuer, service and hosting locations, and the exact CRM, channel, DataDocs, DataHub, carrier, support, and implementation components.
- Database and account boundariesContract specific
- Define brands, accounts, projects, databases, identifiers, channel accounts, permissions, environments, and cross-database behavior. Opt-out state and important controls are database-specific, so the architecture belongs in the signed scope.
Implementation
- Chosen ingestion routeContract specific
- Specify Event Hub, Kafka, REST, scheduled files, manual imports, DataDocs, or DataHub for each data set, with schemas, latency, ordering, duplicates, backfill, reconciliation, failures, and recovery. Do not contract only for generic real-time delivery.
- Suppression and channel setupContract specific
- Map opt-out, self-exclusion, blocking, ignore-opt-out permissions, sender identities, social audiences, third-party channels, delivery receipts, test accounts, and brand-specific acceptance tests before journeys can send.
Operating responsibilities
- Player-state and communication decisionsContract specific
- Assign truth and synchronization for consent, opt-out, self-exclusion, cooling-off, blocks, promotion eligibility, content approval, override permission, channel compliance, delivery failure, and incident action across operator and connected systems.
- Retention and data rightsContract specific
- The DPA must cover controller and processor roles, hosting, subprocessors, transfers, retention for contacts, messages and DataDocs, anonymization, deletion across integrated systems, security support, and incident notice.
Operations and service
- Control and resilience testingContract specific
- Test database-scoped opt-out, blocked and self-excluded segment results, override permissions, late or duplicated events, file failure, Kafka interruption, API retries, channel outage, anonymization, audit retrieval, rollback, and recovery.
Commercial terms
- License and add-on pricingNot disclosed
- Public pricing is unavailable. Separate implementation, migration, contacts, messages, databases, environments, channels, carriers, Event Hub or Kafka, DataDocs, DataHub, API use, retention, support, overages, and termination assistance.
Market and approval scope
- Pennsylvania registrationKnown
- Symplify Technologies AB is registered for CRM services to operators and PAMs operating in Pennsylvania through March 21, 2028. This does not authorize an operator or establish approval in another market.
- Other jurisdiction controlsContract specific
- Confirm vendor registration, data location, consent, suppression, channel rules, retention, and audit settings for each additional market, operator entity, brand, product, and database.
Exit and portability
- Export and coordinated deletionContract specific
- Require exports of contacts, identifiers, attributes, transactions, segments, journeys, templates, consent and suppression state, delivery results, permissions, and logs. Define carrier shutdown, API cutover, DataDocs cleanup, deletion across integrations, and completion evidence.
Strengths
- + Daily-file, REST, event-stream, Kafka, DataDocs, and DataHub paths are separated instead of presenting every deployment as generically real time.
- + Database-scoped opt-out, blocked and self-excluded segment behavior, data retention, and API anonymization can be tested before procurement.
- + The Pennsylvania registration names the legal entity and limits its service scope to CRM through March 2028.
What to verify in procurement
- ! Pennsylvania registration is jurisdiction-specific service-provider evidence. It is not a gambling license, operator approval, or permission for any other market.
- ! Confirm the contracting entity, controller and processor roles, hosting, subprocessors, transfers, retention, deletion, security support, model use, and exit assistance in the customer DPA.
- ! Do not buy a generic real-time promise. Specify the actual data path, event schema, latency, ordering, duplicate handling, backfill, reconciliation, outage behavior, and recovery target for each source.
- ! Opt-out is database-specific and Journeys can ignore it. Require cross-database suppression design, narrow permissions for any override, approval and audit logs, and end-to-end tests for opt-out, self-exclusion, cooling-off, and responsible-gambling state changes.
- ! DataHub rules, DataDocs, channels, and carriers can be add-ons or external dependencies. Price and contract each required component instead of assuming they belong to the default package.
Reference documents6
Key public documents supporting the company identity, primary offer, delivery route, and highest-priority questions above.
- DocumentPennsylvania Gaming Control Board — pgcb.pa.gov / Reports / Certified Registered Gaming Service Providers Autho…
- DocumentSymplify — symplify.com / privacy policy
- DocumentSymplify — symplify.com / igaming crm
- DocumentSymplify Expertise — help.symplify.com / articles / 360011073180 Integration overview
- DocumentSymplify Expertise — help.symplify.com / articles / 22442870209180 Overview of Symplify Communication…
- DocumentSymplify Expertise — help.symplify.com / articles / 7993420709020 DataHub Rules
