How do you set up push notifications in MoEngage? The short answer: connect the mobile SDK and push certificates first, build the segment the notification should reach, choose whether it is a one-off campaign or an event-triggered flow, write a message that earns the tap, then test the full path end to end before it goes live for real users. Skipping any one of those steps is the most common reason a MoEngage push notification programme underperforms even when the platform itself is set up correctly.
MoEngage push notifications work across mobile and web, and the underlying mechanics are the same whether a message fires from a single campaign or from an automated journey inside MoEngage's flow builder, covered in more general terms in our guide to what MoEngage is. This guide focuses specifically on getting push right: the setup steps, the decisions that matter most, and the mistakes that quietly reduce delivery and open rates.
What MoEngage Push Notifications Can Do
Push is one of several channels inside MoEngage, alongside email, SMS, and in-app messaging, and it earns its place because it can reach someone who is not currently inside the product. Unlike in-app messages, which only appear while someone has the app open, a push notification can bring a dormant user back, confirm an order has shipped, or flag time-sensitive information such as a price drop or a renewal date.
That reach is also push's main limitation. A notification competes for attention on a lock screen alongside every other app someone has installed, and a platform that defaults to sending too often will see opt-out rates climb quickly. MoEngage's own documentation covers the technical configuration in detail, but the setup decisions below determine whether the channel performs well once it is live, not just whether it is technically working.
Push vs Other Channels in MoEngage
Before building a push campaign, it is worth deciding whether push is actually the right channel for the message. A detailed explanation, a receipt, or anything someone might want to reference later belongs in email. A time-sensitive nudge that benefits from an immediate glance, a cart reminder, a flash sale ending soon, a flight check-in window opening, is a better fit for push. Platforms including Braze follow a broadly similar channel logic, so the decision framework carries across tools even where the interface differs.
How to Set Up MoEngage Push Notifications Step by Step
Step 1: Connect Your Push Certificates and SDKs
Before any notification can send, MoEngage needs the relevant push credentials configured for each platform: APNs certificates or keys for iOS, and Firebase Cloud Messaging credentials for Android. This is a one-time technical setup, usually handled by whoever manages the app's mobile codebase, and it needs to be kept current since an expired certificate will silently stop delivery without an obvious error on the marketing side. Confirm the SDK is correctly integrated and that test devices are registering as expected before building out any campaigns on top of it.
Step 2: Define the Segment
Decide who should receive the notification before writing a word of copy. A broad segment, such as everyone with the app installed, almost always underperforms a narrower one built around actual behaviour, such as people who added an item to a cart in the last 24 hours and have not purchased. MoEngage's segmentation works the same way across channels, so the groundwork covered in a general behavioural segmentation guide applies directly to push audiences as well as email ones.
Step 3: Choose a Trigger or Campaign Type
MoEngage supports both one-off push campaigns, sent to a defined segment at a scheduled time, and event-triggered push, sent automatically when someone takes or fails to take a specific action. A triggered notification, such as one that fires two hours after an abandoned cart, usually performs better than a scheduled blast because it reaches someone close to the moment the behaviour happened, when the context is still fresh. Decide early which type the use case calls for, since the build steps differ.
Step 4: Write and Personalise the Message
Push notifications have very little room: a title, a short body, and sometimes a single rich image or action button. Lead with the specific benefit or reason to open, not a generic brand message, and use whatever personalisation tokens MoEngage has available, a first name, a product name, a specific date, rather than sending the same static line to everyone. A notification that reads like it was written for one person tends to outperform one that reads like it was written for a list.
Step 5: Set Frequency Capping and Quiet Hours
Set a cap on how many push notifications a single person can receive in a day or week, and configure quiet hours so messages do not land in the middle of the night in the recipient's local time zone. Both settings exist inside MoEngage's campaign and channel configuration, and skipping them is one of the fastest ways to drive up opt-outs even when the message content itself is reasonable.
Step 6: Test Before You Send
Send the notification to a small internal test group or test devices first, and check that the title, body, image, deep link, and any personalisation tokens all render correctly on both iOS and Android before the full send goes out. A broken deep link or a token that fails to populate is easy to miss in a preview pane but obvious the moment real recipients start tapping through to the wrong place.
Common Mistakes When Setting Up MoEngage Push Notifications
Sending to everyone instead of a defined segment. The fastest way to see opt-out rates climb is to default to the broadest possible audience for every notification. Segment first, even if that means a smaller initial reach.
Treating push like email with a shorter character count. A notification that tries to cram in multiple pieces of information rarely reads well on a lock screen. One clear idea, with a single reason to tap, consistently performs better than a message trying to do several jobs at once.
Ignoring time zones. A notification scheduled in one time zone but sent globally can land at inconvenient hours for a meaningful share of the audience. Quiet hours settings exist specifically to prevent this and should be configured before the first live send, not added after complaints start.
Never testing the deep link. A notification can have a strong open rate and still fail the user if the tap takes them to the wrong screen, or to a generic home page instead of the specific content the message promised. Test the full tap-through path, not just the notification preview.
How to Measure Whether Your MoEngage Push Notifications Are Working
Track delivery rate first, since a drop here usually points to a certificate or token issue rather than a content problem. From there, open rate, sometimes called click-through rate on push, shows whether the message itself is earning attention, and conversion rate on whatever action the notification was meant to drive, a purchase, a return visit, a completed step, shows whether the channel is actually contributing to the outcome that matters, which ties back to the broader economics explained in HubSpot's research on customer retention, rather than just generating taps.
It is also worth tracking opt-out rate specifically for push, separate from overall channel performance, since push tends to be the channel where over-sending shows up fastest. A comparison of MoEngage and Braze is useful if you are deciding which platform to run this on in the first place, but the measurement principles above apply regardless of which platform ends up hosting the programme.
MoEngage push notifications are straightforward to configure technically but easy to get wrong strategically. Most of the work that actually improves performance happens in segmentation, timing, and message discipline rather than in the setup screens themselves. If push is one channel among several in your lifecycle programme and you want help making sure it works alongside email, SMS, and in-app messaging rather than competing with them, GrowNowNow's retention work covers how each channel fits into the wider customer journey.
Frequently Asked Questions
How do I set up push notifications in MoEngage?
Connect the platform-specific push credentials, APNs for iOS and Firebase Cloud Messaging for Android, to your MoEngage account, confirm the mobile SDK is correctly integrated, then build a segment, choose between a scheduled campaign or an event-triggered send, write the message, and test the full path on real devices before going live.
Why are my MoEngage push notifications not being delivered?
The most common cause is an expired or misconfigured push certificate or token, which can fail silently without an obvious error on the campaign side. Check the certificate and SDK integration status first before assuming the problem is with the campaign setup or the segment.
How often should I send push notifications?
There is no universal number, but most programmes see opt-outs climb once a user receives more than one or two non-essential notifications a week. Setting a frequency cap inside MoEngage is a safer approach than relying on manual discipline across multiple campaigns and teams.
Should push notifications be personalised?
Yes, where the data supports it. A notification that references a specific product, name, or action someone took performs better than a generic blast, and MoEngage supports personalisation tokens for exactly this purpose.
What is the difference between a scheduled push campaign and a triggered one in MoEngage?
A scheduled campaign sends to a defined segment at a set time, regardless of individual behaviour. A triggered notification fires automatically in response to something a specific person did or failed to do, such as abandoning a cart, and generally performs better because it reaches someone closer to the moment the behaviour happened.