1 of 5

Push Notifications

This section allows you to create and manage push notifications campaigns.

If push notifications are not connected
Current campaigns
Creating a new campaign
Push notification report (Simple campaign)
Push notification report (Automated campaign)

If push notifications are not connected

To connect the push notifications service to the app you need to:

Integrate devtodev SDK and activate push notifications during integration
Fill in the required information in the push notifications panel in the Integration section of the application settings

Please note that access to the Integration section is restricted by user access rights.

Detailed information about the process of receiving necessary data and activation of push notifications for each platform can be found in the devtodev SDK integration manual in the ‘Help’ section.

Current campaigns

Here is the list of created push notification campaigns. You can filter them by status. Select one of the campaigns to view a more detailed report about it.

The report shows notification settings, such as campaign and audience info, statistics about campaign results, where:

Audience - the number of users who fit selected conditions and whose push tokens are known
Delivered - the number of delivered push notifications, which haven’t been declined by the push server. The most common reasons for rejection are that app is uninstalled or the token is not correct
Failures - the number of rejected push notifications (the difference between the number of audience and delivered push notifications)
Impressions - the number of impressions. This metric exists only for Android apps. The data come to us if the user opens the app or if it was opened at the time of receiving the push notification.
Clicks - the amount of clicks on a notification

Creating a new campaign

To create a new campaign click the Add new campaign button in the top right corner of a Campaign tab and follow the steps:

Campaign name
Campaign type
Target audience or Triggering conditions
Push-notification content
Push testing
Settings for campaign analysis
Schedule
Confirmation

Name your push campaign

Campaign types

Select the type of the campaign. There are two types of campaign: Simple campaign and Automated campaign

Choose Simple campaign to send a message to a specific segment of users or all users. You can send the push once or schedule it to a specific time, let’s say, every Thursday at 12:00. You can use it to notify all users about a new event in the game, or notify a specific segment about a new promotion available, etc.
Choose Automated campaign (Trigger campaign) if you want to send more personal push notifications or when you want to regularly remind users about the application, e.g. when a user has taken a certain action or has not opened the application for a while.

Target audience / Triggering conditions

When creating a Simple campaign, at the Target audience step you can select the delivery target audience. You can include all the users whose push tokens were received by devtodev system or target a specific audience by using filter conditions.

When creating a trigger campaign, at the Triggering conditions step, you must specify one of the triggers that will launch the campaign:

First open: specify the number of days/hours/minutes that have to pass after the application was first opened. For example, you can remind a new user about a time-limited starter pack 2 days after the app was first opened.

You can filter users by country of origin, language, device, application version, OS version:

Inactivity: specify the number of days since the user's last activity. You can also set specific filters to select users you want to message, for example, you can select the users who used to pay in the application, but were not active for two weeks.
Event: specify one or several events that the user must perform in order to receive a push notification. You can specify the number of days/hours/minutes that should elapse after the conditions of the trigger are met, or you can select Cancellation events. Cancellation events is a condition that prevents notifications from being dispatched if the condition is met within a specified delay period. For example, if you want to re-engage users who abandoned the cart, then as a trigger you can indicate opening a store and adding a specific product to the cart as a trigger and then select the product purchase event as a Cancellation event.

You can send push notification to every user who allows it or choose a particular segment.

Push-notification content

As for the customization of the content, you can add action, button and attachment (image, music or video). If you need to send a notification in different languages, you can click the Add button and customise each of them separately.

You can specify a text message for the default language, and also add other languages with different messages. When sending a notification, the user will receive a push message in the language specified in the user profile. If the language in the user profile is not among the added languages, the user will receive a notification in the default language.

Moreover, you can make the notification invisible.

Settings for campaign analysis

If you want to get a more detailed analysis on your push campaign, you can set the size of the control group. The control group consists of users who meet the conditions of the campaign, but do not receive push notifications. The control group is useful if you want to know the effectiveness of notifications or to compare the metric values of users who received them and those who didn’t.

For the push campaign you can also set a desired action that the user needs to take after receiving the notification. For example, if a push notification informs the user about new items in the store, then the desired action is to open the store screen; if the push informs the user about bargain price offers, then the desired action will be the purchase of the offer, etc.

Setting the target event will allow you to compare the conversion rate of the control group (users who do not receive the notification) with the conversion rate of the audience that receives the notification, it also allows you to compare the conversion rate of the users who opened the message and performed the target action with those who did not open it but still performed the target action.

