In This Article:
- What is Mobile Engage?
- What kinds of messages can I send?
- How is it constructed?
- How does it work?
- Supported Functionality
- Mobile Engage Onboarding
- Mobile Engage End-user Guide
- The Mobile Engage Data Flow Model
- The Mobile Engage API
- The Mobile Engage SDK
- Importing Previous Push Audiences to Mobile Engage
- Obtaining Certifications and Tokens for Sending Push Messages
- Creating a Trackable Deep Link for Mobile in Email
- Advanced Features
- Mobile Engage Glossary
What is Mobile Engage?
Push messages open up a new channel in B2C marketing. They can be highly personalized, even to a 1-to-1 level, which has long been the dream of all marketers. With this in mind, Emarsys created Mobile Engage, allowing you to get in touch with your mobile subscribers – whenever you need to, wherever you need to, and with the right message.
With Emarsys Mobile Engage you can send remote notifications to segmented user groups across multiple platforms and devices.
What kinds of messages can I send?
There are four types of messages:
- Messages to all app users - These are batch campaigns sent to all subscribers to your app, without any segmentation.
- Automation Center messages - These are segmented and/or personalized, usually transactional messages, e.g. "Joe has accepted your friend request", which are sent as part of an Automation Center program.
- Messages to Emarsys segments - These are messages sent to any one of your Emarsys segments.
- Messages to Mobile Engage segments - These are messages sent to Mobile Engage segments. These segments use contacts in the Mobile Engage database, and are listed with the regular Emarsys segments. However, you can use them to create combined segments. For more information, see Mobile Engage Segmentation.
How is it constructed?
Here is an overview of the Mobile Engage service architecture:
The main components of the Mobile Engage service are as follows:
- Emarsys Mobile Engage
- The app provider (you)
- Apple Push Notification service (APNs – for iOS) and Firebase Cloud Messaging (FCM – for Android)
The service architecture also contains some additional supporting elements:
- The Emarsys Platform
- The Automation Center
- Various contact databases and application user databases
How does it work?
When a user installs your app and gives it permission to accept push messages, a push token is generated. This is created using data unique to the application and the device. It is later used to deliver the push message to the device.
The messages are created with the Emarsys Mobile Engage service. When saved, they can also be added to an Automation Center program node.
Finally, the message is delivered to the end users’ apps, with the necessary conditions for triggering them on the device. These conditions are based on customizations applied to the message in Emarsys Mobile Engage or the Automation Center. For more information, see Mobile Engage - End-User Guide.
- Link email, social and mobile data at the contact level.
- Capture mobile browsing behavior with e-commerce activity.
- Accurately link mobile and web browsing experiences.
- Cross-channel automation.
- Choose from several mobile success blueprints that combine mobile push notifications, in-app messages and email.
- Send mobile push messages to users who perform specific mobile events.
- Co-ordinate Marketing and Transactional campaigns.
- Manage transactional push message using the either the Emarsys Automation Center canvas or trigger via API.