· 8 min read
Push notification copy that actually gets tapped
Push notifications live in the most valuable real estate on the phone — the lock screen and the notification shade — and most programs treat them like abbreviated email. They're not. Push has its own rules. The copy that gets tapped feels more like a helpful text than a marketing message. Here's how to write it.
Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
The character budget and where the decision happens
~65chars
Visible iOS title before truncation. Same for Android.
178 / 240
iOS / Android body char limit in expanded view. Most users never see expanded.
~50chars
Web push title. More restrictive than mobile. Test for this constraint.
Most push copy is written to the expanded-view body limit (178 on iOS, 240 on Android). In practice, most users only ever see the collapsed view — the title and the first line of the body. Write for that. The push preview tool shows how each platform renders your specific copy.
The tap decision happens in the first 40 characters on the lock screen. If your value proposition isn't inside those characters, you're relying on the user to tap-to-expand or flip over to their notification shade. Most won't.
The anatomy of push copy that works
Good push reads like something a specific person would say to a specific person. Bad push reads like a headline.
Title: a verb or an answer.Not "Important update" but "Your order shipped". Not "New features" but "Dark mode is live". The title answers an implicit question the user has — what's this about and do I care?
Body: what changed or what to do.One sentence, ideally ending with a hint of the action if tapped. "Arrives tomorrow, 10am–2pm" under the shipped title. Specificity builds trust; abstract "check the app for details" gets ignored.
Never:emoji-leading titles ("🎉 Big news!"), clickbait ("You won't believe…"), false urgency ("LAST CHANCE"). Each of these earns a push-opt-out faster than equivalent email because the channel is louder.
Patterns that reliably outperform
Personal pronouns, tight."Your cart is saved" beats "Cart saved". "Your trial ends Friday" beats "Trial ends Friday". The possessive implicitly makes the message about the recipient, not the brand.
Numbers and specific times."Arrives by 2pm" beats "Arriving soon". "3 new matches" beats "New activity". Specificity is information; abstraction is filler.
Questions when they're real."Still shopping the navy jacket?" beats "Check out these deals!". A question that reflects the user's state works; a rhetorical marketing question doesn't.
The friend-text voice.Push is louder than email so it should sound quieter. "Heads up — your subscription renews tomorrow" reads better than "Your subscription will automatically renew in 24 hours."
Timing + frequency discipline
Time-zone aware sending is not optional. A push scheduled for 9am that fires at 3am in a user's local time is how you lose permission for the channel. Every push program needs per-profile time-zone scheduling, and every sending template should default to local quiet hours (e.g., no sends between 10pm and 7am local).
The Multi-Channel Orchestration skillhandles cross-channel frequency governance so a user doesn't receive a push for an abandoned cart while also getting an email for the same cart within 20 minutes. Shared state across channels is what prevents this.
Frequency cap that works in practice for marketing push: 2 per week max for average users, 1 per week for users with declining engagement. Transactional pushes (order confirmations, security alerts) are exempt. When in doubt, send email — email waits, push interrupts.
The use cases push is actually best at
Push outperforms email for: time-sensitive reminders (appointment in 30 minutes), state changes (order shipped, payment received), real-time events (they replied, their turn to move), and friend-activity (someone commented, someone shared with you). These all share a property: immediate relevance.
Push underperforms email for: product announcements, content digests, newsletters, long-form updates, promotional sales, and anything requiring more than one sentence to explain. Using push for these either wastes the channel or actively damages opt-in rates. Use email; it's slower but it's the right shape for the content.
The 72-hour window guide covers the activation phase where push is uniquely valuable — real-time intervention while the user's product context is still warm.
Frequently asked questions
- What's the character limit for push notifications?
- iOS: ~65 title, ~178 body expanded. Android: ~65 title, ~240 body expanded. Web: ~50 title, ~120 body with no expansion. Most users only see the collapsed view (title + first line of body) on the lock screen. Write for that.
- Should I use emoji in push notifications?
- Sparingly and never leading. One emoji that disambiguates the noun is fine. Leading a title with 🎉 or 🚀 reads as marketing spam and trips internal filters on some devices. Personalised products can skip emoji entirely; utility products may benefit from one.
- How many push notifications per week is too many?
- For marketing push, 2 per week max for average users, 1 per week for users with declining engagement. Transactional pushes are exempt. Once a user hits 'too many', they typically opt out of the entire app's notifications — which you almost never get back.
- What time of day should I send push notifications?
- Respect local time zones, not sender timezone. Default quiet hours 10pm–7am local. Optimal send window is 11am–1pm or 5pm–7pm local, but both vary by audience — test for your specific base.
- When should I use push instead of email?
- Time-sensitive state changes (order shipped, appointment reminder), real-time activity (they replied, their turn), and activation-window interventions. Email for product announcements, digests, promotions, and anything longer than a sentence.
- Do rich push images help?
- Yes, when the image adds information. A product photo in an abandoned-cart push performs better than title+body alone. A decorative image (brand hero shot) adds nothing and can feel intrusive. Use rich media where it teaches, skip it where it decorates.
This guide is backed by an Orbit skill
Related guides
The cadence question: how often should you email?
Everyone asks how often to email and almost nobody answers it properly. This guide is about what 'cadence' actually means, why the right number isn't a single number, and the five inputs that settle the debate for your specific program.
Personalisation that doesn't feel creepy
There's a line between personalisation that earns a user's trust and personalisation that breaks it. This guide is about where the line actually is, how lifecycle programs cross it without noticing, and the specific patterns that keep you on the right side.
Subject line anatomy: the four parts of every line that performs
Most subject line advice is decoration tips. The lines that actually get opened share a structural pattern — four parts in a specific order. This is the anatomy, with the pattern and the three common distortions that ruin it.