Use Cases for MobilePush

These use cases describe MobilePush functionality and the reach of your messages. For example, use lists and tags to segment your audience and send to contacts with the same attribute values.

Marketing Cloud Engagement has several products available. Each use case has suggestions for which combination of products are required in order to implement the solution for a specific use case. However, for all use cases described in this document, MobilePush will need to be configured for your account.

• Implement Tags in MobilePush
  To help better segment your contacts into more precise audiences, use tags in MobilePush.
• Include Only Opted-in Contacts in a Filtered List
  Just because a contact is active doesn’t mean that they have opted in to receive MobilePush notifications.
• Set the Subscriber Key or Contact Key
  Contact key, also known as subscriber key, is the unique identifier used to aggregate a contact’s devices in Marketing Cloud Engagement. Set the contact key to a specific value provided by your customer or to another unique identifier for the contact. You can use a mobile number, customer number, Salesforce ContactID, or another value.
• Use Exclusion Lists and Data Extensions Lists in MobilePush
  To exclude certain subscribers from receiving push notifications from MobilePush, use an exclusion list.
• Use the MobilePush SDK to Send a Location Message to Selected MobilePush Users
  MobilePush can trigger location messages when users enter or exit a geofence or come within range of a beacon. Choosing an existing audience list or data extension can't be done in Marketing Cloud Engagement, so you must use the SDK to segment location message recipients.
• Use Multiple Providers for Push Notifications
  Implementing a push notification provider’s SDK in addition to the MobilePush SDK is not recommended. While multiple push SDKs can be integrated into a single app, this practice can cause issues. Results are not guaranteed.
• Provide a Dynamic Image in a Rich Push Message
  Rich push notifications include an image. For example, you can send your contact an abandoned cart push notification that contains an image of the item left in their cart to entice them to complete the purchase. You can personalize the image that your contact receives by using a recurring send, a data extension that tracks the abandoned cart items, and AMPscript to populate the push notification’s image URL.
• Replace Inbox and Deleted Contacts
  When you send an Inbox message, you can use the Replace Inbox feature to overwrite an existing Inbox message on the user’s device. Here’s an example of what happens when a user is deleted or removed from the source audience in between message sends.