Gaming CRM buying: consent, suppression and campaign hand-offs

CRM control acceptance tests

Resolve the applicable rules and expected results with the responsible privacy and compliance owners. Do not send test campaigns to real customers.

Separate product and channel choices

For the remote licence categories it covers, Gambling Commission SR Code 5.1.12 requires marketing choices by product and channel, defaulted to opt out, and respect for those choices. It lists betting, casino and bingo, and phone, email and SMS where applicable. Its scope contains explicit licence exclusions. Start a buying exercise by confirming applicability and the actual products and channels in use. A single marketing-enabled flag cannot by itself demonstrate the required distinctions for an operation with several relevant choices.

Gambling Commission — Direct marketing preferences, SR Code 5.1.12

Keep the permission record separate from the audience

Our proposed data model records the person or account key, relevant brand or controller scope, product, channel, state, provenance and the time and version of the recorded choice. Keep any wider restriction or objection separately identifiable. Ask which record is authoritative and how each delivery system learns of a change. A segment membership is a temporary selection result, not permanent permission. Require the supplier to explain what happens when it has no reliable preference record, rather than interpreting missing data as a positive choice.

Use suppression to prevent accidental re-entry

The ICO explains that an objection to direct marketing must be respected, including relevant profiling. Its guidance recommends keeping sufficient details on a suppression list rather than merely deleting the contact, so later lists can be checked. It also says a later failure to opt out does not override a previous objection. Have the appropriate privacy owner define the minimal record, access and retention rules. Test the import process against that record; the acquisition of a new email or a fresh supplier list must not silently erase an existing objection.

ICO — Respect people’s preferences

Test the gap between selection and dispatch

Create a synthetic eligible account and select it into a scheduled campaign. Withdraw the relevant permission before dispatch, then inspect the delivery decision in each affected system. Repeat with an already queued retry and a downstream provider temporarily unavailable. The desired evidence is the evaluated preference and restriction version, the decision time and whether a message was handed off. Agree the required propagation behaviour and exception handling before the test. Counting profile updates does not establish that a queued campaign respected the change.

Exercise merges, imports and out-of-order events

Use synthetic records that deliberately disagree: an older positive choice arrives after a newer withdrawal, two accounts merge, a contact reappears through an import and a channel address changes. Ask the integrator to show the explicit conflict rule and the preserved history for each case. Do not treat event arrival order as proof of the person’s latest intention. The system must retain enough provenance to explain its decision, while the responsible team determines the appropriate legal and identity-matching treatment for ambiguous records.

Connect campaign controls with protective restrictions

In addition to marketing preferences, identify the account and safer-gambling restrictions that your approved operating policy requires campaigns to respect. Map where these controls originate and who owns failures in their application. Test a synthetic restriction across promotional email, bonuses and other relevant journeys rather than only the CRM screen. Keep an outage visible and assigned. A supplier can demonstrate propagation mechanics; it cannot establish that your overall policy is appropriate merely by showing an alert or a high-level customer score.

Make the exit and audit trail usable

Ask for a sample export of synthetic preference history, suppression references and outstanding delivery exceptions. Confirm that field meanings, timestamps and scope remain interpretable after leaving the supplier. Establish who can view identifiable evidence and use references in broader procurement reporting. Close each test with an observed outcome, owner and retest date if needed. Keep campaign performance separate from control acceptance: an attractive response rate cannot compensate for an unresolved permission or suppression failure.