Identifying Opt-In Preferences for In-App Messages in Salesforce MobileConnect

Understanding how to manage and identify opt-in preferences for in-app messages is crucial for effective mobile marketing. Based on a recent case I opened with Salesforce support, here are some insights and best practices for managing your audience for push and in-app messages. 

Building Mobile Filtered Lists for Push Messages 

To identify contacts who are opted in to receive push messages, you can create a mobile-filtered list with the following criteria: 

  • Status: Active 
  • Device ID: Not null 
  • Opt-In Status: Opted In 

Identifying Contacts for In-App Messages 

One common question is how to identify contacts who have opted out of push messages but can still receive in-app messages, or vice versa. Here’s what I found:

Opt-In Status for In-App Messages 

Salesforce targets in-app and inbox messages to all Device IDs, regardless of their opt-in status. As long as the Device IDs are valid, in-app and inbox messages will be sent. If Apple Push Notification Service (APNS) or Google indicates that a Device ID is no longer valid (e.g., if the token has expired), Salesforce will stop sending in-app and inbox messages to that Device ID. 

Consent for In-App Messages Consent is not required to send in-app or inbox messages to contacts. This means that even if a contact has opted out of push messages, they can still receive in-app messages as long as their Device ID is valid. For more details, refer to the Salesforce Consent Management documentation.

Ensuring Valid Device IDs 

To ensure you are not targeting invalid devices, you can use the following criteria: 

  • Device ID: Not null 
  • Status: Active 

However, to specifically identify the last active device, you can refer to discussions on Salesforce Stack Exchange, which provide detailed methods for retrieving the last active device. 

https://salesforce.stackexchange.com/questions/289942/mobile-push-demographics-data-shown-multiple-device-id-for-one-contact-in-sfmc?newreg=46f148ce5a9a43138f56aced4a785013

https://salesforce.stackexchange.com/questions/174179/attributes-in-pushaddress-and-pushtag-data-views

Additional Insights 

Handling Inactive Device IDs 

If a Device ID becomes inactive (e.g., due to token expiration), Salesforce will stop sending messages to it. It’s important to regularly update and validate your Device IDs to ensure your messages reach active devices. 

Field Indicators for In-App Messages 

Currently, there is no specific field or indicator that shows opt-in status exclusively for in-app messages. The general practice is to target all valid Device IDs for in-app messaging, regardless of their push message opt-in status. 

By understanding these nuances, you can better manage your mobile marketing campaigns and ensure your messages reach the right audience. If you have any further questions or need more detailed guidance, feel free to reach out!

Comments