Choose the behavior
Define the unfinished goal, habit, social promise, or value worth returning to.
Player retention
Give players a reason to return, not a reason to mute.
Use player context, respectful timing, and disciplined learning to build return loops that protect attention as carefully as engagement.
Illustrative retention audienceAudience estimated
Overview
Audience
Messages
Delivery
Settings
Live workspace
Paused adventurers
Inactive
72h+Level
10+Push ready
8.2kCurrent flow
ExcludeRecently messaged
ContextUnclaimed quest reward
TimingQuiet hours respected
Example data for product illustration. Not customer performance.
Trust is a retention metric.
A notification can create a return today and still damage the channel tomorrow. PushHub keeps relevance, timing, frequency, and evidence in the same decision.
How it works
Build return moments from real player context.
Find the audience
Use activity and player properties to narrow the eligible group.
Protect attention
Respect quiet hours, frequency caps, permission, and recent contact.
Learn over time
Compare message approaches and review opens without overstating attribution.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Inactivity audiences
Use stored activity properties to shape re-engagement segments.
Quiet hours and caps
Apply workspace delivery policy before provider submission.
Message experiments
Test campaign variants and review consistent engagement signals.
Predictive churn scoring
Planned models will require sufficient first-party game data and transparent controls.
In the game
Return loops players can recognize.
Unfinished onboarding
Bring a new player back to a goal they already started.
Social commitment
Notify when a guild, friend, or team action makes the return meaningful.
Earned value
Remind a player about a completed timer or reward they created through play.
Retention should not depend on notification pressure.
Eligibility, caps, quiet hours, invalid-token deactivation, and honest measurement help teams treat the channel as a long-term player relationship.
Policy before provider
Suppressed messages never leave for FCM or APNs.
Invalid-token hygiene
Permanent token failures deactivate future delivery.
No predictive claim
Churn prediction remains Roadmap and is not implied by current segmentation.
Questions teams ask before they commit.
Not today. Predictive churn scoring is Roadmap. Current teams can build audiences from the activity properties they provide.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.