Understanding the Challenge

When using MobilePush in SFMC, contacts with multiple devices can pose a challenge, especially if each device has different tags and opt-in preferences. The current MobilePush functionality sends notifications to all devices owned by a contact, regardless of the tags assigned to each device.

This can lead to a situation where a contact receives notifications on multiple devices, even if they have opted out of certain messages on specific devices. To overcome this challenge, it is essential to find a way to target specific devices with notifications.

Exploring Possible Solutions

One possible solution is to create separate contact records for each device, allowing for more granular control over notification targeting. However, this approach can be complex and may require significant changes to the existing contact management system.

Another approach is to utilize a third-party vendor to integrate push event data for segmentation and message personalization. This can provide more flexibility and control over notification targeting, but may require additional investment and resources.

Implementing a Custom Solution

To implement a custom solution, consider the following steps:

example.txt

// Create a new contact record for each device
// Assign unique tags to each device
// Use the MobilePush API to send notifications to specific devices

It is also important to note that the push SDK now supports event logging, which can provide valuable insights into notification engagement and behavior.

The root cause of this challenge is the current MobilePush functionality, which sends notifications to all devices owned by a contact, regardless of the tags assigned to each device.

Best Practices and Recommendations

To ensure effective targeting of specific devices with notifications, consider the following best practices and recommendations:

Checklist for Targeting Specific Devices

• Create separate contact records for each device, if possible
• Utilize a third-party vendor to integrate push event data for segmentation and message personalization
• Use the MobilePush API to send notifications to specific devices
• Leverage the push SDK event logging feature to gain insights into notification engagement and behavior
• Regularly review and update contact records and device tags to ensure accuracy and effectiveness

Frequently Asked Questions

What is the current MobilePush functionality?

The current MobilePush functionality sends notifications to all devices owned by a contact, regardless of the tags assigned to each device.

How can I target specific devices with notifications?

Consider using a custom solution that involves creating separate contact records or utilizing a third-party vendor to integrate push event data for segmentation and message personalization.

What are the benefits of using a third-party vendor?

Using a third-party vendor can provide more flexibility and control over notification targeting, as well as access to additional features and functionality.

How can I leverage the push SDK event logging feature?

The push SDK event logging feature can provide valuable insights into notification engagement and behavior, allowing for more effective targeting and personalization of notifications.