Schedule

The next step is to schedule a campaign. Simple campaign. Here you can choose between two options - Send ASAP or Schedule sending time.

“Send ASAP” - the push notification will be sent once you complete the campaign creation process.
“Schedule sending time” - set specific parameters for sending the notification. For example, you can choose up to 30 calendar days when you would like to send the same push notification or you can select just one day if it is not a recurring message. Then you can select a delivery time and timezone: the push notification can be sent simultaneously to all users or according to the user's time zone.

A trigger campaign’s Schedule step offers the following settings:

Campaign activity where you need to specify the start and finish date of the campaign. To start the campaign you can choose between two options - Send ASAP or Schedule sending time. If you choose “Send ASAP” then the push notification will be sent once you complete the campaign creation process. As a finish date, you can choose between two options - Never or Schedule sending time.
You can tick the checkbox if you want to prohibit sending a delayed message after the campaign has expired.
In the Delivery time window, select the time interval for the delivery of your message. Specify whether or not the notification should be sent at the next allowed time window if the trigger condition is met outside the specified period.
Expiration: specify the period after which a push notification will be canceled if the device was unavailable. Usually, if possible, messages are delivered immediately, but if the user's device was disconnected from the Internet or turned off, the notification is saved on the server and is sent when it becomes possible. If you didn’t specify the message lifetime, the default settings will be applied. You can also limit the number of notifications sent per period, for example, send no more than one message in four days. For example, if you have specified the message’s lifetime for the iOS platform then APNs stores the notification and tries to deliver it at least once, repeating the attempt as needed until the specified date. If the value is 0, APNs attempts to deliver the notification only once and doesn’t store it. Apple documentation link. FCM messages. Requests that don't contain this field default to the maximum period of four weeks. More information. Windows Push Notification Services. By default, tile and badge notifications expire three days after being downloaded. When a notification expires, the content is removed from the tile or queue and is no longer shown to the user. More information here.

Copying an existing campaign

You easily can create a copy of an existing push campaign. Open the campaign that you would like to duplicate and click on the Copy icon in the upper right corner.

This will copy all of the settings of this campaign, you just need to give it a new name and save.

Push notification report (Simple campaign)

The Advanced report is made up of several widgets:

Campaign info - general information about the sent message: title, alert, action, sound, audience filter and etc.
Campaign statistics
Monetization effect
User structure
User return
Conversion funnel

Based on the widget data you can divide the audience of the campaign into the following segments:

Number of users in the control group, if you specified it when configuring the campaign
Number of users who received the push notification but did not open it
Number of users who received and opened the push notification

These segments will allow you to evaluate the effectiveness of your message. All metrics for evaluating the effectiveness of notifications are measured 7 days before the start of the advertising campaign and 7 days after the receipt of the notification.

Campaign statistics. Audience is the number of users who entered the segment when creating the campaign. The table contains a Revenue value for each segment of the audience, seven days before the start of the campaign and seven days after the start to assess the impact of push notifications on user behavior. Conversion to action shows the percentage of users that have executed the desired action. Monetization effect. You can assess how the campaign has affected metrics such as ARPPU, ARPU, Avg. ARPDAU, Conversion to 1st payment, Conversion to 2nd payment. Based on the metric values you can also build a graph where the red line marks the start of the campaign. User structure. You can analyze the following metrics: Users, Average Session Length, ARPPU, ARPU, Revenue, Group audiences by Country, Paying capacity, days from Install. User return. The widget shows the number of users by their inactivity periods in the application and the number of re-engaged users (within 7 days after the campaign). Conversion Funnels. If you specified the desired action while configuring the campaign, the funnel will consist of three steps.The first step of the funnel contains the event about the campaign start, the second step is opening the push notification event. The third step is the event you specified when configuring your advertising campaign. If you want to add another step or change the current steps, you can go to the Funnel report.

Push notification report (Automated campaign)

Statistics

In the trigger campaign report you can find information about the campaign settings, its status, widgets with statistics. You can also cancel sending push notifications for this campaign or restart it:

Above the report, you can specify a date range for which you want to display data. A trigger push campaign report has three tabs:

Base report - general information about the campaign.
Advanced report - information about the number of users who re-engage after receiving notifications, information about the effectiveness of push notifications and conversion funnels if you specified a conversion event when setting up the campaign.
Efficiency report - on the tab you can see how the campaign affected the monetization metrics.

