Attempted
A durable recipient record exists and provider submission can begin.
Delivery analytics
Know what reached players and what happened next.
Read the notification funnel with campaign, platform, app, and device context instead of blending every delivery state into one success number.
Illustrative analytics viewLive view
Overview
Audience
Messages
Delivery
Settings
Live workspace
Season launch funnel
Attempted
18.4kAccepted
17.9kOpened
624Current flow
AndroidFCM acceptance tracked
iOSAPNs acceptance tracked
SuppressedPolicy reasons visible
Example data for product illustration. Not customer performance.
Provider acceptance is not player delivery.
PushHub names each stage precisely so LiveOps can measure engagement while engineering can diagnose infrastructure and token health.
How it works
Read the funnel in the order it happens.
Accepted
FCM or APNs accepted the request for further delivery.
Delivered
A device receipt confirms arrival where client instrumentation supports it.
Opened
A tracked player interaction connects the notification to an app open.
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 analytics
Review recipient counts and outcomes for each campaign and message variant.
Delivery diagnostics
Group recent failures and suppressions by normalized reason with operator guidance.
App health overview
See device, platform, campaign, and notification trends within an app.
Revenue attribution
Planned conversion models will connect campaign exposure to game-defined business events.
In the game
One report, several operating questions.
Is the provider healthy?
Compare acceptance and normalized failure reasons across platforms.
Was the audience reachable?
Review invalid tokens, suppressions, and registered-device health.
Did the message earn attention?
Compare opened outcomes after accounting for delivery differences.
Clear labels prevent confident mistakes.
Every metric is tied to an observable platform state. Missing receipts do not become invented delivery, and accepted requests do not become claimed conversions.
Normalized outcomes
Sent, delivered, opened, failed, and suppressed remain distinct.
Attempt history
Transient retries retain their provider outcome history.
No invented attribution
Revenue and long-term retention attribution are labeled Roadmap.
Questions teams ask before they commit.
Sent means a provider accepted the request. Delivered requires a later device receipt.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.