For privacy-safe audience matching, advertising and social destinations require Personally Identifiable Information (PII) like email addresses to be hashed. Adobe Experience Platform documentation specifies that the Facebook Custom Audiences, Google Customer Match, and LinkedIn Matched Audiences connectors all mandate the transformation of email addresses into the SHA256 format. Experience Platform can perform this hashing automatically during the activation workflow. These platforms use the hashed value to match users in their systems without processing clear-text PII. Other destination types, like cloud storage or certain marketing automation platforms, do not have this mandatory hashing requirement for their primary function.

B. Amazon S3 is a cloud storage destination; data formatting (like hashing) is determined by the user's export configuration, not a mandatory requirement for matching. Salesforce Marketing Cloud typically ingests clear-text emails.

C. This option incorrectly includes Salesforce Marketing Cloud. The Salesforce Marketing Cloud destination connector is designed to ingest subscriber data, typically with clear-text email addresses for direct communication, and does not mandate SHA256 hashing for identity.

1. Facebook Custom Audiences: Adobe Experience Platform Documentation

"Facebook Custom Audiences destination". In the "Supported identities" section

it explicitly lists EmailSHA256 as the target identity namespace. The "ID matching requirements" section states

"For identifiers such as email addresses or phone numbers

you must provide the data in hashed format."

2. Google Customer Match: Adobe Experience Platform Documentation

"Google Customer Match destination". The "Prerequisites" section notes

"When activating email addresses to Google Customer Match

you must use the EmailSHA256 namespace. Experience Platform handles the hashing of the email addresses automatically."

3. LinkedIn Matched Audiences: Adobe Experience Platform Documentation

"LinkedIn Matched Audiences destination". In the "Map identity" step description

it instructs

"When mapping email addresses to LinkedIn

make sure to hash them using the SHA256 algorithm... To do this

select the Apply transformation checkbox."

4. Salesforce Marketing Cloud (Incorrect Inclusion): Adobe Experience Platform Documentation

"Salesforce Marketing Cloud destination". The "Supported identities" section lists contactKey and Email as target identities

not EmailSHA256. The documentation does not mention a mandatory hashing requirement for email addresses.