Each tab of the tabs contains general information about the campaign:

Average number of campaign notifications per user Average number of all push notifications received by campaign audience. This information can be useful in determining what proportion of notifications a user receives during a given campaign. For example, during this campaign, the user only receives push notifications, in which case you can diversify notifications for this audience. Average time between push notification campaigns. This metric helps you measure how often users receive notifications from a given campaign. Number of delivered push notifications that were not opened Number of errors

In the “Number of days for analysis after the push notification has been sent out” drop-down list below, you can specify your push notification’s period of validity from 1 to 7 days. All metrics for evaluating notification effectiveness will be calculated depending on the specified period. For example, if you chose a seven-day period, then in order to evaluate the effectiveness of the campaign, the metrics will be calculated for 7 days before the start of the ad campaign and for 7 days after the push notification has been received. A similar timeframe will be set for the marketing funnel stages.

In the next "Display statistics for the * push notification" drop-down list, you can select the number of the notification “wave” for which you want to view statistics.

Base report tab

The widget displays the number of sent, opened push notifications, and the conversion from sending to opening. In the controls, you can choose the push notification on which you want to view statistics, for example, on the second or on all at once. You can also choose the count parameter: the number of push notifications or the number of unique users who received these messages.

Advanced report tab

User return. If the “Inactivity” trigger was added when setting up the campaign, this report will contain the Return widget. The widget displays the number of users with a breakdown by the time since their last engagement with the application and the number of users re-engaged due to the campaign. This widget allows you to estimate the optimum time for re-engaging lapsed users. Conversion Funnels. This report contains a funnel widget if you specified the desired action when setting up the campaign. The funnel shows the sequence of user actions and allows you to assess at what stage users “drop out” and do not reach the desired action point. The funnel has three stages. The first stage of the funnel contains the event about the sending of the campaign, the second stage is the push notification open event, and the third stage is the event that you specified when setting up the ad campaign. In case you want to add another stage or change the current stages, you can open the Funnel report The effectiveness of sending push notifications. The widget contains information on the number of push notifications sent in the first wave, the number of notifications opened, the number of push notifications sent and opened in the second wave, and so on. Using the widget, you can assess the effectiveness of the initial and subsequent notifications sent during this campaign. For example, it is possible that users open the first push notification, but don’t open the subsequent ones. In this case, sending a reminder that does not re-engage the player is useless. It might be worth changing the content, the call to action in subsequent messages first.

Efficiency report tab

Monetization effect. You can evaluate the impact of the campaign on such metrics as ARPPU, ARPU, Avg. ARPDAU, Conversion to 1st payment, Conversion to 2nd payment. You can also put these metrics into graph form and display them below the table (the red line stands for the start of the campaign). User structure. You can analyze the following metrics: users, Average Session Length, ARPPU, ARPU, Revenue, segment the audience by Country, Paying capacity, Days from install.

Errors

In some cases, you can encounter errors that occurred while sending push-notifications to the specified campaign in the Status column.

Below you can find examples of possible errors and their meaning.

Android

IOS

Windows

Android Notifications

How to create push notification for Android

Visible notifications

Visible notifications is the most common type of notifications. Users receive a message, which is displayed in the notification center of their devices.

Languages

It is possible to sent notifications in several languages to make them more accessible to users from different countries. When the language used on a device is specified among languages of the campaign, the notification is sent in this language. In case there is no device language among languages of the campaign, the message is sent in the language that is specified as a default language.

To add or remove a language press the button with a ‘+’ sign.

First, you need to choose the language that will be used by default. In most cases it is English.

Each language is presented in a form of a tab. When switching between tabs, please fill the required fields with translations. Translations are necessary for such fields as ‘Title’, ‘Text’ and ‘Share text’ (if it is used). The rest of notification settings are general and do not depend on translations.

Title

A short line that describes the purpose of notification.

Notification titles should:

Be under 30 characters long
Contain the most important information
Exclude the app's name, which already appears in the header

Text

The main message that is presented in a push notification.

The text of notification should:

Not exceed 40 characters
Avoid repeating the title

App icon / small icon

The app icon is a small two-dimensional representation of your app's identity. It appears in monochrome in the status bar. If your app sends a wide range of notifications, you may replace your app's identity icon with a symbol that reflects the type of content. For example, Google now uses a cloud icon for notifications about weather.

