Show Menu
TOPICS×

Data collection HTTP headers

HTTP request and response headers are used to collect additional data beyond what is collected by AppMeasurement. This section describes the headers used during data collection.

HTTP Request Headers

Header Usage
Cookie
Reading cookies previously created by our data collection servers.
As of 2014, Adobe servers will discard all cookies that accompany a server call except those set by Adobe. See Cookies Used in the Experience Cloud for the full list of Adobe's cookies.
User-Agent Used for browser, operating system, and mobile device detection.
X-Device-User-Agent Used as an alternative to User-Agent for correct browser, operating system, and mobile device detection for some browsers like OperaMini.
X-Original-User-Agent Used as an alternative to User-Agent for correct browser, operating system, and mobile device detection for some browsers like OperaMini.
X-OperaMini-Phone-UA Used as an alternative to User-Agent for correct browser, operating system, and mobile device detection for some browsers like OperaMini.
X-Skyfire-Phone Used as an alternative to User-Agent for correct browser, operating system, and mobile device detection for some browsers like OperaMini.
X-Bolt-Phone-UA Used as an alternative to User-Agent for correct browser, operating system, and mobile device detection for some browsers like OperaMini.
UA-OS Used as an alternative was to identify the operating system.
UA-Pixels Used as an alternate source for the screen resolution of the client screen.
UA-Color Used as an alternate source for the color depth of the client screen.
X-moz Detecting that the data collection request was made as part of pre-fetching a webpage.
X-Purpose Detecting that the data collection request was made as the browser was showing a preview of a webpage.
Accept Used to identify the image formats supported by the browser so we know if we need to send back a GIF or WBMP image.
Referrer Used as a fallback for getting information about the page URL the data collection request was made from when it wasn't passed in on the query-string or when it's different from the value in the query-string.
X-Forwarded-For Used to find the correct IP address for the client that made the data collection request. The IP address is used to generate geographic region, mobile carrier, and other reports.
Implementations using dynamic variables have the option of reading in other HTTP request headers not listed above.

HTTP Response Headers

Header
Usage
Access-Control-Allow-Origin
Used to enable support for cross-origin resource sharing style data collection requests to our servers.
Expires
Browser caching control.
Last-Modified
Browser caching control.
Cache-Control
Browser caching control.
Pragma
Browser caching control.
ETag
Browser caching control.
Vary
Browser caching control.
P3P
Provides the default or custom P3P policy for the data collection request.
Status
Contains "SUCCESS" or "FAILURE" status for a no content request. Used only when the request specifies that no content should be returned.
Reason
Contains the reason for the failure status of a no content request. Used only when the request specifies that no content should be returned.
Location
Used to redirect the client making the data collection request off to a different URL. An example is our cookie handshake to detect the ability to set the visitor ID cookie.
Content-Type
Specifies the type of content sent back to the client (GIF, text, Javascript, etc).
Content-Length
Specifies the size of the content sent back to the client.
Other HTTP headers may be set in the response for internal status monitoring. Some of these headers might be returned to the browser, but it is not necessary that they receive them.