Audience Manager Cookies
Audience Manager relies on a few simple cookies to perform different functions. These include things like assigning IDs, recording data calls, error tracking, and testing to see if cookies can be set. This section lists and describes the various cookies set by Audience Manager.
Audience Manager sets this cookie to assign a unique ID to a site visitor. The demdex cookie helps Audience Manger perform basic functions such as visitor identification, ID synchronization, segmentation, modeling, reporting, etc.
The demdex cookie contains a Unique User ID (UUID) as shown in the example below:
See also, Index of IDs in Audience Manager .
Audience Manager sets this cookie to record the last time it made a data synchronization call.
The dextp cookie contains a data provider name or ID and a UNIX UTC timestamp formatted as pipe-delimited strings. In the examples, italics represents a variable placeholder.
See also, the dextp data syntax section below.
dextp Cookie Data Syntax:
The following table lists and defines the elements in a dextp cookie by location in the data string.
First or Second
The position of the data provider name or ID varies depending on if the cookie uses the new or old style formatting.
Old style formatting:
The old style cookie identifies the data provider with a readable name.
New style formatting:
The new style cookie:
The last position contains a UNIX UTC timestamp.
Audience Manager sets this cookie when there's an error sending data to a destination .
The DST cookie contains sets of destination IDs and UNIX time-stamps formatted as pipe-delimited strings. In the examples, italics represents a variable placeholder.
This is a temporary cookie. Audience Manager tries to set the _dp cookie to determine if it can set other cookies in the demdex.net domain in a third-party context. When _dp is set it contains a value of 1. Audience Manager reads this value and immediately removes the cookie. If the _dp cookie is not present, Audience Manager knows it cannot set cookies.