MobilePush and Journey Builder

To use MobilePush with Journey Builder, complete these prerequisites and review the personalization considerations.

• Confirm that MobilePush, Content Builder, and Journey Builder are enabled for your Marketing Cloud Engagement account. If they aren’t, contact your account executive.
• If you don’t see the push notification canvas activity in Journey Builder, your Salesforce admin must give you permission. Enable the permission in the Installed Packages section under Administration and Account in Marketing Cloud Engagement.

Note For messages created after the March 2020 release, the Activity Name replaces the Reporting ID in Journey Builder Push and In-App activities. This update allows for easier identification of your message in reports and data extracts.

Note When contacts delete your app or disable push notifications in their mobile device’s settings, they don’t receive Journey Builder push notifications.

Personalization Considerations

In Journey Builder, you can use Journey Builder entry source attributes to personalize your push messages. Journey Builder first attempts to pull the attribute value from the Journey Builder entry source. If no value is found, Journey Builder attempts to pull the attribute value from the contact record in the MobilePush demographics table.

Note When you use a data extension as an entry source in Journey Builder, you can add personalization strings in the subject line or CloudPage.

• Send Push Notifications with Journey Builder
  You can send push notifications and inbox messages in Journey Builder to create a sequence of messages, such as a welcome experience or an abandoned cart reminder.