Onboarding SHA512 dataset for people based destinations

[bpurce]

The documentation for people based destination's states that a SHA256 email hash is required. 

We're looking to adopt SHA512 as the hashing standard for all user emails and I'm curious if there is any issue with onboarding a SHA512 hash instead of a SHA256. 

Thanks. 

[allanwitts]

Hi

Yes, as per the documentation, SHA256 email hashing is required, not SHA512. The reason for this is that the hashing method used for the email addresses sent to AAM, must be the same as the method used by the destinations (e.g. Google, Facebook, LinkedIn etc).

As Audience Manager is essentially passing through the hashed email addresses (along with segment qualification information) the hashed emails must match the standard required by the destinations themselves, which is SHA256.

Hope this helps!