The source of image can only be the resource of application (its name).

Small icon background

Depending on the version of Android, this function either fills the background, on which the small icon is displayed, with the specified color (Android M), or colors the small icon, app’s name and texts of actions displayed in notifications (Android N).

Large icon

In Android N, the large icon is meant only for specific situations, in which the image meaningfully reinforces the notification's content, including:

Communication from another person, such as the image of someone sending a message
The source of content if it's different from the app that sends the notification, such as the logo from a YouTube channel to which the user is subscribed
Meaningful symbols about the notification, such as an arrow symbol for driving directions
Large icons should have a round shape when showing a person and square in all other cases

The source of image can be the resource of app (its name) and the URL to the file on the web.

Android allows to use images of large size as large icons. However, in case the image will have to be uploaded by the device from the internet, it is better to use images with resolution that provides a good quality of image, but is as small in size as possible.

We recommend to use square images that don’t exceed 192x192 resolution.

Images with different aspect ratio are scaled proportionally along the long side to the display area size.

Big picture

Use this template when your notification contains a picture. The large icon offers a thumbnail of the picture, and the user can get a bigger preview by expanding the notification.

The source of image can only be the URL to the file on the web.

Android allows to use images of large size as a big picture. However the device will have to upload the file from the internet, therefore it is better to use images with resolution that provides a good quality of image, but is as small in size as possible.

We recommend to use images with 2:1 ratio that don’t exceed 768х384 resolution.

If you want the image to be fully displayed in the message, the proportion of the aspect ratio of the image should be 2:1 (width:length). Otherwise, the image will be scaled to the size of the notification display area and centercropped to the ratio 2:1.

Sound

Тhe name of a sound file in the application bundle (resource name). The sound in this file is played as an alert. If the sound file doesn’t exist or “default” is specified as a value, the default alert sound is played. The audio must be in one of the audio data formats that are compatible with the system sounds. If the option is switched off, the notification comes silently.

LED color

You can specify the color of LED that will notify users about an unread message. The device will display the color as close as possible to the one you specified. Unfortunately, not all Android devices have LED. Also, users can block the use of LED.

Collapse key

Notifications are not collapsible by default.

If multiple messages are sent with this key, the most recent message will suppress all previous unread messages with the same key.

Collapsible messages are a better choice from a performance standpoint provided your application doesn't need to use non-collapsible messages. However, if you use collapsible messages, remember that GCM only allows a maximum of 4 different collapse keys to be used by the GCM connection server per registration token at any given time. You must not exceed this number, or it can cause unpredictable consequences.

Parameters

You can pass custom parameters with messages and use them within the app. For instance, you can activate advertising campaign or any other functionality for a user who has received this message.

With this function you will be able to send any data, the processing of which can be pre-programmed, in a key-value format to the app. For example, it is possible to activate a promotion or perform any other activity within the app.

Interaction

Action

The action after a click on the body of a notification. By default, the click opens an app.

It is possible to perform the following actions:

Home screen - this is the default behavior when a user taps on a push notification. It opens app’s home screen
Deep link - directs a user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser or any valid device-level URL, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with the push notification. In case of selecting this action, don’t forget to specify translations of share texts into all languages used in your push campaign

Buttons

Before choosing the template of notification buttons, it is necessary to select the language of the message, which will be used by default (usually it is English).

Accessible button templates can be found in the table with button templates or directly in the interface.

After you have selected the template, you need to set the action of the button. We do not recommend to use actions that contradict the text on the button. Also, the action of the button should not duplicate the action that is used after tapping on the notification body.

In case you are not satisfied with the template you have chosen, you can replace (‘Set another template’ button) or delete it.

The set of accessible actions:

Home screen - this is the default behavior when a user taps on a push notification. It opens app’s home screen
Deep link - directs the user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser, or any valid device-level URL, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with the push notification. In case of selecting this action, don’t forget to specify translations of share texts into all languages used in your push campaign.
Dismiss message - dismiss the message, without taking the user into the app

Invisible notifications

Invisible notifications can be used in case you need to send some command to an app and make it invisible to users. Users will not see the message and will not be notified by a special notification signal. This kind of notification is aimed at the app, not users.

Parameters used for sending the data to the app are the same as described in the section about visible notifications.

