ID Synchronization for Inbound Data Transfers id-synchronization-for-inbound-data-transfers
Describes the syntax and parameters used in the initial HTTP call to synchronize user IDs between a vendor and Audience Manager. ID synchronization can begin after you send your data taxonomy to Audience Manager.
ID synchronization is the first step in the inbound, asynchronous data transfer process. In this step, Audience Manager and the vendor compare and match IDs for their respective site visitors. For example, an Audience Manager customer may know a user by ID 123. However, your data partner could identify this user with ID 456. The synchronization process allows Audience Manager and a data vendor to reconcile these different IDs and identify users in their respective systems. Once complete, Audience Manager and your third-party partner should have corresponding IDs for each unique user seen on our networks.
You can use the following methods to get your data into Audience Manager:
ID Synchronization HTTP Request id-sync-http
In an ID exchange, a properly formatted URL string should look like this:
https://dpm.demdex.net/ibs:dpid=<VENDOR_ID>&dpuuid=<VENDOR_UUID>&redir=<REDIRECT_URL>
The URL for your inbound ID synchronization call should contain variables described in the table below.
<VENDOR_ID><VENDOR_UUID>URL (Percent) Encoded representation of your Unique User ID. In addition to encoding reserved ASCII characters, any non-ASCII characters should be percent encoded based on the UTF-8 character encoding table.
For more information, see the website.
<REDIRECT_URL>An encoded URL redirect with the macro ${DD_UUID} embedded within it.
Note: Added only when the content provider initiates the call.
gdpr = <0|1>Optional. Add this parameter if you are using the Audience Manager Plug-in for IAB TCF.
gdpr can be 0 (GDPR does not apply) or 1 (GDPR applies).
Note: This parameter can only be used together with gdpr_consent.
gdpr_consent=<ENCODED STRING>Optional. Add this parameter if you are using the Audience Manager Plug-in for IAB TCF.
gdpr_consent is the URL-safe base64-encoded GDPR consent string (see ).
Note: This parameter can only be used together with gdpr.
Declared ID Event declared-id-event
For more information, see Declared IDs.
ID Synchronization From an Email Embedded Image id-sync-email-image
The format for matching IDs via an email image is the same as shown above. Note, however, that images in an email must be enabled for this to work. This can affect ID synchronization via email because most mail systems disable images by default.