TL;DR
The best push notification examples share three qualities: they arrive at a relevant moment, communicate one clear benefit, and make the next action effortless. Transactional updates build trust, behavioral reminders recover unfinished tasks, and personalized recommendations create reasons to return.
The 18 examples below cover retail, health and wellness, and travel. Use them as patterns rather than scripts: match the message to the user’s context, avoid artificial urgency, and deep-link directly to the promised destination.
Elevating Omnichannel Messaging with Push Notifications
Push notifications are most valuable when they solve a timing problem.
An email may be appropriate for a receipt or detailed itinerary, while an in-app message can explain a feature after someone opens the product. But neither helps much when a customer’s order has just arrived, a flight gate has changed, or an unread conversation needs attention. A push notification can surface that information immediately, even when the app is closed.
That immediacy makes push useful across the customer journey:
- Acquisition: Encourage a new user to complete onboarding or claim a relevant introductory offer.
- Activation: Bring someone back to the feature or workflow that delivers the product’s core value.
- Conversion: Recover an abandoned cart, incomplete reservation, or interrupted checkout.
- Retention: Share useful reminders, personalized recommendations, and progress updates.
- Service: Communicate order status, schedule changes, security events, or new messages.
- Reactivation: Give an inactive user a credible reason to return without sending a vague “We miss you” alert.
Push should not operate as an isolated broadcast channel. It works best within an omnichannel system that understands what the user has already done. If a customer completed a purchase on the web, the app should suppress the abandoned-cart notification. If a user has already read a chat message on another device, they should not receive a stale alert five minutes later.
This is where many notification strategies fail. Teams optimize the wording but ignore state synchronization, preferences, delivery timing, or the destination after the tap. The result may earn a short-term open, but it also teaches users that notifications are noisy or unreliable.
A better strategy begins with a simple question: What does this person need to know or do right now? If the answer is unclear, the notification probably should not be sent.
What Is a Push Notification?
A push notification is a short message sent by an application or service to a user’s device. It can appear on a phone’s lock screen, in the notification center, as a banner, on a wearable device, or through a supported desktop browser.
Unlike an in-app message, a push notification can reach the user when the application is not open. That makes it useful for time-sensitive updates and carefully selected prompts to return.
A mobile push flow usually involves four parts:
- The user installs an app and grants notification permission.
- The operating system’s push service issues a device token.
- The app sends that token and the user’s preferences to its backend or notification provider.
- The backend sends an eligible event through Apple Push Notification service or Firebase Cloud Messaging, which attempts delivery to the device.
Push notifications are not guaranteed messages in the same sense as a database transaction. A device can be offline, a token can expire, the user can disable permission, or the operating system can delay delivery. Critical information should therefore remain available inside the app, and genuinely sensitive workflows may require another channel.
It is also useful to distinguish push from related app notifications:
- Push notification: Delivered outside the open app through the operating system.
- In-app notification: Displayed while the user is actively using the app.
- Notification center or inbox: A persistent in-app record the user can revisit.
- SMS or email: Delivered through a separate communication channel and governed by different permissions and expectations.
The strongest products coordinate these surfaces. A chat app, for example, might show a push alert when the recipient is offline, update an in-app unread badge when they return, and preserve the message in the conversation history. The push gets attention; the application remains the source of truth.
Permission also matters. On platforms where users must opt in, asking immediately at first launch often produces weak results because the benefit is still abstract. A contextual prompt is more persuasive: request permission after someone tracks an order, follows a topic, books an appointment, or starts a conversation. At that point, the user understands what the notifications will do for them.
Common Types of Push Notifications
Push notifications can be classified by the job they perform. Choosing that job before writing the copy keeps the message focused and helps teams measure the right outcome.
Informational notifications
These deliver useful facts such as weather warnings, product updates, account notices, or local service changes.
An informational notification should explain what changed and why it matters. “There is an update” is weak; “Heavy rain is expected after 6 PM in your area” is actionable.
Transactional notifications
Transactional alerts confirm or update an activity the user initiated. Typical examples include payment confirmations, delivery updates, booking changes, password events, and new chat messages.
Users generally welcome these because they reduce uncertainty. Accuracy matters more than cleverness. Include the object, current status, and next step when one is required.
Reminder notifications
Reminders help users complete something they intended to do, such as attend an appointment, renew a subscription, take medication, or finish a checkout.
A useful reminder respects the task’s natural timing. Sending an appointment reminder two weeks early may be forgettable; sending it five minutes before a long journey is unhelpful.
Behavioral notifications
These respond to an action or omission: leaving an item in a cart, viewing the same destination repeatedly, starting but not completing onboarding, or receiving a message without reading it.
Behavioral triggers can be highly relevant, but they can also feel intrusive. Use the minimum context necessary and avoid revealing sensitive behavior on a lock screen.
Promotional notifications
Promotional push messages announce discounts, new products, limited inventory, or loyalty rewards. They can drive revenue, but they are also the easiest category to overuse.
A broad “20% off everything” alert may be relevant to only a fraction of the audience. A stronger notification connects the promotion to a category, saved item, loyalty status, or demonstrated preference.
Progress and achievement notifications
These show movement toward a goal: a weekly activity streak, course completion, savings milestone, loyalty level, or project status.
The notification should celebrate genuine progress rather than manufacture pressure. If a streak mechanism makes users anxious or punishes them for missing a day, it can undermine the behavior the product is meant to support.
Social and conversational notifications
These alert users to direct messages, mentions, comments, reactions, invitations, and community activity.
Conversation alerts require particularly careful suppression. If the recipient is already viewing the relevant conversation, an external push is redundant. Group notifications should also be bundled or summarized to prevent dozens of alerts from one active thread.
18 Mobile Push Notification Examples Worth Adapting
The examples below are grouped by industry because context changes what “good” looks like. A retail notification may appropriately emphasize availability or price, while a health notification should prioritize support and privacy. A travel alert often succeeds by reducing uncertainty during a time-sensitive journey.
The sample wording is illustrative rather than a quotation from a live campaign. Focus on the underlying pattern: trigger, value, timing, and destination.
Before adapting any example, answer four questions:
- What user action or event triggers the message?
- What does the recipient gain by seeing it now?
- What exact screen should open after the tap?
- When should the alert be suppressed?
Those decisions contribute more to performance than adding an emoji or rewriting the same generic promotion five times.
Retail and E-Commerce Push Notification Examples
Retail notifications must balance conversion with restraint. Purchase history can improve relevance, but using it too explicitly may feel invasive. Product availability and pricing can also change quickly, so the message and destination must stay synchronized.
1. Amazon: Recovering an abandoned cart
Example: “Still deciding? The headphones in your cart are ready when you are.”
The classic cart reminder works because it refers to an unfinished task rather than inventing a new one. The user already expressed interest by adding the item.
A strong version names or displays the product, deep-links to the cart, and disappears from the campaign if the user buys the item elsewhere. Avoid falsely claiming scarcity or a price deadline. If inventory is genuinely low, verify it at send time.
Why it works: High behavioral relevance and minimal effort to resume.
Best trigger: Several hours after abandonment, adjusted for the product’s consideration cycle.
2. H&M: Suggesting an item that completes a purchase
Example: “A finishing touch for your new jacket: accessories selected to match.”
A post-purchase recommendation can feel more useful than a general sale alert because it begins with a known need. The customer has already chosen a style, size range, or category.
Timing is important. Sending the recommendation immediately after checkout can look like an attempt to increase the bill. Waiting until the order has shipped or arrived gives the purchase room to feel complete.
Why it works: The recommendation follows existing intent instead of interrupting with an unrelated product.
Watch out for: Suggesting the same item the user just purchased or promoting a replacement that creates buyer’s remorse.
3. Sephora: Replenishment based on a realistic usage window
Example: “Running low on your moisturizer? Reorder your usual size in a few taps.”
Replenishment reminders are effective for products consumed on a reasonably predictable schedule. They spare the customer from remembering when to restock.
The estimate should account for product type, package size, purchase frequency, and repeat behavior. Do not send the reminder simply because 30 days have passed if the product commonly lasts six months.
Why it works: It removes a recurring mental task and leads to a simple destination.
Best destination: A prefilled product page or cart with the current price and availability visible.
4. Etsy: Bringing a favorited product back at the right moment
Example: “A shop you favorited just added new handmade desk organizers.”
A favorites alert is stronger than a marketplace-wide announcement because users have explicitly indicated interest. It can cover a saved product, followed shop, category, or search.
The alert should be selective. A user who follows dozens of shops does not need an immediate push for every listing. Ranking by category affinity, recency, and notification preference protects the value of the channel.
Why it works: It turns a broad catalog into a personally relevant update.
Watch out for: Overstating personalization when the recommendation is only loosely related.
5. Instacart: Making a substitution decision time-sensitive
Example: “Your preferred pasta is unavailable. Choose a replacement in the next 12 minutes.”
This is an excellent transactional pattern because the alert explains the issue, the deadline, and the required action. The notification is useful even if it does not produce additional revenue.
The tap should open the exact substitution screen, not the store homepage. If no response is received, the system should follow the preference the customer selected during checkout rather than guessing silently.
Why it works: It helps the customer retain control over an active order.
Best trigger: Immediately after the shopper marks an item unavailable.
6. Starbucks: Turning a loyalty balance into a concrete benefit
Example: “You have enough Stars for a free bakery item on your next visit.”
A loyalty notification works when it translates an abstract point balance into something understandable. “You have 100 points” requires interpretation; “You can claim a free item” communicates value immediately.
Location and timing can improve relevance, but overly precise tracking may feel uncomfortable. Give users control over location-based alerts and cap their frequency.
Why it works: It makes an earned benefit visible without relying on a blanket discount.
Best destination: The rewards screen with eligible items and redemption conditions.
Health and Wellness Notifications
Health and wellness apps operate in a more sensitive context. Helpful personalization can easily become judgmental, expose private information, or encourage unhealthy behavior.
Lock-screen copy should be discreet by default. Let users choose whether medication names, pregnancy details, mental health topics, or specific measurements can appear outside the app.
7. Google Calendar and Maps: Combining an appointment with travel time
Example: “Leave by 2:20 PM to arrive at your 3:00 PM appointment on time.”
This pattern combines calendar context, destination data, current traffic, and travel time. Instead of merely repeating that an appointment exists, it tells the user when action is needed.
The message should update if traffic changes significantly, but repeated alerts can become distracting. One initial recommendation and one meaningful change alert are usually more useful than constant recalculation.
Why it works: Multiple data sources create a simple, timely recommendation.
Best destination: Route guidance or appointment details, depending on the user’s immediate need.
8. The Bump: Delivering a stage-specific pregnancy update
Example: “Week 24: Here’s what may change for you and your baby this week.”
Pregnancy apps serve users during a defined and rapidly changing period. Stage-specific updates provide a natural reason to return without relying on discounts or artificial engagement loops.
The copy should avoid presenting general educational content as personal medical advice. It should also accommodate different pregnancy experiences and allow users to control sensitive lock-screen details.
Why it works: The content changes with a meaningful personal timeline.
Watch out for: Assumptive, alarming, or overly intimate wording.
9. Headspace: Offering a low-pressure mindfulness prompt
Example: “A two-minute pause is here when you need it.”
This notification does not scold the user for missing a session. It reduces the perceived effort and frames meditation as an available resource rather than another obligation.
Tone is central to the experience. A message designed to reduce stress should not create stress through aggressive streak warnings or repeated reminders.
Why it works: The message reflects the product’s emotional promise.
Best destination: A short exercise that can begin immediately.
10. MyFitnessPal: Helping users complete a chosen routine
Example: “Want to finish today’s food log? Your recent meals can speed things up.”
The notification refers to a task the user has chosen to track and offers a shortcut. That is more constructive than implying failure or making an unsolicited judgment about eating behavior.
Frequency should follow the user’s routine and preferences. Someone who logs only occasionally should not receive daily guilt-driven prompts.
Why it works: It lowers the effort required to complete an existing habit.
Watch out for: Language that moralizes food choices, body weight, or missed entries.
11. Fitbit: Celebrating progress without overclaiming
Example: “You’re 800 steps from the daily goal you set.”
Progress alerts can motivate when the target is user-defined and realistically within reach. The number gives the recipient enough information to decide whether to act.
A notification sent shortly before bedtime may be counterproductive, especially if it encourages intense activity or anxiety. Quiet hours and health context should override engagement goals.
Why it works: It is specific, measurable, and connected to a chosen objective.
Best destination: The daily activity view rather than a general dashboard.
12. A medication app: Sending a private, actionable reminder
Example: “It’s time for your scheduled dose. Tap to mark it complete.”
For sensitive health workflows, clarity is more important than personality. The app should allow the user to hide medication names on the lock screen, snooze the reminder, record a dose, or indicate that it was skipped.
Push should not be the only record. The medication schedule, adherence history, and safety instructions must remain available inside the app. Developers should also avoid implying that push delivery is guaranteed.
Why it works: It supports an important routine with a clear action.
Watch out for: Exposing private health data or treating a missed push as proof of a missed dose.
Travel App Notification Examples
Travel notifications often reach people who are moving, stressed, offline intermittently, or making decisions under time pressure. The best examples reduce uncertainty and place essential information directly in the message.
Promotional travel alerts can still work, but operational updates should take priority. A gate change should never be buried beneath a destination sale.
13. Uber: Coordinating a real-time pickup
Example: “Maya is arriving in 2 minutes in a white Toyota. Meet at Pickup Zone B.”
This notification answers the rider’s immediate questions: when, who, what vehicle, and where. It reduces the need to reopen the app repeatedly.
Location details must stay current. If the pickup zone changes, the next alert should clearly identify the change rather than repeating most of the previous message.
Why it works: It compresses several pieces of live information into one scannable update.
Best destination: The active trip screen with map and contact options.
14. Airbnb: Prompting a host response before a request expires
Example: “A guest requested May 12–15. Review the trip before the request expires.”
Marketplace notifications must serve both sides of the transaction. A host needs enough context to assess urgency, while the guest benefits from a faster answer.
The notification should state whether the event is a question, reservation request, confirmed booking, or cancellation. Ambiguous copy can cause unnecessary concern.
Why it works: It connects a time-bound decision to a direct review action.
Watch out for: Revealing guest information beyond what is needed on the lock screen.
15. An airline app: Communicating a gate change
Example: “Gate change: Flight 482 now departs from C17 at 6:40 PM.”
Operational travel notifications should lead with the change, not the brand. The passenger can understand the update without opening the app, while a tap can reveal directions, boarding status, and the digital pass.
If the gate changes more than once, use language such as “Updated again” to prevent confusion. The latest in-app state should be prominent.
Why it works: It prioritizes a high-consequence fact and preserves the relevant flight context.
Best trigger: Immediately after the airline’s authoritative operational system confirms the change.
16. Google Maps: Warning about disruption on a familiar route
Example: “Heavy traffic on your usual route home. Leaving 20 minutes later may save time.”
A route alert becomes valuable when it accounts for a regular journey, current conditions, and an alternative. A generic “Traffic is heavy” message offers too little help.
The app should avoid making assumptions when the user’s routine changes. Travel-pattern personalization should be transparent and controllable.
Why it works: It turns broad traffic data into a decision the user can make now.
Best destination: A route comparison showing the recommended alternatives.
17. Booking.com: Using a saved search without false urgency
Example: “Three stays matching your saved Lisbon filters now offer free cancellation.”
Saved-search notifications can reduce the effort of repeating a complex query. They are especially helpful when the message highlights a meaningful change such as availability, cancellation terms, or a verified price reduction.
Travel pricing is dynamic, so the destination must show the latest total, including mandatory fees where possible. Avoid unsupported claims such as “Your last chance” or “Everyone is booking this.”
Why it works: It reconnects the user with an explicit plan and preserves their criteria.
Watch out for: Displaying an attractive price that is no longer available after the tap.
18. TripIt: Summarizing the next step in an itinerary
Example: “Next up: Hotel check-in from 3 PM. It’s 18 minutes from your arrival terminal.”
An itinerary notification is useful because it filters a complex trip into the next relevant action. The user should not need to search through confirmation emails while carrying luggage or navigating an unfamiliar airport.
Offline access is important. Essential addresses, reservation references, and timing should remain available even if connectivity is poor.
Why it works: It reduces cognitive load during a multi-stage journey.
Best destination: The exact itinerary item, with directions and confirmation details.
What the Best Push Notifications Have in Common
Good app notifications are not simply short advertisements. They are small product experiences. The wording matters, but the surrounding logic determines whether the notification feels useful or disruptive.
Start with the user’s context
A strong notification answers “Why now?” The reason may be a new message, a shipment event, an approaching appointment, a price change on a saved item, or a task the user explicitly asked to remember.
Demographic personalization alone is rarely enough. Behavioral and situational context usually provides a more credible reason to send.
Put the value or change first
Users often scan notifications in less than a second. Lead with the information that affects them:
- “Gate change: Now departing from C17”
- “Your order has arrived”
- “New message from Jordan”
- “Price dropped on a saved item”
Brand names, greetings, and playful setup should not push the essential fact out of view.
Use one message and one next action
A push notification has limited space and attention. Trying to announce a sale, explain a loyalty program, recommend three products, and introduce a feature in one alert creates friction.
Choose the most important next step and deep-link directly to it. If the notification says “Review substitution,” the tap should not open the home screen.
Personalize without becoming unsettling
Useful personalization refers to information the user expects the app to know: an active order, saved route, selected goal, followed shop, or current conversation.
Avoid exposing sensitive details on the lock screen or revealing extensive tracking unexpectedly. Give users granular controls for promotional, transactional, social, and reminder notifications.
Match urgency to reality
Urgency should come from the event, not from copywriting tricks. A departing flight, expiring reservation request, or temporary delivery decision is genuinely time-sensitive. A permanently available product does not become urgent because the notification uses capital letters.
Trust is difficult to regain once users recognize false scarcity.
Suppress duplicates and stale alerts
Before sending, check whether the user already completed the action, opened the relevant conversation, changed devices, or became ineligible. Cancel scheduled notifications when their underlying state changes.
For high-volume events such as group conversations, bundle alerts into a summary. “12 new messages in Design Team” is more considerate than 12 separate pushes.
Measure outcomes beyond opens
Open rate can reward sensational wording even when the post-tap experience disappoints. Measure the outcome connected to the notification’s purpose:
- Completed purchases for cart reminders
- On-time arrivals for appointment prompts
- Successful substitution choices for order alerts
- Read conversations for message notifications
- Lower opt-out or uninstall rates across the campaign
Useful notifications may also achieve their purpose without a tap. A gate alert that communicates the correct location on the lock screen still creates value.
How to Build an App Like This with Tencent RTC
For an application inspired by the notification examples in this guide, use Tencent RTC Push as the primary delivery and re-engagement layer. The application backend should decide when a user genuinely needs a notification, while Tencent RTC Push handles AppPush or WebPush delivery, platform channels, audience targeting, and delivery analytics. Keep product events, user preferences, quiet hours, deep-link destinations, and duplicate suppression in your own backend so notification volume remains useful rather than noisy.
Start with the Tencent RTC Push overview. The following TypeScript uses a small adapter around the official Push SDK or server API described in that documentation; keeping the adapter at your boundary makes it explicit which business event produced each notification:
type PushRequest = {
userId: string;
title: string;
body: string;
deepLink: string;
category: "transactional" | "engagement";
};
export async function sendTencentRtcPush(request: PushRequest) {
return pushProvider.send({
audience: { userIds: [request.userId] },
notification: { title: request.title, body: request.body },
data: { deepLink: request.deepLink, category: request.category },
});
}Do not call the provider directly from every feature. Centralize eligibility checks so an event is suppressed when the user is active, has disabled the category, is inside quiet hours, or has already received the same event:
export async function notifyIfUseful(event: RetentionEvent, user: User) {
if (await presence.isActive(user.id)) return;
if (!user.pushPreferences[event.category]) return;
if (quietHours.contains(user.timezone, new Date())) return;
if (await dedupe.seen(event.id, user.id)) return;
await sendTencentRtcPush({
userId: user.id,
title: event.title,
body: event.safePreview,
deepLink: event.deepLink,
category: event.category,
});
};For an application inspired by the notification examples in this guide, measure delivery, open rate, deep-link completion, opt-out rate, and downstream retention or conversion—not sends alone. Test expired device tokens, multiple devices, revoked permissions, quiet hours, sensitive lock-screen previews, stale events, and deduplication. This keeps Tencent RTC Push as the primary implementation rather than using a Chat message-send example as a substitute for notification delivery.
FAQ
What makes a push notification effective?
It should be timely, relevant, specific, and connected to one easy action. Strong notifications also respect user preferences, open the promised destination, and disappear when the underlying event becomes stale.
How often should an app send push notifications?
There is no universal frequency. Transactional alerts should follow real events, while promotional messages need stricter caps. Monitor opt-outs, dismissals, conversions, and user-level engagement rather than optimizing only for send volume.
What is the difference between push and in-app notifications?
Push notifications can appear when the app is closed and are delivered through the device’s notification system. In-app notifications appear while the user is active. Many products use push for timely attention and an in-app inbox for persistent history.