Adobe Target cookies
- Topics:
- Cookies
CREATED FOR:
- Experienced
- Admin
Adobe Target uses cookies to give website operators the ability to test which online content and offers are more relevant to visitors.
at.js
). See Adobe Experience Platform Web SDK cookies for information on Target implementations using the Web SDK.First-party cookies
The following first-party cookies are stored on the customer’s domain:
Cookie | Details |
---|---|
mbox |
Stores anonymous identifiers about the visitor. Cookie domain: The domain from which you serve the mbox. Because this cookie is served from your company’s domain, the cookie is a first-party cookie. If any of your domain names include a country code, such as Server domain: Cookie duration: The cookie remains on the visitor’s browser two years from the last login. You cannot change the cookie duration. The cookie keeps some values to manage how your visitors experience Target activities: session ID: A unique identifier for a given user session. By default the session expires after 30 minutes of inactivity. If you are generating
Routing to a particular node in the edge cluster is done using session ID.
NOTE: See limit on number of concurrent requests for a given session ID. pc ID: A semi-permanent ID for a visitor’s browser. Lasts until cookies are manually deleted. check: A simple test value used to determine if a visitor supports cookies. Set each time a visitor requests a page. disable: Set if a visitor’s load time exceeds the timeout configured in the at.js file. By default, this timeout lasts one hour. |
at_check | Temporary cookie to check if the cookie read/write capability is enabled on the browser. |
mboxEdgeCluster | This cookies is only present when/if overrideMboxEdgeServer setting is set to true . |
It is not possible to use HTTPOnly
on the these first-party cookies. The at.js
JavaScript library needs to read/write to these cookies. These cookies are created by at.js
and are not set from the server.
The secure
setting can be enabled on all of these cookies using the secureOnly: true
configuration in at.js
.
Third-party cookies
Adobe Target users can create customized third-party cookies. The following third-party cookies are stored on tt.omtrdc.net
:
Cookie | Details |
---|---|
customerclientcode!mboxPC | Present if cross domain is enabled. |
customerclientcode!mboxSession | Present if cross domain is enabled. |
These third-party cookies are HTTPOnly out of the box and are set by Adobe Target data collection servers.
The secure
setting can be enabled on all of the cookies using the secureOnly: true
configuration in at.js
.
Target
- Experience Cloud interface and administration
- Services
- Overview
- Getting started
- Assets
- Audience Library
- Exchange
- Customer Attributes
- Overview
- Frequently asked questions about Customer Attributes
- About data file and data sources for Customer Attributes
- Create a Customer Attribute source and upload the data file
- Optional - Upload the data file via FTP
- Validate the schema
- Configure subscriptions
- Update the schema
- Support for General Data Protection Regulation
- Support for California Consumer Privacy Act
- Privacy considerations for Customer Attributes
- Triggers
- Features
- Administration
- Data collection
- More Resources