Push notifications are not a grey area any more. The Gambling Commission treats a re-engagement message fired from a bingo app as advertising, and that classification has consequences that reach further than most operators’ marketing teams realise. A push saying “you haven’t played in 3 days, here are free spins” sent to a self-excluded or GamStop-registered user is a breach even when the underlying offer is perfectly legitimate. The message itself is the problem, not the promotion behind it.

Why the regulator treats a push notification as advertising

The Commission’s position rests on a simple reading of its advertising rules: any promotional communication that encourages participation in gambling falls inside the CAP and UKGC codes, whatever channel carries it. An in-app push is a marketing message delivered to a named account, designed to prompt a deposit or a session. That puts it in the same category as an email, an SMS or a banner, and the same obligations apply.

What has changed is enforcement attention. Bingo apps have become the busiest channel for retention marketing in the sector, and the Commission has been explicit that the medium does not dilute the message. In its guidance on remote customer interaction and in several public statements on advertising, it has repeated that the channel is irrelevant to whether a communication counts as marketing. A native app on an iPhone or Android handset is not a private space where different rules apply.

There is a second layer that catches operators out. The UKGC’s requirements on self-exclusion and on marketing to vulnerable customers sit alongside the advertising codes, and they are stricter. Once a player registers with GamStop or activates self-exclusion through an operator’s own tools, the duty to suppress marketing is absolute. The Commission has fined operators for exactly this: messages that continued after a customer had taken steps to stop gambling.

Where bingo apps go wrong with re-engagement pushes

The typical failure is structural rather than deliberate. A retention team builds a three-day dormancy trigger, the app fires a push with a welcome-style offer attached, and nobody checks the suppression list against the push pipeline. The offer might be a bingo bonus, a batch of free spins or a promo code like WELCOME2026, GOLD50 or BINGO100. All of those are legitimate marketing tools when aimed at the right people. None of them are legitimate when the recipient has asked to be left alone.

The suppression gap between CRM and the app

Most operators run their CRM from a platform that holds the marketing preferences and exclusion flags. The push service that actually delivers the notification often sits on a different system, sometimes a third-party vendor, sometimes an in-house tool bolted onto the app. If the exclusion flag does not propagate to that delivery layer in real time, the app will happily push to a GamStop-registered user because the push service has no idea the flag exists.

The fix is a hard suppression check at the point of send, not at the point of campaign build. An exclusion recorded at 09:00 should block a 09:05 push. Anything less creates a window in which a breach can occur, and the Commission does not accept “the campaign was scheduled last week” as a defence. This is the operational heart of the issue, and it is where the information gain for compliance teams really sits: the breach is not the offer, it is the delivery.

Segmentation that quietly targets the wrong people

Dormancy segments are the usual culprit. A player who has self-excluded often looks identical to a lapsed player in the data: no deposits, no sessions, no logins. If the segment is built on activity alone, the two groups merge, and the push goes to both. Good practice is to exclude anyone with an active exclusion flag, a GamStop match or a marketing opt-out from every retention segment by default, and to require a manual override with a logged reason before any message reaches them.

The same logic applies to players showing harm markers. The Commission expects operators to use their data to protect customers, and a push that nudges a heavy spender back into play after a quiet week is precisely the kind of message that attracts scrutiny. Safer play tools such as deposit limits, time-outs and reality checks exist in the account for a reason; marketing should never undermine them by treating a limit as a signal to push harder.

What compliant push marketing looks like across the major bingo apps

The practical standard is straightforward: every push must be traceable to a consent record, must respect exclusion and opt-out flags at the moment of send, and must carry clear terms where an offer is attached. That applies equally to a native app installed from the App Store or Google Play and to a mobile site where the player has added a home screen bookmark. The delivery route does not change the obligation.

Bingo Daily’s reviews of the best bingo apps UK consistently flag how operators handle this, because it separates the serious brands from the rest. For a closer look at how these platforms compare, see https://bingodaily.uk/bingo-apps/ where the focus stays on notification discipline. 888 Ladies offers an iOS app with a reasonably disciplined notification setup, and Barbados Bingo offers a mobile site where push depends on browser permissions rather than an app install. Betfred Bingo offers an iOS app with in-app messaging tied to the account, and Betfair Bingo offers iOS and Android apps that lean heavily on push for retention. The differences between them are less about the offer mechanics and more about how quickly an exclusion flag stops the next message.

  • Check that the app’s notification permission is requested at a sensible moment, not forced on first launch, so consent is genuine.
  • Confirm in your account settings that marketing preferences are set the way you want, and that turning them off actually stops pushes.
  • If you have used GamStop or self-exclusion, expect all marketing to stop, including pushes, and report any that continue.
  • Read the T&Cs attached to any push offer before opting in, especially where free spins or a bingo bonus carry wagering conditions.
  • Use deposit limits and time-outs in the account to cap spend, and treat a push that ignores those limits as a warning sign.

For operators, the checklist is the mirror image. Keep a record of when consent was given, log every push with its audience definition, and run a monthly audit that tests whether an exclusion recorded today blocks a push sent tomorrow. The Commission expects evidence, and a clean audit trail is the difference between a warning and a fine.

Safer play tools, app updates and the practical compliance routine

Safer play tools only work if marketing respects them. Deposit limits are set in the player’s account, and a push that arrives minutes after a limit is hit, urging a top-up or a bonus, undermines the tool the customer chose. The Commission has been clear that operators must not use marketing to circumvent player-set controls, and push is the easiest channel to get this wrong because it is fast and automated.

App updates add another layer. A new version of an app can reset notification permissions, change how the home screen bookmark behaves on a mobile site, or alter the way a promo code such as WELCOME2026 is applied at account login. Each of those changes needs a compliance check before release, not after. Storage space and mobile data allowance are the player’s concern; whether the update preserves suppression rules is the operator’s.

The routine that works is unglamorous. Map every push to a consent record. Test the exclusion path weekly. Keep the T&Cs for each offer current and visible. Point customers towards BeGambleAware for support and GamCare for counselling, and make sure GamStop registration is honoured across every channel, including the app. Then review the whole pipeline whenever the app is updated or a new vendor is added. That is the difference between an offer that is legitimate and a message that is a breach.