Configure mobile notifications

Mobile notifications are all mobile promotions you can display in a mobile application. Synerise enables you to create different types of mobile notifications. The number of people with smartphones is still growing and so is the amount of time we spend using them. Mobile notifications also give you the possibility to use geo-targeting for your messages. All you need is a mobile app integrated with the Synerise platform.


Before you start

Remember that before you start using mobile notifications you need to have your own mobile app first.


SDK Integrations

The SDK is a set of tools that allow programmers to build your application. It helps with authentication, notification management, event tracking, and so on.

You can find more information in Mobile SDK.


Mobile notification delivery flow

When a user opens the mobile application, a token is requested from Firebase Cloud Messaging (FCM). That token is passed on to Synerise to allow Synerise to authorize sending mobile push notifications to the user’s device.
The push is sent to the last device where the user opened the mobile application.
After the push is delivered and displayed, or if the delivery fails, information about that is saved as an event. See Mobile push events.

Overview of the process of sending a mobile push
Overview of the process of sending a mobile push

Conditions for sending and displaying mobile notifications

In order for mobile notifications to work, the following requirements must be met:

  • The target profile must have an active marketing agreement for mobile push notifications.
    You can check this agreement in the lower-left corner of the profile card, under Push.
    The Subscriptions section on a profile card
    The Subscriptions section on a profile card
  • The target profile must have the snrs_has_mobile_push_devices attribute set to true; the attribute sets to true when both of the following conditions are met:
    1. The device allows push notifications (in the system settings).
      Information about this is included in the client.applicationStarted event, under the systemPushConsent parameter. You can also find it on the profile card, in the Identities section:

      The Identity section on a profile card
      The Identity section on a profile card

      Android 7.0 and above: When the device doesn’t allow push notifications, a push.notView event is generated after the push is sent.

    2. The profile has an active Firebase Cloud Messaging (FCM) token.
      A token is requested from FCM every time the mobile application is started.

      Important: The Audience filter for the push notification should check if the snrs_has_mobile_push_devices attribute in the profile is set to true. Without this filter, the audience size in the campaign’s statistics is larger than the real number of profiles to whom the push is sent.

      Synerise stores the last known FCM token. The notifications are only sent to the last device where the user opened the app.
      The token becomes invalid when:

      • The user opens the app on another device.
        The new device receives a valid token and can receive push notifications.
      • The user uninstalls/reinstalls the app. Synerise doesn’t receive information about this.
        To receive a new token, the user must open the app.
      • The user clears the app data. Synerise doesn’t receive information about this.
        To receive a new token, the user must open the app.

      If the token in Synerise is invalid:

      1. A mobile push is sent, but can’t be delivered to the device.
      2. A push.notRegistered event is generated.
      3. The snrs_has_mobile_push_devices attribute in the profile is set to false.

For more information on FCM and tokens, see Google documentation.

Common reasons for failed delivery

Tip:

Using a large database of real profiles, we calculated that on average it takes 40 days for:

  • the token to become invalid for any reason.
  • the notification permissions for an app to be disabled on the device for any reason.

This is a rough estimate that may differ depending on the behavior of your mobile app users.

The following are the most common reasons for not delivering a push message:

Mobile dashboard

In the Mobile overview, you can find a complete list of your notifications and a summary for each one. In order to see the notification overviews, go to Communication > Mobile.

From there you can manage your Mobile notifications. Below you can find information about all elements which can be helpful in managing this channel. This module is divided into 4 sections:

  • Filters,
  • Templates,
  • Folders,
  • Mobile dashboard.

