MoEngage

Median integrates MoEngage's native SDKs on iOS and Android, including APNS Auth Keys (iOS) and FCM Authentication (Android), and exposes push permission management, user identity, event tracking, and the MoEngage notification center through the Median JavaScript Bridge.

Why use MoEngage

• Push permission management: Prompt for and check notification permissions from JavaScript on Android and iOS.
• Cross-platform user identity: Set stable unique IDs and aliases, and reset user data consistently across installs and platforms.
• Behavioral event tracking: Log named events with or without key-value payloads for MoEngage segmentation and campaigns.
• In-app notification center: Launch the MoEngage inbox and subscription center from any JavaScript context in your app.

👍

Developer Demo

Display our demo page in your app to test during development https://median.dev/moengage/

---

Prerequisites

• A Median.co app with JavaScript Bridge enabled
• MoEngage FCM authentication configured in your MoEngage dashboard (Android)
• MoEngage APNS authentication key configured in your MoEngage dashboard (iOS)
• Median deep linking configured for your app (required for notification links to open in-app destinations)

---

When to use this plugin

MoEngage is essential for apps that need to:

What you'll do

1. Configure credentials: Complete MoEngage FCM (Android) and APNS (iOS) setup per the Plugin setup section.
2. Configure deep linking: Set up Median deep linking so notification links open in-app.
3. Implement permission APIs: Use promptNotification and notificationEnabled from JavaScript bridge functions.
4. Implement user identity and events: Add setUniqueId, setAlias, resetUser, trackEvent, and launchInbox calls.
5. Validate: Run through the Testing checklist and check Troubleshooting for known issues.

---

Key terms

• FCM Authentication: Firebase Cloud Messaging, the push authentication mechanism for Android delivery. Configured in your MoEngage dashboard.
• APNS Auth Key: Apple Push Notification service authentication key for iOS delivery. Configured in your MoEngage dashboard.
• Deep Linking: A Median.co feature that routes notification URLs directly into in-app destinations rather than opening a browser.

📘

Important considerations

• Android push permission dialogs appear on Android 13 and above; on Android 12 and below, permission is always granted without user interaction.
• Deep linking must be configured separately in Median App Studio for in-app notification routing to work.

---

Plugin setup

Enable the plugin

Median uses MoEngage native iOS and Android SDK integrations. Refer to MoEngage's documentation for FCM Authentication and APNS Authentication Key setup steps in the MoEngage dashboard.

---

JavaScript bridge functions

Prompt for Push Notification Permission

Prompts the user for push notification permission. On Android 13 and above, a system dialog is shown. On Android 12 and below, permission is always granted without user intervention.

Provide a callback function, or a promise is returned.

↔️Median JavaScript Bridge

JavaScript

// Using a callback
median.moengage.promptNotification({ callback: function () {} });

// Using a promise
median.moengage.promptNotification().then(function (result) {
  console.log('Notification permission result:', result);
});

Parameters:

Check Push Notification Permission Status

Checks current push notification permission status.

Provide a callback function, or a promise is returned.

↔️Median JavaScript Bridge

Javascript

// Using a callback
median.moengage.notificationEnabled({ callback: function (result) {
  console.log('Notifications enabled:', result);
}});

// Using a promise
median.moengage.notificationEnabled().then(function (result) {
  console.log('Notifications enabled:', result);
});

Parameters:

Set UniqueID

Sets a persistent user identifier across installs and platforms. Call after login to associate subsequent events and push tokens with the user.

↔️Median JavaScript Bridge

Javascript

median.moengage.setUniqueId('uniqueid');

Parameters:

Set Alias

Updates the existing user unique ID with a new alias. Use when a user's identifier changes, for example after account merging.

↔️Median JavaScript Bridge

Javascript

median.moengage.setAlias('alias');

Parameters:

Reset User

Resets unique ID and all data for the current user. Call on logout to disassociate the device from a user account.

↔️Median JavaScript Bridge

Javascript

median.moengage.resetUser();

Log Event With or Without Data

Logs a named event with an optional key-value payload. Use for behavioral analytics and segmentation in MoEngage.

↔️Median JavaScript Bridge

Javascript

// Event with payload
median.moengage.trackEvent(eventName, { key_1: 'value_1', key_2: 'value_2' });

// Event without payload
median.moengage.trackEvent('eventName');

Parameters:

Notification Center

Launches the MoEngage notification and subscription center.

↔️Median JavaScript Bridge

Javascript

median.moengage.launchInbox();

---

Testing checklist

Use this checklist to ensure MoEngage is working correctly in your app:

Basic Functionality

• median.moengage.promptNotification shows the permission prompt on Android 13+ and grants silently on Android 12 and below.
• median.moengage.notificationEnabled returns expected status after permission is granted or denied.
• median.moengage.setUniqueId, setAlias, and resetUser execute without JavaScript errors.
• median.moengage.trackEvent logs events with and without payloads.
• median.moengage.launchInbox opens the notification/subscription center.

Platform Testing

• Push notifications are delivered on Android with FCM authentication configured.
• Push notifications are delivered on iOS with APNS authentication configured.

Deep Linking

• Notification links open directly inside the app with Median deep linking configured.
• Notification links fall back gracefully when deep linking is not configured.

User Experience

• Users receive the push permission dialog at an appropriate point in the onboarding flow.
• Inbox opens correctly from UI entry points in the app.

---

Troubleshooting

Notification links do not open inside the app

Set up Median deep linking in App Studio so notification URLs resolve to in-app destinations. Without deep linking configured, tapping notification links may open an external browser instead.

MoEngage bridge methods are undefined at runtime

Confirm the MoEngage native plugin is enabled in Median App Studio and that the JavaScript Bridge is active for your app. Call bridge methods after the page is fully loaded.

Push notifications not delivered on Android

Verify FCM Authentication is configured correctly in your MoEngage dashboard. Confirm the Google Services configuration in Median App Studio matches your Firebase project.

Push notifications not delivered on iOS

Verify APNS Authentication Key is correctly configured in your MoEngage dashboard. Confirm push entitlements and provisioning profiles are set for your iOS build.

promptNotification has no effect on Android 12 and below

This is expected behavior. On Android 12 and below, push permission is always granted without user intervention. The prompt dialog is shown on Android 13 and above only.

📘

Still having trouble?

For issues related to MoEngage's own configuration, permissions, or platform-specific behavior outside Median's bridge, refer to MoEngage's integration documentation.