Audience Manager cookies 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.
demdex Cookie
The demdex cookie contains a Unique User ID (UUID) as shown in the example below:
06151304227769720433039235178204449977
See also, Index of IDs in Audience Manager.
- Lifetime: The demdex cookie has a time-to-live (TTL) interval of 180-days. The TTL is reset to 180-days upon each user interaction with a partner website. The cookie expires if a user does not come back to your site within the TTL interval.
- Opt-out: Audience Manager resets the cookie with a Do Not Adobe Target string if a user opts-out of data collection. In this case, the cookie TTL is set as 10 years.
dextp Cookie
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.
- Old style: data provider name here -1490307822097| data provider name here -1490307822038
- New style: 21-1-1490307821616|544-1-1490307821793|3-1-1490307821852|420-1-1490307822038|
See also, the dextp data syntax section below.
- Lifetime: The dextp cookie has a time-to-live (TTL) interval of 180-days.
- Opt-out: Audience Manager resets the cookie with a Do Not Adobe Target string if a user opts-out of data collection. In this case, the cookie TTL is set as 10 years.
dextp Cookie Data Syntax:
The following table lists and defines the elements in a dextp cookie by location in the data string.
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:
- Syntax: data provider name - UNIX UTC timestamp
- Example: dataProvider1 - 1490307822038
The old style cookie identifies the data provider with a readable name.
New style formatting:
- Syntax: data provider ID - 1|2 - UNIX UTC timestamp
- Example: 123345 - 1 - 1490307822038
The new style cookie:
- Replaces the readable data provider name with a numeric ID.
- Identifies the call type with ID 1 or ID 2. ID 1 represents an ID synchronization call. ID 2 represents a deprecated call that is no longer used. You should not see many (or any) dextp cookies with ID 2.
dst Cookie
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.
- Syntax: destination ID - UNIX UTC timestamp
- Example: 067797-1490349684|1010788-1490349692|1067797-1490349692
- Lifetime: The dst cookie has a time-to-live (TTL) interval of 180-days.
- Opt-out: Audience Manager resets the cookie with a Do Not Adobe Target string if a user opts-out of data collection.
_dp Cookie
This cookie is temporary. 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.