Page variables directly populate a report, such as pageName, List
Props, List Variables, and so on.
Additional eVars and Events
If you want to track additional information, but don’t have enough variables to do so, you now have access to additional eVars and success events:
The browserHeight variable displays the height of the browser window.
The browserWidth variable displays the width of the browser window.
The campaign variable identifies marketing campaigns used to bring visitors to your site. The value of campaign is usually taken from a query string parameter.
The channel variable is most often used to identify a section of your site.
The colorDepth variable is used to show the number of bits used to display color on each pixel of the screen.
The connectionType variable, in Internet Explorer, indicates whether the browser is configured on a LAN or modem connection.
(Deprecated) The dc variable lets you select the data center to which your data is sent.
The eVar variables are used for building custom reports.
The s.events variable is used to record common shopping cart success events as well as custom success events.
The hierarchy variable determines the location of a page in your site's hierarchy.
The homepage variable, in Internet Explorer, indicates whether the current page is set as the user's home page.
The javaEnabled variable indicates whether Java is enabled on the browser.
The linkName variable is an optional variable used in Link Tracking that determines the name of a custom, download, or exit link.
The linkType variable is an optional variable used in link tracking that determines which report a link name or URL appears (custom, download, or exit links).
List props are a delimited list of values that are passed into a variable, then reported as individual line items. List props are most commonly implemented on pages that contain user-selectable values, such as listed items with check boxes or radio buttons. They are useful in any circumstance where you want to define multiple values in a variable without sending multiple image requests.
Also known as List Var. Similar to how List Props function, List Vars allow multiple values within the same image request. They also act similarly to eVars, which persist beyond the image request they were defined on. You can use these variables to see cause and effect among multiple elements on a single page, such as product lists, wish lists, lists of search refinements, or lists of display ads.
The s.maxDelay variable is used primarily in Genesis DFA integrations to determine the timeout period in contacting the DFA host. If Adobe does not receive a response from DFA's servers within the specified period set in the s.maxDelay variable, the connection is severed, and data is processed normally. Implement this variable if you are concerned with DFA's response time on each page. It is recommended to experiment with this value to determine the optimum timeout period.
The mediaLenght variable specifies the total length of the media being played.
This variable specifies the name of the video or media item.
This variable specifies the player used to consume a video or media item.
This variable specifies the segments of a video or media asset consumed.
The Media.trackEvents variable identifies which events should be sent with a media hit.
The Media.trackVars variable identifies which variables should be sent with a media hit.
The mobile variable controls the order in which cookies and subscriber IDs are used to identify visitors.
The pageName variable contains the name of each page on your site.
The pageType variable is used only to designate a 404 Page Not Found Error page.
The pageURL variable overrides the actual URL of the page.
The plugins variable, in Netscape and Mozilla-based browsers, lists the plugins installed on the browser.
The products variable is used for tracking products and product categories as well as purchase quantity and purchase price. Products is typically set in conjunction with a cart event or a prodView event.
Property (prop) variables are used for building custom reports within the Traffic Module.
The purchaseID is used to keep an order from being counted multiple times in reporting.
The referrer variable can be used to restore lost referrer information.
The resolution variable indicates the monitor resolution of the visitor viewing the web page.
The s_objectID variable is a global variable that should be set in the onClick event of a link.
The server variable is used to show either the domain of a web page (to show which domains people come to) or the server serving the page (for a load balancing quick reference).
The state and zip variables are conversion variables.
This variable lets you customize the timestamp of a hit similar to the AppMeasurement libraries for other platforms.
The trackingServer variable is used for first-party cookie implementation to specify the domain at which the image request and cookie is written.
The trackingServerSecure variable is used for first-party cookie implementation to specify the domain at which the image request and cookie is written.
transactionID Integration Data Sources use a transaction ID to tie offline data to an online transaction (like a lead or purchase generated online).
Visitors can be identified by the visitorID variable or by IP address/User Agent.
The visitorNamespace variable is used to identify the domain with which cookies are set.
The state and zip variables are conversion variables.