Screenshot from Synerise presenting Mobile dashboard

  1. In the Filters section, you can filter notifications based on their status and time when they were created. You can filter them based on a few conditions:

    • All - see the list of all notifications,
    • Recent - see the list of the most recently sent notifications,
    • Draft - see the list of mobile templates,
    • Scheduled - see the list of scheduled notifications,
    • Finished see the list of all sent notifications,
  2. In the Templates section, you can find templates that you can use in your notifications,

  3. The Folder section allows you to add folders to groups and organize notifications,

  4. In the Mobile dashboard, you will find all data connected with notification statistics. On the left side you can see notification statuses (how many of them are active/scheduled/paused), and on the right side you will find statistics from the last 24 hours (number of messages sent, OR and CTR).

Screenshot from Synerise presenting how to move notification to folder

  1. You can also add specific notifications to a folder. Click on the chosen notification.
  2. Then, choose the  Move to option visible on the blue bar.

Create a new mobile notification

Synerise enables you to create different types of mobile notifications. All you need is a mobile app integrated with the Synerise platform. In order to set up a mobile notification, go to Communication > Mobile.

Screenshot from Synerise presenting mobile dashboard

First of all, click the create new button in the upper right side of the screen.

Screenshot from Synerise presenting types of mobile notifications

  1. Enter the name. Optionally you can add there also its description,
  2. Choose the type of notification. Right now, Synerise allows you to choose from among six types of mobile notifications: Simple push, Silent push, Banner, Walkthrough, First run message, Mandatory upgrade.

Send mobile notifications

There are a couple of ways to send mobile notifications in Synerise. In this part we will show you the methods available, including:

  • Manually, from the Communication module
  • Using the Automation module (through Send mobile push)

Send manually

If you want to send a notification to a predefined group of customers or an entire database, you can do so manually from the Communications module.

WARNING: This option will allow you to send a message immediately or schedule it.

Screenshot from Synerise presenting how to save notification

You can manually send your notifications directly in the Communication module after creating your template and adjusting all settings. In order to send a mobile notification, go to Communication > Mobile.

Choose the type of your mobile notification:

After creating a template, click the Send button on the upper right side.

WARNING: The Send button will not be active until all sections described above have been filled in.
  1. When your message is saved as a draft you have to find it on the list in Communication > Mobile and click on it,
  2. If all the boxes are filled, you can click Send.
WARNING: If you set up a scheduled time in the future, the notification will be sent at the time you set after you click Send.

Send automatically

Automation of mobile notifications, based on behavioral data about the customer, saves the marketer’s time while increasing the efficiency of notification delivery. Synerise allows you to send mobile notifications automatically using the Automation module. Remember to use this solution when you want to send or display your mobile communication only to people who meet specific conditions described in the customer workflow.

WARNING: Using automation requires prior preparation of a mobile-push message template. Remember to prepare it earlier before you create the workflow.

In order to use automation for mobile notifications, go to Automation > Workflows > New workflow

You can create a mobile notification in just two steps:

  • Set the automation,
  • Save and/or run the no.

Use notification analytics

Mobile notification analytics let you analyze the results achieved within individual notification. Thanks to them you are able to compare and analyze data from each source in real time, gather information about their effectiveness and track the areas that are most important to you.

This lets you optimize the sending time of notifications, analyze the behavioral and transactional data collected about the user in the system and personalize their content.

In order to check the analytics, go to Communication > Mobile.

Screenshot from the Synerise automation module presenting mobile analytics

Above the list of notifications you can find a dashboard with general data about all notifications.

  1. On the left side you can see the notification statuses (how many of them are active/scheduled/paused), and on the right side you see statistics from the last 24 hours,
  2. You can also check the statistics from every notification. To do this, just double click on the notification.

Screenshot from the Synerise automation module presenting mobile analytics

In the Audience box, you can find all important statistics from a notification.

  1. Total Audience, total number of users in a selected segment,
  2. Estimated reach, the number of users to which the notification was sent. The number can sometimes be different from the total audience because not everyone from your audience can meet conditions necessary to receive the mobile notification (having an app, consent for mobile marketing etc.),
  3. Information about whether the selected segments to see the group of customers selected as the recipients of the notification,

😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker