Apply transformation option on destination activation normalize before hashing
We recommend that you normalize the data/IDs before they are used in your implementation. For e.g., you can convert phone numbers into E.164 format before ingestion or use Data Prep to perform lowercasing or hashing upon ingestion. This will ensure the data is cleansed and can be used in all downstream use cases, including activation.
Description description
Environments
- ÃÛ¶¹ÊÓƵ Experience Platform (AEP)
- Real-time Customer Data Platform (RTCDP)
- Customer Journey Analytics (CJA)
Issue
Does the Apply transformation option on destination activation normalize (For example: lowercase) before hashing?
Resolution resolution
As of early 2023, destinations in AEP don’t support general data normalization.
The apply transformation checkbox in destinations was built specifically for SHA256 hashed emails.
We recommend that you normalize the data/IDs before they are used in your implementation. For e.g., you can convert phone numbers into E.164 format before ingestion or use Data Prep to perform lowercasing or hashing upon ingestion. This will ensure that the data is cleansed and can be used in all downstream use cases, including activation.
It is expected that you use Data Prep during ingestion for such data quality operations.