Mobile push notifications

To send mobile push notifications, you need to link your mobile app to the service, then create and customise the message.

Set up the mobile app as instructed:

You need to fill in:

• Application name - this is used as a service name and is displayed in the Mobile Push preview
• Connection method - Firebase Cloud Messaging

Configuring for Firebase Cloud Messaging

• Upload the Firebase service account key (.json)

Firebase service account key you can get it from the developers who support your mobile app. If you have already sent Mobile Push before - you already have everything you need, if you want to start sending Mobile Push - you need to register and get all the necessary data.

Once you have completed the configuration, inform your personal manager to activate the module.

In order to create a Mobile Push notification go to Mailings ➔ Messages ➔ New message and select the Mobile Push channel

Currently you can only create an instant message - it will be sent immediately after creation

In the creation wizard you can set the sending settings:

• Message subject (on devices, the subject displays approximately 50 characters)
• Message text (about 200 characters)
• Jump URL - this is the action when you tap on the push notification (you can choose from three available options: URL, Deeplink, Open app)
• Image URL - a link to the image that will be displayed on the right side of the push notification.

Once all the send settings are filled in, you can set additional settings. They are not mandatory, but will allow you to personalise the push notification and make it more visible to the recipient.

• Buttons - you can add up to 3 buttons to your notification, for each button you need to set the text and action when you tap on it (the three options are similar to setting up a click URL).
• UTM tags and URL parameters - work only for URL links

You can change the display for iOS and Android

At the same step you can send a test Mobile Push to check if the message is displayed correctly and, if necessary, correct it before sending it to users.

Additionally, in the same window you will be able to track the status of sending the test Mobile Push and find out the reason if the message was not delivered (e.g. if an invalid token was entered).

Test sending is available when you create or edit a Mobile Push message. Go to Mailings → Messages → Message editor (Mobile Push). In the Message editor step, fill in the required fields:

• Message subject;
• URL.

The “Sending test message” button will become active. As soon as you press on it in the opened window:

• enter the device token manually or select from the list of previously used tokens;
• select the operating system (Android or iOS) - it is important to select the OS corresponding to the token, as it will be recorded in the database;
• click “Send” (the button will become active only after entering the token).

The window will display the real-time sending status of the test Mobile Push:

• Sending - with a download indicator;
• Delivered - the message was successfully delivered to the recipient's device;
• Not sent - with an error text, for example, “Requested entity was not found.”

Limitations and Features

• You can only enter one token at a time.
• You can send tests even for tokens that:
  • unsubscribed;
  • not added to the enKod contact database - after a test send they will be added;
  • deleted - after a test send the contact will be restored from the deleted ones.
• Test send statistics are saved until you exit the Message editor (Mobile Push).

After creating the mobile push, you need to specify the recipients of the message. To do this, in the corresponding drop-down lists, include or exclude the segments you need from the mailing list.

In Mobile Push segments, recipients are counted based on the number of unique contacts, however, one contact can have more than one device assigned to it. As a result, the number of messages sent (displayed in Message Details ➔ Device Statistics) may be higher than expected. In the Message Details ➔ Information ➔ Recipients section, you can track the number of recipients, sent and unsent messages separately by unique contacts and separately by number of devices.

If there is an inactive mobile token in the recipients (Firebase Cloud Messaging returns the error requested entity was not found), the message will not be delivered to it, and the token itself will be automatically unsubscribed.