Documentation Index
Fetch the complete documentation index at: https://moengage-user-guide.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
🚀 New Features
Merlin AI Campaign Insight Agent turns campaign metrics into plain-language causes and actions—for example, delivery risks, how this send compares to your past performance, and what to try next on Push and Email one-time and periodic campaigns. Why it helps: You spend less time stitching together dashboards and more time deciding what to send next. Rollout is phased; MFA login applies for early access. Campaign Insight Agent
MoEngage Go is available on the iOS App Store so you can see campaigns, approve or reject items pending review, and pause or stop live sends when you are away from your desk. Sign-in matches the web app (SSO, Google, or email) with the same roles and permissions. Why it helps: You can respond to urgent approvals and incidents without waiting until you are back at a computer. Android was planned to follow after store review. Creating or editing full campaigns stays on desktop on purpose—those flows need a larger screen and review steps.
Just-in-Time (JIT) user provisioning creates and updates workspace users from your identity provider when someone logs in with SSO, instead of relying on manual invites for every person. Why it helps: New teammates get access immediately, admins spend less time on account upkeep, and access can stay aligned with corporate identity rules (including options such as time-bound access, where you configure them). SSO must already be set up for the workspace. Currently in beta, with access controlled per rollout. JIT User Provisioning
April 16, 2026
New Features
April 2026: dark mode, personalization checks, frequency limits, live eligibility
The April 2026 “What’s New” wave includes: dashboard dark mode for a comfortable viewing option; advanced campaign personalization preview so you validate tailored content with more confidence; frequency limits for in-app and on-site messages so you cap how often messages appear; and real-time eligibility checks so in-session behavior can drive which message users qualify for. Why it helps: Teams get clearer validation before sends, reduce message fatigue on owned surfaces, and show more relevant in-session experiences. What’s New on MoEngage
April 15, 2026 — Background Update
New Features
Send silent push data your app can use without a visible notification
The Background Update push template delivers a custom data payload to your app without showing a notification, using the same key–value style setup as other templates and a payload preview before send. Supported on Android and iOS (dashboard) for one-time, periodic, event-triggered sends, and Flows, subject to minimum SDK versions. Why it helps: You can refresh app state, feature flags, or security-related flows in the background—even for users who opted out of visible push—while your app logic decides what to do with the data. Background Update (user)
April 9, 2026
New Features
New data sources, ad audiences, conversion APIs, and Adobe email templates
MoEngage added connected sources (for example Behamics, Adapty, Zoho Landing) to bring intent, subscription, and lead signals into profiles and journeys; audience connections for Amazon Ads and Microsoft Ads; server-side conversion delivery for Meta, TikTok, Snapchat, and Microsoft Ads; and Adobe Experience Manager Experience Fragments synced as multi-locale email templates. Availability varies by data center and Connected Channels packaging where noted. Why it helps: You reduce manual exports, keep audiences and measurement closer to live behavior, and ship creative from AEM with less copy-paste. Browse partner guides on partners.moengage.com.
Primary device per user marks the latest logged-in device so you can restrict sends to that device across Push, Inform, Flows, and APIs when your policy requires it—for example sensitive alerts or less duplicate noise across tablets and phones. The device opt-out API blocks or unblocks a specific device from push through the API, which supports fraud or device-loss scenarios. Why it helps: You align high-trust messages with the device the user actually uses now, and you can cut off a single device quickly when security teams require it. Enablement for primary-device behavior may need a support-requested flag; the opt-out API is broadly available (confirm DC coverage in your contract). Primary device · Device opt-out API
🛠️ Improvements
You can rename custom segments from All Segments or the segment detail view. The segment ID does not change, so APIs, automations, and integrations keep working. Names update across navigation, recent queries, campaign views, edit history, and audit entries; APIs accept optional
segment_id where documented so calls stay unambiguous. Why it helps: Teams keep naming consistent with how the business talks about audiences—without weekend firefights over broken jobs. Rollout uses a feature flag; some segment sources do not support renaming yet—see product docs for the current list.April 15, 2026 — List experience
Improvements
Faster filtering and clearer loading on All Campaigns and All Flows
On All Campaigns and All Flows, lists now use shimmer placeholders while data loads, show a dedicated empty illustration when nothing matches filters, keep your search text and filters when you switch among All / Scheduled / Active, and let you click the search icon to run a search like other search fields. Legacy “loading campaigns” behavior was removed in favor of this clearer pattern. Why it helps: You move between tabs without redoing work, and loading states read as “still fetching,” not as a finished empty workspace.
🩹 Bug Fixes
April 15, 2026 — Empty state while loading
Bug Fixes
Stop showing an empty list while campaigns are still loading
Previously, All Campaigns could show “No campaign found” while results were still loading, which suggested missing data or wrong filters. The UI now waits for load to finish before showing the true empty state. Session insights also drove alignment with search retention and clickable search (captured alongside the improvement above). Why it helps: You trust what you see during navigation and avoid unnecessary support tickets or account checks.