A push message is a notification delivered to a player’s device from an app, even when the game isn’t open. It appears on the lock screen, notification tray, or as a banner. In gaming CX, push messages serve two distinct functions. They alert players when a support conversation has received a reply, and they deliver proactive engagement messages like event announcements, re-engagement nudges, or milestone rewards, based on behavioral triggers or scheduled campaigns.
Because push messages reach players outside the game environment, they’re one of the highest-leverage channels for bringing lapsed or inactive players back into an active session, and for closing the loop on open support interactions before they become abandoned tickets.
Push message vs push notification: are they the same?
In practice, yes. “Push message” and “push notification” are used interchangeably across the industry, app stores, and most documentation. Some platforms use “push message” to refer specifically to the content of the notification (the title plus body copy), while “push notification” describes the broader delivery event. For most product, marketing, and support teams, the two terms point to the same thing.
How push messages work
Push messages travel a short path: the studio sends the message to a push service (Apple’s APNS or Google’s FCM), which then routes it to the player’s specific device using a unique token generated when the player first granted permission. The whole sequence takes seconds.
Three things have to be true for a push message to land. The player must have installed the app, granted notification permission at the OS level, and kept that permission enabled. Any one of those three failing, and the message never arrives. This is why opt-in rates, not send volume, define how much reach a push channel actually has.
Types of push messages
Most push messages in mobile games fall into one of these categories:
- Transactional push: Triggered by a specific user or system event, such as a support reply, a build completing, or an in-app purchase confirmation. Players expect these messages because they map to actions the player initiated.
- Promotional push: Marketing-led messages about sales, bundles, new content, or seasonal offers. Most prone to opt out if overused.
- Re-engagement push: Sent to lapsed players who have not opened the game in a defined window (typically 7 to 30 days). Comeback rewards and limited-time bonuses are the most common formats.
- Geolocation push: Triggered by the player’s physical location, such as proximity to an event, a real-world venue, or a regionally relevant offer.
- Rich and interactive push: Includes images, GIFs, video previews, or action buttons that let the player respond directly from the notification.
Push message best practices
- Use opt-in framing: Show an in-app prompt explaining the value of notifications before triggering the OS-level permission dialog. Pre-permission framing measurably improves opt-in rates.
- Trigger on behaviour, not on app open: Behavioural triggers (level cleared, energy refilled, support reply received) consistently outperform schedule-based blasts.
- Cap frequency by lifecycle stage: Active players can tolerate more frequent pushes than lapsed ones. Over-messaging is the fastest way to lose the channel.
- Deep link every push: Tapping a notification should take the player to the exact screen the message referenced, not the title screen.
- Segment before you send: Generic “come back” pushes train players to mute. Pushes tied to specific in-game state perform several times better.
For practitioner-level depth on each of these, see 9 push notification examples for mobile games.
