FCM priority and deprioritization
High priority pushes wake a sleeping phone, but Android downgrades apps that abuse them.
In one line
Can wake a sleeping Android phone with a high priority push, but misuse gets slowed down
High priority pushes wake a sleeping phone, but Android downgrades apps that abuse them.
High priority is the only way to reach a dozing phone fast. Apps that send high priority with no visible notification get demoted over a 7 day window, so engagement bots must show something.
What it can and can't do
What the user does: Nothing. The app's server picks the priority when it sends a message
It can
- Wake a phone in Doze for something urgent like a call or chat
- Do some short work right after the wake up
- Send normal priority pushes that arrive quietly when the phone is awake
It cannot
- Use high priority for ads without getting downgraded
- Deliver normal priority pushes right away while the phone is in Doze; they wait
- Do long work after a wake up
- Use this on iPhone, which has its own priority levels
How it differs between platforms: Android has normal and high FCM priority. iPhone uses APNs priority 10, 5 and 1.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Not supported |
| First version | Android 6.0 (API 23) | Not available |
| Permission or entitlement | None beyond FCM | Not listed |
| Protection level | none | none |
| How access is granted | install | not-exposed |
| What the user sees | None | Not listed |
| How long it lasts | Deprioritization is evaluated over the previous 7 days per app instance; visible notifications prevent it | Not listed |
| How to take it back | n/a | Not listed |
| Store policy | FCM docs: use high priority only for time-sensitive, user-visible messages | None listed |
| API | AndroidConfig.priority, android_v2 message types (RemoteNotification, BackgroundSync) | Not listed |
| Notes | Normal: delivered immediately if awake, deferred in Doze. High: can wake Doze, allowed limited work; standby bucket no longer sets the quota (Android 13). v2 RemoteNotification gets a 20 s execution window | APNs has apns-priority 10, 5, 1; see mob.notif.apns-delivery |
Data you get
What comes back: Priority class
Shape: enum
How often: Per message
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
priority | enum | None | normal, high | Not listed |
v2_type | enum | None | RemoteNotification, BackgroundSync | Not listed |
window | integer | seconds | about 20 | Not listed |
Technical limits
- Downgrade is automatic and silent
- Proxying (Beta) can reduce delivery metrics up to 15%
The story
What it is
Whether a push can wake a sleeping Android phone right away, with penalties for abuse.
For you
You get a call or chat alert even when the phone is dozing. Less urgent alerts wait until the phone wakes, so you may see them late.
For makers
Makers need high priority to be on time for calls and chat. Android demotes apps that send high priority pushes without showing anything, so they must show a visible alert.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A call app uses high priority so your phone rings when locked. | WhatsApp, Signal |
| health | A glucose monitor sends a high priority low blood sugar alert. | None named |
| rideshare | A driver app gets an urgent ride request on a sleeping phone. | Uber |
| games | A game sends a normal priority daily reward alert that can wait. | None named |
| security | A banking app sends a high priority fraud alert. | None named |
| ads | An ad team learns that silent high priority pushes get penalized, so campaigns must show a notice. | None named |
| smart-home | A doorbell app sends an instant visitor alert. | Ring |
Risks
- Abuse can drain battery
- Late alerts when priority is low
Android and iPhone in short
- Android: Android only. High priority pushes can be demoted over about a week if misused.
- iPhone: iOS has a similar priority number in APNs.
What the platform says
- Google: Message priority. Google explains high and normal priority in FCM and warns that misuse can cause lower priority delivery.
Good uses and abuse
Legitimate uses
- Calls
- Chat
Known abuse
- High priority data wakeups to harvest signals
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2015-10, Android 6.0 (API 23): Doze introduced; high priority FCM is the main exemption
- 2022-08, Android 13 (API 33): High priority count no longer tied to standby bucket; downgrade when no notification is shown
- 2024-07, Android FCM: Legacy HTTP API shutdown begins; HTTP v1 message format with android config required
Related capabilities
Related
- FCM message delivery: payload, TTL, collapse. Can send alerts to an Android phone through Google, up to 4 KB per message
- Doze and idle mode. Can't force the phone to stay awake; Doze delays jobs, alarms and network
Same idea on the web
- Chrome and OS defenses against notification abuse. Can't keep sending spam if you block it; Chrome quiets and removes abusers
Sources
How well checked: Checked against real behavior.