Invisible notifications can use ‘Collapse key’ and ‘Delay while idle’ settings.

IOS Notifications

How to create push notification for iOS

Visible notifications

Visible notifications is the most common type of notifications. Users receive a message, which is displayed in the notification center of their devices.

Languages

To add or remove a language press the button with a ‘+’ sign.

First, you need to choose the language that will be used by default. In most cases it is English.

Title

A short line that describes the purpose of notification. Apple Watch displays this line as a part of notification interface. This line is displayed only briefly and should be written so that it can be understood quickly. This key was added in iOS 8.2.

Alert/body

The text of the alert message.

As long as the title and text are sent in a Unicode format, you can use texts and emoji supported by this format to diversify the way your notifications look. is here. We recommend you to test how messages with emoji are displayed on a device before sending them to wide audiences.

Badge

Optional. The number to be displayed as the badge of the app icon. If this property is absent, the badge is not changed. To remove the badge, set the value of this property to 0.

Sound

The value of this field is the name of a sound file in your app’s main bundle or in the Library/Sounds folder of your app’s data container. The sound in this file is played as an alert. If the sound file cannot be found or if you specify “default” as the value, the system plays the default alert sound.

Attachment

Available from devtodev iOS SDK 1.9, Cordova SDK 1.9, Unity SDK 2.3, UE4 SDK 1.9, Air SDK 1.8

Attachment delivery is available from iOS 10.

It is possible to attach image, video, audio, and GIF to your notification. Specify the type of an attachment ("image", "audio" or "video") and URL that leads to a media file. Please note that iOS uses only “https” protocol.

The following file formats can be used in attachments: "jpg", "jpeg", "png", "gif", "aif", "aiff", "mp3”, "wav","mpg", "mpeg", "mp4", "m4a", "avi".

The maximum file size that can be used in attachments is 5MB for audio files, 10MB for images and animation, 50MB for videos.

When using this option, keep in mind that attachments will not be displayed on some old devices. So create your messages in a way that they are informative even if the attachment is not displayed.

We recommend to optimize media files so that they are of a good quality and the minimum size. There is no point in sending images, which are more than 750 pixels wide.

If you use ad video, try to make it short and not use resolution formats above 720p (576p will be enough) with low frame frequency (24-25 frames per second.)

Images and videos are scaled proportionally along the width of notification display area.

Collapse key

Multiple notifications with the same collapse identifier are displayed to users as a single notification.

Parameters

You can pass custom parameters with messages and use them within an app. For instance, you can activate advertising campaign or any other functionality for a user who has received this message.

Interaction

Action

The action after a click on the body of a notification. By default, a click opens an app. It is possible to perform the following actions:

Home screen - this is the default behavior when a user taps on a push notification. It opens app’s home screen
Deep link - directs the user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser or any valid device-level URL, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with your push notification. In case of selecting this action, don’t forget to specify translations of share texts into all languages used in your push campaign

Buttons

Before choosing the template of notification buttons, it is necessary to select the language of the message, which will be used by default (usually it is English).

Accessible button templates can be found in the table with button templates or directly in the interface.

After you have selected the template, you need to set the action of the button. We do not recommend to use actions that contradict the text on the button. Templates, which have a ‘Dismiss notification’ label, cannot have any other action except for closing the notification. In case you are not satisfied with the template you have chosen, you can replace (‘Set another template’ button) or delete it.

The set of accessible actions:

Home screen - this is the default behavior when a user taps on a push notification. It opens app’s home screen
Deep link - directs the user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser or any valid device-level URL, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with your push notification. In case of selecting this action, don’t forget to specify the translations of share texts into all languages used in your push campaign

Invisible notifications

Parameters used for sending the data to the app are the same as described in the section about visible notifications.

Content available

Provide this checkbox to indicate that new content is available. This is used to support newsstand apps and background content downloads. Newsstand apps are guaranteed to be able to receive at least one push with this key per 24-hour window.

Windows Notifications

How to create push notification for Windows

Let's have a look how can you add the message on Step5 for Windows.

Firstly, you need to select the notification type. For Windows you can make a choice between Toast, Tile and Raw notification.

Toast notification

Languages

It is possible to sent notifications in several languages to make them more accessible to users from different countries. When the language used on a device is specified among languages of the campaign, the notification will be sent in this language. In case there is no device language among languages of the campaign, the message will be sent in the language that is specified as a default language.

