Firebase push features

Firebase push analytics and audience health

Understand reachable devices, stale FCM tokens, platform mix, activity windows, and campaign history before you send another Firebase push.

The problem

A raw token count is not a reachable audience. Tokens go stale after uninstalls, app data clears, inactivity, and device migrations. Without health reporting, campaign planning is based on inflated numbers.

How Pushbrain helps

Pushbrain tracks device metadata and send outcomes so you can see active, stale, platform, environment, permission, and reachability signals around your Firebase push audience.

  • Active and stale FCM token visibility
  • Platform and environment segmentation
  • Permission and reachability context before a broadcast
  • Send history tied back to campaign decisions

Audience health before campaign analytics

Open rates are only meaningful when the denominator is honest. Pushbrain helps separate registered devices from recently reachable devices so campaign numbers are less misleading.

Token hygiene as product infrastructure

Pushbrain prunes stale tokens after send responses and exposes aggregate health signals, reducing the maintenance work that usually hides inside direct FCM integrations.

Questions

Does Firebase tell me which tokens are stale?

Usually only at send time, through per-token errors. Pushbrain processes those outcomes and keeps audience health visible.

Can I segment Firebase push audiences?

Yes. Pushbrain supports push-specific segmentation by platform, environment, permission status, and activity recency.