Capture context
Register devices and update the player attributes your game already understands.
Player segmentation
Build audiences from how players actually play.
Move beyond token lists with reusable audiences shaped by device context, player attributes, progression, and behavior.
Illustrative segment builder18,420 matches
Overview
Audience
Messages
Delivery
Settings
Live workspace
Raid-ready players
Rules
04Platforms
02Reachable
91%Current flow
ProgressionLevel is 20 or higher
ActivitySeen in last 7 days
PreferencePush permission active
Example data for product illustration. Not customer performance.
An audience is a living rule, not a frozen export.
Segments stay connected to the player and device data your game updates, so targeting can evolve without rebuilding lists by hand.
How it works
Make audience logic readable and reusable.
Compose rules
Combine supported property conditions into a named audience definition.
Estimate reach
Check the current match count before attaching a campaign.
Reuse with confidence
Select the same segment across campaigns while its membership evolves.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Property rules
Create segment rules from stored device and player properties using supported operators.
Audience estimate
Calculate eligible reach before launch without creating a campaign.
App-scoped membership
Keep every audience inside the correct app and company boundary.
Event-window segmentation
Planned behavioral windows will combine event frequency and recency with current player properties.
In the game
Audience ideas grounded in game state.
Progression cohort
Reach players who unlocked the systems required for a new event.
Lapsed regulars
Find previously active players whose last session is outside the healthy return window.
Platform rollout
Coordinate messaging around OS, version, locale, or provider readiness.
Precision includes knowing who should not receive.
App boundaries, active-token checks, notification permission, and delivery policies narrow a matched segment to an eligible audience.
No cross-app targeting
Segments and devices remain app-scoped.
Reach is an estimate
The final eligible count can change as player and device state changes.
Consent-aware delivery
Inactive or invalid device tokens are excluded from future work.
Questions teams ask before they commit.
No. A segment stores targeting rules and evaluates them against current app data.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.