Reach players beyond the current session.

Send supported notifications to players who have opted in. Keep your audience informed about relevant updates and moments in your game.

Device registration

Supported sending workflows

Delivery reporting

Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Request consent and manage registered devices, including changes to tokens or preferences.

Send only relevant messages to eligible players through a confirmed provider integration.

Distinguish provider acceptance, device delivery, and player engagement when interpreting results.

ILLUSTRATIVE GAME WORKFLOW

This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Respect player consent and device registration. A provider accepting a notification does not prove device delivery or a player opening the game.

Explore complementary services for your game, with integration details for each building block.

SERVICE 1

Understand what happens across the player journey.

SERVICE 2

Adjust game settings between releases.

A test workspace with access to Push Notifications.

Step 1: pending

A confirmed API version and documented permissions for the workflow.

Step 2: pending

Client and backend tests for successful, invalid, repeated, and interrupted requests.

Step 3: pending

How does this fit my game?

What should my team own?

Can I use this integration today?

YOUR NEXT CHAPTER STARTS HERE

Explore the services and plan your first player experience.