Loading
The Trailblazer Community is now read-only Read More
Marketing Cloud Engagement
Upgrade to Mobile App Messaging in Marketing Cloud Next

Upgrade to Mobile App Messaging in Marketing Cloud Next

Move from MobilePush in Marketing Cloud Engagement to Marketing Cloud Next by adding the mobile app messaging module to your existing app.

Required Editions

Available in: Marketing Cloud Engagement Pro+, Corporate+, and Enterprise+ Editions

Mobile app messaging is built on Salesforce and Data 360, and is available in all regions. You can transition from MobilePush to mobile app messaging without replacing your app's messaging foundation. Your existing device registrations, device IDs, and push permissions carry over.

Engagement SDK Modules and Supported Message Types

The Salesforce Engagement SDK is a single modular SDK embedded in your mobile app, with MobilePush and mobile app messaging as separate modules. MobilePush receives messages from Marketing Cloud Engagement, and mobile app messaging receives messages from Marketing Cloud Next. Because both modules live in the same SDK and share common functionalities, they run simultaneously in the same app.

Mobile app messaging includes push notifications and in-app messages. In-app messages support banner, modal, full-screen, and push primer templates, as well as custom events. Mobile app messaging doesn't support Inbox messages, so you can keep sending Inbox messages from MobilePush in the upgraded app.

Transition Phases for Your Mobile App

The transition is a one-time update for your mobile app, and includes these phases.

  • Upgrade to the Engagement SDK: Your app developer upgrades MobilePush SDK to version 10 or later, or to version 11 or later for in-app messaging.
  • Set up mobile app messaging: Your admin sets up mobile app messaging. For details, see Set Up Mobile App Messaging in Marketing Cloud Next.
  • Add the mobile app messaging module: Your app developer imports and initializes the mobile app messaging module alongside the existing MobilePush module.
  • Release a new app version: Your app developer publishes the updated app to the Apple App Store and Google Play Store.
  • Roll out to your app users: As users update to the new version and open the app, their devices become reachable through mobile app messaging.

For developer setup details, including integration guides for Android and iOS, see the Salesforce Engagement SDK documentation.

Device Registration and Push Permissions After the App Update

When a user opens the updated app for the first time, the mobile device automatically registers for mobile app messaging, using the device ID in MobilePush. The push notification permissions granted on the earlier app version continue to apply.

Note
Note The device of a user whose app is updated in the background doesn’t register until they open the app. To reach these users, send a message from a channel that already reaches them. For example, send a notification from MobilePush with a clear call-to-action to open the app.

Messages That Devices Receive on Each App Version

This table shows which messages each app version receives.

App Version Receives MobilePush Messages (Push, In-App, Inbox) Receives Mobile App Messages (Push, In-App)
Without the mobile app messaging module Yes No
With the mobile app messaging module Yes Yes

During the transition, keep sending from MobilePush so that users on earlier app versions continue to receive your messages.

Licensing and Monthly Active Device Billing

Provisioning at least one unit of the Salesforce Message Credits – Mobile App Regional (1,000) add-on Stock Keeping Unit (SKU) unlocks mobile app messaging.

Marketing Cloud Next bills mobile app messaging by monthly active devices. After Mobile App Regional (1,000) is provisioned, billing for all mobile app messaging usage, including push, in-app, and Inbox messages, changes from per-send billing to monthly active device billing. The change applies to both MobilePush and mobile app messaging.

Salesforce counts monthly active devices by device IDs, and not by physical devices. Because the device ID stays the same across the MobilePush and mobile app messaging modules of the Engagement SDK, you aren’t billed twice for a device that's active in both.

After mobile app messaging is unlocked, Salesforce Message Credits – Mobile App (1,000) SKU and Salesforce Message Credits – Mobile App Regional (1,000) SKU are interchangeable.

Note
Note The Mobile App (1,000) SKU alone enables only MobilePush with per-send billing, and doesn’t unlock mobile app messaging.

For exact entitlement, overage, and pricing terms, contact your account executive. To learn how Salesforce Message Credits – Mobile App usage and other messaging activities consume credits, see Billing Considerations for Unified Messaging.

Example Rollout Across App Versions
Example Rollout Across App Versions

Pacewell Sports Kicks sends mobile app messages from MobilePush and has 100,000 app users on app version 1.0. They add the mobile app messaging module and release app version 2.0.

  • Out of the 100,000 app users, 20,000 update to version 2.0 and open the app. Their devices register with mobile app messaging and receive messages from both MobilePush and mobile app messaging. The push permissions that these users granted on version 1.0 still apply.
  • The other 80,000 app users stay on version 1.0. Until they update to version 2.0, their devices receive push, in-app, and Inbox messages from MobilePush only.

To reach their entire audience during the transition, Pacewell Sports keeps sending from MobilePush, asking users to open the updated app. Each time an app user opens version 2.0 for the first time, another device becomes reachable through mobile app messaging.

 
Loading
Salesforce Help | Article