Shape the moment
Write title, body, data, deep link, and optional message variants.
Campaign management
Make every message worth the return.
Plan, target, deliver, and learn from player campaigns in one calm operating surface built for living games.
Illustrative campaign workspaceReady to schedule
Overview
Audience
Messages
Delivery
Settings
Live workspace
Season finale
Estimated audience
18.4kVariants
02Policy checks
ReadyCurrent flow
Content previewAndroid and iOS
AudienceLevel 20+ active players
SchedulePlayer evening window
Example data for product illustration. Not customer performance.
Relevance before reach.
The goal is not to send more notifications. It is to make the next message feel like a useful part of the game.
How it works
From player moment to measurable outcome.
Know the audience
Choose a reusable segment and estimate eligible reach before launch.
Protect the player
Apply caps, quiet hours, readiness checks, and campaign controls.
Read the outcome
Separate provider acceptance, device receipts, opens, failures, and suppression.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Campaign lifecycle
Create, update, schedule, send, cancel, and inspect campaigns with their operating context intact.
Audience estimation
Validate the expected segment or all-device audience before committing a send.
Batch-safe dispatch
Process recipients in bounded batches with idempotency and cancellation checks between batches.
Player-local delivery policy
Workspace delivery time zones and quiet-hour controls are available while scheduling UX continues to mature.
In the game
Campaigns for the moments players already understand.
New season
Introduce fresh content to the players most likely to value it.
Final hour
Remind eligible participants before progress or rewards expire.
Service notice
Communicate maintenance and restoration with a clear operational record.
A launch should never be a leap of faith.
Readiness checks, deterministic recipient identity, provider diagnostics, and delivery logs make each campaign reviewable before and after dispatch.
No duplicate recipient rows
A campaign and device pair has one durable notification record.
Controlled cancellation
Cancellation is checked before the next recipient batch.
Clear semantics
Sent means provider accepted; delivered and opened require device receipts.
Questions teams ask before they commit.
Yes. Cancellation prevents new batches from starting, while already submitted provider requests remain part of the delivery record.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.