Push Notification Examples: 30 Messages That Get Tapped, With Copy and Payload

Most push notification advice is a list of tips. This guide is a list of actual messages: what a good one looks like for each situation, how it is built, and why it works. A push notification has about two lines and a second of attention to earn a tap, so every word counts. Below you will find the anatomy of a notification, thirty-odd example messages grouped by purpose, the payload behind them, rules for timing and frequency, a worked example and the mistakes that get notifications muted. If you are new to the channel, start with our guide to push notifications and come back for the copy.

The anatomy of a good push notification

A push notification is built from a few parts, and each one has a job. The platform decides how much of each part is shown, which is why the first line matters most.

Four rules behind every example

• Specific beats clever. “Your order #4821 is out for delivery” outperforms a pun every time, because it tells the person something they care about.
• One message, one action. If the notification asks for two things, it gets neither.
• Relevant to what they did. Base it on behaviour, not on the calendar. See behavioral segmentation.
• Worth interrupting for. Ask whether you would want to be interrupted by this message at this moment.

Push notification examples by purpose

Transactional and service

Behavioural and triggered

Promotional

Re-engagement and lifecycle

The example messages above are illustrations for style. Adapt names, amounts and tone to your own brand, and check that every claim in a message, such as a price or delivery date, is true when the message is sent.

What the payload looks like

Behind each example is a small structured message sent through the platform push service. This is a simplified illustration of an iOS-style payload with a title, body, a category for action buttons and a custom field that carries the deep link. Real payloads depend on your provider and SDK.

{
  "aps": {
    "alert": {
      "title": "Back in stock",
      "body": "Your size is back. We've kept it ready for you."
    },
    "category": "PRODUCT_ACTIONS",
    "sound": "default"
  },
  "deeplink": "myapp://product/TR-07?size=9",
  "campaign": "back_in_stock_oct"
}

In Flowfox, the same content is set in a journey step or a campaign, with variables from the profile, as described on the push channel page. The SDK on the device handles delivery, taps and the deep link.

Timing and frequency

A perfect message at the wrong time is a bad message. Triggered messages should go out when the event happens or soon after. For promotional pushes, test windows against your own engagement data and avoid late nights. Our guide to the best time to send email applies the same testing method. Cap the number of notifications per person per day and per week across all campaigns, because people who feel spammed simply switch notifications off, which is hard to reverse. See push opt-in rates for why that permission is precious.

How to write a notification in five minutes

1. Name the moment. What did the person just do, or what is about to happen?
2. State the one thing that matters. The detail, the benefit or the deadline.
3. Write the first line as if it were the whole message. It may be truncated.
4. Pick the destination screen. Deep link to exactly where the action is completed.
5. Test on real devices. Check the preview on iOS and several Android phones, in light and dark mode.

A worked example

Imagine a grocery app that wants to reduce abandoned baskets. Its first attempt is a generic push at 9 pm every day: “Don’t forget your groceries!”. It is ignored. The second version triggers two hours after a basket is left, names the first two items, mentions that slots for tomorrow morning are filling, and opens the basket directly. A third version adds a rule: if the person has already ordered since, send nothing. The team compares each version against a holdout group that gets no push and measures orders per recipient. The numbers are not shown here because the example is invented, but the pattern is typical: relevance, timing and suppression do more than copywriting tricks.

For more on messaging that responds to behaviour, see abandoned cart recovery, event-triggered marketing and mobile app engagement. Apple publishes interface guidelines for notifications at Apple’s Human Interface Guidelines, which are worth reading before you design rich notifications, and the idea of a clear call to action applies to push as much as to email.

Mistakes that get notifications muted

• Generic blasts. The same message to everyone, at the same time.
• Fake urgency. “Last chance!” every week teaches people to ignore you.
• Landing on the home screen. The tap should finish the job.
• Too many a day. Frequency caps protect your permission.
• Promotional messages dressed as alerts. It erodes trust and can break platform rules.
• Never testing on real devices. Truncation surprises are common.

A good push notification feels like a helpful tap on the shoulder. A bad one feels like a pop-up ad on the lock screen.

Read next: push vs SMS, silent push notifications and the blog.