To add or remove a language press the button with a ‘+’ sign.

Firstly, you need to choose a language that will be used by default. In most cases it is English.

Title

Heading that appears above the notification text in Windows notification area. Optional.

Text

The main message that is displayed in your push notification.

Icon

To replace the application icon (that shows up in the top left corner of the toast), use the URL or the resource name.

In Windows 10 the image is expressed using the URI of the image source, using one of the following protocol handlers:

A web-based image: http:// or https://
An image included in the app package: ms-appx:///
An image saved to local storage: ms-appdata:///local/
A local image (Only supported for desktop apps.): file://

Sound

A media file to be played instead of a default sound. If the option is not used, a notification comes silently. This property can have one of the following string values:

On a mobile platform, this property can also contain the path to a local audio file, with one of the following prefixes:

ms-appx:///
ms-appdata:///

Parameters

You can pass custom parameters with messages and use them within an app. For instance, you can activate advertising campaign or any other functionality for a user who has received this message.

Interaction

Available only for Windows 10 and WP 10.

Actions and Buttons options are available in devtodev SDK version 1.9 or higher.

Action

The action after a click on the body of a notification. By default, a click opens an app. It is possible to perform the following actions:

Home screen - this is the default behavior when a user taps on a push notification. Opens app’s home screen
Deep link - directs the user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser or any valid device-level URL, such as Windows Store or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with your push notification. In case of selecting this action, don’t forget to specify the translations of share texts into all languages used in your push campaign.

Buttons

Before choosing the template of notification buttons, it is necessary to select the language of the message, which will be used by default (usually it is English).

Accessible button templates can be found in the table with button templates or directly in the interface.

After you have selected a template, you need to set an action of the button. We do not recommend to use actions that contradict the text on the button. Also, the action of the button should not duplicate the action that is used after tapping on the notification body.

In case you are not satisfied with the template you have chosen, you can replace (‘Set another template’ button) or delete it.

The set of accessible actions:

Home screen - this is the default behavior when a user taps on a push notification. Opens app’s home screen
Deep link - directs a user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser or any valid device-level URI, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with the push notification. In case of selecting this action, don’t forget to specify translations of share texts into all languages used in your push campaign
Dismiss message - dismiss the message, without taking the user into the app

Raw notification

RAW notifications are available on devtodev SDK version 1.9 or higher.

Raw notifications can be used in case you need to send some command to an app and make it invisible to users. Users will not see the message and will not be notified by a special notification signal. This kind of notification is aimed at the app, not users.

Parameters used for sending the data to the app are the same as described in the section about toast notifications.

Tile

The tile template is selected automatically based on the content specified in tile settings.

Text 1

The first line of your tile.

Header

Check ‘Header’ attribute to mark the ‘Text 1’ field as a heading to show it larger.

Text 2, Text 3, Text 4

The second, the third and the fourth lines of the tile.

Image

Application-relative or Internet URI of the image.

Example:

"red.jpg" (if the image is stored in the app’s installation directory or local storage folder)
"http://my.domain.com/img/red.jpg" (for Internet URIs)

We recommend to use images with 336 x 336 pixels resolution.

Important Note:

If you need to use remote Internet URIs for Tile images, you must take the following steps:

Ensure the remote image file size is less than 150 KB
Ensure the image can be downloaded in 60 seconds or less

Button Templates

Table with button templates

The text on the buttons (which are on the list of templates) is translated into Arabic, Chinese, Czech, Danish, Dutch, English, Finnish, French, German, Hungarian, Indonesian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Slovak, Spanish, Swedish, Thai, Turkish, Vietnamese, Indonesian languages. The text is displayed to users individually depending on the locale of a device. In case the user uses another language, texts of buttons will be shown in the default language.

Android Notifications

How to create push notification for Android

Visible notifications

Visible notifications is the most common type of notifications. Users receive a message, which is displayed in the notification center of their devices.

Languages

To add or remove a language press the button with a ‘+’ sign.

First, you need to choose the language that will be used by default. In most cases it is English.

Title

A short line that describes the purpose of notification.

Notification titles should:

Be under 30 characters long
Contain the most important information
Exclude the app's name, which already appears in the header

Text

The main message that is presented in a push notification.

The text of notification should:

Not exceed 40 characters
Avoid repeating the title

App icon / small icon

