Reach 100% of your app users.
No
opt-in required.
In-app notifications are banners, modals, and full-screen messages that appear while someone is using your app. PushEngage in-app messaging triggers them on real behavior and reaches every session, and nobody has to subscribe first.
“PushEngage is quick and easy to implement. It provides results promptly and the analytics presents them in a clear and understandable fashion.” Alex Avery · Database Marketing Executive
75,000+ businesses No permission prompt needed 14-day money-back guarantee
Trusted by 75,000+ businesses in 150+ countries
Why it works
In-app notifications reach the users push can’t reach yet.
Push reaches the people who opted in. Email reaches the people who open it. In-app messages reach everyone who opens your app, at the exact moment they are inside it.
No permission prompt
Push and email need an opt-in before you can say a word. In-app messages show the moment the app opens. Every install is reachable from day one, including users who declined push.
The moment it matters
Trigger on app open or on real events: a cart abandoned, a plan limit reached, a price drop viewed. The message lands while the intent is still warm, in the same session.
Protects your push channel
Operating systems now silence noisy senders. Use an in-app message to earn the push permission at the right moment, so the one OS prompt you get actually converts.
How it works
How in-app messaging works, from app open to action taken.
Design in blocks. Preview it live.
Build messages block by block in a visual editor, with a live phone preview of every display style. Start from a template gallery organized by goal, or save your own designs and reuse them.
- Top banner, bottom banner, center modal, or full screen
- Templates for nine goals, from permission priming to win-back
- No app release needed to ship or change a message
Triggered by behavior. Aimed by attribute.
Show a message automatically on app open, or fire it on a custom event with conditions on the event’s own parameters. Then narrow the audience with attribute groups, so each message reaches only the people it was written for.
- Auto trigger with a delay, or custom event triggers with conditions
- Target by attribute, platform, language, app version, or device region
- Frequency caps, priorities, start and end dates, display duration
What’s included
Templates, targeting, and triggers for in-app messages. Built in.
In-app messaging runs from the same dashboard as your push and WhatsApp campaigns. One SDK integration, every channel after it.
Template gallery
Ready-made designs for nine jobs: get push permission, announce, run offers, onboard, collect ratings, recover carts, win back lapsed users, and grow your other channels.
Audience targeting
Combine attribute conditions into groups, so a first-time user and a returning customer see different messages from the same campaign list.
See segmentationScheduling and frequency
Start and end dates, one-time or recurring displays, and hard caps so a message never overstays its welcome.
Per-message analytics
Impressions, clicks, and closes for every message, so you know what converted and what got dismissed on sight.
See analyticsPush permission priming
Ask with a designed message first, and spend the one-shot OS permission prompt only on users who already said yes. Your opt-in rate becomes a funnel you control.
Works with app push
In-app messages catch users in the session; push notifications bring them back after it. One SDK powers both channels.
Explore app pushCustom event triggers
Fire a message when your app sends an event, such as a cart left behind or a plan limit reached. Conditions on the event’s parameters decide exactly when it counts.
Priority when messages overlap
Give each message a priority from 1 to 3. When two campaigns qualify in the same session, the one that matters more shows first.
No app release per message
The SDK renders every message, so launching, editing, or pausing one happens in the dashboard. Your release calendar stays with engineering; your campaign calendar stays with you.
SDKs & developers
One SDK integration. Two channels out of it.
The same PushEngage SDK that delivers app push renders your in-app messages. If push is already integrated, in-app messaging needs no new engineering.
Mobile app push
The companion channel: reach users on the lock screen when they are not in the app. Same SDK, same dashboard, same subscriber engine.
Explore app pushiOS SDK
Native Swift and Objective-C SDK with APNs delivery for your Apple apps.
iOS pushAndroid SDK
Kotlin and Java SDK with FCM delivery and rich notifications. Existing Firebase tokens migrate cleanly.
Android pushREST API & webhooks (Growth)
Every send, subscribe, and segment operation has a documented endpoint. Nothing is console-only.
API documentationDeveloper hub
SDK guides, integration recipes, and everything engineering needs to ship the one-time setup.
For developersPricing
In-app messaging from the Business plan. Pay only for active subscribers.
Public prices on every tier, no per-message fees (each plan includes a monthly sending volume). Every paid plan carries a 14-day money-back guarantee.
Free
$0
Free forever, no card
- 1 site or app, 200 subscribers
- 30 campaigns (lifetime), 1 active workflow
- In-app messaging not included
Business
$8/month
from $8/month, billed yearly (first-year price)
- In-app messaging included
- 1 site or app, up to 50,000 active subscribers
- Unlimited campaigns, 5 workflows
Premium
$15/month
from $15/month, billed yearly (first-year price)
- More in-app messages live at once
- 2 sites or apps, up to 100,000 subscribers
- A/B testing, drip, goal tracking, timezone sending
Growth
$24/month
from $24/month, billed yearly (first-year price)
- 3 sites or apps, up to 250,000 subscribers
- Cart and browse abandonment
- Back-in-stock and price-drop alerts
Enterprise pricing is custom. Prices shown are first-year rates. See every plan and the pricing calculator.
Side by side
In-app notifications three ways: hard-coded, push alone, or PushEngage.
A capability comparison, not a price list. Hard-coded means prompts your developers build into the app itself.
| Hard-coded in the app | Push notifications alone | PushEngage in-app messaging | |
|---|---|---|---|
| Reaches users who declined push | Yes | No. Needs the OS permission first. | Yes. No opt-in required. |
| Launching or changing a message | An app release, then store review | From a dashboard | From the dashboard. The SDK renders it, no app release. |
| Where it appears | Wherever the code puts it | Lock screen and notification center, outside the app | Over the screen in use: top banner, bottom banner, center modal, or full screen |
| What triggers it | Custom logic per prompt | A send, schedule, or campaign trigger | App open (with an optional delay) or a custom event, with conditions on its parameters |
| Who sees it | Custom logic per segment | Segments of push subscribers | Audience groups built from attribute conditions |
| Frequency and overlap | Custom logic | Your send cadence | One-time, recurring, or capped, with priority 1 to 3 |
| Measurement | Your own analytics events | Sends and clicks | Impressions, clicks, and closes per message |
| Who runs it day to day | Engineering | Marketing | Marketing, after a one-time SDK integration |
The PushEngage column describes in-app messaging on the Business plan and above. Most teams run in-app messages and mobile app push notifications together: in-app converts the current session, push starts the next one.
The numbers
Built for the era of quiet lock screens.
FAQ
In-app messaging questions, answered.
What are in-app notifications?
In-app notifications, also called in-app messages, are banners, modals, and full-screen messages shown inside your app while someone is using it. Push notifications reach the lock screen when the app is closed. In-app notifications reach people during the session, over the screen they are already on.
Do users need to opt in to see in-app messages?
No. Push notifications need a permission prompt; in-app messages render while the app is in use, so they reach every user, including the ones who declined push. The smartest play is to use an in-app message to explain the value of push first, then trigger the OS prompt only for users who tap yes.
How is this different from app push notifications?
Push reaches the lock screen when someone is away from your app. In-app messages reach them while they are inside it, over the screen they are already on. The channels compound: in-app converts the session that is happening now, and push starts the next one.
What can trigger an in-app message?
Two trigger types: automatic on app open, with an optional delay, or a custom event fired from your app, with conditions on the event’s own parameters. On top of the trigger you control frequency (one-time, recurring, or capped), priority, display duration, and a start and end schedule.
Which platforms support in-app messages?
In-app messaging ships first in the PushEngage Android SDK (version 1.0.0 and later). Support in the iOS, Flutter, and React Native SDKs is on the way. Talk to us for the current status on your stack.
Which plan includes in-app messaging?
In-app messaging is included from the Business plan up. Higher tiers can run more active messages at the same time, so a welcome message, a promo, and a win-back campaign can all stay live at once.
Do I need a developer for every message?
No. The SDK integration is a one-time cost, and it is the same SDK that powers app push. After that, every message is designed, targeted, and published from the dashboard. No app release is needed to ship or change a message.
Which message formats can I use?
Four positions: top banner, bottom banner, center modal, and full screen. Start from templates grouped into nine goals, such as push permission, onboarding, offers, cart recovery, ratings, and win-back, or design your own and save it for reuse.
How do I know if an in-app message worked?
Every message reports impressions, clicks, and closes. A message that gets closed on sight tells you as much as one that gets clicked, so you can rewrite, retarget, or retire it from the dashboard.
How much does in-app messaging cost?
In-app messaging is included from the Business plan, from $8/month billed yearly. The Free plan does not include it. You pay only for active subscribers, never per message, and every paid plan has a 14-day money-back guarantee.
They are already in your app. Start the conversation.
In-app messaging is included from the Business plan. If PushEngage isn’t the best fit within 14 days, we refund 100%. No questions asked.
No opt-in required One SDK for push and in-app 14-day money-back guarantee