AEP - Does the ‘Apply transformation’ option on destination activation normalise (e.g. lower case) before hashing?
At this point in time (early 2023), destinations in AEP do not support general data normalization yet.
The “apply transformation” checkbox in destinations was built specifically for
SHA256 hashed emails.
We’d recommend customers normalize data/IDs upstream in their implementation (e.g. converting phone numbers into
E.164 format before ingestion, or using Data Prep to do lowercasing/hashing upon ingestion) so data can be cleansed and used in all downstream use cases, including activation.
We expect customers to use Data Prep during ingestion for such data quality operations.