The source of image can only be the resource of application (its name).

Small icon background

Large icon

In Android N, the large icon is meant only for specific situations, in which the image meaningfully reinforces the notification's content, including:

Communication from another person, such as the image of someone sending a message
The source of content if it's different from the app that sends the notification, such as the logo from a YouTube channel to which the user is subscribed
Meaningful symbols about the notification, such as an arrow symbol for driving directions
Large icons should have a round shape when showing a person and square in all other cases

The source of image can be the resource of app (its name) and the URL to the file on the web.

We recommend to use square images that don’t exceed 192x192 resolution.

Images with different aspect ratio are scaled proportionally along the long side to the display area size.

Big picture

Use this template when your notification contains a picture. The large icon offers a thumbnail of the picture, and the user can get a bigger preview by expanding the notification.

The source of image can only be the URL to the file on the web.

We recommend to use images with 2:1 ratio that don’t exceed 768х384 resolution.

Sound

LED color

Collapse key

Notifications are not collapsible by default.

If multiple messages are sent with this key, the most recent message will suppress all previous unread messages with the same key.

Parameters

You can pass custom parameters with messages and use them within the app. For instance, you can activate advertising campaign or any other functionality for a user who has received this message.

Interaction

Action

The action after a click on the body of a notification. By default, the click opens an app.

It is possible to perform the following actions:

Home screen - this is the default behavior when a user taps on a push notification. It opens app’s home screen
Deep link - directs a user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser or any valid device-level URL, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with the push notification. In case of selecting this action, don’t forget to specify translations of share texts into all languages used in your push campaign

Buttons

Before choosing the template of notification buttons, it is necessary to select the language of the message, which will be used by default (usually it is English).

Accessible button templates can be found in the table with button templates or directly in the interface.

In case you are not satisfied with the template you have chosen, you can replace (‘Set another template’ button) or delete it.

The set of accessible actions:

Home screen - this is the default behavior when a user taps on a push notification. It opens app’s home screen
Deep link - directs the user to a specific resource either within your app or on the web
Web page - opens a web page in a mobile browser, or any valid device-level URL, such as Google Play or app protocol links
Share - the ‘Share’ action drives users to share your message when they interact with the push notification. In case of selecting this action, don’t forget to specify translations of share texts into all languages used in your push campaign.
Dismiss message - dismiss the message, without taking the user into the app

Invisible notifications

Parameters used for sending the data to the app are the same as described in the section about visible notifications.

Invisible notifications can use ‘Collapse key’ and ‘Delay while idle’ settings.

Push Notifications

This section allows you to create and manage push notifications campaigns.

If push notifications are not connected
Current campaigns
Creating a new campaign
Push notification report (Simple campaign)
Push notification report (Automated campaign)

If push notifications are not connected

To connect the push notifications service to the app you need to:

Integrate devtodev SDK and activate push notifications during integration
Fill in the required information in the push notifications panel in the Integration section of the application settings

Please note that access to the Integration section is restricted by user access rights.

Current campaigns

Here is the list of created push notification campaigns. You can filter them by status. Select one of the campaigns to view a more detailed report about it.

The report shows notification settings, such as campaign and audience info, statistics about campaign results, where:

Audience - the number of users who fit selected conditions and whose push tokens are known
Delivered - the number of delivered push notifications, which haven’t been declined by the push server. The most common reasons for rejection are that app is uninstalled or the token is not correct
Failures - the number of rejected push notifications (the difference between the number of audience and delivered push notifications)
Impressions - the number of impressions. This metric exists only for Android apps. The data come to us if the user opens the app or if it was opened at the time of receiving the push notification.
Clicks - the amount of clicks on a notification

Creating a new campaign

To create a new campaign click the Add new campaign button in the top right corner of a Campaign tab and follow the steps:

Campaign name
Campaign type
Target audience or Triggering conditions
Push-notification content
Push testing
Settings for campaign analysis
Schedule
Confirmation

Name your push campaign

Campaign types

Select the type of the campaign. There are two types of campaign: Simple campaign and Automated campaign

Choose Simple campaign to send a message to a specific segment of users or all users. You can send the push once or schedule it to a specific time, let’s say, every Thursday at 12:00. You can use it to notify all users about a new event in the game, or notify a specific segment about a new promotion available, etc.
Choose Automated campaign (Trigger campaign) if you want to send more personal push notifications or when you want to regularly remind users about the application, e.g. when a user has taken a certain action or has not opened the application for a while.

