ÃÛ¶¹ÊÓƵ

From the Marketing activities window, create a new marketing activity.

Note that a single push notification can also be created from a campaign or from the ÃÛ¶¹ÊÓƵ Campaign home page.

You can also use a push notification delivery activity in a workflow. This activity is presented in the Push notification delivery section.

Select Push notification.

Select a template.

By default, you can select one of the following two templates:

• Send push to Campaign profiles: use this template to target the ÃÛ¶¹ÊÓƵ Campaign CRM profiles who have subscribed to your mobile application and have opted in to receive push notifications. You can insert personalization fields into your push notification, such as the recipient’s first name.
• Send push to app subscribers: use this template to send a push notification to all known and anonymous mobile application users who have opted in to receive notifications from your application. You can personalize these messages with data collected from your mobile application.

You can also select multilingual templates. For more information, refer to Creating a multilingual push notification.

For more on templates, refer to the Managing templates section.

Enter your push notification properties and select your mobile app in the Associate a Mobile App to a delivery field.

Please note that the drop-down will display both SDK V4 and Experience Platform SDK applications.

You can link the push notification to a campaign. To do this, select it from the campaigns that have already been created.

In the following screen, you can specify an audience, for example all of your VIP customers who subscribed to a specific mobile application. For more on this, see Creating audiences.

Your audience will be automatically filtered based on the mobile application selected in the previous step.

You can now customize your push notification. First, choose the message style: Alert/Message/Badge or Silent push. The push notification types are described in the About push notifications section.

Edit the content of your push notification and define the advanced options. See Customizing a push notification.

The push notification content and options configured here are passed to your mobile app in the form of a payload. The detailed structure of the payload is described in the Understanding Campaign Standard push notifications payload structure technote.

Click Create.

Before sending the notification, you can test it with test profiles and then see exactly what your recipients will see before sending the delivery. Select Audiences from your delivery summary and click the Test profiles tab.

For more on sending tests, refer to Test profiles.

Select your test profiles and click Preview to display the notification: content is personalized with the test profile data.

Check the push notification layout on different devices: select iPhone, Android phone, iPad or Android tablet to preview rendering.

The Estimated Payload Size is an estimate based on test profile data. Actual payload size may vary. The limit of the message is 4KB.

Click Prepare to compute the target and generate the notifications.

Once the preparation has finished successfully, the Deployment window presents the following KPIs: Target and To deliver. Note that the To deliver count is lower than the Targeted one due to exclusions which can be viewed by clicking button at the bottom of the Deployment window.

In the Exclusion logs tab, you can find the list of all the messages excluded from the target sent and the reason behind this exclusion.

Here, we can see that one of our mobile app subscribers was excluded because the address was on the denylist and the other subscribers because the profile was a duplicate.

Click the Exclusion causes tab to display the volume of excluded messages.

You can now click Confirm to start sending push notifications.

Check the status of your delivery through the message dashboard and logs. For more on this, see Sending messages and Delivery logs.

In this example, the message dashboard displays that ÃÛ¶¹ÊÓƵ Campaign attempted to send two push notifications: one was delivered successfully to the device and another one failed. To know why the delivery has errors, click the button at the bottom of the Deployment window.

From the Deployment window, click the Sending logs tab to access the list of sent push notifications and their statuses. For this delivery, one push notification was successfully sent whereas the other failed due to a bad device token. This subscriber will then be added to the denylist from further deliveries.