Skip to main content

Supported ID types

The following ID types can be used as input fields for matching data or as output fields that can be returned in the result set. For further details on how these are utilized within each application template, see Matching Options and the Configure dentsu.Composable Translate App section of the application README.

ID type ID subtype Description Availabe as
clear_email   Properly formatted email address of an individual, including @ and . characters. Raw/clear email only (NOT hashed). Input
hashed_email md5 Lowercase raw/clear email of an individual using MD5 Hash. Does not include B2B emails at this time. Input
hashed_email sha1 Lowercase raw/clear email of an individual using SHA1 Hash. Does not include B2B emails at this time. Input
hashed_email sha256 Lowercase raw/clear email of an individual using SHA256 Hash. Does not include B2B emails at this time. Input
device idfa Device of an individual as an uppercase Apple ID for Advertisers (IDFA). Input
device aaid Device of an individual as a lowercase Google Android Advertising ID (AAID). Input
phone   A phone number for an individual formatted as a numeric value only (non-numeric characters stripped) and includes partials (<11 digits). Input
ip   IPv4 Input
fluid fluid dentsu.ID Family Living Unit ID as a dentsu-encrypted household ID. Output
fluid fluid_client dentsu.ID Family Living Unit ID as a client-hashed household ID. Output
druid druid dentsu.ID Domestic Residence Unit ID as a dentsu-encrypted address ID. Output
druid druid_client dentsu.ID Domestic Residence Unit ID as a client-hashed address ID. Output
hmid   dentsu.ID, digitally sourced and client-hashed. Input
cmid cmid_m1v1 dentsu.ID, terrestrially sourced and dentsu-encrypted. Input
cmid cmid_client dentsu.ID, terrestrially sourced and client-encrypted. Input