Target audience / Triggering conditions

When creating a trigger campaign, at the Triggering conditions step, you must specify one of the triggers that will launch the campaign:

First open: specify the number of days/hours/minutes that have to pass after the application was first opened. For example, you can remind a new user about a time-limited starter pack 2 days after the app was first opened.

You can filter users by country of origin, language, device, application version, OS version:

Inactivity: specify the number of days since the user's last activity. You can also set specific filters to select users you want to message, for example, you can select the users who used to pay in the application, but were not active for two weeks.
Event: specify one or several events that the user must perform in order to receive a push notification. You can specify the number of days/hours/minutes that should elapse after the conditions of the trigger are met, or you can select Cancellation events. Cancellation events is a condition that prevents notifications from being dispatched if the condition is met within a specified delay period. For example, if you want to re-engage users who abandoned the cart, then as a trigger you can indicate opening a store and adding a specific product to the cart as a trigger and then select the product purchase event as a Cancellation event.

You can send push notification to every user who allows it or choose a particular segment.

Push-notification content

Moreover, you can make the notification invisible.

Settings for campaign analysis

Schedule

The next step is to schedule a campaign. Simple campaign. Here you can choose between two options - Send ASAP or Schedule sending time.

“Send ASAP” - the push notification will be sent once you complete the campaign creation process.
“Schedule sending time” - set specific parameters for sending the notification. For example, you can choose up to 30 calendar days when you would like to send the same push notification or you can select just one day if it is not a recurring message. Then you can select a delivery time and timezone: the push notification can be sent simultaneously to all users or according to the user's time zone.

A trigger campaign’s Schedule step offers the following settings:

Campaign activity where you need to specify the start and finish date of the campaign. To start the campaign you can choose between two options - Send ASAP or Schedule sending time. If you choose “Send ASAP” then the push notification will be sent once you complete the campaign creation process. As a finish date, you can choose between two options - Never or Schedule sending time.
You can tick the checkbox if you want to prohibit sending a delayed message after the campaign has expired.
In the Delivery time window, select the time interval for the delivery of your message. Specify whether or not the notification should be sent at the next allowed time window if the trigger condition is met outside the specified period.
Expiration: specify the period after which a push notification will be canceled if the device was unavailable. Usually, if possible, messages are delivered immediately, but if the user's device was disconnected from the Internet or turned off, the notification is saved on the server and is sent when it becomes possible. If you didn’t specify the message lifetime, the default settings will be applied. You can also limit the number of notifications sent per period, for example, send no more than one message in four days. For example, if you have specified the message’s lifetime for the iOS platform then APNs stores the notification and tries to deliver it at least once, repeating the attempt as needed until the specified date. If the value is 0, APNs attempts to deliver the notification only once and doesn’t store it. Apple documentation link. FCM messages. Requests that don't contain this field default to the maximum period of four weeks. More information. Windows Push Notification Services. By default, tile and badge notifications expire three days after being downloaded. When a notification expires, the content is removed from the tile or queue and is no longer shown to the user. More information here.

Copying an existing campaign

You easily can create a copy of an existing push campaign. Open the campaign that you would like to duplicate and click on the Copy icon in the upper right corner.

This will copy all of the settings of this campaign, you just need to give it a new name and save.

Push notification report (Simple campaign)

The Advanced report is made up of several widgets:

Campaign info - general information about the sent message: title, alert, action, sound, audience filter and etc.
Campaign statistics
Monetization effect
User structure
User return
Conversion funnel

Based on the widget data you can divide the audience of the campaign into the following segments:

Number of users in the control group, if you specified it when configuring the campaign
Number of users who received the push notification but did not open it
Number of users who received and opened the push notification

Push notification report (Automated campaign)

Statistics

Above the report, you can specify a date range for which you want to display data. A trigger push campaign report has three tabs:

Base report - general information about the campaign.
Advanced report - information about the number of users who re-engage after receiving notifications, information about the effectiveness of push notifications and conversion funnels if you specified a conversion event when setting up the campaign.
Efficiency report - on the tab you can see how the campaign affected the monetization metrics.

Each tab of the tabs contains general information about the campaign:

In the next "Display statistics for the * push notification" drop-down list, you can select the number of the notification “wave” for which you want to view statistics.