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
No-code gamification for On-Site Messaging lets marketers build Spin the Wheel and Scratch Card experiences in the visual editor, including prizes, probabilities, styling, and coupon delivery—without custom HTML. Starter templates are available from the template gallery under the gamification use case. Web SDK 2.65.00 or higher is required; the capability is feature-flagged, and users below the minimum SDK will not see experiences once the flag is on. Rollout is phased (for example, early enablement for workspaces on supported SDKs in specific data centers); enablement is requested through support with SDK verification.
Portfolio now supports In-App Messaging and On-Site Messaging (OSM) so orchestration can span apps and the web from a unified portfolio profile. Marketers can run in-session and on-site experiences informed by cross-app behavior—for example, coordinated upsell, onboarding nudges across apps, and consistent creative across push, in-app, and web. The announcement states the channels are live for Portfolio-enabled accounts, with linked setup guides for Portfolio-powered In-App and OSM.
Email operations gain self-serve suppression management (subscribe, unsubscribe, bounce, and complaint handling in the UI), immutable audit logs for who changed reachability and when, profile events for resubscribe and bounce or complaint resets, and a unified sender data model across sender creation paths. The update is framed for email customers with a phased rollout to general availability and optional early enablement via support ticket.
Dark Mode is available across the MoEngage dashboard via the top-bar toggle, subject to new navigation being enabled. The release notes describe a phased rollout (for example, an initial set of workspaces on selected data centers), available to all pricing plans that receive the new navigation experience.
Re-evaluate Campaign Eligibility performs a live eligibility check before an In-App or OSM message is shown so segment and attribute changes within a session can change which campaign runs—for example, after a plan upgrade. Support is described for user-attribute and RTSE-backed definitions, Android SDK 9.7.0+ and iOS SDK 7.04.0+, up to five campaigns, with OSM following the global SDK where applicable. The capability ships behind a flag for controlled early customers pending broader enablement.
The March 2026 What’s New program calls out Merlin AI for in-app templates, Flow Assist for journey building, background app updates via push, splitting transactional volume across vendors, and mapping existing API payloads into Inform. The What’s New website is described as redesigned with clearer structure, capability tags, and filters. Distribution includes the web hub, social carousels, customer newsletter, and a planned video walkthrough.
Improvements
Conditional stages in Flows are redesigned for a clearer two-step flow (what to evaluate, then when), a visual time slider instead of opaque time controls, optional classic view, one-click branch duplication on Conditional Split, and drag-and-drop branch ordering. Rollout follows the standard data center sequence for SMB and MM segments first, with enterprise and large-hub waves after an initial feedback window.
Classic navigation and theme are deprecated effective March 31, 2026, after a long parallel run with the new experience. From April 1, 2026, all customers move to new navigation without reverting to classic. In-product cues and email reminders support migration; customer-facing teams are encouraged to prompt early adoption before the cutoff.
For workspaces on the revamped Flows system, Flow statistics can align to the app timezone configured when a Flow version went live (with continuity rules for already-active Flows noted in the source). Custom segments whose filters are RTSE-capable can execute in real time instead of on a multi-hour refresh when used as Flow audiences; eligible existing Flows pick up the behavior after edit and re-publish. Both capabilities reference phased enablement and rollout schedules communicated separately.
Funnel Analysis adds a logarithmic chart scale so small steps remain visible next to large ones, and a conversion percentage toggle for table exports and on-screen tables. Preferences persist on custom dashboards and saved queries.
The WhatsApp Info and Analytics experience adds total versus unique metrics, a number versus percentage view toggle, and a dedicated Click Analysis tab to separate link performance from the primary dashboard. Delivery follows a controlled rollout plan published to internal teams.
The Web SDK supports a CSP nonce at initialization so dynamically injected scripts and refactored inline handlers align with strict
script-src policies, reducing breakage for OSM, Web Personalisation, and Cards on hardened sites. WebP can append the nonce on the script URL. Coverage is called out for NPM, GTM, and Flutter Web; the scope explicitly addresses inline script CSP limitations, not every CSP directive family.Early AccessNo-code gamification for On-Site Messaging lets marketers build Spin the Wheel and Scratch Card experiences in the visual editor, including prizes, probabilities, styling, and coupon delivery—without custom HTML. Starter templates are available from the template gallery under the gamification use case. Web SDK 2.65.00 or higher is required; the capability is feature-flagged, and users below the minimum SDK will not see experiences once the flag is on. Rollout is phased (for example, early enablement for workspaces on supported SDKs in specific data centers); enablement is requested through support with SDK verification.
Paid AddonNo-code gamification for On-Site Messaging lets marketers build Spin the Wheel and Scratch Card experiences in the visual editor, including prizes, probabilities, styling, and coupon delivery—without custom HTML. Starter templates are available from the template gallery under the gamification use case. Web SDK 2.65.00 or higher is required; the capability is feature-flagged, and users below the minimum SDK will not see experiences once the flag is on. Rollout is phased (for example, early enablement for workspaces on supported SDKs in specific data centers); enablement is requested through support with SDK verification.