People Based Destinations with only Hashed Emails and no DPUUID sync

[caseyo84500701]

Hello,

Is it possible to onboard a file for People-Based Destinations without having a DPUUID sync? In this scenario we want to only onboard our customer email lists, and do not have an ID sync with a customer ID to a AAM UUID. The file contents example is below:

hashed_email<tab>trait=1

514df3958cb8489844677845e17690c2223cc7bac9ddef917d1c9f88e3ed949d<TAB>d_sid=xxxxxx

Thank you

[shweta_singh]

Hi @caseyo84500701 ,

As mentioned in our doc here, we need to match DPUUIDs/CRM IDs to Hashed Email Addresses via File-Based ID Synchronization.

For people base destination, Id sync is between DPUUIDs/CRM Ids and hashed email addresses.

Regards,

Shweta

[caseyo84500701]

Hi @shweta_singh

So if we do not have an ID sync collecting a DPUUID/CRM ID into a data source, it is not possible to upload a file of just hashed email addresses and use AAM as a conduit to share this segment out to a People-Based Destination? 

Why is there a dependency on the DPUUID? Requiring this massively cuts scale (due to only linking hashed emails to those who have authenticated in the ID sync), and makes this integration useless as it becomes similar to simply using a Facebook website custom audience pixel.