Why your push open rates dropped in 2025 (and how to get them back)

If you run a D2C brand or a consumer app in India, you have probably watched your push notification open rates slide through 2024 and fall off a cliff in 2025 — without changing a thing about your campaigns. You are not imagining it, and your copywriter is not the problem. The operating system changed the rules.

What actually changed

Two shifts landed within months of each other. On iOS, Apple shipped Scheduled Summaryand leaned harder into notification grouping. Instead of buzzing the user the moment your push arrives, iOS now collects “non-urgent” notifications and delivers them in a batched digest at times the user picks — often once in the morning and once in the evening. When your push lands in that digest, it competes with dozens of others and shows up as a single collapsed line. With Apple Intelligence on newer devices, that line can even be an AI summary of several of your notifications — your carefully written copy gets paraphrased by a model you do not control.

On Android, the story is bundling and channel importance. Android aggressively groups notifications from the same app and demotes anything on a low-importance channel into a silent, collapsed stack. Android 15 continued tightening “notification cooldown” behavior for apps that fire frequently. If your marketing pushes share a channel with everything else, or sit at DEFAULT importance, they get buried.

Why this crushed open rates specifically

Push used to be a near-guaranteed interrupt: it lit up the lock screen, buzzed the phone, and earned a glance. That glance was the open. The 2025 OS behavior breaks the interrupt. A push that lands in a summary does not buzz, does not light the screen, and is shown — if at all — as one truncated line inside a stack the user scrolls past. No interrupt, no glance, no open.

The brands hit hardest are exactly the ones who treated push as a firehose: high volume, generic copy, lots of emojis and exclamation marks, everything sent at the same default priority. The OS reads those exact signals — frequency, low relevance, “marketing-shaped” text — as reasons to summarize and demote. The more you blast, the harder you get throttled.

The fixes that actually move the needle

You cannot opt out of the OS behavior. But you can send notifications the OS treats as worth surfacing. Three levers do most of the work:

1. Front-load and shorten the copy.Summaries truncate hard. The single most important word — the offer, the number, the action — has to be in the first 30–40 characters of the title. “Big sale is live!!!” says nothing in a collapsed stack. “₹300 off ends tonight” survives, because even truncated it carries the value and the deadline.

2. Set the right priority signal per platform. On iOS, genuinely time-sensitive pushes can be sent with an interruption-level of time-sensitive, which lets them break through Scheduled Summary — but you have to earn it with content that justifies it (an expiring offer, an order update), or users mute you. The relevance-score decides which of your pushes ranks at the top of a stack. On Android, the equivalent is putting transactional and time-sensitive pushes on a separate HIGH-importance channel, and leaving routine marketing on a calmer one.

3. Strip the signals that get you demoted.Triple exclamation marks, “FREE”, “WIN”, stacks of emojis — these read as spam to both the OS heuristics and the user. Clean, specific, benefit-led copy is treated more like a communication notification and less like a broadcast.

Why “just write better copy” isn’t enough

The hard part is that you are now optimizing for two different OS ranking systems at once, you cannot see how either one scored your notification, and your analytics dashboard probably reports “delivered” even when the push was silently summarized into oblivion. “Delivered” from FCM or APNs means the payload reached the device — not that a human ever saw it. That gap between delivered and actually surfaced is where your open rate quietly died, and most teams never measure it.

What we built

PushSaver is the layer that sits between your campaign and FCM/APNs. You send us the raw push; we rewrite the copy to survive truncation, score how likely it is to make it past the summary (0–100), and tell you the exact iOS interruption level and Android channel importance to set. Then you report sent / delivered / opened / suppressed back to us, and the dashboard finally shows the real funnel — split by iOS, Android, and Web — instead of a flattering “delivered” number.

It is one API call before you send, no SDK, and the free tier covers 1,000 pushes a month so you can prove it on a single campaign before paying a rupee.