sha256 hashed email
(see below for how to cleanse the email prior to hashing)
sha256 hashed phone number
(remove all characters besides numbers before hashing)
|3||cross-partner user id value|
(i.e. a user id that could be used across ID5 Partner IDs)
cross-partner user id source
(value provided by ID5)
|5||partner-specific user id value|
(i.e. a user id that is specific to a single ID5 Partner IDs)
Apple ID for Advertising (IDFA)
Google Advertising ID (GAID)
firstname.lastname@example.org, and want to share it with ID5 to strengthen the value of the UID we respond with. You also have your own user id for this user that you can share:
möller&françois(note: we discourage the use of special characters in the IDs, this is just for illustration purposes). Except for values that are sha256-hashed, in general other values should be URL-encoded (according to RFC 3986) using UTF-8 charset.
1(for the hashed email) and
5(for the URL-encoded user id), separated by
&’s (the order doesn’t matter):
pdfield in any of our integrations.
.(ASCII code 46) from the username of the email address.
+(ASCII code 43) and all subsequent characters from the username of the email address.