Understanding the Implications

Using an email address as a subscriber key can limit the ability to send other types of messaging, such as SMS or push notifications, as email addresses cannot be used as a subscriber key for these channels. This means that if the client wants to add these channels in the future, they will have to perform a subscriber key migration, which can be complicated and time-consuming.

The root cause of this issue is the use of an email address as a subscriber key, which can lead to data inconsistencies and limitations in terms of messaging channels. It is generally recommended to use a unique identifier, such as a Salesforce contact ID, as the subscriber key to avoid these issues.

To handle journeys with Salesforce objects as an entry source, it is possible to write an automation in Sales Cloud that identifies the email address and merges the email subkey with the contact or lead record. However, this approach depends on the specific business logic and data requirements of the client.

In terms of managing subscriber keys, there are multiple techniques that can be used, including using a unique identifier as the subscriber key, implementing a data governance process to ensure data consistency, and using automation tools to merge duplicate records.

Step-by-Step Solution

To address the issue of using an email address as a subscriber key, the following steps can be taken:

SFMC Automation

// Write an automation in Sales Cloud to identify the email address and merge the email subkey with the contact or lead record
// Use a unique identifier, such as a Salesforce contact ID, as the subscriber key
// Implement a data governance process to ensure data consistency

Heads up: When implementing a subscriber key migration, it is essential to carefully plan and test the process to avoid data inconsistencies and ensure a smooth transition.

Checklist

Best Practices for Managing Subscriber Keys

• Use a unique identifier, such as a Salesforce contact ID, as the subscriber key
• Implement a data governance process to ensure data consistency
• Use automation tools to merge duplicate records
• Plan and test subscriber key migrations carefully
• Monitor data quality and address issues promptly

Frequently Asked Questions

What are the implications of using an email address as a subscriber key?

Using an email address as a subscriber key can lead to data management issues and limit the ability to send other types of messaging.

How can I handle journeys with Salesforce objects as an entry source?

You can write an automation in Sales Cloud that identifies the email address and merges the email subkey with the contact or lead record.

What are the best practices for managing subscriber keys?

Use a unique identifier as the subscriber key, implement a data governance process, and use automation tools to merge duplicate records.

How can I address data inconsistencies when using an email address as a subscriber key?

You can use automation tools to merge duplicate records and implement a data governance process to ensure data consistency.