Over 5 million apps compete for the same screen time. Most of them lose. The ones that stick around have figured out one thing: how to talk to their users without annoying them. Push notifications are the fastest, most direct way to do that, but only if you know which types to use and when.
This guide covers the core push notification types by channel and device, 12 campaign formats that actually move retention and revenue, and the best practices that separate good campaigns from noise. We’ll also show where Pushwoosh fits: how behavioral segmentation, the Customer Journey Builder, and real-time analytics help you orchestrate it all from one platform.
What are push notifications?
A push notification is a short, clickable message that appears on a user’s device — phone, desktop, or wearable — even when they’re not using your app or browsing your site. The message comes from your server, goes through a platform-specific push service (APNs for iOS, FCM for Android and web), and lands on the user’s screen. The only prerequisite: the user has opted in to receive them.
A typical push notification has these parts:
- Title — a short headline that draws attention
- Message body — the actual content, usually containing a call to action
- Rich media — images, GIFs, or short video that boost tap-through
- Action buttons — “Shop Now,” “Learn More,” “Accept” — let users act without opening the app
- App icon / favicon — visual ID of the sender
- Timestamp — when the notification arrived
Pushwoosh handles the entire delivery pipeline. You build the campaign, pick the audience, add rich media and action buttons — the SDK handles APNs, FCM, and web push protocols behind the scenes.
Why push matters for business: push notifications have higher visibility than email or in-app messages. They appear on the screen immediately, which drives stronger engagement, better retention, and stronger conversion rates when campaigns are well-targeted.
Types of push notifications by delivery channel and device
Mobile app push notifications
These come from an installed mobile app. They show up on the lock screen, in the notification tray, and as badge updates. They can deep-link users to specific screens inside the app.
One important nuance: iOS requires explicit permission to send any push notifications. Android has historically been more permissive, though recent OS versions are tightening this. There are also differences in rich media support, notification grouping, and priority levels (iOS has Critical Alerts for urgent, time-sensitive info).
Pushwoosh provides SDKs for both iOS and Android with behavioral segmentation to target the right users at the right time.
Common use cases: app updates, personalized reminders, re-engagement prompts, feature adoption nudges.
Web push notifications
Web push notifications are messages delivered through the browser — desktop or mobile — from websites the user has opted into. No app install required. They appear as native system notifications and can skip ad and email spam filters.
Browser support is wide: Chrome, Firefox, Edge, Opera all work. Safari on macOS works too, though mobile Safari does not support web push yet.
Common use cases: e-commerce promos, content updates, back-in-stock alerts, breaking news.
Desktop push notifications
Desktop push can come from web browsers, dedicated desktop apps (Slack, Spotify, news readers), or Progressive Web Apps. They show up in the OS notification center and can work independently of an active browser window.
Common use cases: SaaS tool alerts (task assigned, new comment), productivity reminders, real-time news updates.
Wearable and IoT notifications
These go to smartwatches, fitness trackers, and other connected devices. The screen is small, so the content has to be glanceable. Most wearable notifications are paired with a mobile app for setup and full content display.
Common use cases: health alerts (high heart rate, activity goals), transit updates, smart home alerts (doorbell, package delivery). Pushwoosh’s API supports orchestrating wearable and IoT notifications as part of a broader omnichannel strategy.
Wallet push notifications
These come from Apple Wallet, Google Pay, and similar apps. They’re tied to passes, loyalty cards, tickets, or coupons, and can be triggered by location or time — for example, a gate change alert when you’re at the airport, or a coupon reminder when you walk past a store.
Common use cases: flight updates, location-based coupon reminders, loyalty point changes, event ticket updates.
12 campaign formats that deliver real results
The channel is just the delivery mechanism. What matters more is how you use it. These 12 formats cover the full user lifecycle — from first open to long-term loyalty.
| Format | Goal | Key trigger |
|---|---|---|
| Welcome / onboarding | Activate new users, reduce early churn | App install or registration |
| Promotional / sales | Drive purchases, announce offers | Segment-based or calendar event |
| Abandoned cart | Recover lost revenue | Cart abandonment event |
| Transactional / status | Build trust with order and account updates | System event (order, login, payment) |
| Re-engagement / retention | Bring back inactive users | Inactivity threshold (e.g. 7+ days) |
| Location-based | Drive foot traffic, contextual offers | Geofence or beacon trigger |
| Event-triggered / time-sensitive | Capture attention at critical moments | In-app event or external trigger |
| Dynamic personalization | Boost relevance with tailored content | Behavioral data + user tags |
| Feedback / ratings | Collect user input, improve app store ranking | Post-purchase or milestone event |
| Social / community | Increase platform stickiness | Social interaction event |
| Rich media / interactive | Boost CTR with visuals and actions | Campaign-based |
| Cross-channel orchestration | Unified experience across channels | Journey entry + fallback logic |
1. Welcome and onboarding
New users have high intent. If you don’t show them value fast, they leave. A welcome sequence that walks users through core features, celebrates first actions (completing a profile, making a first purchase), and sets expectations with respect to future communication can significantly reduce early churn.
Example: “Welcome to [App Name]! Here’s how to customize your feed in three steps.”
In Pushwoosh, the Customer Journey Builder automates multi-stage onboarding sequences triggered by registration or install. Each message adapts to what the user has or hasn’t done, with dynamic content filling in names and preferences.
2. Promotional and sales alerts
Flash sales, discount codes, new product launches, pre-orders, seasonal offers. Push gets these in front of users faster than email, and the direct-to-screen delivery means higher visibility for time-critical deals.
Example: “30% off all summer collections for the next 24 hours. Shop now.”
Use behavioral segmentation to target users who viewed specific products but haven’t purchased. A/B test the offer copy, creative, and CTA to find what converts best.
3. Abandoned cart recovery
Users who add items to a cart have already shown purchase intent. A well-timed reminder — sometimes with a small incentive like free shipping — recovers a meaningful share of that lost revenue.
Example: “You left something behind! Complete your order for [Product Name] and get free shipping.”
The Customer Journey Builder handles automated abandoned cart sequences with escalating incentives: first a tactful reminder, then a discount, then a last-chance message. Dynamic content pulls in the exact product name and image.
4. Transactional and status updates
Order confirmations, shipping updates, password resets, security alerts, appointment reminders. These aren’t promotional, but they’re critical for trust. Users expect them, and dependable delivery builds confidence in your app.
Example: “Your order #12345 has been shipped! Expected delivery: [Date]. Track it here.”
Pushwoosh provides secure, reliable delivery for transactional messages with real-time analytics to monitor delivery and engagement.
5. Re-engagement and retention campaigns
Retaining an existing user is far cheaper than acquiring a new one. Re-engagement campaigns target users who have gone quiet — reminding them of unfinished actions, announcing features relevant to their past behavior, or using gamification (“Your streak is about to break!”).
Example: “We miss you! Your favorite [Category] has new updates. Come back and see what’s changed.”
Use RFM segmentation to identify users at risk of churning. The Customer Journey Builder designs multi-stage flows for different inactivity levels, and A/B testing finds the message that actually brings people back.
6. Location-based and geo-targeted notifications
When a user walks into a geofenced area (near your store, at a conference, in a specific neighborhood), you can trigger a push that feels perfectly timed. This drives foot traffic and makes the message feel contextual rather than random.
Example: “Welcome to [Store Name]! Show this notification at checkout for 10% off today.”
Pushwoosh’s geolocation targeting supports geofences and beacons. Combine it with the Customer Journey Builder to make location just one node in a larger campaign flow.
7. Event-triggered and time-sensitive alerts
These fire in response to specific user actions (or inactions) and external events. A user browses a category but doesn’t buy — send a follow-up. A price drops on a wishlisted item — alert them. A webinar starts in 15 minutes — remind them.
Example: “Your favorite team’s game starts in 15 minutes! Tune in now.”
In Pushwoosh, behavioral segmentation with Tags and Events detects in-app actions like “viewed category X” or “added to wishlist.” The Customer Journey Builder triggers the right message at the right moment.
8. Dynamic content personalization
Generic messages get ignored. Personalized ones get tapped. When a push includes the user’s name, references their recent browsing, or recommends products based on purchase history, it feels relevant rather than spammy.
Example: “Based on your recent activity, check out these new arrivals in [Category].”
Pushwoosh’s dynamic content lets you insert user-specific data (tags, events, properties) directly into templates. The result: every notification feels like it was written for that one person.
9. Feedback, ratings, and survey requests
Asking for a rating right after a positive experience (successful payment, completed task, milestone reached) gets much better results than asking at random. Push is a good trigger; in-app messages can follow up with the full survey.
Example: “Enjoying [App Name]? Rate us on the App Store — it takes 10 seconds.”
A/B test different phrasing and timing to maximize response rates.
10. Social and community involvement
Friend requests, comments, mentions, leaderboard updates, new content from followed accounts. These notifications tap into social motivation and keep users coming back to participate.
Example: “[Friend Name] just commented on your post! Check it out.”
Real-time event-based triggers in Pushwoosh fire instantly when a social event occurs. Dynamic content includes the friend’s name, the post title, or whatever context makes the notification actionable.
11. Rich media and interactive pushes
Plain text is easy to ignore. An image carousel showing three products, a GIF previewing a new feature, or action buttons that let users “Add to cart” without opening the app — these formats are more attention-grabbing and consistently outperform text-only pushes on CTR.
Example: [Image carousel] “Explore our new collection! Swipe to see more.”
Pushwoosh supports rich push notifications with images, GIFs, video, carousels, and custom action buttons directly from the visual editor.
12. Cross-channel orchestration
Push alone is one channel. Combine it with email, in-app messages, and SMS, and you get a system that catches users wherever they are. An abandoned cart push can be followed by an email reminder if the user doesn’t respond. A welcome push can trigger an in-app onboarding tour. SMS can serve as a fallback for critical alerts.
Example: Cart reminder via push. If no action in 1 hour, email follows. If still nothing, in-app message on next session.
The Customer Journey Builder is built for this. It lets you visually map cross-channel flows with conditional logic, segment splits, and Reachability Check nodes that automatically fall back to the next best channel. RFM segmentation informs which channel works best for each segment.
Best practices for high-performing push notifications
Segment by behavior, not just demographics
Age and location tell you who the user is. In-app events, purchase history, and engagement patterns tell you what they care about. The second dataset is what makes push notifications actually work. Behavior-based targeting lifts CTR by 2–3x compared to broadcast sends.
Pushwoosh offers behavioral segmentation with Tags and Events plus RFM segmentation to build precise audiences and identify your most valuable users automatically.
Optimize timing and frequency
Notification fatigue is the #1 reason users disable push. Send at the wrong time or too often, and you lose them. Factor in time zones, daily habits, and message urgency. Use frequency capping to limit how many pushes a user gets per day or week.
Pushwoosh’s AI-driven send time optimization picks the best delivery window for each user based on their engagement history. Frequency capping is built in.
Write concise, action-oriented copy
Lead with value, not your brand name. Use strong verbs, create urgency or curiosity, keep it under 3 lines. Add rich media — images and GIFs consistently improve CTR. Every push should have one goal and one CTA. “Shop Now” or “Claim Reward” — not both.
A/B test continuously
Don’t assume you know what works. Test headlines, message copy, CTAs, images, send times, and audience segments. A 5% CTR improvement per quarter compounds to a 22% lift over a year. Pushwoosh A/B testing supports multiple variants with built-in statistical significance tracking.
Measuring success: key push notification metrics
Without metrics, you’re guessing. Here are the numbers that matter:
| Metric | What it tells you |
|---|---|
| Opt-in rate | How effective your permission request strategy is |
| Delivery rate | Whether messages actually reach devices |
| Click-through rate (CTR) | How relevant and compelling your content is |
| Conversion rate | Whether clicks turn into business outcomes (purchases, activations) |
| Churn rate | Whether your notifications help retain users or push them away |
| Unsubscribe rate | Whether you're sending too many or too irrelevant messages |
Pushwoosh analytics provides real-time dashboards for all of these, with the ability to drill into individual campaigns and segments.
Increase retention and conversions with Pushwoosh
Improving push notification performance isn’t about sending more messages. It’s about sending the right format, to the right user, at the right point in their lifecycle — and knowing whether it worked.
Pushwoosh gives you behavioral segmentation, RFM segmentation, A/B testing, rich push notifications, and a visual Customer Journey Builder to orchestrate campaigns across push, email, SMS, and in-app — all from one platform.
