Capture
Register the device and update the player context the moment depends on.
Player moment library
Start with the moment your game already creates.
Explore practical notification patterns across activation, LiveOps, social play, progression, commerce, and service operations.
Illustrative moment mapSix patterns
Overview
Audience
Messages
Delivery
Settings
Live workspace
Player lifecycle
Activation
02Engagement
03Recovery
01Current flow
player.reward_readyProgression reminder
guild.raid_startedSocial return
service.restoredOperational update
Example data for product illustration. Not customer performance.
The best trigger is usually already in the game.
A useful push extends a player goal, social promise, live event, earned reward, or operational need rather than inventing urgency outside the experience.
How it works
A repeatable pattern for every use case.
Target
Define who is eligible and who should be excluded.
Send
Use a scheduled campaign, direct notification, or authenticated event trigger.
Learn
Review delivery, opens, variants, suppressions, and operational history.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Onboarding and progression
Support unfinished goals, unlocked systems, completed timers, and earned rewards.
Live events and social play
Coordinate starts, deadlines, guild activity, invitations, and results.
Commerce and service recovery
Handle relevant offers, interrupted purchases, maintenance, and restoration.
Multi-step lifecycle journeys
Planned orchestration will connect several moments into one adaptive player path.
In the game
Six families of useful player communication.
Activation
Welcome players back to unfinished onboarding and newly unlocked systems.
LiveOps
Announce events, remind eligible participants, and close reward windows.
Social
Make a return meaningful through guild, friend, and team activity.
Progression
Surface completed crafting, energy, quests, and earned rewards.
Commerce
Connect relevant offers and recovery steps to trusted game context.
Operations
Communicate maintenance, incidents, and restoration with clarity.
Every pattern starts with a reason not to send.
Eligibility, recent contact, permission, caps, quiet hours, and current game state belong in the workflow before creative is approved.
Audience fit
The player can use or value the moment.
Timing fit
The message arrives inside an appropriate window.
Evidence fit
The team knows which observable outcome will inform the next decision.
Questions teams ask before they commit.
Choose one high-confidence game event with clear player value, reliable data, and a measurable response.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.