Skip to Content
Platform.Ontology

FCM message delivery: payload, TTL, collapse

Google's push channel: 4 KB payload, up to 4 weeks held, delivered through Play services.

Works without askingNotifications and backgroundPushAndroid and iPhoneIn the background

In one line

Can send alerts to an Android phone through Google, up to 4 KB per message

Google's push channel: 4 KB payload, up to 4 weeks held, delivered through Play services.

A server can nudge an Android install with small data. Limits shape what a marketer can do: little payload, and queued messages expire or collapse, so apps fetch the real content after the nudge.

What it can and can't do

What the user does: You allow notifications on Android 13 or newer, or just install the app

It can

  • Send a message that can wait up to 4 weeks if you are offline
  • Replace an older message with a newer one using a collapse key
  • Send data to the app quietly without showing an alert

It cannot

  • Show a visible alert on Android 13 or newer if you said Don't allow
  • Send more than about 4 KB, or 2 KB to topics
  • Hold messages longer than 4 weeks
  • Use this on iPhone, where Apple's own system does the job

How it differs between platforms: Android uses Google's FCM. iPhone uses Apple's APNs.

On Android and iPhone

AndroidiPhone
StatusSupportedNot supported
First versionAndroid 1.0 (API 1)Not available
Permission or entitlementINTERNET, com.google.android.c2dm.permission.RECEIVE (handled by Play services)Not listed
Protection levelnormalnone
How access is grantedinstallnot-exposed
What the user seesNone for data messages; notification messages need POST_NOTIFICATIONS on 13+Not listed
How long it lastsMessages are stored while offline: default TTL 4 weeks (0 to 2,419,200 s); up to 100 pending messages per device then a full resyncNot listed
How to take it backPer app: notifications off, force stop, uninstallNot listed
Store policyPlay services required; not on China devices without Google Mobile ServicesNone listed
APIFirebaseMessagingService.onMessageReceived()Not listed
NotesPayload limit 4096 bytes (data), 2 KB for topic messages; 4 collapse keys per device; rate limits per device applyApple equivalent is APNs; see mob.notif.apns-delivery

Data you get

What comes back: Push message
Shape: object
How often: Per message

FieldTypeUnitRangePrecision
payloadbinarybinary0 to 4096exact
ttlintegerseconds0 to 24192001 s
collapse_keystringkeymax 4 distinct per deviceexact

Technical limits

  • 4 KB payload ceiling
  • Messages to an app in the stopped state are not delivered until the user opens the app
  • Normal priority is deferred in Doze

The story

What it is

Google's push system that carries small messages from an app's server to an Android phone.

For you

You see an alert appear almost instantly. If your phone is off, it can be held for up to four weeks and then drop. Repeated alerts may be merged into one.

For makers

Makers use it for chat, orders and news. The size limit is small, so the push just nudges and the app downloads the real content after.

Where you see it

TypeExampleApps
messagingA chat app sends a tiny nudge, and the app then fetches and shows the message.WhatsApp, Telegram
deliveryAn order app updates your food status with a message that replaces the older one.Uber Eats
gamesA game tells you a friend beat your score, with a short life so it is not stale.Words With Friends
shoppingA store sends a flash sale alert with a time limit.Amazon
newsA news app sends a breaking story and merges older ones.Google News
securityA login app sends a sign in approval push to your phone.Duo, Google
adsA marketer sends a campaign push and counts opens as a measure.None named

Risks

  • Opens and delivery can be tracked
  • Spam if overused

Android and iPhone in short

  • Android: Android only. Alerts need permission from Android 13 on.
  • iPhone: iOS uses APNs.

What the platform says

Good uses and abuse

Legitimate uses

  • Chat nudges
  • Order updates

Known abuse

  • Notification spam

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility5 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

A real example: LinkedIn

LinkedIn Android app uses FCM for notifications

History

  • 2022-08, Android 13 (API 33): Visible notifications additionally need POST_NOTIFICATIONS
  • 2024-07, Android FCM: Legacy API sunset begins; HTTP v1 and OAuth2 tokens required

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page