FCM message delivery: payload, TTL, collapse
Google's push channel: 4 KB payload, up to 4 weeks held, delivered through Play services.
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
| Android | iPhone | |
|---|---|---|
| Status | Supported | Not supported |
| First version | Android 1.0 (API 1) | Not available |
| Permission or entitlement | INTERNET, com.google.android.c2dm.permission.RECEIVE (handled by Play services) | Not listed |
| Protection level | normal | none |
| How access is granted | install | not-exposed |
| What the user sees | None for data messages; notification messages need POST_NOTIFICATIONS on 13+ | Not listed |
| How long it lasts | Messages are stored while offline: default TTL 4 weeks (0 to 2,419,200 s); up to 100 pending messages per device then a full resync | Not listed |
| How to take it back | Per app: notifications off, force stop, uninstall | Not listed |
| Store policy | Play services required; not on China devices without Google Mobile Services | None listed |
| API | FirebaseMessagingService.onMessageReceived() | Not listed |
| Notes | Payload limit 4096 bytes (data), 2 KB for topic messages; 4 collapse keys per device; rate limits per device apply | Apple equivalent is APNs; see mob.notif.apns-delivery |
Data you get
What comes back: Push message
Shape: object
How often: Per message
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
payload | binary | binary | 0 to 4096 | exact |
ttl | integer | seconds | 0 to 2419200 | 1 s |
collapse_key | string | key | max 4 distinct per device | exact |
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
| Type | Example | Apps |
|---|---|---|
| messaging | A chat app sends a tiny nudge, and the app then fetches and shows the message. | WhatsApp, Telegram |
| delivery | An order app updates your food status with a message that replaces the older one. | Uber Eats |
| games | A game tells you a friend beat your score, with a short life so it is not stale. | Words With Friends |
| shopping | A store sends a flash sale alert with a time limit. | Amazon |
| news | A news app sends a breaking story and merges older ones. | Google News |
| security | A login app sends a sign in approval push to your phone. | Duo, Google |
| ads | A 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
- Google: Firebase Cloud Messaging. Google describes FCM as a cross platform way to deliver messages reliably, with options for how long they live.
Good uses and abuse
Legitimate uses
- Chat nudges
- Order updates
Known abuse
- Notification spam
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough 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
Related capabilities
Related
- FCM priority and deprioritization. Can wake a sleeping Android phone with a high priority push, but misuse gets slowed down
- Push token registration (FCM token, APNs device token). Can get an address so its server can reach your app, even when closed
Same idea on the web
- Push API (Web Push). Can send you notifications after you leave, once you allow them
Sources
How well checked: Based on official documentation.