Acquiring Embedded Object Requests (Page Tags)

IMPORTANT

Read more about Data Workbench’s End-of-life announcement.

After the HTML of a page is requested by a browser, the browser requests the embedded objects referenced in the HTML of that page from a web server to fill in the page shown by the browser.

Such embedded object requests are most commonly requests for image files or JavaScript files, though there are hundreds or maybe thousands of types of embedded objects used on the Internet today. Many of these embedded object requests are not generally useful in analyzing or reporting on the business activity of an Internet site; many such requests are therefore not desirable for acquisition unless they have a specific business purpose, such as presenting an advertisement or taking another measurement of site activity.

For example, an image may be an advertisement, and you may want to know that the advertisement was impressed upon a visitor. A JavaScript snippet may be in use to take a measurement that the particular browser has a certain characteristic and pass it back to a Sensor for acquisition. Each page on a site may have 10 or 100 embedded object requests in it. If a site stores the log information for each of these requests, the amount of data storage needed to keep the log data available for future analysis is multiplied by the number of embedded object requests for each page requested. For this reason, Site lets you keep the requests that are important for analysis and discard others before you incur unnecessary storage costs.

By using the override feature provided in the content-type filtering capabilities of Sensor (appending “Log=1” to the query string of an embedded object request URL), that particular embedded object request and the related measurement data can be acquired without requiring the site manager to store all requests of that type (for example, all <image> requests).

Sensor collects the measurement data in the following table for each embedded object request made of the web server, assuming that Sensor is not configured to filter it out or that the filter has been overridden. The collected information is related to the visitor and session and subsequent sessions through the x-trackingid or cs(cookie) log field entries.

W3C Name Data Collected Explanation Example
x-trackingid Tracking Identifier (unique visitor) Identifier read from a cookie placed in the user’s browser by Sensor on initial request V1st=3C94007B4E01F9C2

Date

Time

Timestamp Time at which request was processed by server (at 100ns precision; accuracy depends on server environment and NTP) 2002-11-21 17:21:45.123
sc(content-Type) Content Type Type of object returned from server text/html
sc-status HTTP Response Status Code Numerical code generated by the server that notes the status of the HTTP server's response 200
cs-uri-stem URI Stem The “stem” portion of the URI requested by the client pagedir/page.asp
c-ip Client IP IP Address of the requesting client 127.0.0.1
s-dns Server Domain Name Domain name of the web server processing the request www.domain.com
cs(referrer) Referring URL Contents of the HTTP referrer field sent by the client https://www.referringsite.com
cs(user-agent) User Agent Device used to make a request to the HTTP server

Mozilla/4.0+(compatible;+MSIE+6.0;

+Windows+NT+5.1)

cs(cookie) Client Cookies from Domain Contents of all of the user’s cookies for the site

KL_TC1 1038058778312

KL972 x1038058778312282052

KL_PVKL972 0

cs-uri-query Query String The query string portion, if any, of the URI requested by the client PAGENAME=dynamic1&link=3001

Business.Adobe.com resources

Docs links
Audio Analytics Custom Variables Data Explorer Anomaly Detection General Data Protection Regulation Predictive Analytics

On this page