The Mobile Engage overview page is located in the Campaigns menu, Mobile Engage. Here you can see the details of your Push Messages, and you have the option to switch to the Reporting or the Apps tabs.


The Push Messages tab

On this tab you can see details of your push messages: the Recipient source, the Status of the message, the App name, the number of messages Sent, the date of creation and its modification.

Click the icons to reporting-icon view the summary, edit-icon edit or delete-icon delete the messages.

Creating a new message – Settings

Click Create New to open the message creation wizard.


Here you can define the General settings. The possible Recipient source elements are the following:

  • Broadcast – This sends a message to all subscribers of your application.
  • Automation Center – This sends push messages using Automation Center programs.
  • Using a segment – This sends a push message from Mobile Engage to a pre-defined segment, without the need for an Automation Center program.

When you are finished with these, save your message for the first time to continue to the Content Creation step.

Creating a new message – Content

In the Message tab of the New Push Message window, you can create the content of your message and apply the platform-specific (iOS or Android) settings.


Type your message in the text box.

The live Preview pane on the right shows how your message will appear. Cycle through the available displays using the arrows under the phone. In the upper right corner, you can switch between Apple and Android phone previews.

Create a new message – Languages

To the right of the text editor you will see the distribution of languages for all the downloads of the selected app in your Emarsys database. The percentages refer to the language settings when the app was downloaded and give you an indication of which languages your customers prefer.

Note: These figures apply to your entire database, not to the launch list for this campaign.

  • To add and remove languages, click Manage language. You can select a language from the drop-down or use the dynamic search field to find it.


Every language now has a tab where you can write the message content in that language.

  • If a tab contains no content, those customers will receive an empty message, so make sure to remove any empty tabs before you send.
  • Languages which are not shown here will receive the content in the English tab by default.

Platform settings

Click the Platform Settings tab to set the platform-specific values of your messages.

Two platforms are available: iOS and Android.

iOS-specific settings

  • Badges – The iOS badge number you want to send with your message. You can also enter +n or -n to increase/decrease the current badge number by the value of n (i.e. entering +1 will increase the badge value by 1). Sending 0 clears the badge from your app’s icon.
  • Sound – Enter the name of a custom sound file in the main bundle of your application. This sound will play when the message is delivered.
  • Root parameters -The root level parameters to the APS dictionary.
  • Expiration time – The period after which the push will not be delivered if the device is offline.

Android-specific settings

  • Badges – The badge number you want to send with your message. You can also enter +n or -n to increase/decrease the current badge number by the value of n (i.e. entering +1 will increase the badge value by 1). Sending 0 clears the badge from your app’s icon.
  • Sound – Enter the name of a custom sound file in the “res/raw” folder of your application, without the file extension. This sound will play when the message is delivered.
  • Header – You can specify your Android notification header here.
  • LED color – choose an LED color; the device will create its best approximation.
  • Image background color – Set the background color of the image.
  • Force Vibration – Set the device to vibrate on arrival. It is recommended to use this for urgent messages only.
  • Icon -Enter the path to the notification icon.
  • Custom icon – Enter the path to the custom notification icon.
  • Banner – Enter the image URL here. The image must be =< 450px wide, with ~2:1 aspect ratio, and be center cropped.
  • Root parameters – The root-level parameters for the Android payload, custom key-value object.
  • Priority – The priority of the push in the Android push drawer.
  • Expiration time – The period after which the push will not be delivered if the device is offline.

When you are finished, you can continue and test your message.

Test message

In the Send Test Message window, you can specify an email address to which a test message will be sent.


To test your message, click Save & Send.

If sending of the test message fails, a red warning message appears on the screen. The reasons for this could be the following:

  • No contact has been found in Emarsys database with the given email address.
  • The email address has been found, but there is no device associated to it.

For more information on association of contacts and devices, see the App login endpoint


When you have tested your message, you can continue to the Launch step.


On this screen, the number of recipients displayed depends on the Recipient source chosen in the Push Message Settings step:

  • Automation Center – If this is selected, the number of push messages sent will be calculated in the Automation Center program.
  • Broadcast – If this is selected, the number of all app users with a push token will be displayed.
  • Using a segment – If this is selected, the number of app users in the segment will be displayed.
  • Using a Mobile Engage segment – If this is selected, the number of contacts in an app-specific, Mobile Engage segment with device- and behavior-level criteria will be displayed.

    Note: Apart from the Mobile Engage segments, which use the Mobile Engage database, the number of users in the other kinds of segments comes from the Emarsys Suite database. In order to make this number reflect the actual number of opted-in customers, i.e. the exact number of messages that will be sent out, when creating the segment Push Accepted should be used as a contact criteria.


In the Scheduling section, you can either select Launch now for immediate action, or you can define a specific date and time to launch your push message. In this case, the contents of the message are editable until launch and they can even be withdrawn, if needed. For example, you can schedule weekend campaigns on the last working day of the week, without the need of involving an Automation Center program for the scheduling part.

Scheduling is available to all kinds of recipients, except the Automation Center ones.

To launch your message, click Launch.


On this tab you can see the summary of your push message.


In the Overview section, the Opens and the Installs are displayed, while in the Distribution by platform window the breakdown of platforms can be seen, based on Total installs, Active users and Opt-ins.

The following list contains explanations for the terms used:

  • Opens – The application is opened from a push message directly
  • Total sent – The total number of push messages sent by Emarsys.
  • Total installs – The total number of known application installs.
  • Active users – The number of users who opened and used the application in the last 30 days.
  • Opt-ins – All users who agreed to accept push messages.
  • Opt-outs – The number of users without a push token.



A list of your applications using the Mobile Engage service is displayed here. You can see the App ID, the App name as well as the Platform used and its date of creation and modification. Click the details icon to display the General Settings of your application, including the Application name, the Application code and the Icon URL.

Debugging features

The are two methods for debugging:

  • Click the users-icon icon to display the last 20 application installs with details like Contact ID, Hardware ID, Push token, Platform, Device model, Timezone, Language, etc.

  • Click the sdk-events-icon icon to display the last 20 incoming Mobile Engage events and response codes for the application.

These pieces of information help you in debugging your API integration by examining the first test installs and incoming events. You can then check the correct installation and responses for API calls.


You can now onboard your own apps for Mobile Engage without the help of Emarsys Support. After registering with our delivery partner, you can now add your API Access token in the Settings tab:

First, you have to obtain your push token at our delivery partner’s Control Panel.


Click Save when you have copied the secret into the Mobile Engage user interface.

When the app is created and added to your inventory, the key Emarsys system fields are automatically mapped.


The mapped local fields are editable, so they can be re-assigned as needed. You can also view your Emarsys Mobile Engage application password.