Quick answer
A push notification is a short message a server sends to a user's phone or browser without the user asking for it at that moment. It shows up on the lock screen or in the notification drawer even when the app is closed, but only if the user has allowed notifications.
Formula: Yield = users who did the intended action ÷ devices the push was delivered to
What is a push notification?
A push notification is a short message that a server sends to a user's device without the user asking for it at that moment. It appears on the lock screen, in the notification drawer or as a banner, even when the app is closed or the website tab is not open. The word "push" describes the direction: the sender starts the delivery, instead of the app "pulling" new data when the user opens it.
Three parties are involved. Your server decides what to send and to whom. A platform push service (Apple's, Google's, or the browser vendor's) carries the message to the device. The operating system or browser then shows it, if the user allowed notifications. If any of the three says no, nothing appears.
Mobile push vs web push
| Mobile (app) push | Web push | |
|---|---|---|
| Needs | An installed app | A website and a browser that supports it |
| Permission | iOS asks in a system prompt; on Android 13 and later a runtime permission (POST_NOTIFICATIONS) is required, and notifications are off by default for new installs | Browser permission prompt tied to the site |
| Technology | The platform's push service, reached through the app | The Push API with a service worker, which can show the notification even when the page is not loaded |
| Typical use | Order status, messages, reminders, re-engagement | Content alerts, back-in-stock, abandoned-cart reminders |
| Opens | A screen inside the app (often through a deep link) | A page on the site |
Two details from the official documentation matter for planning. On Android, a user who selects "Don't allow" blocks all notification channels for your app, so the moment you ask is part of the design. On the web, the Push API requires an active service worker and the user's opt-in.
The three steps that decide whether a push worked
Counting "sent" tells you nothing about results. A push has to survive three steps:
- Delivered. The message reached a device that still has the app installed, has notifications on and was reachable before the message expired. Devices that uninstalled the app, revoked permission or went dead drop out here.
- Clicked. The user saw it and tapped it. This is the step the copy, the timing and the sender name control.
- Came back and did something. The tap opened the app, and the user reached the screen you intended and finished the action. A click that lands on the home screen and goes nowhere is a wasted push.
Each step has its own rate, and the product of the three is the real yield.
A worked example: two campaigns, same audience
Sample data: two pushes, each sent to 10,000 opted-in devices. Campaign A is a plain order-status update with a link to the order screen. Campaign B is a "Don't miss out" promotion that opens the app's home screen.
| Step | Campaign A | Campaign B |
|---|---|---|
| Sent | 10,000 | 10,000 |
| Delivered | 9,200 (92.0% of sent) | 9,300 (93.0%) |
| Clicked | 460 (5.0% of delivered) | 744 (8.0% of delivered) |
| Did the intended action | 138 (30.0% of clicks) | 112 (15.1% of clicks) |
| Yield: action ÷ delivered | 1.50% | 1.20% |
Read it as a decision rule: judge a push by the last row, not by clicks. B wins on clicks (8.0% against 5.0%) but loses on results (1.20% against 1.50%) because its landing screen did not match its promise. If you had stopped at click rate you would have rolled out the weaker message.
Frequency, timing and opt-outs
Push is a permission you can lose. When users feel over-messaged they switch notifications off for the whole app, and from then on you cannot reach them at all. A rule of thumb that works: set a weekly cap per user, give transactional messages (order shipped, password reset) priority over promotions, and watch opt-outs after every campaign.
Sample data: before sending, 6,000 of your 20,000 installs can receive push (30%). After a week of daily promotions, 5,100 can (25.5%). You lost 900 reachable users, 15% of your push audience, to get a handful of extra clicks. Track the number of devices that can receive push as its own metric, next to click rate.
A related point is the permission prompt. On Android 13 and later, the official guidance is to explain why before asking, and to ask after the user has had a chance to see value, for example after placing an order or tapping an alert bell, rather than at first launch.
Common mistakes
- Treating delivery as success. "Sent" and even "delivered" say nothing about whether the message worked; count clicks and actions.
- Sending the same message to everyone. A push to people who bought yesterday and a push to people who have been away for 60 days are different jobs. Use a segment for each.
- Landing on the home screen. If the message is about a product or an order, open that screen. This is the most common reason clicks do not turn into results.
- Confusing push with other channels. Push needs an app or a browser opt-in; email and SMS have their own rules. Do not compare their rates one to one.
- Judging a push by next-day opens only. Some pushes (a shipping update) are meant to be tapped rarely and valued anyway. Judge each push against its own goal.
- Measuring without a control group. Users who tap pushes are often already your most engaged users. Hold out a small share who receive nothing and compare their retention with those who received the push.
Measuring push notifications in TapCub
TapCub does not send push notifications; use your push provider for that. TapCub measures what the user does around them. Here is how the example above would be checked.
- Find the event. TapCub's preset event list for apps includes
$push_click(the user tapped a push) and$deeplink_launch(a deep link opened the app). Whether your SDK sends them automatically depends on the platform, so check the SDK page; if it does not, send the event yourself with the same name. - Build the funnel. In All-platform analytics › Behavior › Behavior analysis, make a funnel of
$push_clickfollowed by your own order or action event. This gives the "clicks to action" step of the table above. Delivered and sent counts come from your push provider, not from TapCub. - Check who comes back. In App analytics › Users › Retention, compare retention of users who tapped a push with the rest, keeping in mind the hold-out point above.
- Look at the channel. If you write a channel value (
$channel) on events, App analytics › Users › Channels shows new users per day, next-day retention and active share per channel. - Watch the version. If a push opens a new screen, App analytics › Users › Versions shows which app versions users are on, so you do not send people to a screen their version does not have.
For the wider set of app metrics, see app engagement metrics; for win-back flows, re-engagement campaigns. Push is most useful for apps; read what a native app is if you are deciding between app and web.
See also: Push Notifications: What They Are and How to Measure Whether They Work.
See also: What is an in-app message? Types and when to use vs push.
Sources
- Android Developers, Notification runtime permission.
- MDN Web Docs, Push API.
- IBM, What is a push notification?
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.