[Content]: Trade Desk doc not aligned with functionality

[bailey-trotter-segment]

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/actions-the-trade-desk-crm/#faqs:~:text=If%20any%20of,the%20ingestion%20process.

What part(s) of the article would you like to see updated?

It would seem Trade Desk prefers you send clear text emails over which we can handle just fine, where it gets confusing is here.

We seem to imply if you are storing the hashed version in Segment, to set the PII Type to "Hashed Email". When doing testing of the code, I discovered we actually do a lot more and the docs to not make it clear.

TTD expects an email to be normalized, sha256 hashed then hex base64 encoded. What we do, when you select the "hashed email" in the drop down is a handful of things:

• if its a plain text email, we normalize and hash as needed for TTD
• if the email is sha256 hash, we assume you normalized it correctly per TTD requirements and hex base64 encode it
• if the email is base64 encoded, we assume you normalized and sha256 hash it correctly per TTD requirements and send it on as is

Additional information

• Here, if user selects "hash email" we set pii_type to EmailHashedUnifiedId2

• here if pii_type is EmailHashedUnifiedId2 we call the hashing function