Player messaging
Satori’s Messages feature enables game teams to reach players through multiple channels. For example:
- Send players a push notification reminder for an upcoming tournament
- Send direct messages to a likely-to-spend segment of players for special promotions
- Provide a notification inbox experience in your game
Message types #
Satori supports two message types: scheduled and direct. The distinction determines who receives the message, when it sends, and whether a template is required.
| Scheduled | Direct | |
|---|---|---|
| Recipients | A player audience (segment) | One or more specific players by identity ID |
| Trigger | Automated: fixed date, cron schedule, or live event timing | On demand: sent immediately by a team member |
| Template | Required | Optional: write ad-hoc content inline |
| Use for | Tournament reminders, event notifications, recurring broadcasts | Support resolutions, targeted rewards, urgent one-off notifications |
Scheduled messages run without human intervention at send time, so content must be defined in a template upfront. Direct messages are sent by a person in the moment, so writing content inline is supported.
Delivery channels #
Satori delivers messages through two paths, which may be used on their own or combined:
- In-game inbox: Messages are stored server-side and fetched by the game client when the player is active. No external integration required.
- Push and email: Messages are sent through external integrations (OneSignal, APNS, FCM, Facebook A2U, or a custom Webhook) to reach players outside the game.
Key capabilities #
| Reach players inside and outside the game | Messages are stored in the player's in-game inbox and delivered via push notification or email through your chosen integrations. |
| Personalise every message with player data | Templates support property placeholders (default, computed, and custom) so messages reflect each player's name, level, spend tier, or any other attribute. |
| Send messages in each player's language | Add translations to any template and Satori automatically selects the correct version based on the player's language property. |
| Tie message delivery to live event timing | Connect a schedule to a live event and trigger delivery before the event starts, when it ends, or at any configured offset. |
| Target specific audiences and exclude others | Apply the same audience segments you use for experiments and live events to every message schedule. |
| Send one-off messages to individual players | Direct messages go to one or more specific players via the Console API or the dashboard identity page. |
How Satori is different #
Built-in segmentation #
The same audience you built for your live event is the audience your message targets. When a player moves out of that segment, they’re excluded automatically.
Live event integration #
You set a reference point (before the event starts, after it ends, or at a specific offset) and Satori handles the timing. No webhooks to maintain, no external scheduler to coordinate.
Offline messaging via external messaging services #
Distribute messages to your players while they aren’t interacting with your game. Satori provides integrations with OneSignal, Apple Push Notification Service, Firebase Cloud Messaging, Facebook App-to-User Notifications and Webhook.
Send email to players with HTML formatting #
In addition to push notifications, Satori supports email for OneSignal integration. If you collect player emails, you can reach them via Satori’s OneSignal integration too. With Satori’s HTML templates, you can send visually appealing emails that promote your content in a customizable format.
