Adobe Analytics Implementation

Below you will find brief information for Adobe Analytics Implementation Guide. This guide provides comprehensive instructions for implementing Adobe Analytics, covering JavaScript implementation, tag management, variable configuration, troubleshooting, and optimization techniques. It helps you collect and analyze website data effectively.
PDF
Document
Adobe&reg; Marketing Cloud
Adobe Analytics Implementation
Contents
Adobe Analytics Implementation.........................................................................11
JavaScript Implementation...................................................................................14
Example Page Code and Global Configuration.....................................................................16
About AppMeasurement for JavaScript..............................................................18
Migrating to AppMeasurement for JavaScript.......................................................................19
AppMeasurement Plug-in Support........................................................................................20
Additional Web and Mobile Measurement Libraries...........................................22
Implementing Analytics using HTML image tags..................................................................23
Implementing without JavaScript Guidelines............................................................................................23
Sample Code...........................................................................................................................................26
Mobile Tracking over WAP and I-Mode Protocols..................................................................27
Mobile Network Protocols........................................................................................................................27
Mobile Protocol Network Gateway...........................................................................................................27
Tagging Pages For Mobile Protocols........................................................................................................28
Reports for Devices Using Mobile Protocols............................................................................................28
Custom Link Measurement on Mobile Protocols......................................................................................29
Tag management 2.0.............................................................................................................30
Tag management Architecture.................................................................................................................30
Tag management Quick Start...................................................................................................................33
Migrating to tag management 2.0 from tag management 1.0 .................................................................36
Migrating to tag management 2.0 from a Legacy Implementation...........................................................40
Marketing Cloud Deployment...................................................................................................................43
Custom Tag Deployment..........................................................................................................................44
Tag management Permissions.................................................................................................................45
amc.on Tag Event Callbacks....................................................................................................................45
Troubleshooting........................................................................................................................................47
Last updated 4/8/2015
Adobe Analytics Implementation
Contents
Analytics Variables................................................................................................51
Additional eVars and Events.................................................................................................51
Variables and Limitations......................................................................................................52
Illegal JavaScript Characters.................................................................................................56
s_account..............................................................................................................................56
browserHeight.......................................................................................................................58
browserWidth........................................................................................................................58
campaign...............................................................................................................................59
charSet..................................................................................................................................60
channel..................................................................................................................................60
colorDepth.............................................................................................................................61
connectionType.....................................................................................................................61
cookieDomainPeriods...........................................................................................................62
cookieLifetime.......................................................................................................................63
cookiesEnabled.....................................................................................................................64
currencyCode........................................................................................................................64
dc..........................................................................................................................................65
doPlugins..............................................................................................................................65
dynamicAccountList..............................................................................................................66
dynamicAccountMatch..........................................................................................................67
dynamicAccountSelection.....................................................................................................68
dynamicVariablePrefix...........................................................................................................69
eVarN....................................................................................................................................69
Additional eVars and Events.................................................................................................71
events....................................................................................................................................73
fpCookieDomainPeriods........................................................................................................75
hierN......................................................................................................................................76
homepage.............................................................................................................................77
javaEnabled...........................................................................................................................77
javascriptVersion...................................................................................................................77
linkDownloadFileTypes..........................................................................................................78
Last updated 4/8/2015
Adobe Analytics Implementation
linkExternalFilters..................................................................................................................79
linkInternalFilters...................................................................................................................80
linkLeaveQueryString............................................................................................................81
linkName...............................................................................................................................82
linkTrackEvents......................................................................................................................83
linkTrackVars.........................................................................................................................84
linkType.................................................................................................................................85
List Props..............................................................................................................................85
List Variable...........................................................................................................................86
maxDelay..............................................................................................................................88
mediaLength.........................................................................................................................88
mediaName...........................................................................................................................89
mediaPlayer..........................................................................................................................90
mediaSession........................................................................................................................91
Media.trackEvents.................................................................................................................92
Media.trackVars.....................................................................................................................92
mobile....................................................................................................................................92
pageName.............................................................................................................................93
pageType...............................................................................................................................94
pageURL...............................................................................................................................94
plugins...................................................................................................................................95
products................................................................................................................................96
propN....................................................................................................................................99
purchaseID..........................................................................................................................100
referrer.................................................................................................................................100
resolution.............................................................................................................................101
s_objectID...........................................................................................................................101
server..................................................................................................................................103
state....................................................................................................................................103
timestamp............................................................................................................................104
trackDownLoadLinks...........................................................................................................105
Last updated 4/8/2015
Adobe Analytics Implementation
Contents
trackExternalLinks...............................................................................................................106
trackingServer.....................................................................................................................107
trackingServerSecure..........................................................................................................107
trackInlineStats....................................................................................................................107
transactionID.......................................................................................................................108
s_usePlugins.......................................................................................................................109
visitorID...............................................................................................................................109
visitorNamespace................................................................................................................110
zip........................................................................................................................................110
Context Data Variables........................................................................................112
Processing Rules................................................................................................................113
Dynamic Variables...............................................................................................114
Dynamic Variable Examples................................................................................................115
Merchandising Variables.....................................................................................117
Implementing a Merchandising Variable..............................................................................118
Instances on Merchandising Variables................................................................................120
The s.t() Function - Page Tracking......................................................................122
The s.tl() Function - Link Tracking......................................................................123
Automatic Tracking of Exit Links and File Downloads.........................................................125
Manual Link Tracking Using Custom Link Code..................................................................126
Link Tracking Using an Image Request...............................................................................127
Setting Additional Variables for File Downloads, Exit Links, and Custom Links..................127
Using Function Calls with Custom Link Code.....................................................................128
Popup Windows with useForcedLinkTracking .....................................................................129
Links from URL Shorteners.................................................................................................130
Link Tracking Variables in doPlugins...................................................................................130
Validating File Downloads, Exit Links, and Custom Links...................................................131
Last updated 4/8/2015
Adobe Analytics Implementation
The s.sa() Function..............................................................................................132
The s.clearVars() Function..................................................................................133
The s_gi() Function..............................................................................................134
Util.cookieRead....................................................................................................135
Util.cookieWrite....................................................................................................136
Util.getQueryParam.............................................................................................137
Offline Tracking....................................................................................................138
Data Collection.....................................................................................................140
Data Collection HTTP Headers...........................................................................................140
Variable Overrides...............................................................................................................141
Report Suite IDs - Dynamic Accounts.................................................................................142
Common Errors......................................................................................................................................143
Collecting Data From Form Elements.................................................................................144
Tracking Across Different Implementation Types.................................................................145
Implementation Guidelines.....................................................................................................................145
Implementation Example........................................................................................................................145
AJAX-Tracking Rich Media Applications..............................................................................146
Implementing with AJAX........................................................................................................................148
External Email Tracking.......................................................................................................149
Implementing Adobe Opt-Outs............................................................................................151
Add an Opt-Out Link..............................................................................................................................152
Testing and Validation.........................................................................................154
Testing and Validation Process............................................................................................154
Identifying the s_account Variable in the DigitalPulse Debugger...........................................................154
JavaScript JS File...................................................................................................................................154
Last updated 4/8/2015
Adobe Analytics Implementation
Contents
Code Modifications.................................................................................................................................155
Variables and Values..............................................................................................................................155
Custom Variables...................................................................................................................................156
Implementation Acceptance...................................................................................................................156
Data Accuracy Validation........................................................................................................................157
Adobe Debugger.................................................................................................................158
Adobe Debugger Installation..................................................................................................................158
Launching DigitalPulse Debugger..........................................................................................................159
Packet Analyzers.................................................................................................................160
NS_Binding_Aborted in Packet Monitors...............................................................................................161
Common Syntax Mistakes...................................................................................................161
Putting Analytics Code in the Head Tag.................................................................................................161
Using s.linkTrackVars and s.linkTrackEvents..........................................................................................163
Common Mistakes in the Products Variable...........................................................................................163
Setting the PageType Variable Correctly................................................................................................165
Using White Space in Variable Values....................................................................................................165
Using Quotes.........................................................................................................................................166
Replacing Your Analytics Code...............................................................................................................166
Table of Common Syntax Mistakes........................................................................................................167
Vulnerability Scanner...........................................................................................................167
Optimizing your Implementation..........................................................................................168
Page Naming..........................................................................................................................................168
Variable Length......................................................................................................................................170
HTML Code Snippet...............................................................................................................................170
Javascript Library File............................................................................................................................170
Caching Directives.................................................................................................................................170
Tables.....................................................................................................................................................171
File Compression...................................................................................................................................171
Secure Pages.........................................................................................................................................171
Content Delivery Services/Networks......................................................................................................171
JavaScript File Location and Concurrency.............................................................................................171
Peering...................................................................................................................................................172
Report to Variable Mapping.................................................................................................172
Variable to Report Mapping.................................................................................................178
Last updated 4/8/2015
Adobe Analytics Implementation
Implementation Plug-ins.....................................................................................182
Calling Plug-ins with doPlugins Function............................................................................182
s.abort flag..........................................................................................................................183
appendList...........................................................................................................................184
doPlugins Function..............................................................................................................186
getAndPersistValue.............................................................................................................187
getDaysSinceLastVisit.........................................................................................................188
getLoadTime.......................................................................................................................189
getNewRepeat.....................................................................................................................190
getPageVisibility..................................................................................................................191
getPercentPageViewed.......................................................................................................193
getPreviousValue................................................................................................................195
getQueryParam...................................................................................................................197
getTimeParting....................................................................................................................199
getValOnce..........................................................................................................................201
getVisitNum.........................................................................................................................202
trackTNT..............................................................................................................................203
Traffic props and Conversion eVars...................................................................204
Comparing Props and eVars...............................................................................................204
Using props as Counters.....................................................................................................205
Counting Content Hierarchies.............................................................................................206
What is a Predefined Event?...............................................................................................206
Detailed Product View Page...................................................................................................................207
What is a Custom Event?....................................................................................................208
Pathing..................................................................................................................209
Enabling Pathing on a prop.................................................................................................209
Pathing by Campaign or Tracking Code..............................................................................209
Reasons Pathing may not be Recorded..............................................................................210
Moving from Section to Section...........................................................................................210
Last updated 4/8/2015
Adobe Analytics Implementation
Contents
Moving from Page Template to Page Template...................................................................210
Segmenting Paths by User Type.........................................................................................210
Purchase Events..................................................................................................212
Event Serialization...............................................................................................213
Methods of Event Serialization............................................................................................213
Identifying Unique Visitors.................................................................................216
Custom Visitor ID................................................................................................................216
Marketing Cloud Visitor ID Service......................................................................................217
Analytics Visitor ID..............................................................................................................217
Fallback ID Methods............................................................................................................218
Identifying Mobile Devices...................................................................................................218
Cross-Device Visitor Identification.....................................................................221
Connecting Users Across Devices......................................................................................222
Data Impact of Cross-Device Visitor Identification..............................................................223
Example Visit.......................................................................................................................224
Visitors................................................................................................................................225
Visits....................................................................................................................................226
Segments............................................................................................................................226
Geo-Segmentation Data.....................................................................................................226
Attribution and Persistence.................................................................................................226
Visitor Migration..................................................................................................229
Redirects and Aliases.........................................................................................231
Analytics and Redirects.......................................................................................................231
Implementing Redirects......................................................................................................232
Configure Referrer Override JavaScript Code........................................................................................232
Modify the Redirect Mechanism.............................................................................................................233
Capture the Original Referrer.................................................................................................................233
Last updated 4/8/2015
Adobe Analytics Implementation
Verify the Referrer with the Adobe Debugger.........................................................................................233
FAQ........................................................................................................................235
Contact and Legal Information...........................................................................236
Last updated 4/8/2015
Adobe Analytics Implementation
Adobe Analytics Implementation
11
Adobe Analytics Implementation
This guide contains a description of data collection variables, and details on implementing data collection code in
JavaScript.
AppMeasurement guides for other platforms and Mobile SDKs are available at Developer &amp; Implementation Guides.
The Admin &amp; Analytics Reference provides report and metric descriptions, and admin reference information for
Adobe Analytics.
Documentation Revision History
Date
Description
19 March, 2015
Added information on additional eVars and events.
Added getPageVisibility plug-in.
22 May, 2014
17 April, 2014
s_code version H.27 was released to provide support for the Visitor ID service and the Analytics
for Target integration in the legacy AppMeasurement library.
Support for the Analytics for Target integration.
The Visitor ID service now uses a Marketing Cloud organization ID.
Updated the AppMeasurement Plug-in Support to indicate that the manageVars,
channelManager, getPageName, and Cookie Combining Utility are tested and verified as
compatible.
20 November, 2013
14 November, 2013
14 November, 2013
15 August, 2013
Added support for the Visitor ID service.
Updated Merchandising Variables.
Added Offline Tracking.
Added the getLoadTime plugin. This plugin gets the page load time in tenths of a second and
lets you store the value in a prop, eVar, and/or a numeric event.
Added a description for Max Values to List Variable.
07 June, 2013
Updated transactionID to indicate that transactionIDs should contain alphanumeric characters,
and that multiple transactionIDs should be comma-delimited.
23 May, 2013
Added information on the new desktop and mobile tracking library, About AppMeasurement
for JavaScript.
14 May, 2013
29 April, 2013
Added Data Collection HTTP Headers to describe the request and response headers that are
used during data collection.
In H.26, the useForcedLinkTracking option that is described in Manual Link Tracking Using
Custom Link Code now applies to Firefox 20+ (previously this applied to WebKit browsers
only).
Adobe Analytics Implementation
Date
18 April, 2013
12
Description
tag management 2.0 is now available and is enabled for all Analytics customers.
Single image requests can now contain a 64-bit numeric or currency event values. This
removes the previous limits of 2,147,483,648 for numeric and currency events, and
2,000,000,000 for counter events.
12 March, 2013
Added details on decimal values in Currency/Numeric Events that are in the events list to
events.
28 February, 2013
Added details on how custom links affect Time Spent metrics to AJAX-Tracking Rich Media
Applications.
21 February, 2013
• Added scope limitations for the useForcedLinkTracking option to Manual Link Tracking Using
Custom Link Code.
• Updated pageURL to indicate that the size is no longer limited to 256 bytes.
15 November, 2012 Added maxDelay variable information.
18 October, 2012
6 September, 2012
30 August, 2012
Updated content in events. You can assign numeric integer values to counter events if you
are on H.23 code or higher.
Added List Var and List Prop topics.
Added several additional topics that were previously distributed as white papers:
• Report to Variable Mapping
• Page Naming
• External Email Tracking
• Event Serialization
• AJAX-Tracking Rich Media Applications
• Mobile Tracking over WAP and I-Mode Protocols
• Common Syntax Mistakes
• Report Suite IDs - Dynamic Accounts
• Collecting Data From Form Elements
19 July, 2012
20 April, 2012
Added information on custom link tracking on WebKit browsers introduced in H.25, including
details on the overloaded s.tl() method. See Manual Link Tracking Using Custom Link
Code.
The dc variable is deprecated. You should set trackingServer for all implementations to the
value that is generated by Code Manager in s_code.js.
Added documentation stating that a single image request cannot contain a numeric or currency
event higher than 2,147,483,648, or a counter event higher than 2,000,000,000. Note that
this behavior has not changed, the limits are being documented for clarification.
Added the timestamp variable.
Adobe Analytics Implementation
Date
6 March, 2012
7 October, 2012
13
Description
Added a note to linkInternalFilters stating that you should periodically review partner
contracts to determine if they contain restrictions on link tracking. For example, you might be
prohibited from tracking links that appear in partner display ads.
Added Cross-Device Visitor Identification.
JavaScript Implementation
14
JavaScript Implementation
To begin using Analytics, data must be sent to a report suite to display in reporting. The easiest and most common
way to send data to Analytics is by using JavaScript implementation.
Note: This section describes the legacy method of implementing Analytics. All Analytics customers have
access to Dynamic Tag Management which is the standard method to deploy Marketing Cloud tags.
Marketing Cloud Visitor ID Service
This implementation process describes an Analytics deployment that uses the Marketing Cloud Visitor ID Service.
Before you implement the Visitor ID service, your company must be provisioned for the Marketing Cloud. After your
company is provisioned, you'll receive a Marketing Cloud organization ID that must be provided during Visitor ID
service initialization. See Getting Started with Adobe Marketing Cloud.
Implementation Steps
To successfully implement a page with code to collect data, you must have access to your hosting servers to upload
new content to your website. It is also useful to have an existing site to implement code.
The following steps walk you through a basic Analytics implementation.
Step
Task
Download
AppMeasurement for
JavaScript and the
Visitor ID service.
Description
The download is available in Code Manager.
This download zip contains several files, for now we are concerned only with
AppMeasurement.js and VisitorAPI.js.
Configure the Visitor ID
In VisitorAPI.js, add the following visitor ID initialization code at the beginning
service.
of the file:
var visitor = new Visitor(&quot;INSERT-MCORG-ID-HERE&quot;);
visitor.trackingServer = &quot;INSERT-TRACKING-SERVER-HERE&quot;; // same
as s.trackingServer
visitor.trackingServerSecure =
&quot;INSERT-SECURE-TRACKING-SERVER-HERE&quot;; //same as
s.trackingServerSecure
/*
============== DO NOT ALTER ANYTHING BELOW THIS LINE !
============
• &quot;INSERT-MCORG-ID-HERE&quot; - (Required) This Adobe Marketing Cloud
Organization ID is sent to your administrator when your company is provisioned
for the Adobe Marketing Cloud.
• &quot;INSERT-TRACKING-SERVER-HERE&quot; - (Required) Your Analytics tracking server.
• &quot;INSERT-SECURE-TRACKING-SERVER-HERE&quot; - (Required if ssl is enabled) Your
Analytics secure tracking server.
Update
AppMeasurement.js.
Copy the Example AppMeasurement.js Code and paste it at the beginning of
your AppMeasurement.js file. At a minimum, update the following variables:
• s.account=&quot;INSERT-RSID-HERE&quot;
• s.trackingServer=&quot;INSERT-TRACKING-SERVER-HERE&quot;
• s.visitorNamespace = &quot;INSERT-NAMESPACE-HERE&quot;
JavaScript Implementation
Step
Task
15
Description
• s.visitor = Visitor.getInstance(&quot;INSERT-NAMESPACE-HERE&quot;)
See Correctly populate the trackingServer and trackingServerSecure variable
or contact Client Care if you are unsure about any of these values. If they are
not set correctly, data will not be collected by your implementation.
Host
AppMeasurement.js
and VisitorAPI.js.
Reference
These core JavaScript files must be hosted on a web server that is accessible
to all pages on your site. You need the path to these files in the next step.
Include the Visitor ID Service by adding the following line of code in the &lt;head&gt;
AppMeasurement.js
and VisitorAPI.js on or &lt;body&gt; tag on each page. VisitorAPI.js must be included before
AppMeasurement.js:
all site pages.
&lt;script language=&quot;JavaScript&quot; type=&quot;text/javascript&quot;
src=&quot;http://INSERT-DOMAIN-AND-PATH-TO-CODE-HERE/VisitorAPI.js&quot;&gt;&lt;/script&gt;
Include AppMeasurement for JavaScript by adding the following line of code in
the &lt;head&gt; or &lt;body&gt; tag on each page:
&lt;script language=&quot;JavaScript&quot; type=&quot;text/javascript&quot;
src=&quot;http://INSERT-DOMAIN-AND-PATH-TO-CODE-HERE/AppMeasurement.js&quot;&gt;&lt;/script&gt;
Update and deploy page
Copy the Example Page Code and paste it just after the opening &lt;body&gt; tag
code.
on each page you want to track. At a minimum, update the following variables:
• var s=s_gi(&quot;INSERT-RSID-HERE&quot;)
• s.pageName=&quot;INSERT-NAME-HERE&quot; // for example,
s.pageName=document.title
Use the DigitalPulse
Debugger to verify that
data is being sent.
Install the Adobe Debugger bookmarklet. After it is installed, load a page where
you have deployed page code and then open the debugger. The debugger
displays details about the collection data that was sent.
Caching
The JavaScript file is cached in the visitor's browser after it is initially loaded, and is typically downloaded no more
than once per session. The file is not downloaded on each page, even though it is used by every page on the site.
On most websites, users average more than a few page views per session, so transferring JavaScript that is used
multiple times into this file can result in less overall downloaded data.
JavaScript for AppMeasurement Compression
If you are concerned about page weight (size) of H Code (AppMeasurement for JavaScript 1.0 is pre-compressed),
Adobe recommends that you consider compressing the file using GZIP. GZIP is supported by all major browsers
and offers better performance than JavaScript compression to compress and decompress the core s_code.js
JavaScript file.
The following links help explain how you can use GZIP functionality on your site to handle compression of the
s_code.js JavaScript code:
• http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
JavaScript Implementation
16
• http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/25d2170b-09c0-45fd-8da4-898cf9a7d568.mspx?mfr=true
• http://www.cubicleman.com/2007/04/06/enabling-gzip-compression-with-tomcat-and-flex/
Example Page Code and Global Configuration
This section contains example code for your core JavaScript file and the pages on your site.
Important: This example uses the visitor ID service, which is deployed as part of your JavaScript
Implementation. Enabling the visitor ID service in AppMeasurement before you have included the Visitor API
JavaScript file on all site pages could result in duplicate visitor counts. To avoid duplicate visitor counts, make
sure that you understand and follow the process described in Visitor ID Service.
Example AppMeasurement.js Code
For new implementations, you can paste the following global configuration code at the beginning of
AppMeasurement.js to get started:
//initialize AppMeasurement
var s_account=&quot;INSERT-RSID-HERE&quot;
var s=s_gi(s_account)
/******** VISITOR ID SERVICE CONFIG - REQUIRES VisitorAPI.js ********/
s.visitor=Visitor.getInstance(&quot;INSERT-MCORG-ID-HERE&quot;)
/************************** CONFIG SECTION **************************/
/* You may add or alter any code config here. */
/* Link Tracking Config */
s.trackDownloadLinks=true
s.trackExternalLinks=true
s.trackInlineStats=true
s.linkDownloadFileTypes=&quot;exe,zip,wav,mp3,mov,mpg,avi,wmv,pdf,doc,docx,xls,xlsx,ppt,pptx&quot;
s.linkInternalFilters=&quot;javascript:&quot; //optional: add your internal domain here
s.linkLeaveQueryString=false
s.linkTrackVars=&quot;None&quot;
s.linkTrackEvents=&quot;None&quot;
/* uncomment below to use doPlugins */
/* s.usePlugins=true
function s_doPlugins(s) {
//
//
//
//
use implementation plug-ins that are defined below
in this section. For example, if you copied the append
list plug-in code below, you could call:
s.events=s.apl(s.events,&quot;event1&quot;,&quot;,&quot;,1);
}
s.doPlugins=s_doPlugins */
/* WARNING: Changing any of the below variables will cause drastic
changes to how your visitor data is collected. Changes should only be
made when instructed to do so by your account manager.*/
s.trackingServer=&quot;INSERT-TRACKING-SERVER-HERE&quot;
s.trackingServerSecure=&quot;INSERT-SECURE-TRACKING-SERVER-HERE&quot;
/************************** PLUGINS SECTION *************************/
// copy and paste implementation plug-ins here - See &quot;Implementation Plug-ins&quot; @
// https://marketing.adobe.com/resources/help/en_US/sc/implement/#Implementation_Plugins
// Plug-ins can then be used in the s_doPlugins(s) function above
/****************************** MODULES *****************************/
// copy and paste implementation modules (Media, Integrate) here
JavaScript Implementation
17
// AppMeasurement_Module_Media.js - Media Module, included in AppMeasurement zip
// AppMeasurement_Module_Integrate.js - Integrate Module, included in AppMeasurement zip
/* ============== DO NOT ALTER ANYTHING BELOW THIS LINE ! ===============
Example Page Code
For new implementations, you can paste the following page code just after the opening &lt;body&gt; tag on pages you
want to track:
&lt;script language=&quot;JavaScript&quot; type=&quot;text/javascript&quot;&gt;&lt;!-/* You may give each page an identifying name, server, and channel on
the next lines. */
s.pageName=&quot;&quot;
s.server=&quot;&quot;
s.channel=&quot;&quot;
s.pageType=&quot;&quot;
s.prop1=&quot;&quot;
s.prop2=&quot;&quot;
s.prop3=&quot;&quot;
s.prop4=&quot;&quot;
s.prop5=&quot;&quot;
/* Conversion Variables */
s.campaign=&quot;&quot;
s.state=&quot;&quot;
s.zip=&quot;&quot;
s.events=&quot;&quot;
s.products=&quot;&quot;
s.purchaseID=&quot;&quot;
s.eVar1=&quot;&quot;
s.eVar2=&quot;&quot;
s.eVar3=&quot;&quot;
s.eVar4=&quot;&quot;
s.eVar5=&quot;&quot;
var s_code=s.t();if(s_code)document.write(s_code)//--&gt;&lt;/script&gt;
Make sure that you have also included a reference to AppMeasurement.js and VisitorAPI.js on each page. See
JavaScript Implementation for instructions.
About AppMeasurement for JavaScript
18
About AppMeasurement for JavaScript
AppMeasurement for JavaScript is a new library that provides the same core functionality of s_code.js, but is
lighter and faster for use on both mobile and desktop sites.
Things to know before you migrate
The following list contains changes you need to understand before switching to this new AppMeasurement version:
• Some plug-ins are longer supported. See AppMeasurement Plug-in Support.
• The library does not support dynamic account selection (dynamicAccountList, dynamicAccountMatch, and
dynamicAccountSelection).
• The library and page code can be deployed inside the &lt;head&gt; tag.
• The Media and Integrate modules are supported using updated module code that is in the JavaScript
AppMeasurement download package. The Survey module is not supported.
• Your existing page code is compatible with the new version.
• The library provides native utilities to get query parameters, read and write cookies, and perform advanced link
tracking.
Unsupported browsers
This version drops support for the following browsers:
• IE 4 and 5
• Opera 6 and earlier
Initialization process
Call s_gi(), passing the report suite ID to initialize an AppMeasurement instance:
var s_account=&quot;INSERT-RSID-HERE&quot;
var s=s_gi(s_account)
When s_gi is called, if an AppMeasurement instance does not exist for the specified s_account, a new instance is
created. Otherwise the existing instance is returned. This helps avoid creating duplicate objects for the same account.
You can also create a new AppMeasurement object using the constructor:
s = new AppMeasurement()
s.account=&quot;INSERT-RSID-HERE&quot;
Note that calling new always creates a new object, even if you previously created an instance for the specified
account. Use caution when calling the constructor to avoid creating duplicate instances.
Retrieve an AppMeasurement instance
Throughout your code, call the global s_gi() function to retrieve an existing AppMeasurement instance.
Utilities
JavaScript AppMeasurement provides the following built-in utilities:
• Util.cookieRead
• Util.cookieWrite
• Util.getQueryParam
Clear Vars
A new clearVars method is available to clear the following values from the instance object:
• props
About AppMeasurement for JavaScript
19
• eVars
• hier
• list
• events
• eventList
• products
• productsList
• channel
• purchaseID
• transactionID
• state
• zip
• campaign
For example:
s.clearVars()
Benefits
• 3-7x faster than H.25 code.
• Only 21k uncompressed and 8k gzipped (H.25 code is 33k uncompressed and 13k gzipped).
• Native support for several common plugins ().
• Small and fast enough to be used with mobile sites, and robust enough to be used on the full desktop web, allowing
you to leverage a single library across all web environments.
Migrating to AppMeasurement for JavaScript
The following table contains a list of tasks you need to perform to migrate your implementation.
Note: We recommend migrating to the Visitor ID Service when you migrate to AppMeasurement for JavaScript.
Step
Task
Where
Description
Check plug-in compatibility
s_code.js
Some plug-ins are longer supported. See
AppMeasurement Plug-in Support .
Download the new
AppMeasurement
Admin Console &gt; Code
Manager
Copy your s_code.js
customization to
AppMeasurement.js.
s_code.js and
AppMeasurement.js
(Optional) Update plug-ins
AppMeasurement.js
The download zip contains a minified
AppMeasurement.js file, and Javascript files
for the Media and Integrate modules.
Move all code that appears before the DO NOT
ALTER ANYTHING BELOW THIS LINE section
in s_code.js to the beginning of
AppMeasurement.js.
If you are using the getQueryParam plug-in,
update these calls to use the new utility,
Util.getQueryParam.
About AppMeasurement for JavaScript
Step
20
Task
Where
Description
(Optional) Update Media and
Integrate modules
AppMeasurement.js
If you are using either of these modules, copy
and paste the code from
AppMeasurement_Module_Media.js
and/or
AppMeasurement_Module_Integrate.js
and paste it just before the DO NOT ALTER
ANYTHING BELOW THIS LINE in
AppMeasurement.js.
Deploy new JavaScript
Your website
The new JavaScript file can be deployed
according to your standard process. Your
existing page code is compatible with this
version.
AppMeasurement Plug-in Support
Plug-in support has changed in the new version of JavaScript AppMeasurement.
Tested Plugins
The following plug-ins were tested and verified as compatible:
• appendList
• crossVisitParticipation
• userAgentManager
• getTimeParting
• join
• split
• getDaysSinceLastVisit
• getNewRepeat
• getTimeToComplete
• manageVars (requires s.pt plugin utility)
• channelManager
• Cookie Combining Utility
• getPageName
Untested Plugins
The following plugins should continue to work since the underlying functionality is still supported, but they have not
been tested and verified as compatible. You should test these plug-ins in your development environment before
migration.
• getActionDepth
• getAndPersistValue
• getCookiesAccepted
• getValOnce
About AppMeasurement for JavaScript
21
Unsupported Plugins
These plugins are not supported and no longer function due to their use of functionality that no longer exists in the
new AppMeasurement for JavaScript library.
• callBack
• channelExtract
• detectRIA
• deviceOrientationChanges
• DynamicObjectIDs
• Form Analysis
• manageQueryParam
• HTML5Storage
Additional Web and Mobile Measurement
Libraries
22
Additional Web and Mobile Measurement Libraries
Lists the available measurement libraries.
The following table outlines the libraries available to collect Analytics data across all available platforms. For more
information, see Data Collection in Analytics.
Location
Web Browser
Options
All Marketing Cloud customers have access to dynamic tag management, which is the
standard for deploying JavaScript and HTML page tags for all solutions to your website.
Other ways of implementing JavaScript and HTML measurement are described in the
Analytics Implementation Guide.
Web Server
You can use native PHP and Java libraries on your web server to send analytics data.
The Data Insertion API lets you send XML data directly to the data collection server using
HTTP POST and GET, and Data Sources lets you send delimited hit data directly to
Analytics.
• PHP AppMeasurement
• Java AppMeasurement
• Data Insertion API
• Data Sources
Mobile Device
Native libraries are provided for iOS, Android, Windows Phone 8, Blackberry, Symbian,
and others.
• iOS AppMeasurement 4.x (latest version)
• iOS AppMeasurement 3.x
• Android AppMeasurement 4.x (latest version)
• Android AppMeasurement 3.x
• Windows Phone 8 AppMeasurement 3.x (latest version)
• Blackberry AppMeasurement
• Symbian AppMeasurement
• Silverlight, .NET, XBOX, and Windows Phone 7 AppMeasurement
Flash
Flash apps using ActionScript can be measured on the desktop and on the web.
Flash, Flex, and OSMF AppMeasurement
Desktop
Video
• WinRT for Windows 8 AppMeasurement 3.x (latest version)
• OS X AppMeasurement 3.x (latest version)
• Java AppMeasurement
• Silverlight, .NET, XBOX, and Windows Phone 7 AppMeasurement
Video measurement across all platforms is available in the following guides:
• Heartbeat video measurement (latest version)
• Milestone video measurement
Additional Web and Mobile Measurement
Libraries
23
REST and SOAP Web Services (on Developer Connection)
• Getting Started
• API Documentation Home
Implementing Analytics using HTML image tags
Implement Analytics using an HTML image tag (hardcoded image request).
The browser then requests the image. Data moves with this image request via variables in the query string of the
image request. The JavaScript combines browser-level variables with page-level variables for a comprehensive
data collection solution. In some cases, a fully server-created image tag is appropriate. The standard elements of
a JavaScript-based implementation are listed as follows:
HTML Code
JavaScript Library
This portion consists of JavaScript code that is placed in HTML pages (or
templates) that set the value of JavaScript variables.
This file contains common code that:
• Queries the browser about various properties, such as JavaScript version,
OS version, the size and resolution of monitor being used, and other variables
• Encodes and concatenates all the variables into an image request (&lt;img&gt;)
that transports these variables to the data collection servers. It then references
a JavaScript library file which is loaded and executed.
&lt;noscript&gt; tag
A simplified version of the image request is placed within a &lt;noscript&gt; tag that
executes if the user has disabled JavaScript, or does not have JavaScript
capabilities. This part of the implementation is optional and generally applies
to approximately 2% of the Internet population.
JavaScript can detect browser settings that are not available to a server, such as browser window height/width,
monitor resolution, and Netscape plug-ins. By using a server-side method to create an image tag, these variables
cannot be captured. The JavaScript sets a random number in the image request to overcome browser and proxy
server caching. This allows all page views to be accurately tracked. In certain situations, server-side code has
advantages over the JavaScript-based code, including the following:
• JavaScript is very accurate (98-100%). There are times when the utmost accuracy is desired, even in situations
where a user quickly clicks to another page before the JavaScript has executed. Creating the image tag server-side
increases the accuracy level by several percentage points.
• For tracking conversion events, such as purchases, where accuracy is very important.
• This strategy may also be used to fully populate the image request within the &lt;noscript&gt; tag for tracking users
without JavaScript, or with JavaScript disabled.
Note: The use of server-generated image tags requires additional time to implement, and is more difficult to
debug, deploy, and maintain. Adobe strongly encourages clients to use JavaScript-based data collection on
every page where possible. Various reports and features, including visitor click map, download links, exit links,
and browser-based variables (browser width/height, etc.) cannot be collected or supported using this
implementation method.
Implementing without JavaScript Guidelines
There are additional requirements and configurations for implementing Analytics without JavaScript.
Additional Web and Mobile Measurement
Libraries
24
You can view sample code to further understand the implementation. The following table outlines the additional
requirements and configurations:
Requirement
Description
Case-Sensitive
The parameter names (pageName, purchaseID, and so forth) are
case-sensitive and will not properly record data unless they appear as
designated in the table displayed in .
Encode Query Parameters
The values for each of the query string parameters must be URL encoded.
URL encoding converts characters that are normally illegal when appearing
in a query string, such as a space character, into an encoded character
beginning with %. For example, a space character is converted into %20.
The JavaScript version of this function is called escape (and to decode,
unescape). Microsoft IIS Version 5.0 also includes an Escape and
Unescape function for encoding query strings. Other Web server scripting
languages also provide encoding/decoding utilities.
Maximum Variable Length
Each variable has a maximum length. This length is specified for each
variable in Analytics Variables. Exceeding the maximum length for a
variable causes the value of this variable to be truncated for storage and
display in Analytics.
Invalid Characters
Characters with character codes above decimal 128 are invalid, as are
not-printing character codes under 128. HTML formatting (&quot;&lt;h1&gt;&quot;) is also
invalid, as are trademark, registered trademark, and copyright symbols.
Secure (https:&gt; vs. Non-Secure (http:)
On pages that are accessed via https (secure protocol), the URL portion
Image Requests
of the image request changes to accommodate a different set of data
collection servers.
The following table illustrates the different URLs used for secure and
non-secure image requests.
Protocol
URL
https:
https://namespace.&lt;data
center-specific…&gt;.2o7.net/b/ss/ reportsuite
/1/G.5--NS/…
http:
http://namespace.&lt;data center-specific
URL*&gt;.2O7.net/b/ss/ reportsuite /1/G.5--NS/…
The * in the URL above denotes a data-center specific URL that is provided
to you by your Adobe Consultant. Adobe uses several data centers, and
it is necessary to implement the correct URL your organization has been
assigned. Any code downloaded out of Admin Console within your company
account has the correct data center supplied automatically. Code provided
from external sources may need to be corrected in order to point to the
correct data center.
Additional Web and Mobile Measurement
Libraries
Requirement
25
Description
For clients who use multiple report suites, they should be listed only in the
directory section, and not the domain section of the URL, as shown below.
Protocol
URL
https:
https://102.112.2O7.net/b/ss/ suite1,suite2
/1/G.5--NS/...
http:
http:// suite1 .112.2O7.net/b/ss/ suite1,suite2
/1/G.5--NS/...
The * in the URL above denotes a data-center specific URL that is provided
to you by your Adobe Consultant. Adobe uses several data centers, and
it is necessary to implement the correct URL to which your organization
has been assigned.
URL and Referring URL
The URL and Referring URL may be populated from the server in the g=
and r= variables. Use the Request ServerVariables (HTTP_REFERRER)
or Request ServerVariables (URL) (IIS/ASP), or the appropriate variable
for your server/scripting technology. The referring URL (r=) is extremely
important for tracking referring URLs, domains, search engines, and search
terms.
If pageName is not being used, it is imperative that the Current URL field
is uniquely populated. If neither pageName nor Current URL (g=) is
populated, the record is invalid and is not processed. At a minimum, the
URL is a required field in order to process the record.
Effects of Caching
HTML and other Web pages can be cached by browsers or servers that
are between the visitor and the website that is serving the content. Caching
prevents an accurate count of page views and other events unless a
&quot;cache-busting' technique is employed.
Adobe's standard JavaScript includes a dynamic method of changing the
image request to avoid page and image caching, allowing an accurate
count of page views.
However, in creating a server-side image request, this randomization does
not occur. Page reloads and cached pages (either in the browser's cache
or in a proxy server) are not counted in certain cases when using
server-side image requests.
SSL (https:) pages are not, by definition, ever cached so this warning
applies only to non-secure (http:) pages. Additionally, pages with
parameters (http://www.samplesite.com/page.asp?parameter=1)
or certain file extensions (.asp, .jsp, etc.) are also not cached.
The examples below also illustrate a minimal JavaScript solution that
primarily assembles the image request server-side, and tacks on a random
number in the browser. This method overcomes the caching that would
Additional Web and Mobile Measurement
Libraries
26
Requirement
Description
otherwise be encountered on static HTML pages accessed via the http:
protocol.
nameSpace Variable
The nameSpace query string parameter is required for non-JavaScript
implementations.
Example: ns=nameSpace
Contact your Adobe Consultant or Account Manager to obtain your
organization's nameSpace value.
Sample Code
Examples to illustrate the use of a server-generated image tag within a HTML sample page.
The table below displays the values used in the sample.
Variable
Value
pageName
Order Confirmation
Current URL
https://www.somesite.com/cart/confirmation.asp
events
purchase,event1
c1
Registered
purchaseID
0123456
products
Books;Book Name;1;19.95
state
CA
zip
90210
a random #
123456
Example 1
The example below displays a server-side image tag. The highlighted random number prevents caching of the
image.
&lt;html&gt;
&lt;head&gt;
&lt;/head&gt;
&lt;body&gt;
Order Confirmation&lt;br&gt;
Thanks for your order #0123456.
&lt;img src=&quot;https://102.112.2O7.net/b/ss/suite1,suite2/1/G.4--NS/123456?pageName=Order%20
Confirmation&amp;events=purchase%2Cevent1&amp;c1=Registered&amp;purchaseID=0123456&amp;products=Books%3BBook%20Name%3B1%3B19.95&amp;state=CA&amp;zip=90210&amp;g=https%3A//www.somesite.com/cart/confirmation.asp&quot;
width=&quot;1&quot; height=&quot;1&quot; border=&quot;0&quot; /&gt;
&lt;/body&gt;
&lt;/html&gt;
Example 2
The example below shows a minimal JavaScript image tag.
&lt;html&gt;
&lt;head&gt;
Additional Web and Mobile Measurement
Libraries
27
&lt;/head&gt;
&lt;body&gt;
Order Confirmation&lt;br&gt;
Thanks for your order #0123456.
&lt;script language=&quot;javascript&quot;&gt;&lt;!—
s.s_date = new Date();
s.s_rdm = s.s_date.getTime();
s.s_desturl=&quot;&lt;img width=\&quot;1\&quot; height=\&quot;1\&quot;
src=\&quot;https://102.112.2O7.net/b/ss/suite1,suite2/1/G.4--NS/&quot; + s.s_rdm +
&quot;?pageName=Order%20Confirmation&amp;events=purchase%2Cevent1&amp;c1=Registered
&amp;purchaseID=0123456&amp;products=Books%3BBook%20Name%3B1%3B19.95&amp;state=CA&amp;zip=90210&amp;g=http
s%3A//www.somesite.com/cart/confirmation.asp\&quot;&gt;&quot;;
document.write(s.s_desturl);
//--&gt;&lt;/script&gt;
&lt;/body&gt;
&lt;/html&gt;
Mobile Tracking over WAP and I-Mode Protocols
This section describes the tracking methodology for legacy mobile devices that do not use http browsers.
Mobile Network Protocols
WAP and I-Mode are the two major protocols or standards used today. WAP is mostly used in the US, and I-Mode
is popular in Japan and Europe.
Sites must often be designed separately for different protocols. The Adobe image tag does not need to be customized
for each protocol.
WAP 1.0
WAP 1.0 is quickly losing popularity in the US. This required pages be built in WML, and had
its own protocol.
WAP 2.0
Most phones are WAP 2.0 compliant, meaning they support XHTML MP (a mobile version of
XHTML).
I-Mode
I-Mode supports CHTML (compact HTML) and does not download third-party images. First-party
collection domain implementations should always be used with I-Mode sites so images are
downloaded.
Mobile Protocol Network Gateway
When a mobile device requests a page from a Web server, the request is sent through a gateway, which converts
the mobile request (usually in the WAP or I-Mode protocol) into an HTTP request that is sent to a Web server.
When a mobile device requests a page from a Web server, the request is sent through a gateway, which converts
the mobile request (usually in the WAP or I-Mode protocol) into an HTTP request that is sent to a Web server. The
Web server responds to the gateway, which forwards the request to the phone. This gateway acts much like a
standard proxy server. The gateway does, however, pass the user agent string of the mobile device on to the Web
server. This lets the Web server respond with a page that is built specifically for the device requesting it.
Because screen size on WAP mobile devices is so limited, mobile pages are very light, often containing only text
and one cached image. When the image tag is added to the pages, a request is sent on every page for an image
from Adobe servers. When the image, a WBMP, is returned, Adobe servers instruct the browser not to cache it.
Consequently, the image is requested again on subsequent pages. The random number described above should
be used to protect against browsers that do not obey the Adobe no-cache directives.
Additional Web and Mobile Measurement
Libraries
28
Tagging Pages For Mobile Protocols
Mobile tracking code is placed on the page in the form of a server-generated image tag.
Mobile tracking code is placed on the page in the form of a server-generated image tag. Because scripting languages
like JavaScript and WMLScript are not generally supported across mobile devices, the tracking beacon cannot be
generated dynamically via a scripting language.
&middot; While the mobile beacon image is actually 2x2 pixels, to ensure support for all mobile devices, you should set
height and width properties to 5. For example:
&lt;img sr c=&quot;http://metric.mydomain.com/b/ss/&lt;Report_Suite_Name&gt;/5/&lt;random_number&gt;?pageName=&quot;
alt=&quot;&quot; width=&quot;5&quot; height=&quot;5&quot;/&gt;
Use a Random Number to Prevent Caching
While Adobe servers instruct browsers not to cache the tracking beacon, not all browsers are guaranteed to follow
those instructions. To further prevent caching of the beacon, it is recommended that the Web server dynamically
generate a random number in the image URL path. Doing so insures greater accuracy of reporting. The random
number should be in the last section of the path, as shown here:
&lt;img src=&quot;http://rsid.112.2O7.net/b/ss/rsid/5/H.5--WAP/12345?pageName=&quot; /&gt;.
Include an ALT Tag
Some mobile browsers require that all images have alt text included in the image tag. The following shows how the
ALT attribute should appear in the image tag:
&lt;img src=&quot;http://rsid.112.2O7.net/b/ss/rsid/5/H.5--WAP/12345?pageName=&quot; alt=&quot;&quot;/&gt;.
It is important that the /5/ always appears correctly in the path. This is used by Adobe servers to identify mobile
devices. If the standard /1/ is used, Adobe servers attempt to set a cookie on the mobile device.
Change the Default Image Type
If the default image type is not supported on a particular device, no data is returned. To avoid this, you can force
the Adobe data collection server to return a particular graphic type that the mobile device supports. The code following
the report suite name specifies the image type:
• /5/ returns the default image type.
• /5.1/ or /1/ always returns a GIF image.
• /5.5/ always returns a WBMP image.
SeeIdentifying Mobile Devices.
Reports for Devices Using Mobile Protocols
Because mobile devices are tracked via a beacon, just like other visitors, most reports are available and correct.
VISTA can be used to alter data collected from both Mobile and standard methods. All CustomInsight (prop and
eVar), Event, Site Traffic, and Pathing reports are supported.
Additional Web and Mobile Measurement
Libraries
29
Search Engines, Search Keywords, Referring Domains, and Referrers
These reports only have data if the referrer is populated in the image request sent from the mobile page. The referrer
is populated via the &quot;r&quot; query string parameter, as outlined in the Implementing without JavaScript white paper. You
must also manually pass the referrer information into the image request.
The ‘r’ query string parameter must include the protocol of the referrer. If the protocol is left off, the referrer report
is not populated. For example, use r=http://msn.com not r=msn.com.
Geosegmentation and Domains
Geosegmentation reports are based on the IP address of the device sending the request. Because mobile devices
rely on a gateway to request images from Adobe servers, the gateway's IP address is used to determine the
geo-location of the user. Because gateways and their IP addresses are registered for large networks, the associated
geo-location is often less accurate.
Domains are also based on the IP address of the gateway, which means the domains report often contains the name
of the carrier who owns the gateway. Due to Mobile Virtual Network Operators (MVNOs), this may not be accurate.
Connection Types
Adobe maintains a known range of IP addresses that belong to mobile carriers. When a hit is received from an IP
range that belongs to a known mobile carrier, the hit appears as &quot;Mobile Carrier&quot; on the Connection Type Report.
Otherwise, mobile traffic is listed under &quot;Lan/Wifi&quot;.
Time Zones, Cookies, Java, JavaScript, Monitor Colors and Resolutions, Browser Width and Height, and
Netscape Plug-ins
These reports are all collected by using JavaScript to detect specific settings of the browser. Because JavaScript
is not used to create the image beacon on mobile devices, data collected from mobile users is not included in these
reports.
Custom Link Measurement on Mobile Protocols
Many mobile device users download files to their devices such as podcasts, ring tones, and similar files. Because
many mobile devices do not support JavaScript, link measurement must be implemented through redirects. To use
redirects, you must modify the href links in the html to include the REDIR element. The general format for a custom
link is as follows:
http://&lt;your_Namespace&gt;.112.2o7.net/b/ss/&lt;RSID&gt;/4/REDIR/
?url=&lt;destination_URL&gt;&amp;pe=&lt;link_type&gt;&amp;pev1=&lt;current_URL&gt;&amp;pev2=&lt;link_name&gt;
Keep in mind the following when creating link reference:
• The URL value must be URL encoded.
• You should set a pageName or page URL (g) parameter.
• Dynamic variables can read the URL parameter but not set it.
• If no cookie is set, Adobe servers perform a normal cookie handshake.
• To track links, you must include pe, pev1, and pev2 parameters.
A custom link measurement URL looks similar to the following:
&lt;a href=&quot; http://johnny_appleseed.122.2o7.net/b/ss/appleseedpodcasts/4/REDIR/
?url=http%3A%2F%2Fwww.johnny_appleseed.org%2Fmpegs%2Fplanting_apple_trees.mpeg&amp;pe=lnk_d
&amp;pev1=http%3A%2F%2Fwww.johnny_appleseed.org%2Fmpegs%2Fplanting_apple_trees.mpeg&amp;pev2=pl
anting_apple_trees&amp;&quot;&gt;Planting an Apple Tree&lt;/a&gt;
Additional Web and Mobile Measurement
Libraries
30
Tag management 2.0
Note: This section describes the legacy tag management method of implementing Analytics. All Analytics
customers have access to Dynamic Tag Management which is the standard method to deploy Marketing Cloud
tags.
Adobe Tag Manager provides a tag management framework that serves as a tag container, housing the tags that
an Adobe customer may require, including Adobe Marketing Cloud tags and third-party tags.This simplicity accelerates
time to deployment versus standalone tag management products, which require more significant changes and
resources to implement.
The tags within the container are managed through an administrative user interface where the customer can insert
or remove tags (from Adobe or other partners) without making changes to a website. The ability to rapidly add and
remove tags combined with common techniques to conditionally fire or timeout tags gives advertisers and publishers
more control over their valuable data and helps manage pages for fast loading.
Tag management Documentation Revision History
Revision Date
Description
April 18, 2013
Initial tag management 2.0 release.
Tag management Architecture
This section describes the architecture of tag management and changes to the architecture from version 1.0.
Before tag management, an Analytics implementation included a JavaScript file that you hosted on your website,
called s_code.js. Each page included a snippet of code that leveraged this core JavaScript file. When updates
were released or if you wanted to use an additional module or plug-in, the JavaScript file had to be updated. Target,
AudienceManager, and other products used a similar process.
With tag management, you now place a snippet of code on your pages, and all tags are loaded directly from tag
management, including any core JavaScript required. Tag updates and new tag deployments are managed in the
tag management UI.
Additional Web and Mobile Measurement
Libraries
31
Tag management architecture includes the following:
• New, product-agnostic page code for invoking the tag loader and tag containers.
• A fully-hosted tag loader on an Adobe-managed CDN (Akamai), with built-in availability safeguards to prevent
errors. You are not required to host any JavaScript on your web server.
• Support for Targetmbox.js and global mbox deployment.
• Optional synchronous loading alongside the asynchronous container.
• Controls for managing the execution of on-page function calls.
• Enhanced rule building functionality to control tag firing, including reusable rules and support for regular expressions.
• Backwards compatibility with current Tag management page code and containers.
Changes from tag management 1.0
Version 2.0 of tag management includes significant changes to the architecture of the tool.
Tag management 1.0 leveraged existing script tagging and page code from legacy Analytics implementations. Tag
management 1.0 replaced the contents of the s_code.js file with a tag container. This architecture simplified
deployment since page code updates weren't required, but it had several limitations.
In tag management 2.0, the loader and tag containers are hosted on the Adobe CDN and are managed by tag
management. To deploy tag management 2.0, you must update the page code on your pages. With these changes,
you can deploy multiple Adobe Marketing Cloud products with the same page code and are enabled to quickly deploy
new functionality when it is added to the product.
Tag Container Environments
Tag management provides a dev, stage, and live environment for each tag container. Each environment has a
separate current version and revision history.
Tag management uses the same page code for each environment. This lets you test multiple code versions on the
same site without requiring page-level changes. You can use these environments to align with your existing release
process. For example, your development team can use the dev version of the tag container to test changes directly
on your live site without impacting the live version.
Selecting the Tag Container Environment
When you load a page that includes the tag loader, an attempt is made to load the current live version of the tag
container. To instruct the tag loader to retrieve the version from the stage or dev environment, you can set a cookie
in your browser that instructs the JavaScript tag loader to retrieve a different version:
Additional Web and Mobile Measurement
Libraries
32
The cookie can be set using the bookmarklets available in the tag management interface. If your browser does not
support adding the bookmarklet, you can manually create a bookmark by copying and pasting the URL:
javascript:document.cookie='s_tagEnv=dev;%20path=/';void(0)
These bookmarklets can be used to quickly switch between the current versions in each environment.
Setting the Dev Cookie to Test a New Tag Container
When you create a tag container, a version is initially created in the dev environment only. There is no version of
this tag container deployed to the stage or production environments:
If you browse to a site that includes the tag loader without setting the dev cookie, an attempt is made to load the
live version. Since there isn't a version in live, the tag container is not found and the loader fails gracefully.
If a tag container fails to load make sure the dev cookie is set correctly or that you have promoted a live version of
the tag container.
Tag Processing Order
By default, most tag management tags are executed asynchronously. This provides a number of performance
benefits, since your page continues to load while tags execute. However, there are some cases where you need to
load and execute a tag synchronously, such as with an implementation of Adobe Target. Synchronous loading was
added as an option in tag management 2.0 to provide for this use case.
Additional Web and Mobile Measurement
Libraries
33
When a page loads, tag management inserts all synchronous tags defined in a tag container at the location of the
page code, which should be placed directly after the opening &lt;body&gt; tag.
These synchronous tags are executed in order in the main processing thread. Asynchronous tags are executed in
separate threads, and multiple asynchronous scripts might be executed in parallel depending on the browser.
For example, in the previous diagram, synchronous tag 1 executes before synchronous tag 2. Asynchronous tags
can be executed in any order, depending on how long they take to execute and the processing architecture of the
browser. In the previous diagram, asynchronous tag 2 might complete before asynchronous tag 1, but might complete
after synchronous tag 2.
Product Tag On Load
Each product tag provides an On Load section in the UI. Code placed in this section is executed after the tag loads.
If you need more control over tag execution, you can also execute code based on tag events. See amc.on Tag Event
Callbacks.
Tag management Quick Start
This section contains an overview of the tasks required to deploy tag management.
Step
Task
Step 1
Create a New Container
Step 2
Define Tags
Step 3
Copy Environment Bookmarklets
Location
Tag management
UI
Description
Define a tag container to provide analytics on
your website.
Tag management
UI
Add support for products, Genesis
integrations, and affiliate beacons to the tag
container.
Tag management
UI
Save bookmarklets that let you switch between
the dev, state, and live environments to test
your tag container.
Additional Web and Mobile Measurement
Libraries
34
Step
Task
Location
Description
Step 4
Include the Page Code on Site
Pages
Your website
Add tag management page code to each page
on your website.
Step 5
Test and Promote Revisions
Tag management
UI
Set up your workflow to test and promote tag
container versions.
Create a New Container
The first step is to define a tag container in the Admin interface. A tag container is associated with a digital property.
See Create a tag container for detailed instructions.
Define Tags
After you create a new tag container, the Edit Tags page displays. This page is where you add product tags and
add any custom code.
Keep the following key concepts in mind as you create and deploy a tag container:
• Tag containers are hosted on a CDN. Each time a new revision is deployed it takes several minutes to propagate
to the edge nodes.
• Tag Containers are optimized to use asynchronous loading where possible to improve performance. If variables
are not being populated or resources are not being found, make sure the code is inserted in the correct location
or if necessary, switch to synchronous loading.
• Each tag container has a dev, stage, and live environment. New tag containers are created with a dev version
only. You must set a cookie to load the dev version. See Tag Container Environments.
For details on product deployment, see Marketing Cloud Deployment.
If you are an existing Analytics, Target, or Media Optimizer customer migrating to tag management, see Migrating
to tag management 2.0 from a Legacy Implementation.
If you are an existing tag management 1.0 customer migrating to tag management 2.0, see Migrating to tag
management 2.0 from tag management 1.0.
Additional Web and Mobile Measurement
Libraries
35
Copy Environment Bookmarklets
To test each version of the tag as it moves from dev, stage, and live, copy the bookmarklets from the Environment
Overview page. SeeTag Container Environments for additional details.
Include the Page Code on Site Pages
Place the page code directly after the &lt;body&gt; tag on site pages.
Variables and other properties are set in the UI in the Tag Code or in the On Load section of the tag container. If
you include code that is dependent on tag code outside of the tag manager interface, code must be wrapped in
amc.on Tag Event Callbacks.
&lt;!-- example, do not copy - each tag container has unique page code -- &gt;
&lt;!-- Adobe Marketing Cloud Tag Loader Code
Copyright 1996-2013 Adobe, Inc. All Rights Reserved
More info available at http://www.adobe.com/solutions/digital-marketing.html --&gt;
&lt;script type=&quot;text/javascript&quot;&gt;//&lt;![CDATA[
var amc=amc||{};if(!amc.on){amc.on=amc.call=function(){}};
document.write(&quot;&lt;scr&quot;+&quot;ipt type=\&quot;text/javascript\&quot;
src=\&quot;http://www.adobetag.com/d1/v2/amc.js\&quot;&gt;&lt;/sc&quot;+&quot;ript&gt;&quot;);
//]]&gt;&lt;/script&gt;
&lt;!-- End Adobe Marketing Cloud Tag Loader Code --&gt;
The custom page code for each Tag Container is available in the interface by clicking Get Page Code.
Test and Promote Revisions
When you are ready, use the links in the Actions column to copy a revision to the next environment. The current
version in Live Environment is sent to users when they view a page that includes the tag loader.
Create a tag container
A tag container is associated with a digital property.
Note: Tag Containers cannot be deleted or renamed after they are created.
1. Start tag management.
Additional Web and Mobile Measurement
Libraries
36
2. Click Create New Container.
3. (Optional) Assign group access to the new container. All groups that have tag management Environment
Privileges are displayed in the Container Groups Access list. If a group is selected, the container is added to
the list of containers to which the users in that group receive the access defined by Environment Privileges.
For example, if the &quot;TM Devs&quot; group has Development privileges and that group is selected on this screen,
members are granted Development access to the new tag container.
Container access can be assigned or modified at any time. See Tag management Permissions.
4. On the Container Environment Overview page, click Create to create an initial version in the Development
environment.
See Tag Container Environments.
5. On the Edit Tags page, define tags to deploy Marketing Cloud products.
See Marketing Cloud Deployment.
6. Click Save and Deploy, or click Save and deploy the container at a later time from the Container Environment
Overview page.
Check the Status column for confirmation that the container was deployed.
Migrating to tag management 2.0 from tag management 1.0
Tag management provides a migration wizard and tag backward compatibility to help migrate from tag management
1.0.
The migration process is designed to keep your live tag management 1.0 implementation operational throughout
the migration. The following table contains details on each of the migration steps:
Step
Step 1
Step 2
Task
Location
Upgrade the Tag Container
Tag
Manager UI Start the tag container Migration Wizard.
Update Page Code
Your website
Description
The tag management 2.0 page code is backward
compatible with 1.0 tag containers.
During the migration, your live 1.0 tag container and
development 2.0 tag container can use the same 2.0 page
code. This lets you migrate your page code first, then test
Additional Web and Mobile Measurement
Libraries
Step
Task
37
Location
Description
and deploy a 2.0 tag container without disrupting your live
implementation.
Step 3
Step 4
Step 5
Create a 2.0 Revision
Deploy and Test
Promote to Live
Tag
Manager UI Create a 2.0 revision of the tag container and migrate your
tags. See 1.0 to 2.0 Tag Mapping.
Your website
Deploy and test the 2.0 tag container in the dev and stage
environments to make sure everything works correctly.
Tag
Manager UI When testing is complete, promote the 2.0 tag container
to the live environment.
The tag management 1.0 guide is available for reference during your migration.
Upgrade the Tag Container
Edit your 1.0 tag container, and under the Upgrade to tag management 2.0 heading, click the Upgrade this
Container button. This starts the Migration Wizard.
Update Page Code
Important: Do not edit the page code in your live environment until you have completed Step 5 and have
deployed a 2.0 tag container to live and verified the deployment status.
Replace your existing 1.0 page code with the 2.0 page code in a dev environment. The 2.0 page code should be
inserted directly after the opening &lt;body&gt; tag. For now, the 2.0 page code continues to reference the 1.0 tag container.
After the new page code is deployed, click the I have deployed the Page Code button.
Create a 2.0 Revision
After the page code is deployed, click Create Revision. This creates a new 2.0 tag container in the dev environment.
Your live 1.0 tag container continues to operate in the live environment.
Additional Web and Mobile Measurement
Libraries
38
Because of the new structure of tag management 2.0 containers, you need to recreate your 1.0 tags using 2.0 tags.
See 1.0 to 2.0 Tag Mapping.
Deploy and Test
Deploy and test the 2.0 tag container in the dev and stage environments to make sure everything works correctly.
Promote to Live
When testing is complete, promote the 2.0 tag container to the live environment. After you have verified that the tag
container is deployed to live, you can update the page code in your live environment.
1.0 to 2.0 Tag Mapping
This section describes how to migrate from each tag management 1.0 tag to a tag management 2.0 tag.
Custom Core Javascript
1.0 Custom Core 2.0 Tag
Javascript Tag
Custom Core
Javascript
JavaScript or Remote
Script
Migration Instructions
Insert a Custom Code Javascript tag and paste the code directly
into this tag. This tag should appear before any product tags that
depend on functionality defined in this tag.
(optional) Tag management 2.0 adds the ability to load remote scripts
before products. Depending on the size of the code in this section,
you might consider moving it to an external file and then referencing
it using a remote script tag instead. If so, insert a Custom Code
Remote Script tag instead and select the synchronous option.
Product Code
1.0 Product Code 2.0 Tag
Tag
SiteCatalyst
Adobe Analytics
SiteCatalyst &gt;
Survey
Adobe Analytics &gt; Survey
Migration Instructions
Copy all of the code from the 1.0 SiteCatalyst Tag Code section to
the 2.0 Analytics Tag Code section.
Copy all of the code from the 1.0 Survey Tag Code section to the
2.0 Survey Tag Code section.
Additional Web and Mobile Measurement
Libraries
1.0 Product Code 2.0 Tag
Tag
SiteCatalyst &gt;
Video Tracking
Adobe Analytics &gt; Video
SiteCatalyst &gt; *
Adobe Analytics &gt;
Integrate Module
Genesis
Integrations
39
Migration Instructions
Copy all of the code from the 1.0 Video Tracking Tag Code section
to the 2.0 Video Tag Code section.
Insert any additional tags under the Analytics product or in the
Genesis Integrations section using the Integrate Module tag.
For each tag, insert a new Integrate Module tag and set the
Description field equal to the integration name set in the
Integrate.add call:
s.Integrate.add(&quot;DFA&quot;)
Copy all of the code from the 1.0 tag to the 2.0 tag.
Target
Adobe Target
Insert a new 2.0 Target tag and provide your client code when
prompted.
Locate the mboxOnLoad function in your 1.0 Target tag. Copy the
contents of this function to the matching function in the On Load
section of the 2.0 tag.
Note: Do not overwrite the entire On Load section as the 2.0
tag contains some syntax differences.
Demdex
AudienceManager
The 2.0 AudienceManager tag delivers the required JavaScript library
and plug-ins for Audience Manager.
Copy your implementation code from the 1.0 Demdex Tag Code
section to the 2.0 AudienceManager Tag Code section.
Custom Code (after products)
1.0 Custom Code 2.0 Tag
Tag
HTML
HTML
Javascript
Javascript
Image Beacon
HTML
Remote
JavaScript
Remote Script
Migration Instructions
Copy all of the code from the 1.0 tag to the 2.0 tag and recreate the
Firing Rules.
Copy all of the code from the 1.0 tag to the 2.0 tag and recreate the
Firing Rules.
Copy the image URL from the 1.0 tag, then insert an &lt;img&gt; tag into
an HTML tag and recreate the Firing Rules.
Copy all of the code from the 1.0 tag to the 2.0 tag and recreate the
Firing Rules.
Additional Web and Mobile Measurement
Libraries
1.0 Custom Code 2.0 Tag
Tag
IFrame
IFrame
40
Migration Instructions
Copy all of the code from the 1.0 tag to the 2.0 tag and recreate the
Firing Rules.
Migrating to tag management 2.0 from a Legacy Implementation
The following process describes the steps required to migrate from a legacy implementation to tag management.
If you are currently using tag management 1.0, see Migrating to tag management 2.0 from tag management 1.0.
Step
Task
Location
Description
Step 1
Tag management Quick
Start
Tag
Create a new tag container and deploy it in a
management development environment. Add the tag management
UI
page code to some pages in a development
environment, but do not make any changes to your
live site.
Step 2
Migrate Legacy
Implementation Code
Tag
Migrate your legacy implementation code to tags. See
management Legacy Implementation to Tag Mapping.
UI
Step 3
Ensure Tag Availability
Tag
Update your implementation to leverage asynchronous
management tag loading.
UI
Step 4
Promote a Live Version
Tag
Deploy and test the tag container to make sure
management everything works correctly. When testing is complete,
UI
promote a tag container to the live environment.
Step 5
Update Live Page Code
Your
website
Replace the current page code on your live site with
the updated tag management 2.0 page code.
Migrate Legacy Implementation Code
Migrate your legacy implementation code to tags. See Legacy Implementation to Tag Mapping.
Ensure Tag Availability
If you have a legacy implementation with all variables set in the page code section, tag management migration is
straightforward.
The biggest barrier existing customers face when migrating to tag management 2.0 are references to the s object
within the page itself and within external JavaScript files. Since tag management leverages asynchronous loading
for enhanced performance, you might need to modify how you interact with the s object since you can't guarantee
it is available as the page loads. This also prevents JavaScript errors in the rare case that the CDN is unavailable.
If you need to interact with the s object within the page, for example when a link is clicked or other content is loaded,
use one of the following options:
Attach an Event Handler in tag management
Additional Web and Mobile Measurement
Libraries
41
Instead of placing AppMeasurement for JavaScript code directly in the page, you can place amc.on Tag Event
Callbacks directly in the tag management UI. For example, to track the following custom exit link:
&lt;a href=&quot;http://anothersite.com&quot; id=&quot;linkExit1&quot;&gt;
The following code is added in the On Load section of the Site Catalyst component :
amc.on('domcontentloaded', function () {
var link = document.getElementById('linkExit1');
link.onclick = function() {
s.tl(this,'e','AnotherSite',null,'navigate'); return false;
}
});
When the DOM is loaded and this callback is executed, this code retrieves the link using the ID and attaches the
s.tl call to the link click event.
If you need advanced functionality, you could use a jQuery or similar loop to add similar tracking code to all links on
the page.
Wrap the Code Directly in an amc.on Callback
If you have only a few locations where you need to interact with the s object, you can wrap calls directly in a callback:
&lt;a href=&quot;http://anothersite.com&quot; onclick=&quot;var scope=this; amc.on('tagload.analytics',function()
{s.tl(scope,'e','AnotherSite',null,'navigate'); }); return false;&quot;&gt;
The &lt;a&gt; object is stored in a variable named scope, which is passed to the s.tl function. When the Analytics tag
is loaded, the event handler is attached.
Aside from the code management difficulties, the biggest drawback is that this link won't function in the rare case
that the tag container can't be loaded from the CDN. For situations where tag unavailabilty prevents interaction with
the page, we recommend adding the event handler in tag management.
Promote a Live Version
Deploy and test the tag container to make sure everything works correctly. When testing is complete, promote a tag
container to the live environment.
Update Live Page Code
Replace current page code on your live site with the updated tag management 2.0 page code.
Legacy Implementation to Tag Mapping
This section describes how to migrate code from a legacy implementation to a tag management 2.0 tag.
Additional Web and Mobile Measurement
Libraries
42
Description
Current Code
Tag
Action
External
JavaScript
Libraries
Remote Script External JavaScript libraries
&lt;script
src=&quot;http://mysite.com/scripts/utilities.js&quot;
are placed in a remote Script
type=&quot;text/javascript&quot;&gt;&lt;/script&gt;
tag. If other tags depend on
this library, select
synchronous and place it
before any dependent tags.
Target
var
mboxServerHost='omniture.tt.omtrdc.net;'
(function mboxOnLoad() {
Target
//place code here that will
//run after Target is loaded
Add a Target tag, provide
your client code, and then add
code to execute after Target
is loaded.
})();
SiteCatalyst
Code
var s_account=&quot;rs&quot;
var s=s_gi(s_account)
s.debugTracking=false
s.charSet = &quot;UTF-8&quot;
...
s.linkTrackEvents=&quot;None&quot;
Adobe
Insert an Analytics tag, and
Analytics &gt;
reporting and replace the generated code in
the tag with the code from
analytics
your current page code and
s_code.js.
The Analytics tag in the tag
management UI matches the
structure of your existing
Analytics page code, and your
configuration can be copied
straight to the Tag Code
section of the Analytics tag.
Plugins
s.usePlugins=true
function s_doPlugins(s) {
/* Add usage of plugins here */
}
s.doPlugins=s_doPlugins
Adobe
Analytics &gt;
reporting and
analytics
Overwrite the default plugins
code that is generated in the
Analytics Product Code
section with your current
plugins code.
Survey
s.loadModule(&quot;Survey&quot;)
Adobe
Analytics &gt;
reporting and
analytics &gt;
Survey
Insert a Survey tag, and then
overwrite the default code with
your current Survey module
code.
Media Module s.loadModule(&quot;Media&quot;)
Adobe
Analytics &gt;
reporting and
analytics &gt;
Video
Insert a Video tag, and then
overwrite the default code with
your current Media module
code.
Genesis
Integrations
Adobe
Analytics &gt;
reporting and
analytics &gt;
Integrate
Module
s.Integrate.add(&quot;DFA&quot;);
For each integration, insert a
Integrate Module tag and set
the Description field equal to
the integration name set in the
Integrate.add call:
Additional Web and Mobile Measurement
Libraries
Description
Current Code
43
Tag
Action
s.Integrate.add(&quot;DFA&quot;)
Copy your current integration
code to the Tag Code section.
Marketing Cloud Deployment
Marketing Cloud products are added by selecting the product in the Add Product or Code drop-down list when
editing a tag container.
Analytics
Analytics implementations though tag management support all of the variables and functions available with a legacy
implementation.
For detailed information on implementing Analytics, see the Analytics Implementation Guide.
Setting
Description
Accounts
Select one or more report suites to receive the data that is sent by this tag.
Secure Server
(Optional) If you have a secure server URL, provide it here. Leave it blank to default to
the non-secure server URL.
Character Set
Select the character set used by your report suite.
Currency Code
Select the currency code used by your report suite.
Instance Variable
If your instance variable name has changed from the default, provide the new variable
name.
When a new version of AppMeasurement for JavaScript is release, you are prompted to upgrade the next time you
edit.
JavaScript Video Measurement
Video measurement code is placed in the code block in the Video Tracking section.
Implementation details on measuring video are included in the Measuring Video in Analytics guide.
Survey
Integration with Survey is provided through the Survey module. After you add the module, you can define any
additional settings required by your implementation.
See Standard Survey Implementations on the Web.
s.loadModule(&quot;Survey&quot;)
var s_sv_dynamic_root = &quot;delivery.d1.sv.omtrdc.net/survey/dynamic&quot;
var s_sv_gather_root = &quot;collection.d1.sv.omtrdc.net/survey/gather&quot;
Target
Provide your client id when prompted. The necessary dependencies, such as mbox.js are delivered automatically.
You can use the On Load field to deliver a global mbox at the top of the page. You can also leverage amc.on to
control the execution of on-page mbox create function calls.
Additional Web and Mobile Measurement
Libraries
44
AudienceManager
The Audience Manager tag delivers the required JavaScript library and plug-ins for Audience Manager.
After adding this tag, place your implementation code in the On Load section of the tag.
Custom Tag Deployment
Third-party and custom tags are deployed using custom code sections.
Custom code tags can be conditionally executed.
HTML
HTML custom code tags are typically used to deploy third-party tags that use &lt;img&gt;, &lt;script&gt;, or &lt;iframe&gt; elements.
All HTML elements defined in an HTML custom code tag, with the exception of Document.write() in &lt;script&gt;
elements, are appended to the page.
Since you can't specify a location to append tags, custom code tags should not be used to change page content.
JavaScript
JavaScript custom code tags contain a snippet of JavaScript code.
Code in a JavaScript tag is executed synchronously. Functions and other code in these sections cannot be used in
the &lt;head&gt; element on the page since that loads before the page code.
Remote Script
Remote scripts are loaded by providing the full URL to the script.
Remote Scripts can be loaded synchronously or asynchronously. If you are loading frameworks, such as jQuery,
that you want to use throughout the page, we recommending loading these scripts synchronously. This ensures that
any functions defined are available to other elements on the page.
Functions and other code defined in script tags cannot be used in the &lt;head&gt; element on the page since that loads
before the page code.
IFrame
IFrame custom code tags are created by providing the full URL to the page to load in the IFrame.
The IFrame element is generated automatically and inserted at the location where the tag loads. Since you can't
specify a location to append tags, custom code tags should not be used to change page content.
Conditional Execution using Firing Rules
Tags defined in custom code tags can be fired conditionally based on matching criteria.
All conditions that you define for a custom code tag must be met for the code to execute. For example, if you provide
a Host Match and Path Match, both conditions must match.
The following match parameters are available:
• Host
• Path
• Cookie
Additional Web and Mobile Measurement
Libraries
45
• Query Parameter
• Date
The following match conditions are available:
• Contains
• Matches RegEx
• Does not contain
• Does not match RegEx
RegEx conditions use standard JavaScript RegEx patterns.
Match strings in contains and does not contain conditions are case-sensitive.
Tag management Permissions
All administrators have access to tag management.
Using groups, you can define the following permissions for other users:
• Access to all tag containers in a specific environment (dev, stage, or live).
• Access to a specific tag container in all environments.
Assign Permissions
Admin &gt; User Management &gt; Groups&gt; Click a group.
Tag management permissions can be assigned to any custom group or any individual members of a custom group.
amc.on Tag Event Callbacks
To avoid errors due to asynchronous tag loading and rare cases of CDN unavailability, you should use the tag event
callbacks provided by amc.on to wrap any code that depends on tags delivered by tag management.
Avoiding Availability Errors
An amc object is defined in the tag management page code:
var amc=amc||{};if(!amc.on){amc.on=amc.call=function(){}};
Since this object is defined on the page, any code that is contained in amc.on event callbacks fails silently if the tag
container does not load for any reason.
Additional Web and Mobile Measurement
Libraries
46
Callback Events
Instead of relying on browser execution order, tag management provides an interface that lets you execute code
based on tag events. This lets you deliver tags asynchronously to optimize performance, and still execute additional
code after a tag loads or when other events occur.
Callbacks can be associated with the following events using amc.on:
Event name
Description
tagload
Triggered when a tag has been loaded and is ready to use.
tagappend
Triggered when a tag is appended in the page by tag management.
tagignore
Triggered when by some unknown reason one tag could not be append in the page.
pageload
Triggered when the onload event is triggered by the browser.
domcontentloaded Triggered when the DOMContentLoaded event from the browser is triggered.
load
Triggered when all the tags have been loaded.
tagload.tagid
For the events starting with tag (tagload, tagappend, tagignore) hierarchical event names
are supported. This means that the id of the tag can be added after the event name.
tagappend.tagid
tagignore.tagid
Don't confuse these events with the DomContentLoaded or the onload events from browser. These events can be
triggered before or after the events triggered by the browser.
Callback methods have the following syntax:
amc.on('eventname', function (event, data) {
});
Each callback method receives the following arguments:
• event - the event name for which this callback will be processed.
• data - an object having the following structure:
{
id: 'tagid',
tag: TagInstance
}
Note: Any code using the amc.on method should be added in the page after the page code. Code that depends
on tags that are delivered by tag management should not be placed in the &lt;head&gt; element.
Examples
The following examples are based on a tag container that has 2 components:
• Analytics - with the id 'analytics'
• Target - with the id 'testandtarget'
Load
amc.on('load', function (event, data) {
// Here we can add code that will be triggered once all the tags have been loaded by tag
management.
// For set eVars, props, events, and then call s.t(). You can also do this directly
Additional Web and Mobile Measurement
Libraries
47
// in tagmanager UI if you don't need page elements
});
Tag Load
amc.on('tagload', function (event, data) {
//called twice. Once for Analytics, and once for Target
});
You can find out the component for which the event was triggered by looking at the data object. This callback is for
advanced users who need complex functionality. For example, you might have 10 tags to add in the page, but want
to define an action when only 3 of them are loaded, independent of the other 7.
Specific Tag Loaded
amc.on('tagload.analytics', function (matchedmessage, data) {
});
This callback is triggered when the tag with the ID of analytics has been loaded by the browser. This is the same
as placing the code in the On Load section of the Analytics tag in the tag management UI (assuming your Analytics
tag has an id of 'analytics').
For example, if you need to place code that is dependent on Analytics in the Target tag, you can add code similar
to the following in the On Load section of the Target tag:
var mboxServerHost='omniture.tt.omtrdc.net;'
(function mboxOnLoad() {
//place code here that will run after Target is loaded
})();
amc.on('tagload.analytics', function () {
//place code here that will run after Analytics and Target are loaded
});
Nested DOM Content Loaded within the Analytics Tag
If you need to call s.t on the page instead of within the On Load section in the Analytics tag, the call should be
contained within two callbacks. The first when the Analytics tag is loaded, and the second when the DOM is loaded:
amc.on('tagload.analytics', function (matchedmessage, data) {
amc.on('domcontentloaded', function () {
if (s) {
s.pageName = document.getElementById('pagetitle').innerHTML;
s.t();
}
});
});
This method is used if you need to interact with the DOM before making the tracking call.
Troubleshooting
This section contains instructions to help troubleshoot tag container deployment.
Confirm that the container is deployed
The Status column on the Container Environment Overview displays which revision is deployed in each environment.
Additional Web and Mobile Measurement
Libraries
48
Confirm that a tag revision is deployed in the environment you are testing.
Verify the environment cookie
If you are testing a development or stage version, verify that the s_tagEnv cookie is set with a value of dev, stage,
or live:
If not, use the environment bookmarklets to set the environment cookie, or define the cookie using a debugger:
• name: s_tag_Env
• host: your hostname
• path: /
• expiration: session
• value: dev, stage, or live
Verify the page code and amc.js
Use a debugger to verify that the tag management 2.0 page code is on the page directly after the opening &lt;body&gt;
element.
Additional Web and Mobile Measurement
Libraries
49
If the page code is present but the tag container is not loading on some of your pages, verify that the bucket_id in
your page code matches the bucket_id in amc.js:
Additional Web and Mobile Measurement
Libraries
50
To get the bucket_id of a tag container, click Get Page code and find the bucket_id. Confirm that the bucket ID
of this page code matches the page code you deployed.
Analytics Variables
51
Analytics Variables
Analytics provides a number of variables to collect Analytics data. For example, the value in the pageName variable
is the name of the Web page being reported. This section lists the variables that are supported by AppMeasurment.
For a listing of how each variable appears in Analytics reports, see Variables - How They Are Used in Reporting.
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:
Overview
If you have this Adobe
Analytics Product
You now have access to
SiteCatalyst
75 eVars, 100 Events
Adobe Analytics (Standard) 100 eVars, 1000 Events
Adobe Analytics - Mobile
Apps
100 eVars, 1000 Events
Adobe Analytics Premium - 250 eVars, 1000 Events
Attribution
Adobe Analytics Premium - 250 eVars, 1000 Events
Predictive Intelligence
Adobe Analytics Premium - 250 eVars, 1000 Events
Customer 360
Adobe Analytics Premium - 250 eVars, 1000 Events
Complete
Populating Variables and Events
• Variables can be populated in the data collection library if you are using these versions of AppMeasurement:
• AppMeasurement for JavaScript version 1.4+
• AppMeasurement for Flash version 3.9+
• AppMeasurement for Java version 1.2.8+
• AppMeasurement for Silverlight/.NET version 1.4.2+
• AppMeasurement for PHP version 1.2.2+
• If you are on an earlier version of code, or on JavaScript H.*, you can populate context data and use processing
rules to populate variables.
• All versions of data collection code can populate events 101-1000.
• Processing rules can be used to populate eVars 76-250 based on context data or other variables.
Frequently Asked Questions
• Will all Adobe Analytics interfaces have immediate access to these new variables?
These interfaces will have immediate access: Reports &amp; Analytics, Report Builder, Ad Hoc Analysis, and APIs.
However, the Data Workbench feed from Analytics will not be updated for the new variables until May. If you turn
Analytics Variables
52
on a variable, you won't be able to access it in Data Workbench until the next version of Data workbench is released
(in the May 2015 time frame.)
• Will these additional eVars and events automatically show up in my data feeds?
Data feeds will have access to the new variables and events once enabled. New eVar columns will not appear
until you choose to include them. However, new events will appear in the event_list column as soon as they’re
enabled, and the events lookup table contains the event names for those event IDs. Do not enable new events
unless you are ready to consume them in Data Feeds.
• How do I request new data feed columns?
To request new columns, refer to Configuring Data Feeds.
• What if I am an Analytics Premium customer who wants to go back to Analytics Standard and I currently
have 150 eVars enabled?
Adobe will not disable any of your existing eVars, but we are also not going to allow you to enable more. If you
disable eVars, you cannot turn them back on until you are below the limit of 100 enabled eVars that Analytics
Standard qualifies you for.
Variables and Limitations
The JavaScript file used to track Web pages is extremely versatile. However, potential problems and pitfalls may
arise with an increased level of flexibility.
The following table lists the available Analytics variables:
Variable
Description
s_account
Determines the report suite where data is stored and
reported.
browserHeight
Displays the height of the browser window.
browserWidth
Displays the width of the browser window.
campaign
Identifies marketing campaigns used to bring visitors to
your site. The value of campaign is usually taken from a
query string parameter.
channel
Usually identifies a section of your website. For example,
a merchant may have sections such as Electronics, Toys,
or Apparel. A media site may have sections such as
News, Sports, or Business.
charSet
Translates the character set of the Web page into UTF-8.
colorDepth
Displays the number of bits used to display color on each
pixel of the screen.
connectionType
Indicates (in Microsoft Internet Explorer) whether the
browser is configured on a LAN or modem connection.
cookieDomainPeriods
Determines the domain on which the Analyticsvisitor ID
(s_vi) cookie will be set by determining the number of
periods in the domain of the page URL. For
www.mysite.com, cookieDomainPeriods should be &quot;2.&quot;
For www.mysite.co.jp, cookieDomainPeriods should be
&quot;3.&quot;
Analytics Variables
53
Variable
Description
cookieLifetime
Used by both JavaScript and Analytics servers to
determine the lifespan of a cookie.
cookiesEnabled
Indicates whether a first-party session cookie could be
set by JavaScript.
currencyCode
Determines the conversion rate to be applied to revenue
as it enters the Analytics databases. Analytics databases
store all monetary amounts in a currency of your choice.
If that currency is the same as that specified in
currencyCode, or currencyCode is empty, no conversion
is applied.
dc
Lets you set the data center to which your data is sent.
doPlugins
doPlugins is a reference to the s_doPlugins function. It
allows the s_doPlugins function to be called at the
appropriate location within the JavaScript file.
dynamicAccountList
Dynamically selects a report suite to which data is sent.
The dynamicAccountList variable contains the rules that
used to determine the destination report suite.
dynamicAccountMatch
Uses the DOM object to retrieve the section of the URL
to which all rules in dynamicAccountList are applied. This
variable is only valid when dynamicAccountSelection is
set to 'True.'
dynamicAccountSelection
Lets you dynamically select the report suite based on the
URL of each page.
dynamicVariablePrefix
Allows deployment to flag variables that should be
populated dynamically. Cookies, request headers, and
image query string parameters are available to be
populated dynamically.
eVarN
Used for building custom reports within the
AnalyticsConversion Module. When an eVar is set to a
value for a visitor, Analytics remembers that value until
it expires. Any success events that a visitor encounters
while the eVar value is active are counted toward the
eVar value.
events
Records common shopping cart success events and
custom success events.
fpCookieDomainPeriods
Determines the domain on which Analytics cookies other
than the visitor ID (s_vi) cookie will be set by determining
the number of periods in the domain of the page.
hierN
Determines the location of a page in your site's hierarchy.
This variable is most useful for sites that have more than
three levels in the site structure.
homepage
Indicates (in Internet Explorer) whether the current page
is set as the user's home page.
javaEnabled
Indicates whether Java is enabled in the browser.
Analytics Variables
54
Variable
Description
javascriptVersion
Displays the version of JavaScript supported by the
browser.
linkDownloadFileTypes
A comma-separated list of file extensions. If your site
contains links to files with any of these extensions, the
URLs of these links appear in the File Downloads report.
linkExternalFilters
If your site contains many links to external sites, and you
don't want to track all exit links, linkExternalFilters can
be used to report on a specific subset of exit links.
linkInternalFilters
Determines which links on your site are exit links. It is a
comma-separated list of filters that represent the links
that are part of the site.
linkLeaveQueryString
Determines whether or not the query string should be
included in the Exit Links and File Download reports.
linkName
An optional variable used in Link Tracking that
determines the name of a custom, download, or exit link.
The linkName variable is not normally needed because
the third parameter in the tl() function replaces it.
linkTrackEvents
Contains the events that should be sent with custom,
download, and exit links. This variable is only considered
if linkTrackVars contains &quot;events.&quot;
linkTrackVars
A comma-separated list of variables that will be sent with
custom, exit, and download links. If linkTrackVars is set
to &quot;&quot;, all variables that have values are sent with link data.
linkType
An optional variable used in link tracking that determines
which report a Link Name or URL will appear (custom,
download, or exit Links). linkType is not normally needed
because the second parameter in the tl() function replaces
it.
mediaLength
Specifies the total length of the media being played.
mediaName
Specifies the name of the video or media item. It is only
available via the Data Insertion API and Full Processing
Data Source.
mediaPlayer
Specifies the player used to consume a video or media
item.
mediaSession
Specifies the segments of a video or media asset
consumed.
Media.trackEvents
Identifies which events should be sent with a media hit.
It is only applicable with JavaScriptActionSource..
Media.trackVars
Identifies which variables should be sent with a media
hit. It is only applicable with JavaScriptActionSource..
mobile
Controls the order in which cookies and subscriber ids
are used to identify visitors.
s_objectID
A global variable that should be set in the onClick event
of a link. By creating a unique object ID for a link or link
Analytics Variables
Variable
55
Description
location on a page, you can improve visitor click map
tracking or use visitor click map to report on a link type
or location, rather than the link URL.
pageName
Contains the name of each page on your site. If
pageName is blank, the URL is used to represent the
page name in Analytics.
pageType
Used only to designate a 404 Page Not Found Error page.
It only has one possible value, which is &quot;errorPage.&quot; On
a 404 Error page, the pageName variable should not be
populated.
pageURL
In rare cases, the URL of the page is not the URL that
you would like reported in Analytics. To accommodate
these situations, Analytics offers the pageURL variable,
which overrides the actual URL of the page.
plugins
On Netscape and Mozilla-based browsers, lists the
plugins installed in the browser.
products
Used for tracking products and product categories as well
as purchase quantity and purchase price. The products
variable should always be set in conjunction with a
success event. Optionally, the products variable can track
custom numeric and currency events, as well as
Merchandising eVars.
propN
Used for building custom reports within the
AnalyticsTraffic Module. props may be used as counters
(to count the number of times a page view is sent), for
pathing reports, or in correlation reports.
purchaseID
Used to keep an order from being counted multiple times
by Analytics. Whenever the purchase event is used on
your site, you should use the purchaseID variable.
referrer
Restores lost referrer information.
resolution
Displays the monitor resolution of the visitor viewing the
Web page.
server
Shows 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).
state
Captures the state in which a visitor to your site resides.
trackDownloadLinks
Set trackDownloadLinks to 'true' if you want to track links
to downloadable files on your site. If trackDownloadLinks
is 'true,' linkDownloadFileTypes determines which links
are downloadable files.
trackExternalLinks
If trackExternalLinks is 'true,' linkInternalFilters and
linkExternalFilters determines whether any link clicked is
an exit link.
Analytics Variables
56
Variable
Description
trackingServer
Used for first-party cookie implementation to specify the
domain at which the image request and cookie is written.
Used for non-secure pages.
trackingServerSecure
Used for first-party cookie implementation to specify the
domain at which the image request and cookie is written.
Used for secure pages.
trackInlineStats
Determines whether visitor click map data is gathered.
transactionID
Ties offline data to an online transaction (like a lead or
purchase generated online). Each unique transactionID
sent to Adobe is recorded in preparation for a Data
Sources upload of offline information about that
transaction. See the Data Sources Guide.
s_usePlugins
If the s_doPlugins function is available and contains
useful code, s_usePlugins should be set to 'true.' When
usePlugins is 'true,' the s_doPlugins function is called
prior to each image request.
visitorID
Visitors may be identified by the visitorID tag, or by IP
address/User Agent. The visitorID may be up to 100
alphanumeric characters and must not contain a hyphen.
visitorNamespace
If visitorNamespace is used in your JavaScript file, do
not delete or alter it. This variable is used to identify the
domain with which cookies are set. If visitorNamespace
changes, all visitors reported in Analytics may become
new visitors. In short, do not alter this variable without
approval from an Adobe consultant.
zip
Captures the ZIP code in which a visitor to your site
resides.
Illegal JavaScript Characters
Characters and strings that are never allowed in JavaScript variables.
• Tab (0x09)
• Carriage return (0x0D)
• Newline (0x0A)
• ASCII characters with codes above 127 (unless multi-byte characters are enabled and charSet is populated
appropriately)
• HTML tags (e.g. &lt;b&gt;&lt;/b&gt; or &amp;#153)
Many variables, most notably products, hierarchy, and events, have additional limitations or syntax requirements.
For individual variable limitations and syntax requirements, see the section corresponding to the s_account variable
parameters.
s_account
The s_account variable determines the report suite where data is stored and reported.
Analytics Variables
57
If sending to multiple report suites (multi-suite tagging), s_account may be a comma-separated list of values. The
report suite ID is determined by Adobe.
Parameters
Max Size
Debugger Parameter
Reports Populated
Default Value
40 Bytes
In the URL path
N/A
N/A
Each report suite ID must match the value created in the Admin Console. Each report suite ID must be 40 bytes or
less, but the aggregate of all report suites (the entire comma-separated list) has no limit.
The report suite is the most fundamental level of segmentation in reporting. You can set as many report suites as
your contract allows. Each report suite refers to a dedicated set of tables that are populated in Adobe's collection
servers. A report suite is identified by the s_account variable in your JavaScript code.
Within Analytics, the site drop-down box in the upper left of the reports displays the current report suite. Each report
suite has a unique identifier called a report suite ID. The s_account variable contains one or more report suite IDs
to which data is sent. The report suite ID value, which is invisible to Analytics users, must be provided or approved
by Adobe before you use it. Every report suite ID has an associated &quot;friendly name&quot; that can be changed in the
report suites section of the Admin Console.
The s_account variable is normally declared inside the JavaScript file (s_code.js). You can declare the s_account
variable on the HTML page, which is a common practice when the value of s_account may change from page to
page. Because the s_account variable has a global scope, it should be declared immediately before including Adobe's
JavaScript file. If s_account does not have a value when the JavaScript file is loaded, no data is sent to Analytics.
Adobe's DigitalPulse Debugger displays the value of s_account in the path of the URL that appears just below the
word &quot;Image,&quot; just after /b/ss/. In some cases, the value of s_account also appears in the domain, before 112.2o7.net.
The value in the path is the only value that determines the destination report suite. The bold text below shows the
report suites that data is sent to, as it appears in the debugger. See Adobe Debugger .
http://mycompany.112.2o7.net/b/ss/mycompanycom,mycompanysection/1/H.1-pdv-2/s21553246810948?[AQB]
Syntax and Possible Values
The report suite ID is an alphanumeric string of ASCII characters, no more than 40 bytes in length. The only
non-alphanumeric character allowed is a hyphen. Spaces, periods, commas and other punctuation are not allowed.
The s_account variable may contain multiple report suites, all of which receive data from that page.
var s_account=&quot;reportsuitecom[,reportsuite2[,reportsuite3]]&quot;
All values of s_account must be provided or approved by Adobe.
Examples
var s_account=&quot;mycompanycom&quot;
var s_account=&quot;mycompanycom,mycompanysection&quot;
Configuring the Variable in Analytics
The friendly name associated with each report suite ID can be changed by Adobe ClientCare. The friendly name
can be seen in Analytics in the site drop-down box in the top, left section of the screen.
Analytics Variables
58
Pitfalls, Questions, and Tips
• If s_account is empty, not declared, or contains an unexpected value, no data is collected.
• When the s_account variable is a comma-separated list (multi-suite tagging), do not put spaces between report
suite IDs.
• If s.dynamicAccountSelection is set to 'True,' the URL is used to determine the destination report suite. Use the
DigitalPulse Debugger to determine the destination report suite(s).
• In some cases, VISTA can be used to alter the destination report suite. UsingVISTA to re-route or copy the data
to another report suite is recommended when using first-party cookies, or if your site has more than 20 active report
suites.
• Always declare s_account inside the JS file or just before it is included.
browserHeight
The browserHeight variable displays the height of the browser window.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Parameters
Query Param
Value
Example
Reports Affected
bh
A positive integer
865
Traffic &gt; Technology &gt;
Browser Height
browserWidth
The browserWidth variable displays the width of the browser window.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Parameters
Query Param
Value
Example
Reports Affected
bw
A positive integer
1179
Traffic &gt; Technology &gt;
Browser Width
Analytics Variables
59
campaign
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.
Parameters
Max Size
Debugger Parameter
Reports Populated
Default Value
255 Bytes
v0
Conversion &gt; Campaigns &quot;&quot;
&gt; Tracking Code
Every element in a marketing campaign should have an associated unique tracking code. For example, a paid search
engine keyword may have a tracking code of 112233. When someone clicks the keyword with the 112233 tracking
code and is routed to the corresponding website, the campaign variable records the tracking code.
There are two main ways to populate the campaign variable:
• The getQueryParam plug-in, used in the JavaScript file, retrieves a query string parameter from the URL. For
more information on the getQueryParam plugin, see Implementation Plug-ins.
• Assign a value to the campaign variable in the HTML on the Web page.
With either method of populating the campaign variable, the Back button traffic may inflate the actual number of
click-throughs from a campaign element.
For example, a visitor enters your site by clicking a paid search keyword. When the visitor arrives on the landing
page, the URL contains a query string parameter identifying the tracking code for the keyword. The visitor then clicks
a link to another page, but then immediately clicks the Back button to return to the landing page. When the visitor
arrives a second time on the landing page, the URL with the query string parameter identifies the tracking code
again. And a second click-through is registered, thereby falsely inflating the number of click-throughs.
To avoid this inflation of click-throughs, Adobe recommends using the getValOnce plugin to force each campaign
click-through to be counted only once per session. For more information on the getValOnce plugin, see Implementation
Plug-ins.
Syntax and Possible Values
s.campaign=&quot;112233&quot;
The campaign variable has the same limitations as all other variables. Adobe recommends limiting the value to
standard ASCII characters.
Case Sensitivity
eVars are case insensitive, but they are displayed in the capitalization of the first occurrence. For example, if the
first instance of eVar1 is set to &quot;Logged In,&quot; but all subsequent instances are passed as &quot;logged in,&quot; reports always
show &quot;Logged In&quot; as the value of the eVar.
Examples
s.campaign=&quot;112233&quot;
s.campaign=s.getQueryParam('cid');
Analytics Variables
60
Configuration Settings
Each campaign value remains active for a user, and receives credit for that user's activities and success events
until it expires. You can change the expiration of the campaign variable in the Admin Console.
Pitfalls, Questions, and Tips
• To keep click-throughs from being inflated, use the getValOnce plugin to let the click-through for a campaign be
counted only once per session. For more information on the getValOnce plug-in, see Implementation Plug-ins.
• For more information on tracking marketing campaigns and keyword buys, see Campaigns.
• Use the DigitalPulse Debugger to see the actual value of campaigns (v0 in the debugger). If v0 does not appear
in the debugger, no campaign data is recorded for that page.
charSet
The charSet variable translates the character set of the Web page into UTF-8.
If the charSet variable contains an incorrect value, the data in all other variables are translated incorrectly. If JavaScript
variables on your pages (e.g. pageName, prop1, or channel) contain only ASCII characters, charSet does not need
to be defined. However, if the variables on your pages contain non-ASCII characters, the charSet variable must be
populated.
Parameters
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
CE
N/A
&quot;&quot;
The charSet variable is used to identify the character set of the page. For more information on character sets, see
the Multi-byte Character Sets white paper before using the charSet variable.
Syntax and Possible Values
The charSet variable may only contain one of a predefined set of values, as listed in Multi-byte Character Sets.
s.charSet=&quot;character_set&quot;
Examples
s.charSet=&quot;ISO-8859-1&quot;
s.charSet=&quot;SJIS&quot;
Pitfalls, Questions, and Tips
• The value of charSet must match the possible values listed in Multi-byte Character Sets.
• The value of charSet should reflect the character set of the page.
channel
The channel variable is most often used to identify a section of your site.
For example, a merchant may have sections such as Electronics, Toys, or Apparel. A media site may have sections
such as News, Sports, or Business.
Analytics Variables
61
Max Size
Debugger Parameter
Reports Populated
Default Value
100 Bytes
CH
Site Content &gt; Site Sections &quot;&quot;
Adobe recommends populating the channel variable on every page. You can also turn on a correlation between the
channel and page name variables.
When sections have one or more levels of subsections, you can show those sections in the channel variable or use
separate variables to identify levels. For more information, see the Channels and Hierarchies white paper.
Syntax and Possible Values
s.channel=&quot;value&quot;
The channel variable has no extra limitations on its values.
Examples
s.channel=&quot;Electronics&quot;
s.channel=&quot;Media&quot;
Pitfalls, Questions, and Tips
If your site contains multiple levels, you can use the hierarchy or another variable to designate those levels. The
channel value does not persist, but the success events fired on the same page are attributed to the channel value.
colorDepth
The colorDepth variable is used to show the number of bits used to display color on each pixel of the screen.
For example, 32 represents 32 bits of color on the screen. This variable is populated after the page code and before
doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
Reports Affected
c
8,16, and 32
32
Traffic &gt; Technology &gt;
Monitor Color Depth
connectionType
The connectionType variable, in Internet Explorer, indicates whether the browser is configured on a LAN or modem
connection.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
Analytics Variables
62
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
Reports Affected
ct
lan or modem
lan
Traffic &gt; Technology &gt;
Connection Type
cookieDomainPeriods
The cookieDomainPeriods variable determines the domain on which the Analytics cookies s_cc and s_sq are set
by determining the number of periods in the domain of the page URL. This variable is also used by some plug-ins
in determining the correct domain to set the plug-in's cookie.
The default value for cookieDomainPeriods is &quot;2&quot;. This is the value that is used if cookieDomainPeriods is omitted.
For example, using the domain www.mysite.com, cookieDomainPeriods should be &quot;2&quot;. For www.mysite.co.jp,
cookieDomainPeriods should be &quot;3&quot;.
If cookieDomainPeriods is set to &quot;2&quot; but the domain contains three periods, the JavaScript file attempts to set cookies
on the domain suffix.
For example, if setting cookieDomainPeriods to &quot;2&quot; on the domain www.mysite.co.jp, the s_cc and s_sq cookies
are created on the domain co.jp. Because co.jp is an invalid domain, almost all browsers reject these cookies.
As a consequence, visitor click map data is lost, and the Visitor Profile &gt; Technology &gt; Cookies report indicates
that almost 100% of visitors reject cookies.
If cookieDomainPeriods is set to &quot;3&quot; but the domain contains only two periods, the JavaScript file sets the cookies
on the subdomain of the site. For example, if setting cookieDomainPeriods to &quot;3&quot; on the domain www2.mysite.com,
the s_cc and s_sq cookies are created on the domain www2.mysite.com. When a visitor goes to another subdomain
of your site (such as www4.mysite.com), all cookies set with www2.mysite.com cannot be read.
Note: Do not include additional subdomains as part of cookieDomainPeriods. For example,
store.toys.mysite.com would still have cookieDomainPeriods set to &quot;2&quot;. This variable definition correctly
sets the cookies on the root domain, mysite.com. Setting cookieDomainPeriods to &quot;3&quot; in this example would
set cookies on the domain toys.mysite.com, which has the same implications as the prior example.
See also fpCookieDomainPeriods.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
CDP
Affects multiple reports as &quot;2&quot;
it controls how the visitor ID
is stored and handled.
Examples
Setting the variable manually:
s.cookieDomainPeriods = &quot;3&quot;;
Several examples to dynamically set the variable if your core Javascript file hosts both types:
document.URL.indexOf(&quot;.co.&quot;) &gt; 0 ? s.cookieDomainPeriods = &quot;3&quot; : s.cookieDomainPeriods = &quot;2&quot;;
s.cookieDomainPeriods = &quot;2&quot;;
var d=window.location.hostname;
Analytics Variables
63
if(d.indexOf(&quot;.co.uk&quot;) &gt; 0 || d.indexOf(&quot;.com.au&quot;) &gt; 0)
{s.cookieDomainPeriods = &quot;3&quot;;}
s.cookieDomainPeriods = &quot;2&quot;;
if(window.location.indexOf(&quot;.co.jp&quot;) &gt; 0 || window.location.indexOf(&quot;.com.au&quot;) &gt; 0)
{s.cookieDomainPeriods = &quot;3&quot;;}
Pitfalls, Questions, and Tips
• If you notice that visitor click map data is absent, or that the Traffic &gt; Technology &gt; Cookies report shows a large
percentage of visitors who reject cookies, check that the value of cookieDomainPeriods is correct.
• If cookieDomainPeriods is higher than the number of sections in the domain, cookies will be set with the full domain.
This can cause data loss as visitors switch between subdomains.
• The cookieDomainPeriods variable was used in deprecated implementations prior to trackingServer to set the
visitor ID cookie. Though only present in outdated code, failure to correctly define cookieDomainPeriods in this
circumstance puts your implementation at risk of data loss.
cookieLifetime
The cookieLifetime variable is used by both JavaScript and data collection servers in determining the lifespan of a
cookie.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
cl
Traffic &gt; Technology &gt;
Cookies All visitor-related
reports
&quot;&quot;
If cookieLifetime is set, it overrides any other cookie expirations for both JavaScript and data collection servers, with
one exception, described below. The cookieLifetime variable can have one of three values:
• Analytics Cookies
• Cookies
• JavaScript Settings and Plugins
Syntax and Possible Values
s.cookieLifetime=&quot;value&quot;
The possible values are listed as follows:
• &quot;&quot;
• &quot;NONE&quot;
• &quot;SESSION&quot;
• An integer representing the number of seconds until expiration
Examples
s.cookieLifetime=&quot;SESSION&quot;
s.cookieLifetime=&quot;86400&quot; // one day in seconds
Configuration Settings
None
Analytics Variables
64
Pitfalls, Questions, and Tips
cookieLifetime affects Analytics tracking. If, for example, cookieLifetime is two days, then monthly, quarterly, and
yearly unique visitor reports will be incorrect. Use caution when setting cookieLifetime.
cookiesEnabled
The cookiesEnabled variable indicates whether a first-party session cookie could be set by JavaScript.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
k
Y or N
Y
currencyCode
The currencyCode variable determines the conversion rate to be applied to revenue.
All monetary amounts are stored in a currency of your choice. If that currency is the same as that specified in
currencyCode, or currencyCode is empty, no conversion is applied.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
cc
Conversion &gt; Purchases &gt; &quot;USD&quot;
Revenue
All Conversion reports
showing Revenue or
monetary values
If your site allows visitors to purchase in multiple currencies, you should use the currencyCode variable to make
sure revenue is stored in the appropriate currency. For example, if the base currency for your report suite is USD,
and you sell an item for 40 Euros, you should populate the currencyCode with &quot;EUR&quot; on the HTML page. As soon
as data collection receives the data, it uses the current conversion rate to convert the 40 Euros to its USD equivalent.
Populating the currencyCode variable on the HTML page instead of in the JavaScript file is recommend if you sell
in multiple currencies. If you want to use your own conversion rates rather than the conversion rates used by Adobe,
set the currencyCode to equal the base currency of your report suite. You then convert all revenue before sending
it into Analytics.
Currency conversion applies to both revenue and any currency events. These are events that are used to sum
values similar to revenue, such as tax and shipping. The revenue and currency events are specified in the products
string. For more information on products, see events. For more details on how currencies are managed, see
Multi-Currency Support..
Analytics Variables
65
Syntax and Possible Values
s.currencyCode=&quot;currency_code&quot;
Only the currency codes listed in Multi-Currency Support are allowed.
Examples
s.currencyCode=&quot;GBP&quot;
s.currencyCode=&quot;EUR&quot;
Configuration Settings
Adobe ClientCare can change the default currency setting for your report suite. When you change the base currency
for a report suite, the existing revenue in the system is not converted. All new revenue values will be converted
accordingly.
Pitfalls, Questions, and Tips
• If you notice surprisingly large amounts of revenue in reports, ensure that the currencyCode variable and base
currency of the report suite are set correctly.
• The currencyCode variable is not persistent, meaning that the variable must be passed in the same image request
as any revenue or other currency-related metrics.
• Currency events should not be used for non-currency purposes. If you need to count arbitrary or dynamic values
that are not currency, use the numeric event type.
• When the currencyCode variable is empty, no conversion is applied.
dc
(Deprecated) The dc variable lets you select the data center to which your data is sent.
Note: The dc variable is deprecated. You should set trackingServer for all implementations to the value that
is generated by Code Manager in s_code.js.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
112
The data center is identified in the dc variable in order to match ActionSource.
doPlugins
The doPlugins variable is a reference to the s_doPlugins function, and allows the s_doPlugins function to be called
at the appropriate location within the JavaScript file.
The s_doPlugins function is called each time any of the following occurs:
• The t() function is called
• The tl() function is called
• An exit or download link is clicked
• Any page element being tracked by visitor click map is clicked
Analytics Variables
66
The doPlugins function is used to run customized routines to gather or alter data. If you are using an object name
other than &quot;s,&quot; make sure that the s_doPlugins is renamed appropriately. For example, if your object name is s_mc,
the s_doPlugins function should be called s_mc_doPlugins.
Syntax and Possible Values
The s_doPlugins function should not be in quotes, and doPlugins should always be assigned to the exact name of
the s_doPlugins function (if that function is renamed).
s.doPlugins=s_doPlugins;
Examples
s.doPlugins=s_doPlugins;
s_mc.doPlugins=s_mc_doPlugins;
Configuration Settings
None
Pitfalls, Questions, and Tips
• The only reason to change the object name (such as from s to s_mc) is if you share content with or pull content
from other customers. Renaming the s_doPlugins function to s_mc_doPlugins ensures that another client's
JavaScript file does not overwrite your doPlugins function.
• If you unexpectedly start pulling in content from another Adobe customer, and your s_doPlugins function is being
overwritten, it is possible to simply rename the s_doPlugins function without changing the object name. While the
best solution is to use a different object name than other JavaScript files on the same page, doing so is not required.
dynamicAccountList
AppMeasurement for JavaScript can dynamically select a report suite to which it sends data. The dynamicAccountList
variable contains the rules used to determine the destination report suite.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
&quot;&quot;
This variable is used in conjunction with the dynamicAccountSelection and dynamicAccountMatch variables. The
rules in dynamicAccountList are applied if dynamicAccountSelection is set to 'true,' and they apply to the section of
the URL specified in dynamicAccountMatch.
If none of the rules in dynamicAccountList matches the URL of the page, the report suite identified in s_account is
used. The rules listed in this variable are applied in a left-to-right order. If the page URL matches more than one
rule, the left-most rule is used to determine the report suite. As a result, your more generic rules should be moved
to the right of the list.
In the following examples, the page URL is http://www.mycompany.com/path1/?prod_id=12345,
dynamicAccountSelection is set to 'true,' and s_account is set to &quot;mysuitecom.&quot;
DynamicAccountList Value
DynamicAccountMatch Value
Report Suite to Receive Data
mysutie2=www2.mycompany.com;mysutie1=mycompany.com&quot; window.location.host
mysuite1
&quot;mysuite1=path4,path1;mysuite2=path2&quot; window.location.pathname
mysuite1, mysuite2
Analytics Variables
67
DynamicAccountList Value
DynamicAccountMatch Value
Report Suite to Receive Data
&quot;mysuite1=path5&quot;
window.location.pathname
mysuitecom, mysuite1
&quot;myprodsuite=prod_id&quot;
window.location.search?window.location.search:&quot;?&quot;) myprodsuite
Syntax and Possible Values
The dynamicAccountList variable is a semicolon-separated list of name=value pairs (rules). Each piece of the list
should contain the following items:
• one or more report suite ID (separated by commas)
• an equals sign
• one or more URL filters (comma-separated)
s.dynamicAccountList=rs1[,rs2]=domain1.com[,domain2.com/path][;...]
Only standard ASCII characters should be used in the string (no spaces).
Examples
s.dynamicAccountList=&quot;mysuite2=www2.mycompany.com;mysuite1=mycompany.com&quot;
s.dynamicAccountList=&quot;ms1,ms2=site1.com;ms1,ms3=site3.com&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• Dynamic account selection is not supported by About AppMeasurement for JavaScript.
• If the page URL matches multiple rules, the furthest rule on the left is used.
• If no rules match, the default report suite is used.
• If your page is saved to someone's hard drive or translated via a web-based translation engine (such as Google's
translated pages), the dynamic account selection probably won't work. For more precise tracking, populate the
s_account variable server-side.
• The dynamicAccountSelection rules apply only to the section of the URL specified in dynamicAccountMatch.
• When using dynamic account selection, be sure to update dynamicAccountList every time you obtain a new domain.
• Use the DigitalPulse Debugger when trying to identify the destination report suite. The dynamicAccountSelection
variable always overrides the value of s_account.
dynamicAccountMatch
The dynamicAccountMatch variable uses the DOM object to retrieve the section of the URL to which all rules in
dynamicAccountList are applied.
This variable is only valid when dynamicAccountSelection is set to 'True.' Since the default value is
window.location.host, this variable is not required for Dynamic Account Selection to work. For additional
information, see dynamicAccountList.
The rules found in dynamicAccountList are applied to the value of dynamicAccountMatch. If dynamicAccountMatch
only contains window.location.host (default), the rules in dynamicAccountList apply only to the domain of the
page.
Analytics Variables
68
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
window.location.host
Syntax and Possible Values
The dynamicAccountMatch variable is usually populated by the Adobe consultant who provides the AppMeasurement
for JavaScript file. However, the values listed below may be applied at any time.
s.dynamicAccountMatch=[DOM object]
Description
Value
Domain (default)
window.location.host
Path
window.location.pathname
Query String
(window.location.search?window.location.search:&quot;?&quot;)
Domain and Path
window.location.host+window.location.pathname
Path and Query String
window.location.pathname+(window.location.search?window.location.search:&quot;?&quot;)
Full URL
window.location.href
Examples
s.dynamicAccountMatch=window.location.pathname
s.dynamicAccountMatch=window.location.host+window.location.pathname
Configuration Settings
None
Pitfalls, Questions, and Tips
• Dynamic account selection is not supported by About AppMeasurement for JavaScript.
• When pages are saved to a hard drive, window.location.host is empty, causing those page views to be sent
to the default report suite (in s_account).
• When a page is translated via a web-based translation engine, such as Google, the Dynamic Account Selection
does not work as designed. For more precise tracking, populate the s_account variable server-side.
dynamicAccountSelection
The dynamicAccountSelection variable lets you dynamically select the report suite based on the URL of each page.
Note: dynamicAccountSelection does not work with custom link tracking.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
False
Note: Both dynamicAccountList and dynamicAccountMatch are ignored if the dynamicAccountSelection
variable is not declared or set to 'false.'
Analytics Variables
69
Syntax and Possible Values
s.dynamicAccountSelection=[true|false]
Only 'true' and 'false' are allowed as values of dynamicAccountSelection.
Examples
s.dynamicAccountSelection=true
s.dynamicAccountSelection=false
Configuration Settings
None
Pitfalls, Questions, and Tips
• Dynamic account selection is not supported by About AppMeasurement for JavaScript.
• Always use the DigitalPulse Debugger to determine which report suite is receiving data from each page.
dynamicVariablePrefix
The dynamicVariablePrefix variable allows deployment to flag variables, which should be populated dynamically.
Cookies, request headers, and image query string parameters are available to be populated dynamically.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
D=
Any
D=
Syntax and Possible Values
s.prop1=&quot;D=User-Agent”
OR USE CUSTOM FLAG FOR DYNAMIC VARIABLES
s.dynamicVariablePrefix=&quot;..&quot;
Examples
s.prop1=&quot;D=User-Agent”
OR USE CUSTOM FLAG FOR DYNAMIC VARIABLES
s.dynamicVariablePrefix=&quot;..&quot;
s.prop1=&quot;..User-Agent&quot;
Pitfalls, Questions, and Tips
• Dynamic variables can be used to significantly reduce the total length of the URL by copying values into other
variables.
• Dynamic variables can be used to collect data from headers and cookies not otherwise available for data collection.
eVarN
The eVar variables are used for building custom reports.
When an eVar is set to a value for a visitor, the value is remembered until it expires. Any success events that a
visitor encounters while the eVar value is active are counted toward the eVar value.
Analytics Variables
70
Max Size
Debugger Parameter
Reports Populated
Default Value
255 Bytes
V1-v75 (or v100 or v250)
Custom Conversion
&quot;&quot;
Expiration
eVars expire after a time period you specify. After the eVar expires, it no longer receives credit for success events.
eVars can also be configured to expire on success events. For example, if you have an internal promotion that
expires at the end of a visit, the internal promotion receives credit only for purchases or registrations that occur
during the visit in which they were activated.
There are two ways to expire an eVar:
• You can set the eVar to expire after a specified time period or event.
• You can use force the expiration of an eVar, which is useful when repurposing a variable.
If an eVar is used in May to reflect internal promotions and expires after 21 days, and in June it is used to capture
st
internal search keywords, then on June 1 , you should force the expiration of, or reset, the variable. Doing so will
help keep internal promotion values out of June's reports.
Case Sensitivity
eVars are case insensitive, but they are displayed in the capitalization of the first occurrence. For example, if the
first instance of eVar1 is set to &quot;Logged In,&quot; but all subsequent instances are passed as &quot;logged in,&quot; reports always
show &quot;Logged In&quot; as the value of the eVar.
Counters
While eVars are most often used to hold string values, they may also be configured to act as counters. eVars are
useful as counters when you are trying to count the number of actions a user takes before an event. For example,
you may use an eVar to capture the number of internal searches before purchase. Each time a visitor searches, the
eVar should contain a value of '+1.' If a visitor searches four times before a purchase, you will see an instance for
each total count: 1.00, 2.00, 3.00, and 4.00. However, only the 4.00 receives credit for the purchase event (Orders
and Revenue Metrics). Only positive numbers are allowed as values of an eVar counter.
Subrelations
A common requirement for a Custom eVar report is the ability to break down one Custom eVar report by another.
For example, if one eVar contains gender, and another contains salary, you may ask the following question: of the
female visitors to my site, how much revenue was generated by women who make more than $50,000 per year.
Any eVar that is fully sub-related allows this type of break down in reports. For example, if the gender eVar has full
subrelations enabled, all other custom eVar reports can be broken down by gender, and gender can be broken down
by all others. To see the relationship between two reports, only one of them needs full subrelations enabled. By
default, Campaigns, Products, and Category reports are fully sub-related (any eVar can be broken down by
campaign or products).
Syntax and Possible Values
While eVars may be renamed, they should always be referred to in the JavaScript file by eVarX, where X is a number
between 1 and 75 (or 100, or 250).
s.eVarX=&quot;value&quot;
Analytics Variables
71
When not used as a counter, eVars have the same limitations as all other variables. If the eVar is a &quot;counter,&quot; it is
expected to receive numeric values like &quot;1&quot; or &quot;2.5.&quot; If more than two decimal places are given, the eVar counter
rounds to two decimal places. An eVar counter may not contain negative numbers.
Examples
s.eVar1=&quot;logged in&quot;
s.eVar23=&quot;internal spring promo 4&quot;
Configuration Settings
eVars can be configured in the Admin Console. All eVars can be configured with a Name, Type, Allocation, Expire
After Setting, or Reset. Each configuration setting is addressed separately.
Setting
Description
Name
Allows you to change the name of the eVar report within Analytics.
The eVar should still be referenced as s.eVarX in the JavaScript code, no matter
what name is given to the report in Analytics.
Type
Allows you to show whether the eVar is a Text String or Counter.
Allocation
Used to configure which value of the eVar receives credit for success events.
If Allocation is set to &quot;Most Recent (Last),&quot; then B receives credit.
If Allocation is set to &quot;Original Value (First)&quot; then A receives credit.
If Allocation is set to &quot;Linear&quot;, then both A and B receive credit for half the purchase
value.
Expire After
Lets you determine whether an eVar expires on a specific event, like purchase, or
after a custom or predefined time period.
Reset
By selecting the Reset check box for an eVar, and clicking Save at the bottom of
the page, all values of that eVar are immediately expired. After this happens, only
new values of the eVar receive credit for success events.
Pitfalls, Questions, and Tips
• Unlike prop variables, eVar variables are not allowed to be lists of delimited values. If you populate an eVar with
a list of values, for example &quot;one,two,three,&quot; then that exact string appears in reports.
• eVar counters may not contain negative numbers.
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:
Overview
If you have this Adobe
Analytics Product
You now have access to
SiteCatalyst
75 eVars, 100 Events
Analytics Variables
If you have this Adobe
Analytics Product
72
You now have access to
Adobe Analytics (Standard) 100 eVars, 1000 Events
Adobe Analytics - Mobile
Apps
100 eVars, 1000 Events
Adobe Analytics Premium - 250 eVars, 1000 Events
Attribution
Adobe Analytics Premium - 250 eVars, 1000 Events
Predictive Intelligence
Adobe Analytics Premium - 250 eVars, 1000 Events
Customer 360
Adobe Analytics Premium - 250 eVars, 1000 Events
Complete
Populating Variables and Events
• Variables can be populated in the data collection library if you are using these versions of AppMeasurement:
• AppMeasurement for JavaScript version 1.4+
• AppMeasurement for Flash version 3.9+
• AppMeasurement for Java version 1.2.8+
• AppMeasurement for Silverlight/.NET version 1.4.2+
• AppMeasurement for PHP version 1.2.2+
• If you are on an earlier version of code, or on JavaScript H.*, you can populate context data and use processing
rules to populate variables.
• All versions of data collection code can populate events 101-1000.
• Processing rules can be used to populate eVars 76-250 based on context data or other variables.
Frequently Asked Questions
• Will all Adobe Analytics interfaces have immediate access to these new variables?
These interfaces will have immediate access: Reports &amp; Analytics, Report Builder, Ad Hoc Analysis, and APIs.
However, the Data Workbench feed from Analytics will not be updated for the new variables until May. If you turn
on a variable, you won't be able to access it in Data Workbench until the next version of Data workbench is released
(in the May 2015 time frame.)
• Will these additional eVars and events automatically show up in my data feeds?
Data feeds will have access to the new variables and events once enabled. New eVar columns will not appear
until you choose to include them. However, new events will appear in the event_list column as soon as they’re
enabled, and the events lookup table contains the event names for those event IDs. Do not enable new events
unless you are ready to consume them in Data Feeds.
• How do I request new data feed columns?
To request new columns, refer to Configuring Data Feeds.
• What if I am an Analytics Premium customer who wants to go back to Analytics Standard and I currently
have 150 eVars enabled?
Analytics Variables
73
Adobe will not disable any of your existing eVars, but we are also not going to allow you to enable more. If you
disable eVars, you cannot turn them back on until you are below the limit of 100 enabled eVars that Analytics
Standard qualifies you for.
events
The events variable is used to record common shopping cart success events as well as custom success events.
Max Size
Debugger Parameter
No Limit
events
Reports Populated
Shopping Cart Events
Default Value
N/A
Custom Events
An event should be considered a milestone within a site. Success events are most commonly populated on the final
confirmation page of a process, such as a registration process or newsletter sign-up. Custom events are defined by
populating the events variable with the literal values defined in the Possible Values section below.
By default, success events are configured as counter events. Counter events count the number of times a success
event is set (x+1). Events can also be configured as numeric events. Numeric events allow you to specify the number
to increment (as might be necessary when counting dynamic or arbitrary values, such as the number of results
returned by an internal search).
A final event type, currency, allows you to define the amount to be added (similar to numeric events), but displays
as currency in reports, and is subject to currency conversions based on the s.currencyCode value and the default
currency setting for your report suite. For additional information on using numeric and currency events, see Products.
Configuring the Variable
The s.events variable is enabled by default for all implementations. The seven pre-configured conversion events
are automatically enabled for all new report suites. New custom events (event1-event100 or event1000) can be
enabled by any admin-level user using the Admin Console.
Possible Values
The following is a list of possible values for the events variable:
Event
Description
Reports Populated
prodView
Product Views
Products
scOpen
Open / Initialize a new shopping cart Carts
scAdd
Add item(s) to the shopping cart
Cart Additions
scRemove
Remove item(s) from the shopping
cart
Cart Removals
scView
View shopping cart
Cart Views
scCheckout
Beginning of the checkout process
Checkouts
purchase
Completion of a purchase (order)
Orders
event1 - event1000 (event100 for
point product)
Custom events
Custom Events
Analytics Variables
74
Syntax and Examples
Counter Events
Counter events are set by placing the desired events in the s.events variable, in a comma-separated list (if multiple
events are to be passed).
s.events=&quot;scAdd&quot;
s.events=&quot;scAdd,event1,event7&quot;
s.events=&quot;event5&quot;
s.events=&quot;purchase,event10&quot;
If on H23 code or higher, counter events can have integers greater than one assigned to them.
s.events=&quot;event1=10&quot;
s.events=&quot;scRemove=3,event6,event2=4&quot;
Implementing counter events with assigned integer values treat the event as if it fired multiple times within the image
request. Counter events do not allow decimals- it is recommended to use numeric events instead if this functionality
is required.
Numeric/Currency Events
Numeric and currency events must be included in the s.events variable, though they typically receive their numerical
value (e.g., 24.99) in the s.products variable. This allows you to tie specific numeric and currency values to individual
product entries.
With Products
s.events=&quot;event1&quot;
s.products=&quot;Footwear;Running Shoes;1;99.99;event1=4.50&quot;
s.events=&quot;event1,event4&quot;
s.products=&quot;Footwear;Running Shoes;1;99.99;event1=4.50|event4=1.99&quot;
Without Products
You can also track these types of events by leaving the product and category fields blank. This was the process to
measure data such as tax and shipping before support was added for decimal values outside of the products string.
If you want to pass a numeric or currency value but do not want to tie these to an individual product (such as a
discount applied to an entire order, or a value captured outside of the product view or shopping cart process), this
can be done by using s.products as shown below, but leaving the product and category fields blank.
s.events=&quot;event1&quot;
s.products=&quot;;;;;event1=4.50&quot;
s.events=&quot;event1,event4&quot;
s.products=&quot;;;;;event1=4.50|event4=1.99&quot;
In the Events List
Numeric/Currency Events that are given a value directly in events list apply to all products in the products list.
This is useful to track order-wide discounts, shipping, and similar values, without modifying the product price or by
tracking it in the product list separately. For example, if you configured event10 to contain order-wide discounts, a
purchase with a 10% discount might appear similar to the following:
s.events=&quot;purchase,event10=9.95&quot;
s.products=&quot;Footwear;Running Shoes;1;69.95,Running Essentials;Socks;10;29.50&quot;
On Numeric/Currency Event reports, the report total represents the de-duplicated event total (in this example, the
total amount of discounts during the reporting period), not the sum of the event values for each product.
Analytics Variables
75
Note: if a value for a Numeric/Currency Event is specified in the products string and in the event string, the
value from the event string is used.
Combining Counter Events and Numeric/Currency Events
Counter events can be passed along with numeric/currency events by passing all desired events in the s.events
variable, and then passing only the numeric/currency events in the s.products variable.
Event Serialization
By default, an event is counted every time the event is set on your site.
See Event Serialization for more information.
Syntax
s.events=&quot;event1:3167fhjkah&quot;
Examples
s.events=&quot;scAdd:003717174&quot;
s.events=&quot;scAdd:user228197,event1:577247280,event7:P7fhF8571&quot;
fpCookieDomainPeriods
The fpCookieDomainPeriods variable is for cookies set by JavaScript (s_sq, s_cc, plug-ins) that are inherently
first-party cookies even if your implementation uses the third-party 2o7.net or omtrdc.net domains.
The fpCookieDomainPeriods variable should never be dynamically set . If you use cookieDomainPeriods, it is good
practice to specify a value for fpCookieDomainPeriods as well. fpCookieDomainPeriods inherits the
cookieDomainPeriods value. Note that fpCookieDomainPeriods does not affect the domain on which the visitor ID
cookie is set, even if your implementation treats this as a first-party cookie.
The name &quot;fpCookieDomainPeriods&quot; refers to the number of periods (&quot;.&quot;) in the domain when the domain begins
with &quot;www.&quot; For example, www.mysite.com contains two periods, while www.mysite.co.jp contains three periods.
Another way to describe the variable is the number of sections in the main domain of the site (two for mysite.com
and three for mysite.co.jp).
The AppMeasurement for JavaScript file uses the fpCookieDomainPeriods variable to determine the domain with
which to set first-party cookies other than the visitor ID (s_vi) cookie. There are at least two cookies affected by
this variable, including s_sq and s_cc (used for visitor click map and cookie checking respectively). Cookies used
by plug-ins such as getValOnce are also affected.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
cookieDomainPeriods
Sample Code for Setting Cookie Domain Variables
s.fpCookieDomainPeriods=&quot;2&quot;
var d=window.location.hostname
if(d.indexOf('.co.uk')&gt;-1||d.indexOf('.com.au')&gt;-1)
s.fpCookieDomainPeriods=&quot;3&quot;
Analytics Variables
76
Syntax and Possible Values
The cookieDomainPeriods variable is expected to be a string, as shown below.
s.fpCookieDomainPeriods=&quot;3&quot;
Examples
s.fpCookieDomainPeriods=&quot;3&quot;
s.fpCookieDomainPeriods=&quot;2&quot;
Configuration Settings
None
hierN
The hierarchy variable determines the location of a page in your site's hierarchy.
This variable is most useful for sites that have more than three levels in the site structure. For example, a media
site may have 4 levels to the Sports section: Sports, Local Sports, Baseball, and Red Sox. If someone visits the
Baseball page, Sports, Local Sports, and Baseball, all levels reflect that visit.
Max Size
Debugger Parameter
Reports Populated
Default Value
255 Bytes
H1-H5
Hierarchy
&quot;&quot;
There are five hierarchy variables available, which must be enabled by Adobe ClientCare. At the time the hierarchy
is enabled, you should decide on a delimiter for the variable and the maximum number of levels for the hierarchy.
For example, if the delimiter is a comma, the sports hierarchy may display as follows.
s.hier1=&quot;Sports,Local Sports,Baseball&quot;
Make sure that none of your section names have the delimiter in them. For example, if one of your sections is called
&quot;Coach Griffin, Jim,&quot; then you should choose a delimiter other than comma. Each hierarchy section is limited to 255
bytes, while the total variable limit is 255 bytes. After a delimiter is chosen (at the time the hierarchy is created) it is
not easily changed.
Contact Adobe ClientCare about changing the delimiter for an existing hierarchy. Delimiters may also consist of
multiple characters, such as || or /|\, which are less likely to appear in a hierarchy section.
Syntax and Possible Values
Do not put a space between each delimiter. In the following example syntax, N is a number between one and five.
s.hierN=&quot;Level 1[&lt;delimiter&gt;Level 2[&lt;delimiter&gt;Level 3[...]]]&quot;
Do not use the delimiter except to delimit the levels of the hierarchy. The delimiter may be any character or characters
of your choice.
Examples
s.hier1=&quot;Toys|Boys 6+|Legos|Super Block Tub&quot;
s.hier4=&quot;Sports/Local Sports/Baseball&quot;
Configuration Settings
None
Analytics Variables
77
Pitfalls, Questions, and Tips
• Before implementing hierarchies, see the Channels and Hierarchies white paper.
• The delimiter may not be changed after the hierarchy is set up. If the delimiter for your hierarchy must be changed,
contact Adobe ClientCare.
• The number of levels may not be changed after the hierarchy is set up.
Note: Changes to hierarchies can result in a service charge.
homepage
The homepage variable, in Internet Explorer, indicates whether the current page is set as the user's home page.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
Reports Affected
hp
Y or N
Y
Traffic &gt; Technology &gt;
Home Page
javaEnabled
The javaEnabled variable indicates whether Java is enabled on the browser.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
Reports Affected
v
Y or N
Y
Traffic &gt; Technology &gt; Java
javascriptVersion
The javascriptVersion variable indicates the version of JavaScript supported by the browser.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Analytics Variables
78
Query Param
Value
Example
Reports Affected
j
1.0, 1.1, 1.2, … 1.7
1.7
Traffic &gt; Technology &gt;
JavaScript Version
Version H.10 and higher of the JavaScript file accurately detect up to version 1.7 (the highest version at the time
H.10 was released). Prior versions of the JavaScript file only detected up to version 1.3
linkDownloadFileTypes
The linkDownloadFileTypes variable is a comma-separated list of file extensions.
If your site contains links to files with any of these extensions, the URLs of these links will appear in the File
Downloads report.
Max Size
Debugger Parameter
Reports Populated
N/A
N/A
Traffic &gt; Site Traffic &gt; File
Downloads
Default Value
&quot;exe,zip,wav,mp3,mov,mpg,avi,wmv,
doc,pdf,xls&quot;
The linkDownloadFileTypes variable is only relevant when trackDownloadLinks is set to 'True.'
Only left-mouse-clicks on a link are counted in the File Downloads report. All file downloads that start automatically
when a page loads, or that are only downloaded after a redirect, are not counted in the File Downloads report.
When you right-click a file and select the &quot;Save Target As...&quot; option, it is not counted in the File Downloads report.
The linkDownloadFileTypes variable may be used to track clicks to RSS feeds. If you have links to RSS feeds with
a .xml or other extension, appending &quot;,xml&quot; to the linkDownloadFileTypes list allows you to see how often each RSS
link is clicked.
The following sections contain more information:
• Syntax and Possible Values
• Examples
• Configuration Settings
• Pitfalls, Questions, and Tips
Syntax and Possible Values
Only include file extensions (no spaces).
s.linkDownloadFileTypes=&quot;type1[,type2[,type3[...]]]&quot;
Any file extension may be included in the list. Be careful not to include a common file extension, such as htm or
aspx, in linkDownloadFileTypes. Doing so causes an extra image request to be sent for each click, which will be
billed as a primary server call.
Examples
s.linkDownloadFileTypes=&quot;exe,zip,wav,mp3,mov,mpg,avi,wmv,doc,pdf,xls&quot;
s.linkDownloadFileTypes=&quot;exe,zip,wav,mp3,mov,mpg,avi,wmv,doc,pdf,xls,xml&quot;
Configuration Settings
None
Analytics Variables
79
Pitfalls, Questions, and Tips
• Only left-clicks on download files cause the URL to appear in the File Downloads report.
• Including a common file extension in linkDownloadFileTypes may significantly increase the total server calls sent
to Adobe's servers.
• Links to server-side redirects or HTML pages that automatically begin downloading a file are not counted unless
the file extension is in linkDownloadFileTypes.
• Links that use JavaScript (such as javascript:openLink( )) are not counted in file downloads.
linkExternalFilters
If your site contains many links to external sites, and you do not want to track all exit links, use linkExternalFilters
to report on a specific subset of exit links.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
Paths &gt; Entries &amp; Exits &gt;
Exit Links
&quot;&quot;
The linkExternalFilters variable is an optional variable used in conjunction with linkInternalFilters to determine whether
a link is an exit link. An exit link is defined as any link that takes a visitor away from your site. Whether the target
window of an exit link is a popup or the existing window, it does not affect whether the link appears in the exit links
report. Exit links are tracked only if trackExternalLinks is set to 'true.' The filters in linkExternalFilters and
linkInternalFilters are case insensitive.
Note: If you don't want to use linkExternalFilters, delete it or set it to &quot;&quot;.
The filters list in linkExternalFilters and linkInternalFilters apply to the domain and path of any link by default. If
linkLeaveQueryString is set to 'true,' the filters apply to the entire URL (domain, path, and query string). These filters
are always applied to the absolute path of the URL, even if a relative path is used as the href value.
Most companies find that linkInternalFilters gives them enough control over exit links that they don't need
linkExternalFilters. Using linkExternalFilters simply decreases the likelihood that an exit link is considered external.
If linkExternalFilters has a value, then a link is considered only external if it does not match linkInternalFilters and
does match linkExternalFilters.
The following example illustrates how this variable is used. In this example, the URL of the page is
http://www.mysite.com/index.html.
s.trackExternalLinks=true
s.linkInternalFilters=&quot;javascript:,mysite.com&quot;
s.linkExternalFilters=&quot;site1.com,site2.com,site3.com/partners&quot;
s.linkLeaveQueryString=false
...
&lt;a href=&quot;http://www.mysite.com&quot;&gt;Not an Exit Link&lt;/a&gt;
&lt;a href=&quot;/careers/job_list.html&quot;&gt;Not an Exit Link&lt;/a&gt;
&lt;a href=&quot;http://www2.site3.com&quot;&gt;Not an Exit Link&lt;/a&gt;
&lt;a href=&quot;http://www.site1.com&quot;&gt;Exit Link&lt;/a&gt;
&lt;a href=&quot;http://www2.site3.com/partners/offer.asp&quot;&gt;Exit Link&lt;/a&gt;
Syntax and Possible Values
The linkExternalFilters variable is a comma-separated list of ASCII characters. No spaces are allowed.
s.linkExternalFilters=&quot;site1.com[,site2.com[,site3.net[...]]]&quot;
Any portion of a URL might be included in linkExternalFilters, separated by commas.
Analytics Variables
80
Examples
s.linkExternalFilters=&quot;partnersite.com,partnertwo.net/path/&quot;
s.linkExternalFilters=&quot;&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• Using linkExternalFilters can result in fewer links on your site being exit links. Do not use this variable in place of
linkInternalFilters to force internal links to become exit links.
• If linkExternalFilters should be applied to the query string of a link, make sure linkLeaveQueryString is set to 'true.'
See linkLeaveQueryString before setting to &quot;true&quot;.
• To disable exit link tracking, set trackExternalLinks to &quot;false&quot;.
linkInternalFilters
The linkInternalFilters variable is used to determine which links on your site are exit links.
It is a comma-separated list of filters that represent the links that are part of the site.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
Paths &gt; Entries &amp; Exits &gt;
Exit Links
&quot;javascript:&quot;
The linkInternalFilters variable is used to determine whether a link is an exit link, which is defined as any link that
takes a visitor away from your site. Whether the target window of an exit link is a pop-up, or the existing window,
does not affect whether the link appears in the exit links report. Exit links are only tracked if trackExternalLinks is
set to &quot;true&quot;. The filters in linkInternalFilters are not case-sensitive.
The list of filters in linkInternalFilters applies to the domain and path of any link by default. If linkLeaveQueryString
is set to &quot;true&quot;, then the filters apply to the entire URL (domain, path, and query string). The filters are always
applied to the absolute path of the URL, even if a relative path is used as the href value.
Be careful that all the domains of your site (and any partners who are using your JavaScript file) are included in
linkInternalFilters. If you do not have all domains included in the list, all links on and to those domains are considered
exit links, increasing the server calls sent. If you would like multiple domains or companies to use a single
AppMeasurement for JavaScript file, you may consider populating linkInternalFilters on the page, overriding the
value specified in the JavaScript file. If you have vanity domains that immediately redirect to your main domain,
those vanity domains do not need to be included in the list.
The following example illustrates how this variable is used. In this example, the URL of the page is
http://www.mysite.com/index.html.
s.trackExternalLinks=true
s.linkInternalFilters=&quot;javascript:,mysite.com&quot;
s.linkExternalFilters=&quot;&quot;
s.linkLeaveQueryString=false
...
&lt;a href=&quot;http://www.mysite.com&quot;&gt;Not an Exit Link&lt;/a&gt;
&lt;a href=&quot;/careers/job_list.html&quot;&gt;Not an Exit Link&lt;/a&gt;
&lt;a href=&quot;http://www2.site3.com&quot;&gt;Exit Link&lt;/a&gt;
&lt;a href=&quot;http://www2.site1.com/partners/&quot;&gt;Exit Link&lt;/a&gt;
Analytics Variables
81
Syntax and Possible Values
The linkInternalFilters variable is a comma-separated list of ASCII characters. No spaces are allowed.
s.linkInternalFilters=&quot;javascript:,site1.com[,site2.com[,site3.net[...]]]&quot;
The default value of linkInternalFilters contains &quot;javascript:&quot; because any links to a JavaScript function are not
usually exit links. If &quot;javascript:&quot; were not in the list, then all links to JavaScript functions would be considered
external.
Examples
s.linkInternalFilters=&quot;javascript:,mysite.com&quot;
s.linkInternalFilters=&quot;javascript:,mysite.com,mysite.net,vanity1.com&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• Include all domains that the AppMeasurement for JavaScript file may be served under in the filter list.
• Periodically check the Paths &gt; Entries &amp; Exits &gt; Exit Links report to make sure that none of the entries in that
report are incorrect.
• Periodically review partner contracts to determine if they contain restrictions on link tracking. For example, you
might be prohibited from tracking links that appear in partner display ads. Filter partner links by adding their domain
to linkInternalFilters:
s.linkInternalFilters=&quot;javascript:,mysite.com,mysite.net,mypartner.net/adclick&quot;
linkLeaveQueryString
By default, query strings are excluded from all reports.
For some exit links and download links, the important portion of the URL can be in the query string, as shown in the
following sample URL.
http://www.mycompany.com/download.asp?filename=myfile.exe
The download file name can be defined in the query string and, consequently, the query string is necessary to make
the File Downloads report more accurate.
The linkLeaveQueryString variable determines whether or not the query string should be included in the Exit Links
and File Download reports.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
Exit Links
false
File Downloads
Note: Setting linkLeaveQueryString=true includes all query string parameters for all exit links and download
links.
Syntax
s.linkLeaveQueryString=[false/true]
Analytics Variables
82
Examples
s.linkLeaveQueryString=false
Possible Values
s.linkLeaveQueryString=false
s.linkLeaveQueryString=true
Configuring the Variable
No configuration is necessary for this variable.
Pitfalls, Questions, and Tips
• Setting s.linkLeaveQueryString=true includes all query string parameters for all exit links and download links.
• The linkLeaveQueryString variable does not affect recorded page URLs, visitor click map, or Path reports.
linkName
The linkName variable is an optional variable used in Link Tracking that determines the name of a custom, download,
or exit link.
The linkName variable is not normally needed because the third parameter in the tl() function replaces it.
Max Size
Debugger Parameter
100 bytes
pev2
Reports Populated
File Downloads
Default Value
&quot;&quot;
Custom Links
Exit Links
Custom Links refer to links that send tracking data. The linkName variable (or the third parameter in the tl() function)
is used to identify the value that appears in the Custom, Download, or Exit Links report. If linkName is not populated,
the URL of the link appears in the report.
Syntax and Possible Values
s.linkName=&quot;Link Name&quot;
There are no limitations on linkName outside of the standard variable limitations.
Examples
s.linkName=&quot;Nav Bar Home Link&quot;
s.linkName=&quot;Partner Link to A.com&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• The linkName variable is replaced by the third parameter in the tl() function.
• If the linkName variable and the third parameter in the tl() function are blank, the full URL of the link (with the
exception of the query string) appears in the report (even if the link is relative).
Analytics Variables
83
linkTrackEvents
The linkTrackEvents variable is a comma-separated list of events that are sent with a custom, exit, or download
link.
If an event is not in linkTrackEvents, it is not sent to Analytics, even if it is populated in the onClick event of a link,
as shown in the following example:
s.linkTrackVars=&quot;events&quot;
s.events=&quot;event1,event2&quot;
s.t() // both event1 and event2 are recorded
&lt;a href=&quot;help.php&quot; onClick=&quot;s=s_gi('rs1');s.tl(this,'o')&quot;&gt;event1 is recorded&lt;/a&gt;
&lt;a href=&quot;test.php&quot; onClick=&quot;s=s_gi('rs1');s.events='event2';s.tl(this,'o')&quot;&gt;No events are
recorded&lt;/a&gt;
In the first link to help.php, notice that the events variable retains the value that was set before the link was clicked,.
This allows event1 to be sent with the custom link. In the second example, the link to test.php, event2 is not
recorded because it is not listed in linkTrackEvents.
To avoid confusion and potential problems, Adobe recommends populating linkTrackVars and linkTrackEvents in
the onClick event of a link that is used for link tracking.
The linkTrackEvents variable contains the events that should be sent with custom, download, and exit links. This
variable is only considered if linkTrackVars contains &quot;events.&quot;
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
Conversion
&quot;None&quot;
Syntax and Possible Values
The linkTrackEvents variable is a comma-separated list of events (no spaces).
s.linkTrackEvents=&quot;event1[,event2[,event3[...]]]&quot;
Only event names are allowed in linkTrackEvents. These events are listed in Events. If a space appears before or
after the event name, the event can not be sent with any link image requests.
Examples
s.linkTrackEvents=&quot;purchase,event1&quot;
s.linkTrackEvents=&quot;scAdd,scCheckout,purchase,event14&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• The JavaScript file only uses linkTrackEvents if linkTrackVars contains the &quot;events&quot; variable. &quot;events&quot; should be
included in linkTrackVars only when linkTrackEvents is defined.
• Beware if an event is fired on a page, and is listed in linkTrackEvents. That event is recorded again with any exit,
download, or custom links unless the events variable is reset prior to that event (in the onClick of a link or after
the call to the t() function).
• If linkTrackEvents contains spaces between event names, the events are not recorded.
Analytics Variables
84
linkTrackVars
The linkTrackVars variable is a comma-separated list of variables that are sent with custom, exit, and download
links.
If linkTrackVars is set to &quot;&quot;, all variables that have values are sent with link data. To avoid inflation of instances or
page views associated with other variables, Adobe recommends populating linkTrackVars and linkTrackEvents in
the onClick event of a link that is used for link tracking.
All variables that should be sent with link data (custom, exit, and download links) should be listed in linkTrackVars.
If linkTrackEvents is used, linkTrackVars should contain &quot;events.&quot;
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
Any
&quot;None&quot;
When populating linkTrackVars, do not use the 's.' prefix for variables. For example, instead of populating linkTrackVars
with &quot;s.prop1,&quot; you should populate it with &quot;prop1.&quot; The following example illustrates how linkTrackVars should be
used.
s.linkTrackVars=&quot;eVar1,events&quot;
s.linkTrackEvents=&quot;event1&quot;
s.events=&quot;event1&quot;
s.eVar1=&quot;value A&quot;
s.eVar2=&quot;value B&quot;
s.t() // eVar1, event1 and event2 are recorded
&lt;a href=&quot;http://google.com&quot;&gt;event1 and eVar1 are recorded&lt;/a&gt;
&lt;a href=&quot;test.php&quot; onClick=&quot;s=s_gi('rs1');s.eVar1='value C';s.events='';s.tl(this,'o')&quot;&gt;eVar1
is recorded&lt;/a&gt;
Because the link to google.com is an exit link (unless you are Google), event1 and eVar1 are sent with the exit link
data, increasing the instances associated with eVar1 and the number of times event1 is fired. In the link to test.php,
eVar1 is sent with a value of 'value C' because that is the current value of eVar1 at the time that tl() is called.
Syntax and Possible Values
The linkTrackVars variable is a case-sensitive, comma-separated list of variable names, without the object name
prefix. Use 'eVar1' instead of 's.eVar1.'
s.linkTrackVars=&quot;variable_name[,variable_name[...]]&quot;
The linkTrackVars variable may contain only variables that are sent to Analytics, namely: events, campaign,
purchaseID, products, eVar1-75, prop1-75, hier1-5, channel, server, state, zip, and pageType.
Examples
s.linkTrackVars=&quot;events,prop1,eVar49&quot;
s.linkTrackVars=&quot;products&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• If linkTrackVars is blank, all variables that have values are tracked with all server calls.
• Any variable listed in linkTrackVars that has a value at the time of any download, exit, or custom link, are tracked.
Analytics Variables
85
• If linkTrackEvents is used, linkTrackVars must contain &quot;events.&quot;
• Do not use the &quot;s.&quot; or &quot;s_objectname.&quot; prefix for variables.
linkType
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).
The linkType variable is not normally needed because the second parameter in the tl() function replaces it.
Max Size
Debugger Parameter
One character
pe=[lnk_o|lnk_d|lnk_e]
Reports Populated
File Downloads
Default Value
&quot;&quot;
Custom Links
Exit Links
Custom links send data to Analytics. The linkType variable (or the second parameter in the tl() function) is used to
identify the report in which the link name or URL appears (Custom, Download, or Exit Links report).
For exit and download Links, the linkType variable is automatically populated depending on whether the link clicked
is an exit or download link. A custom link may be configured to send data to any of the three reports with this variable
or with the second parameter in the tl() function. By setting linkType to 'o,' 'e,' or 'd,' the linkName or link URL is sent
to the Custom Links, Exit Links, or File Downloads report respectively.
Syntax and Possible Values
The linkType variable may only contain a single character, namely 'o,' 'e,' or 'd.'
s.tl(this,’o’,’Link Name’);
Examples
&lt;a href=&quot;index.html&quot; onClick=&quot;
var s=s_gi('rsid'); **see note below on the rsid**
s.tl(this,'o','Link Name');
&quot;&gt;My Page&lt;/a&gt;
Configuration Settings
None
Pitfalls, Questions, and Tips
• If linkType is not specified, custom links ('o') is assumed.
List Props
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.
Considerations
Analytics Variables
86
• List props are enabled only on traffic variables (props).
• Pathing and correlations cannot be enabled for list props.
• Analytics provides visits and unique visitors to almost every report, including all list prop reports.
• Classifications are supported for list props.
• Any custom traffic variable can become a list prop. (Exceptions: pageName, channel, and server.)
• When defining duplicate values in the same image request, instances are not deduplicated.
A prop can be changed into a list prop on the Admin Tools &gt; Report Suite &gt; Traffic Variables page by enabling List
Support and then selecting a delimiter. Popular delimiters are colons, semi-colons, commas, or pipes. The delimiter
can technically be any of the first 127 ASCII characters.
Implementation Examples
When you request enabling of list props, indicate the delimiter that you would like to use. After the s.prop of your
choice is enabled, multiple values can be set in the variable as shown in the following examples:
A list prop delimited by a pipe, passing in two values:
s.prop1=&quot;Banner ad impression|Sidebar impression&quot;
A list prop delimited by a comma passing in several values:
s.prop2=&quot;cerulean,vermilion,saffron&quot;
List props can also be sent with a single value:
s.prop3=&quot;Single value&quot;
The delimiter can be changed at any time. However, the implementation must match the new delimiter. Failure to
use the correct delimiter results in the list prop value being treated as a single concatenated line item in reporting.
Because a list prop is still a Traffic Variable, it is subject to Traffic Variable limitations. List props are limited to 100
bytes of data and are affected by case sensitivity settings.
List Variable
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.
Considerations:
• List Vars remember their specific values by referencing the VisitorID cookie in the visitor's browser.
• Each delimited value can contain a maximum of 255 characters (or less if using multi-byte characters).
• There is no limit to the number of characters within this variable. The only exception to this limitation is within older
Internet Explorer browsers, which impose a 2083-character limitation on all URL requests.
• A total of three List Vars are available per report suite.
• Using List Vars requires H23 code or higher.
• List Vars can be classified.
• If duplicate values are defined in the same image request, list vars deduplicate all instances of those values.
• The most granular list vars can be segmented is on a hit (or page view) level. If you have a list var with three values
in the same image request, any segment rules that match one value will pull all three into reporting. Conversely,
if an exclude rule is defined that matches a single value, all three values are excluded.
Analytics Variables
87
Configuration
An Adobe representative must enable List Vars. The following customizations are available, which are to be included
when requesting to enable one:
• Value Delimiter: The character used to separate values within the List Var. Most commonly these are characters
such as commas, colons, pipes, or something similar.
Note: Multi-byte characters are not supported as delimiters in List Vars. The delimiter must be single byte.
• Expiration: Similar to eVar expiration, this determines the amount of time that can occur between the List Var and
the conversion event for them to be related.
• At a page view or visit level: Success events beyond the page view or visit would not link back to any values
within the List Var.
• Based on a time period, such as day, week, month, etc: Success events beyond the specified time period
would not link back to any values within the List Var. A custom number of days can be defined as well.
• Specific conversion events: Any other success events that fire after the specific event designated would not
link back to any values within the List Var.
• Never: Any amount of time can pass between the List Var and success event.
• Allocation: This setting determines how success events divide credit between values:
• Full: All variable values defined prior to the variable's expiration get full credit for success events.
• Linear: All variable values defined prior to the variable's expiration get credit divided credit for conversion events.
• Variable values are never overwritten, but instead added to the values that get credit for success events.
• Max Values: Designates the number of active values allowed for this list variable. For example, if set to 3, only
the last 3 values captured is saved and any previous values captured are discarded. Note that if multiple values
for the same list var are sent in on the same hit and you have restricted using max values, each value will have
the same timestamp and there is not guarantee as to which value is saved. The default is unlimited (0).
The Max Values setting is useful to limit attribution to a specific number of values. For example, if a list var is set
to &quot;A,B,C&quot; on the first page of a visit, then set to &quot;X,Y,Z&quot; on the next page, attribution is distributed to these six
values based on the allocation. If you wanted to limit attribution to only &quot;X,Y,Z&quot;, you can set max values to three.
To set up or edit List Vars, go to Analytics &gt; Admin &gt; Report Suites &gt; Edit Settings &gt; Conversion &gt; List
Variables.
Implementation Examples
Each of the following examples use a comma for the value delimiter.
Defining a single value within a List Var:
s.list1=&quot;Cat&quot;;
Passing in multiple values:
s.list2=&quot;Tabby,Persian,Siamese&quot;;
s.list1=&quot;Product 1,Product 2,Product 3&quot;;
Attributing revenue to a List Var:
//Define this code on the landing page:
s.list3=&quot;Top Banner Ad,Side Bar Ad,Internal Campaign 1&quot;;
//Have these variables fire on the purchase confirmation page:
s.products=&quot;;Kitten;1;50&quot;
s.events=&quot;purchase&quot;;
Analytics Variables
88
This result would show three line items with $50 each in revenue. (Top Banner Ad; Side Bar Ad; and Internal
Campaign 1.) Note the total for this report deduplicates revenue, so the total would also reflect $50.
Attributing revenue to a List Var that was set multiple times during a visit:
Allocation: Full
Expiration: Visit
Page
s.list1
s.events/s.products
Page 1
s.list1=”value1,value2,value3”;
(not set)
Page 2
s.list1=”value4,value5,value6”;
s.events=”purchase”;
s.products=”;product;1;200”
Result: All values set in the list var1 at any point during the visit (value1,value2,value3,value4,value5,value6) get
full credit for the purchase.
maxDelay
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.
Implementation Example
s.maxDelay=&quot;750&quot;;
Properties
• This variable is an optional event metric populated via the JavaScript implemented on your site.
• If the DFA host does not respond within the given amount of time, the event designated to Timeout runs (assigned
via the Genesis integration wizard).
• This variable can only contain a numeric value.
• The amount of time specified is measured in milliseconds.
• Increasing the wait time collects more DFA data, but also increases the risk of losing Analytics hit data.
Losing Analytics hit data would occur when the user navigates away from the page during the s.maxDelay period.
• Decreasing the wait time will lower the risk of losing Analytics hit data, but can reduce the amount of DFA data
sent with hit data.
Losing DFA integration data would occur when the s.maxDelay period does not accommodate enough time for the
DFA host to respond.
Note: Adobe does not have control over DFA's response time. If you are seeing consistent issues even after
raising the max delay period to a reasonable time frame, consult your organization's DFA account administrator.
mediaLength
The mediaLenght variable specifies the total length of the media being played.
Analytics Variables
Max Size
89
Debugger Parameter
No max size for entire pev3 pev3
request - size is limited to
the browser's URL length
limit.
Reports Populated
Default Value
Time Spent on Video;
None
Video Segments Viewed
Syntax and Possible Values
autoTrack Method:
If using s.Media.autoTrack, the mediaLength variable does not need to be implemented explicitly. It is determined
automatically by the AppMeasurement for JavaScript code.
Manual Tracking Method:
Syntax:
s.Media.open(mediaName,mediaLength,mediaPlayerName)
Possible Values:
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
Examples
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
Resulting pev3 parameter syntax: pev3= [Asset Name]--**--[Total length of asset]--**--[Player
name]--**--[Total seconds consumed]--**--[Timestamp]--**--[Chronological record of all starts
and stops along with accompanying markers]
Possible pev3 values: pev3=de_bofr_1045Making_400k--**--414--**--Windows Media Player
11.0.5721.5230--**--288--**--1207893838--**--S0E0S0E256S0E32
Pitfalls, Questions, and Tips
• You must call the media tracking methods only if the player cannot be tracked using s.Media.autoTrack = true.
• If not tracking using autoTrack, be sure to set the length in seconds.
mediaName
This variable specifies the name of the video or media item.
It is only available via the Data Insertion API and Full Processing Data Source.
Max Size
Debugger Parameter
Reports Populated
Default Value
100 Bytes
pev3
Videos; Next Video Flow;
None
Previous Video Flow; Video
Segments Viewed; Time
Spent on Video
Syntax and Possible Values
autoTrack Method:
If using s.Media.autoTrack, the mediaName variable does not need to be implemented explicitly. It is determined
automatically by the AppMeasurement for JavaScript code.
Analytics Variables
90
Manual Tracking Method:
Syntax:
s.Media.open(mediaName,mediaLength,mediaPlayerName)
s.Media.play(mediaName,mediaOffset)
s.Media.stop(mediaName,mediaOffset)
s.Media.close(mediaName)
Possible Values:
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;0&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;)
s.Media.close(&quot;de_bofr_1045Making_400k&quot;)
Examples
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;0&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;)
s.Media.close(&quot;de_bofr_1045Making_400k&quot;)
Resulting pev3 parameter syntax: pev3=[Asset Name]--**--[Total length of asset]--**--[Player
name]--**--[Total seconds consumed]--**--[Timestamp]--**--[Chronological record of all starts
and stops along with accompanying markers]
Possible pev3 Values:
pev3=de_bofr_1045Making_400k--**--414--**--Windows Media Player
11.0.5721.5230--**--288--**--1207893838--**--S0E0S0E256S0E32
Pitfalls, Questions, and Tips
• You must call the media tracking methods only if player cannot be tracked using s.Media.autoTrack = true.
mediaPlayer
This variable specifies the player used to consume a video or media item.
Max Size
Debugger Parameter
Reports Populated
Default Value
100 Bytes
pev3
Video Players
None
Syntax and Possible Values
autoTrack Method:
s.Media.playerName = &quot;My Custom Player Name&quot;
ActionSource
//configure player name in global JavaScript or
Manual Tracking Method:
s.Media.open(mediaName,mediaLength,mediaPlayerName)
Possible Values:
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
Analytics Variables
91
Examples
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
Resulting pev3 parameter syntax: pev3=[Asset Name]--**--[Total length of asset]--**--[Player
name]--**--[Total seconds consumed]--**--[Timestamp]--**--[Chronological record of all starts
and stops along with accompanying markers]
Possible pev3 Values: pev3=de_bofr_1045Making_400k--**--414--**--Windows Media Player
11.0.5721.5230--**--288--**--1207893838--**--S0E0S0E256S0E32
Pitfalls, Questions, and Tips
You must call the media tracking methods only if player cannot be tracked using s.Media.autoTrack = true.
mediaSession
This variable specifies the segments of a video or media asset consumed.
Max Size
Debugger Parameter
Reports Populated
Default Value
255 Bytes
pev3
Time Spent on Video
None
Video Segments Viewed
Syntax and Possible Values
autoTrack Method:
If using s.Media.autoTrack, the mediaName does not need to be implemented explicitly. It will be determined
automatically by the AppMeasurement for JavaScript code.
Manual Tracking Method:
Syntax:
s.Media.open(mediaName,mediaLength,mediaPlayerName)
s.Media.play(mediaName,mediaOffset)
s.Media.stop(mediaName,mediaOffset)
Possible Values:
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;0&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;)
Examples
s.Media.open(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;,&quot;Windows Media Player 11.0.5721.5230&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;0&quot;)
s.Media.play(&quot;de_bofr_1045Making_400k&quot;, &quot;414&quot;)
Resulting pev3 parameter syntax: pev3=[Asset Name]--**--[Total length of asset]--**--[Player
name]--**--[Total seconds consumed]--**--[Timestamp]--**--[Chronological record of all starts
and stops along with accompanying markers]
Possible pev3 Values: pev3=de_bofr_1045Making_400k--**--414--**--Windows Media Player
11.0.5721.5230--**--288--**--1207893838--**--S0E0S0E256S0E32
Analytics Variables
92
Pitfalls, Questions, and Tips
You must call the media tracking methods only if player cannot be tracked using s.Media.autoTrack = true.
Media.trackEvents
The Media.trackEvents variable identifies which events should be sent with a media hit.
It is only applicable with JavaScript and ActionSource.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
s.Media.trackEvents=&quot;None&quot;
Syntax and Possible Values
Event names such as event1 or purchase.
Examples
s.Media.trackEvents=”event1,purchase”
Pitfalls, Questions, and Tips
Make sure to populate trackVars with &quot;events&quot; whenever this variable is populated.
Media.trackVars
The Media.trackVars variable identifies which variables should be sent with a media hit.
It is only applicable with JavaScript and ActionSource.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
s.Media.trackVars=&quot;None&quot;
Syntax and Possible Values
Variable names such as propN, eVarN, events, channel, and so forth.
Examples
s.Media.trackVars=”prop2,events,eVar3”
Pitfalls, Questions, and Tips
• Even if eVar3 is specified in trackVars, it is sent with the media hit.
mobile
The mobile variable controls the order in which cookies and subscriber IDs are used to identify visitors.
See Mobile Tracking over WAP and I-Mode Protocols.
Analytics Variables
93
Max Size
Debugger Parameter
Reports Populated
N/A
/5/ or /1/ in path of image url N/A
Default Value
None
Syntax and Possible Values
s.mobile=&quot;any_string&quot; //subscriber id used first, produces /5/ in path of image url
s.mobile=&quot;&quot; // if set to an empty string or not set at all, cookies used first, produces /1/
in path of image url
Pitfalls, Questions, and Tips
Use cross-visitor identification to mitigate possible spikes in visitor traffic when using the s.mobile variable with the
JavaScript cookie implementation.
pageName
The pageName variable contains the name of each page on your site.
Max Size
Debugger Parameter
100 bytes
pageName
Reports Populated
Pages
Default Value
page URL
Paths
The pageName variable should be populated with a value that business users recognize. In most cases the pageName
value is not the URL or the path to the file. Common pageName values include names such as &quot;Home Page,&quot;
&quot;Checkout,&quot; &quot;Purchase Thank you,&quot; or &quot;Registration.&quot;
Be careful not to allow new-line, -em or -en dashes, or any HTML characters to appear in the page name and other
variables. Some browsers send new line characters while others don't, which causes the data in Analytics to be split
between two seemingly identical page names. Many word processors and email clients will automatically convert a
hyphen into an -en or -em dash when typing. Since -en and -em dashes are illegal characters in Analytics variables
(ASCII characters with codes above 127), Analytics won't record the page name containing the illegal character and
show the URL instead.
If pageName is left blank, the URL is used to represent the page name. Leaving pageName blank is often problematic
because the URL may not always be the same for a page (www.mysite.com and mysite.com are the same page
with different URLs).
Syntax and Possible Values
The pageName variable should contain a useful identifier for business users of Analytics.
s.pageName=&quot;page_name&quot;
There are no limitations on pageName outside of the standard variable limitations.
Examples
s.pageName=&quot;Search Results&quot;
s.pageName=&quot;Standard Offer List&quot;
Analytics Variables
94
Configuration Settings
Administrators have the ability to change the visible page name in Analytics with the Name Pages tool, which is
potentially dangerous and may negatively affect your reports. Please contact Adobe ClientCare before using the
Name Pages tool.
Pitfalls, Questions, and Tips
Make sure the pageName doesn't contain illegal characters.
pageType
The pageType variable is used only to designate a 404 Page Not Found Error page.
Max Size
Debugger Parameter
Reports Populated
Default Value
20 bytes
pageType
Paths &gt; Pages &gt; Pages
&quot;&quot;
Not Found
The pageType variable captures the errant URL when a 404 Error page is displayed, which allows you to quickly
find broken links and paths that are no longer valid on the custom site. Set up the pageType variable on the error
page exactly as shown below.
Do not use the page name variable on 404 error pages. The pageType variable is only used for the 404 Error page.
In most cases, the 404 Error page is a static page that is hard-coded. In these cases, it is important that the reference
to the .JS file is set to an appropriate global or relative path/directory.
Syntax and Possible Values
The only allowable value of pageType is &quot;errorPage&quot; as shown below.
s.pageType=&quot;errorPage&quot;
Examples
s.pageType=&quot;errorPage&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
To capture other server-side errors (such as 500 errors), use a prop to capture the error message and put &quot;500
Error: &lt;URL&gt;&quot; where &lt;URL&gt; is the URL requested, in the pageName variable. By following this course of action,
you can use Pathing reports to see which paths caused users to generate 500 errors. The prop explains which error
message is given by the server.
pageURL
The pageURL variable overrides the actual URL of the page.
In rare cases, the URL of the page is not the URL that you would like reported in Analytics.
Analytics Variables
Max Size
No Limit*
95
Debugger Parameter
Reports Populated
Default Value
G
Traffic &gt; Segmentation &gt;
Page URL
Most Popular Pages Paths
Note: Although Adobe allows pageURL values up to 64k, some browsers impose a size limit on the URL of
image requests. To prevent truncation of other data, page URLs longer than 255 bytes are split, with the first
255 bytes appearing in the g= parameter, with the remaining bytes appearing later in the query sting in the
-g= query parameter.
Syntax and Possible Values
The pageURL variable must be a valid URL, with a valid protocol. The domain will be forced to display in lower-case
before being populated in reports, and the query string may be stripped, depending on Analytics settings.
s.pageURL=&quot;proto://domain/path?query_string&quot;
Only URL-compatible characters are allowed as the page URL.
Note: It is strongly advised that you contact your Adobe consultant or ClientCare before using the pageURL
variable for custom purposes.
Examples
s.pageURL=&quot;http://mysite.com/home.jsp?id=1224&quot;
s.pageURL=&quot;http://www.mysite.com/&quot;
Configuration Settings
None
plugins
The plugins variable, in Netscape and Mozilla-based browsers, lists the plugins installed on the browser.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
Reports Affected
p
Recognized plugins
IE Tab Plug-in;QuickTime Traffic &gt; Technology &gt;
Plug-in 7.1.6;Mozilla Default Plugins
Plug-in;iTunes Application
Detector;Adobe
Acrobat;ActiveTouch
General Plugin
Container;Shockwave
Flash;Microsoft Office
2003;Java(TM) Platform SE
Analytics Variables
96
Query Param
Value
Example
Reports Affected
6 U1;Windows Media
Player Plug-in Dynamic Link
Library;Microsoft&reg; DRM;
products
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 product view event.
The products variable tracks how users interact with products on your site. For instance, the products variable can
track how many times a product is viewed, added to the shopping cart, checked out, and purchased. It can also
track the relative effectiveness of merchandising categories on your site. The scenarios below are common for using
the products variable.
The products variable should always be set in conjunction with a success event.
Max Size
The &quot;Product&quot; and
&quot;Category&quot; sections of
products each have a limit
of 100 bytes. Adobe does
not impose a size limit on
products, though most
browsers impose a size limit
on the total URL length of
image requests.
Debugger Parameter
Reports Populated
Default Value
products
Products
&quot;&quot;
Categories (optional)
Revenue (optional)
Units (optional)
Custom Events (optional)
eVars (optional)
Syntax of the Products Variable
&quot;Category;Product;Quantity;Price;eventN=X[|eventN2=X2];eVarN=merch_category[|eVarN2=merch_category2]&quot;
Field
Definition
Category
Contains the associated product category. In version 15, products can be associated with
multiple categories which fixes a limitation present in version 14. If you were previously not
recording a product category, you are encouraged to start populating this field for report suites
that are on version 15.
Product
(Required) The identifier used to track a product. This identifier is used to populate the Products
report. Be sure to use the same identifier through the checkout process.
Quantity
The number of units purchased. This field must be set with a purchase event to be recorded.
Price
Refers to the combined cost of the total quantity purchased (units x individual unit price), not
to the individual price. This field must be set with a purchase event to be recorded.
Events
Currency events associated with the specified product. See Product-Specific Currency Events
and Order-Wide Currency Events.
eVars
Merchandising eVar values associated with a specific product. See Merchandising Variables.
Analytics Variables
97
The values included in the products variable are based on the type of event you are recording. The category/product
delimiter (;) is required as a place holder when omitting Category. Other delimiters are required only if they are
necessary to distinguish which parameter you are including, as shown in the examples on this page.
Setting products with Non-Purchase Events
The products variable must be set in conjunction with a success event.
Syntax
s.events=&quot;prodView&quot;
s.products=&quot;Category;Product[,Category;Product]&quot;
In the examples below, product attributes (category) are separated by semicolons. Multiple products are separated
by commas.
Example 1: Single Product
s.events=&quot;prodView&quot;
s.products=&quot;Footwear;Running Shoes&quot;
Example 2: Multiple Products
s.events=&quot;prodView&quot;
s.products=&quot;Footwear;Running Shoes,;Running Socks&quot;
Setting products with a Purchase Event
The purchase event should be set on the final confirmation (&quot;Thank You!&quot;) page of the order process. The product
name, category, quantity, and price are all captured in the products variable. Although the purchaseID variable is
not required, it is strongly recommended in order to prevent duplicate orders.
Syntax
s.events=&quot;purchase&quot;
s.products=&quot;Category;Product;Quantity;Price[,Category;Product;Quantity;Price]&quot;
s.purchaseID=&quot;1234567890&quot;
Example 1: Single Product
s.events=&quot;purchase&quot;
s.products=&quot;Footwear;Running Shoes;1;69.95&quot;
s.purchaseID=&quot;1234567890&quot;
Example 2: Multiple Products
s.events=&quot;purchase&quot;
s.products=&quot;Footwear;Running Shoes;1;69.95,Running Essentials;Running Socks;10;29.99&quot;
s.purchaseID=&quot;1234567890&quot;
Note: Price refers to the total price (unit price x units). For instance, 3 widgets purchased at 19.99 each would
equal 59.97 (such as &quot;;Widget;3;59.97&quot; ).
Product-Specific Currency Events
If a currency event receives a value in the products variable instead of the events variable, it applies only to that
value. This is useful to track product-specific discounts, product shipping, and similar values. For example, if you
configured event 1 to track product shipping, a product with a &quot;4.50&quot; shipping charge might appear similar to the
following:
s.events=&quot;event1&quot;
s.products=&quot;Footwear;Running Shoes;1;99.99;event1=4.50&quot;
Analytics Variables
98
In this example, the value of 4.50 is associated directly with the &quot;Running Shoes&quot; product. If you add event1 to the
products report, you'll see &quot;4.50&quot; listed for the &quot;Running Shoes&quot; line item. Similar to Price, this value should reflect
the total for the quantity listed. If you have 2 items with a 4.50 shipping charge each, event1 should be &quot;9.00&quot;.
Example 1: Single Numeric/Currency Event
s.events=&quot;purchase,event1&quot;
s.products=&quot;Footwear;Running Shoes;1;69.95;event1=7.59&quot;
Example 2: Multiple Numeric/Currency Events
s.events=&quot;purchase,event1,event2&quot;
s.products=&quot;Footwear;Running Shoes;1;69.95;event1=7.59|event2=19.45&quot;
Order-Wide Currency Events
If a currency event receives a value in the events list instead of the products variable, it applies to all products in the
products variable. This is useful to track order-wide discounts, shipping, and similar values, without modifying the
product price or by tracking it in the product list separately.
For example, if you configured event10 to contain order-wide discounts, a purchase with a 10% discount might
appear similar to the following:
s.events=&quot;purchase,event10=9.95&quot;
s.products=&quot;Footwear;Running Shoes;1;69.95,Running Essentials;Running Socks;10;29.50&quot;
s.purchaseID=&quot;1234567890&quot;
On currency event reports, the report total represents the de-duplicated event total (in this example, the total amount
of discounts during the reporting period), not the sum of the event values for each product. For example, you would
see &quot;9.95&quot; listed for both &quot;Running Shoes&quot; and &quot;Running Socks&quot;, and the total would also be &quot;9.95&quot;.
Note: if a value for the same Numeric/Currency Event is specified in the products variable and in the events
variable, the value from the events is used.
Setting products with Merchandising eVars
See Merchandising Variables.
Pitfalls, Questions, and Tips
• The products variable should always be set in conjunction with a success event (events). If no success event is
specified, the default event is prodView.
• Strip all commas and semicolons from product and category names before populating products.
• Strip all HTML characters (registered symbols, trademarks, and so forth).
• Strip currency symbols ($) from the price.
Examples
s.products=”Category;ABC123”
s.products=”Category2;ABC123,;ABC456”
s.products=”Category3;ABC123;1;10”
s.products=”Category;ABC123;1;10,;ABC456;2;19.98”
s.events=”event1”
s.products=&quot;Category;ABC123;;;event1=1.99&quot;
Analytics Variables
99
s.events=”event1”
s.products=&quot;Category;ABC123;1;10;event1=1.99&quot;
s.events=”event1”
s.products=&quot;Category;ABC123;1;10;event1=1.99,;ABC123;2;19.98;event1=1.99&quot;
s.events=”event1,event2”
s.products=&quot;Category;ABC123;1;10;event1=1.99|event2=25&quot;
s.events=”event1,event2”
s.products=&quot;Category;ABC123;1;10;event1=1.99|event2=25;evar1=2 Day Shipping&quot;
s.events=”event1,event2”
s.products=&quot;Category;ABC123;1;10;event1=1.99|event2=25;evar1=2 Day Shipping|evar2=3 Stars&quot;
s.events=”event1,event2”
s.products=&quot;Category;ABC123;1;10;event1=1.99|event2=25;evar1=2 Day Shipping,
;ABC456;2;19.98;event1=1.99|event2=100;evar1=Ground Shipping&quot;
s.events=”event1,event2,event3”
s.products=&quot;Category;ABC123;1;10;event1=1.99|event2=25;evar1=2 Day
Shipping,;ABC456;2;19.98;event1=1.99|event2=100;evar1=Ground Shipping,;;;;event3=2.9;evar3=20%
off&quot;
s.events=”event1,event2,event3=9.95”
s.products=&quot;Category;ABC123;,;ABC456;2;19.98;event1=1.99|event2=100;evar1=Ground
Shipping,;;;;event3=2.9;evar3=20% off&quot;
propN
Property (prop) variables are used for building custom reports within the Traffic Module.
The props variable may be used as counters (to count the number of times a page view is sent), for pathing reports,
or in correlation reports.
Max Size
Debugger Parameter
Reports Populated
Default Value
100 bytes
c1-c75
Custom Traffic
&quot;&quot;
Syntax and Possible Values
s.propN=&quot;value&quot;
There are no limitations on property variables outside of the standard variable limitations.
Examples
s.prop2=&quot;editorial&quot;
s.prop15=&quot;toy category&quot;
Analytics Variables
100
Configuration Settings
Contact Adobe ClientCare about showing Visit, Visitor, and Path metrics for prop variables.
purchaseID
The purchaseID is used to keep an order from being counted multiple times in reporting.
Whenever the purchase event is used on your site, you should use the purchaseID variable.
Max Size
Debugger Parameter
Reports Populated
Default Value
20 bytes
purchaseID
Conversion &gt; Purchases &gt; &quot;&quot;
Revenue Conversion
When a visitor purchases an item from your site, purchaseID is populated on the &quot;Thank You&quot; page at the same
place the purchase event is fired. If the purchaseID is populated, the products on the &quot;Thank You&quot; page are counted
only once per purchaseID. This is critical because many visitors to your site will save the &quot;Thank You&quot; or &quot;Confirmation
Page&quot; for their own purposes. The purchaseID keeps purchases from being counted each time the page is viewed.
In addition to keeping the purchase data from being counted twice, the purchaseID, when used, keeps all conversion
data from being double counted in reports.
Syntax and Possible Values
s.purchaseID=&quot;unique_id&quot;
The purchaseID must be 20 characters or fewer, and be standard ASCII.
Examples
s.purchaseID=&quot;11223344&quot;
s.purchaseID=&quot;a8g784hjq1mnp3&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
The purchaseID variable allows all conversion variables on the page to be counted only once in reports.
referrer
The referrer variable can be used to restore lost referrer information.
Server-side and JavaScript redirects are often used to route visitors to proper locations. However, when a browser
is redirected, the original referring URL is lost.
Max Size
Debugger Parameter
Reports Populated
Default Value
255 bytes
R
Traffic &gt; Finding Methods
Conversion &gt; Finding
Methods
document.referrer
Analytics Variables
101
Many companies use redirects in many places throughout their websites. For example, a visitor may be sent through
a redirect from a search engine paid search result. When a browser is redirected, the referrer is often lost. The
referrer variable may be used to restore the original referrer value on the first page after a redirect. The referrer may
be populated server-side, or via JavaScript from the query string.
For Analytics to record a referrer, it must be &quot;well formed,&quot; meaning that it must follow the standard URL format,
with a protocol and appropriate location.
Syntax and Possible Values
s.referrer=&quot;URL&quot;
Only URL-compatible values should be in the referrer. Make sure the string is URL encoded (no spaces).
Examples
s.referrer=&quot;http://www.google.com/search?q=search+string&quot;
s.referrer=&lt;%=referrerVar%&gt; // populated server-side
if(s.getQueryParam('ref')
s.referrer=s.getQueryParam('ref')
Configuration Settings
None
Pitfalls, Questions, and Tips
The referrer must look like a standard URL and include a protocol.
resolution
The resolution variable indicates the monitor resolution of the visitor viewing the web page.
This variable is populated after the page code and before doPlugins is run.
Note: This variable should only be read and never set.
You may read these values and copy them into props/eVars, but you should never alter them. This variable is
introduced with version H.11 of the JavaScript file.
Query Param
Value
Example
Reports Affected
s
WxH
1680x1050
Traffic &gt; Technology &gt;
Monitor Resolution
s_objectID
The s_objectID variable is a global variable that should be set in the onClick event of a link.
By creating a unique object ID for a link or link location on a page, you can either improve visitor click map tracking
or use visitor click map to report on a link type or location, rather than the link URL.
Analytics Variables
102
Max Size
Debugger Parameter
Reports Populated
Default Value
100 Bytes
OID
ClickMap
The Absolute URL of a
Clicked Link
There are three common reasons to use s_objectID:
• To aggregate clicks on links that change often during a day
• To separate clicks on links that visitor click map combines
• To improve accuracy of visitor click map data reporting
Aggregate Clicks on Highly Dynamic Links
If your site is highly dynamic, and links on some pages change throughout the day, s_objectID may used to identify
the location of a link on the page. If s_objectID is set to &quot;top left 1&quot; or &quot;top left 2,&quot; which represents the first link in
the top left of the page for example, then all links that appear in that location (or that have s_objectID set to the same
value) are reported together with visitor click map. If you don't use s_objectID, you see the number of times that a
specific link was clicked, but you lose insight into how all the other links in that location were used by visitors to your
site.
Separate Clicks Combined
If the pageName variable on your site is used to show the section or template a visitor is viewing, rather than the
specific page the visitor is viewing, you may want to use s_objectID to separate links that appear on multiple versions
of that page template. For example, if you have a template page for all products on your site, it is likely that there is
a link to your home page and to a search box from that template on all pages. If you want to see how those links
are used on an individual product basis (rather than a template basis), you can populate s_objectID with a product
specific value such as &quot;prod 123789 home page&quot; or &quot;prod 123789 search.&quot; Once completed, visitor click map reports
on those links at an individual product basis.
Improving visitor click map Accuracy
In some cases, browsers other than Internet Explorer, Firefox, Netscape, Opera, and Safari are not reported. Although
this is a small percentage, it accounts for some clicks and other metrics. Using s_objectID within links to uniquely
identify the addresses the browser reporting issue. The following is an example of how to update your links to use
s_objectID:
&lt;a href=&quot;/art.jsp?id=559&quot; onClick=&quot;s_objectID='top left 1'&quot;&gt;Article 559&lt;/a&gt;
&lt;a href=&quot;/home.jsp&quot; onClick=&quot;s_objectID='prod 123789 home page'&quot;&gt;Home&lt;/a&gt;
Syntax and Possible Values
s_objectID may contain any text identifier.
s_objectID=&quot;unique_id&quot;
There are no limitations on s_objectID outside of the standard variable limitations.
Examples
s_objectID=&quot;top left 2&quot;
s_objectID=&quot;prod 123789 search&quot;
Configuration Settings
None
Analytics Variables
103
server
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).
Max Size
Debugger Parameter
Reports Populated
Default Value
100 bytes
server
Servers
&quot;&quot;
If your site has more than one domain serving the same content, the server variable can be used to track which of
those domains visitors are using. The following JavaScript will populate the domain of the page into the server
variable.
s.server=window.location.hostname
If you are using the server variable to give a quick guide to load balancing, you could put a server name or number
into the server variable. See the following example:
s.server=&quot;server 14&quot;
While the Most Popular Servers report may be used as a load balancing quick reference, it is not a precise measure
of server load. For example, back-button traffic does not increase server load, but is shown in reports. The report
does not show which servers are serving images or large downloads.
Syntax and Possible Values
s.server=&quot;server_name&quot;
There are no limitations on the server variable outside of the standard variable limitations.
Examples
s.server=&quot;server 18&quot;
s.server=window.location.hostname
Configuration Settings
None
Pitfalls, Questions, and Tips
The server variable can be used to show which domains are most popular or which servers are serving the most
pages.
state
The state and zip variables are conversion variables.
They are like eVars in that they capture events, but unlike eVars, they don't persist. The zip and state variables are
like eVars that expire immediately.
Max Size
Debugger Parameter
Reports Populated
Default Value
50 bytes
state
Conversion &gt; Visitor Profile &quot;&quot;
&gt; States
Analytics Variables
104
Because the state and zip variables expire immediately, the only events associated with them are events that are
fired on the same page on which they are populated. For example, if you are using state to compare conversion
rates by state, you should populate the state variable on every page of the checkout process. For conversion sites,
Adobe recommends using the billing address as the source for the Zip Code, but you may choose to use the shipping
address instead (assuming there is only one shipping address for the order). A media site may choose to use zip
and state for registration or ad click-through tracking.
Syntax and Possible Values
s.state=&quot;state&quot;
The state variable does not impose any special value or format restrictions. There are no limitations on state outside
of the standard variable limitations.
Examples
s.state=&quot;california&quot;
s.state=&quot;prince edward island&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• Populate state on every page that a relevant event is fired (such as each page of the checkout process).
• The zip and state variables act like eVars that expire on the Page View.
timestamp
This variable lets you customize the timestamp of a hit similar to the AppMeasurement libraries for other platforms.
Max Size
Debugger Parameter
Reports Populated
Default Value
4 bytes
Date/Time
Not reported directly.
Set by data collection
servers.
Syntax
s.timestamp=&quot;UNIX or ISO-8601 format timestamp&quot;
The timestamp variable must be in the format explained in the next section.
Important: Your report suite must be timestamp-enabled by Customer Care before you can use the timestamp
variable. After timestamp support is enabled, all hits sent to this report suite from JavaScript must have a
timestamp manually set (using s.timestamp) or the hits will not be recorded.
Additionally, if you enable timestamp support on a report suite to support offline tracking, all hits sent to this
report suite from JavaScript must also have a timestamp manually set (using s.timestamp). You cannot send
both time-stamped and non-time-stamped hits to the same report suite.
Analytics Variables
105
Timestamp Formats
Timestamps must be in UNIX (seconds since Jan 1st 1970) or ISO-8601 format, with the following restrictions on
the accepted ISO-8601 format:
• Both date and time must be provided, separated by &quot;T&quot;
• The date must be a calendar date with full precision (year, month, and day). . Week dates and ordinal dates are
not supported.
• The date can be in standard or extended format (YYYY-MM-DD or YYYYMMDD), but they must include the hour and
minute. Seconds are optional (HH:MM, HH:MM:SS, HHMM, or HHMMSS). Fractional minutes and seconds can be passed
in, but the fractional part is ignored.
• An optional timezone can be specified in standard or extended format (&plusmn;HH, &plusmn;HH:MM, &plusmn;HH, &plusmn;HHMM, or Z)
UNIX timestamps continue to be supported (seconds since Jan 1st 1970).
Examples
s.timestamp=Math.round((new Date()).getTime()/1000);
s.timestamp=&quot;2012-04-20T12:49:31-0700&quot;;
The following list contains examples of valid ISO-8601 format timestamps:
2013-01-01T12:30:05+06:00
2013-01-01T12:30:05Z
2013-01-01T12:30:05
2013-01-01T12:30
Configuration Settings
A report suite must be enabled to accept custom timestamps by ClientCare before you can use this variable. After
custom timestamps are enabled, all hits sent to the report suite must contain a timestamp or they are discarded.
Pitfalls, Questions, and Tips
• Timestamps are primarily used to track offline data on mobile platforms. Custom timestamps are typically disabled
unless you are collecting both web and offline app data in the same report suite.
• Data is time stamped when offline data is enabled in the mobile SDK (default setting) or anytime a report suite is
configured to accept time-stamped data. Data collected offline on mobile devices may be sent hours or weeks after
the date when it happened. These hits may be queued within the Analytics platform for minutes or hours longer
than hits without time stamps:
• For time-stamped data sent in very near current time, the probable delay is 10-15 minutes.
• For time-stamped data sent in from yesterday, the probable delay is about 2 hours.
• For time-stamped data sent in that is older than yesterday, every day adds about 1 hour of delay, up to 15 days
ago, when the delay stops going up.
trackDownLoadLinks
Set trackDownloadLinks to 'true' if you would like to track links to downloadable files on your site.
If trackDownloadLinks is 'true,' linkDownloadFileTypes is used to determine which links are downloadable files.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
True
Analytics Variables
106
The trackDownloadLinks variable should only be set to 'false' if there are no links to downloadable files on your site,
or you don't care to track the number of clicks on downloadable files. If trackDownloadLinks is 'true,' when a file
download link is clicked, data is immediately sent to Analytics. The data that is sent with a download link includes
the link download URL, and visitor click map data for that link. If trackDownloadLinks is 'false,' then visitor click map
data for links to downloadable files on your site is likely to be under reported.
Syntax and Possible Values
The trackDownloadLinks variable is expected to be either 'true' or 'false.'
Examples
s.trackDownloadLinks=true
s.trackDownloadLinks=false
Configuration Settings
None
Pitfalls, Questions, and Tips
• When trackDownloadLinks is 'false,' links that people use to download files on your site are likely to be under
reported in visitor click map.
• When trackDownloadLinks is 'true,' data is sent each time a visitor clicks a file download link.
trackExternalLinks
If trackExternalLinks is 'true,' linkInternalFilters and linkExternalFilters are used to determine whether any link clicked
is an exit link.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
True
The trackExternalLinks variable should only be set to 'false' if there are no exit links on your site, or if you don't care
to track the number of clicks on those exit links. An exit link is any link that takes a visitor off of your site. If
trackExternalLinks is 'true,' then when you click an exit link, tracking data is immediately sent. The data that is sent
with an exit link includes the link URL, link name, and visitor click map data for that link. If trackExternalLinks is
'false,' then visitor click map data for exit links on your site is likely to be under reported.
Syntax and Possible Values
The trackExternalLinks variable is expected to be either 'true' or 'false.'
s.trackExternalLinks=true|false
Examples
s.trackExternalLinks=true
s.trackExternalLinks=false
Configuration Settings
None
Analytics Variables
107
Pitfalls, Questions, and Tips
• When trackExternalLinks is 'false,' links that take people away from your site are likely to be under reported in
visitor click map.
• When trackExternalLinks is 'true,' data is sent each time a visitor clicks on an exit link (before link target loads).
trackingServer
The trackingServer variable is used for first-party cookie implementation to specify the domain at which the image
request and cookie is written.
Used for non-secure pages. If trackingServer is defined, nothing goes to 2o7.net. If trackingServer is not defined
(and dc is not defined), data goes to 112.2o7.net.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
&quot;&quot;
A list of Adobe data centers can be found here.
trackingServerSecure
The trackingServerSecure variable is used for first-party cookie implementation to specify the domain at which the
image request and cookie is written.
Used for secure pages. If trackingServerSecure is not defined, SSL data goes to trackingServer.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
&quot;&quot;
trackInlineStats
The trackInlineStats variable determines whether visitor click map data is gathered.
If trackInlineStats is 'true,' data about the page and link clicked are stored in a cookie called s_sq. If 'false,' s_sq will
have a value of &quot;[[B]],&quot; which is considered null.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
ClickMap
True
Syntax and Possible Values
s.trackInlineStats=true|false
The trackInlineStats variable is expected to be either 'true' or 'false.'
Examples
s.trackInlineStats=true
s.trackInlineStats=false
Analytics Variables
108
Configuration Settings
None
transactionID
Integration Data Sources use a transaction ID to tie offline data to an online transaction (like a lead or purchase
generated online).
Each unique transactionID sent to Adobe is recorded in preparation for a Data Sources upload of offline information
about that transaction. See Data Sources.
Max Size
Debugger Parameter
Reports Populated
Default Value
100 bytes
xact
n/a
&quot;&quot;
Syntax and Possible Values
s.transactionID=&quot;unique_id&quot;
The transactionID should contain only alphanumeric characters. If multiple transactionIDs should be recorded in
a single hit, you can use a comma to delimit multiple values.
Examples
s.transactionID=&quot;11123456&quot;
s.transactionID=&quot;lead_12345xyz&quot;
s.transactionID=s.purchaseID
Configuration Settings
Before transactionID values are recorded, transactionID recording must be enabled by an Adobe representative.
To see whether transactionID recording is enabled for a report suite, go to reporting and analytics &gt; Data Sources
&gt; Manage.
Pitfalls, Questions, and Tips
• If transactionID recording is not enabled, transactionID values will be discarded and unavailable for use with
Integration Data Sources. Make sure to set a conversion variable or event (an eVar or the events variable) on
the page where transactionID is set. Otherwise, no data is recorded for the transactionID.
• If you are recording transactionIDs for multiple systems, such as purchases and leads, make sure the value in
transactionID is always unique. This can be accomplished by adding a prefix to the ID, such as lead_1234 and
purchase_1234. Integration Data Sources do not function as expected (Data Source data will tie to the wrong
data) if a unique transactionID is seen twice.
• By default, transactionID values are remembered for 90 days. If your offline interaction process is longer than 90
days, contact Customer Care to have the limit extended.
Note: The transactionID variable can contain any character other than a comma. It should be in the same
location where the character limit (100 bytes) is specified. If multi-byte characters are used, multi-byte character
support must be enabled in order to avoid problems with unexpected characters in the transactionID.
Analytics Variables
109
s_usePlugins
If the s_doPlugins function is available and contains useful code, s_usePlugins should be set to 'true.'
When usePlugins is 'true,' the s_doPlugins function is called prior to each image request.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
True
Syntax and Possible Values
s.usePlugins=true|false
The usePlugins variable is expected to be either 'true' or 'false.'
Examples
s.usePlugins=true
s.usePlugins=false
The usePlugins variable should only be false (or not declared) if the s_doPlugins function is not declared in your
JavaScript file.
Configuration Settings
None
visitorID
Visitors can be identified by the visitorID variable or by IP address/User Agent.
The visitorID can be up to 100 alpha-numeric characters and must not contain a hyphen.
If you explicitly set a custom ID, it will always be used before the other ID methods.
This is the order of use: s.visitorID &gt; s_vi &gt; s_fid &gt; IP/UA.
Max Size
Debugger Parameter
Reports Populated
Default Value
100 bytes
vid
n/a
&quot;&quot;
Syntax and Possible Values
s.visitorID=&quot;visitor_id&quot;
Note: The visitorID variable should not contain a hyphen.
Examples
s.visitorID=&quot;abc123&quot;
Configuration Settings
None
Analytics Variables
110
visitorNamespace
The visitorNamespace variable is used to identify the domain with which cookies are set.
If visitorNamespace is used in your JavaScript file, do not delete or alter it. If visitorNamespace changes, all visitors
reported in Analytics may become new visitors. Visitor history becomes disconnected from current and future traffic.
Do not alter this variable without approval from an Adobe representative.
Max Size
Debugger Parameter
Reports Populated
Default Value
N/A
N/A
N/A
&quot;&quot;
Analytics uses a cookie to uniquely identify visitors to your site. If visitorNamespace is not used, the cookie is
associated 2o7.net. If visitorNamespace is used, the cookie is associated with a sub-domain of 2o7.net. All visitors
to your site should have their cookies associated with the same domain or sub-domain.
The reason for using the visitorNamespace variable is to avoid the possibility of overloading a browser's cookie limit.
Internet Explorer imposes a limit of 20 cookies per domain. By using the visitorNamespace variable, other companies'
Analytics cookies will not conflict with your visitors' cookies.
Syntax and Possible Values
The value of visitorNamespace must be provided by Adobe and is a string of ASCII characters that don't contain
commas, periods, spaces, or special characters.
s.visitorNamespace=&quot;company_specific_value&quot;
Visitor Identification across Report Suites
If you do not specify a visitorNamespace, each report suite in your company receives its own visitor ID cookie
written as s_vi_[random string]. If you specify visitorNamespace, the same s_vi_[namespace] cookie will be
used for all report suites that send data to the specified trackingServer. If you have implemented multi-suite
tagging, make sure you specify the visitor namespace so the same cookie is used by each report suite.
Examples
s.visitorNamespace=&quot;company_name&quot;
s.visitorNamespace=&quot;Adobe&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• If you use a CNAME to make Analytics cookies into first-party cookies, the s.visitorNamespace variable may be
left blank. It is acceptable to leave it as constituted.
• If your third-party cookie implementation uses the s.trackingServer variable, you may not have an
s.visitorNamespace variable. This is normal. The s.trackingServer variable serves the same purpose as
s.visitorNamespace..
zip
The state and zip variables are conversion variables.
Analytics Variables
111
They are like eVars in that they capture events, but unlike eVars, they don't persist. The zip and state variables are
like eVars that expire immediately.
Max Size
Debugger Parameter
Reports Populated
Default Value
50 bytes
zip
Conversion &gt; Visitor Profile &quot;&quot;
&gt; ZIP/Postal Codes
Since the state and zip variables expire immediately, the only events associated with them are events fired on the
same page that are populated. For example, if you are using zip to compare conversion rates by Zip Code, you
should populate zip on every page of the checkout process. Adobe recommends using the billing address as the
source for the Zip Code. You may choose to use the shipping address instead (assuming there is only one shipping
address for the order). A media site may choose to use zip and state for registration or ad click-through tracking.
Syntax and Possible Values
s.zip=&quot;zip_code&quot;
The zip variable does not impose any value or format restrictions. There are no limitations on zip outside of the
standard variable limitations.
Examples
s.zip=&quot;92806&quot;
s.zip=&quot;92806-4115&quot;
Configuration Settings
None
Pitfalls, Questions, and Tips
• Populate zip on every page in which a relevant event is fired (such as each page of the checkout process).
• The zip and state variables act like eVars that expire on the Page View.
Context Data Variables
112
Context Data Variables
Context data variables let you define custom variables on each page that can be read by processing rules.
Instead of explicitly assigning values to props and eVars in your code, you can send data in context data variables
that are mapped using processing rules. Processing rules provide a powerful graphical interface to make changes
to data as it is received. Based on the values sent in context data, you can set events, copy values to eVars and
props, and execute additional conditional statements.
Note: Context data variables are not case sensitive. For example, the following 2 variables are effectively
identical:
s.contextData['article_title'] = 'Weekend Concert Controversy';
and
s.contextData['ARTICLE_TITLE'] = 'Weekend Concert Controversy';
Using context data helps prevent you from making code updates to support different report suite configurations.
For example, you can define the following s.contextData variable:
s.contextData['myco.rsid'] = 'value'
Using processing rules you can add a condition that checks for a myco.rsid context data variable. When this variable
is found, you can add an action to copy it to a prop or eVar.
Context data variables can also be defined directly in the processing rules interface to temporarily store a value, or
to collect values from a context data variable you know will be used on the report suite. For example, if you need to
swap two values, you could create a context data variable to store a value during the swap.
Since processing rules are applied only when data is collected, it is important to set up processing rules before you
start sending context data. Context data values that are not read by processing rules when a hit is processed are
discarded.
Rules
Rule
Description
Supported names and characters
Context data variable names can contain only alphanumeric characters,
underscores and dots. Any additional characters are stripped out. Context
cata variables do not have a numeric designation. Rather, they are named.
For example, the context data variable login_page-home automatically
becomes login_pagehome. All data sent to the login_page-home variable
is allocated under login_pagehome.
Namespace
A good practice is to prefix your variables with your company name, site name,
or a similar value to make sure the name is unique across your report suite.
Context data variables can be named similar to other JavaScript variables.
Be aware that the namespace a.* is reserved for use by Adobe products in
context variable names. For example, the AppMeasurement Library for iOS
uses a.InstallEvent to measure application installations.
Context Data Variables
113
Rule
Description
URL Limits
When using context data variables on the Web, be aware of the URL limits
of browsers. For example, IE truncates URLs at 2000 bytes. You can use the
DigitalPulse debugger to determine the size of a URL string.
Supported AppMeasurement version Context data variables require at least H23 code or higher.
Sending Context Data on a Track Link Call
Include ContextData + the name of the variable that you would like included in s.linkTrackVars:
s.contextData['myco.value'] = &quot;some value&quot;;
s.linkTrackVars = &quot;contextData.myco.value&quot;;
s.tl(true,&quot;o&quot;,&quot;Link Name&quot;);
Examples
Possible ways to replace implementation of the s.pageName variable, assuming that processing rules are set up
correctly for each:
s.contextData['page'] = &quot;Home Page&quot;
s.contextData['pagename'] = document.title // Takes the web page's title and passes it into
the pageName context data variable
s.contextData['pagevar'] = s.pageName // This example would be considered redundant, as both
the pageName and contextData variable are available in Processing rules
Other examples to implement context data variables:
s.contextData['owner'] = &quot;Jesse&quot;
s.contextData['campaign'] = &quot;Campaign A&quot;
s.contextData['author'] = &quot;Sheridan Andrius&quot;
For an example, see Copy a Context Data Variable to an eVar in Analytics Reference.
Processing Rules
Processing rules let you make changes to data as it is received.
For more information, see Processing Rules in the Analytics Reference.
Dynamic Variables
114
Dynamic Variables
Dynamic variables let you copy values from one variable to another without typing the full values multiple times in
the image requests on your site.
Dynamic variables are used when capturing the same data (for example, campaign tracking codes) in multiple
variables concurrently. This is a common practice in cases where different reports offer unique and important metrics.
For example, capturing internal search keywords in a Custom Conversion variable and in a Custom Traffic variable
lets you view the Revenue and the Weekly Unique Visitors metrics associated with these keywords, respectively
Dynamic variables are also useful for viewing data under various reporting conditions. A campaign tracking code
can be captured in multiple eVars with various allocation and cookie expiration settings. This lets users choose the
way they want to attribute conversion metrics to these campaigns.
A significant benefit of dynamic variables is the ability to capture long strings of data in multiple variables without
actually passing the long string repeatedly. Some browsers limit the maximum length of HTTP GET requests (including
the Adobe image request). Using dynamic variables ensures that all data is captured by reducing the length of the
request to Adobe servers in cases where data is duplicated across several variables.
In the Adobe image request that occurs on the page view, if you are using dynamic variables to copy the value of
Custom Traffic 1 to Custom Conversion 1, you would see v1=D=c1. If eVar1 received a value previously in the
request, Adobe's servers dynamically copy the value of Custom Traffic 1 to Custom Conversion 1 during data
processing. As a result, the value originally passed using Custom Traffic 1 also appears in the Custom Conversion
1 reports.
Dynamic variables are passed by setting a variable to the desired value and then setting other variables to
D=[variable abbreviation]. For abbreviations for each variable, see . Dynamic variables can pull data from the
following locations:
• Other query-string variables
• HTTP headers (except for the Cookie HTTP header)
To create a dynamic variable, add a special prefix to the start of the value. The default prefix is &quot;D=&quot;. There are two
methods of flagging dynamic variables:
• Use a default prefix of D= (For example: s.prop1=&quot;D=User-Agent&quot; )
• For non-JavaScript implementations, you can define a custom prefix using the &quot;D&quot; query-string parameter. For
example, if the query-string parameter is &quot;&amp;D=$&quot;, you can create a dynamic variable with the following command:
s.prop1=&quot;$User-Agent&quot; .
The variable abbreviation used must match the variable parameter name passed in the image request. Some
variables have multiple accepted parameters used in different cases. For example, pageName= and gn= both pass
the page name, but the latter is most often used in mobile and hard-coded implementations. If the image request
uses pageName= to pass the page name, then D=pageName is acceptable but D=gn is not. If the image request uses
gn=, then D=gn is acceptable, but D=pageName is not.
The following information applies to dynamic variables:
• Dynamic variables work with all versions of AppMeasurement code.
• Dynamic variables are case sensitive.
• Dynamic variables support literal strings contained in quotes.
• Dynamic variable replacement occurs before processing rules, VISTA, and other processing.
• The dynamic variable prefix &quot;D=&quot; must be at the start of the variable value not in the middle. For example, use
c2=D=&quot;test7&quot;+User-Agent rather than c2=&quot;test7&quot;+D=User-Agent .
Dynamic Variables
115
• As with all implementation techniques, Adobe strongly recommends testing dynamic variable implementations
heavily in a development environment before deploying to production. Because the full strings that are copied are
not visible in client-side debugging tools, review the affected Analytics reports to confirm successful implementation.
• When copying values between variables with different maximum lengths, note that copying a value that exceeds
the maximum length of the destination variable causes truncation. For example, Custom Traffic variables have
100-character limits and Custom Conversion variables have 255-characters limits. When copying a 150-character
value from s.eVar1 to s.prop1 using dynamic variables, this value is truncated in the Custom Traffic report at
100 characters.
Dynamic Variable Examples
Examples of dynamic variables you can use in Analytics.
In the Adobe image request that occurs on the page view, if you are using dynamic variables to copy the value of
Custom Traffic 1 to Custom Conversion 1, you would see v1=D=c1. If eVar1 received a value previously in the
request, Adobe's servers dynamically copy the value of Custom Traffic 1 to Custom Conversion 1 during data
processing. As a result, the value originally passed using Custom Traffic 1 also appears in the Custom Conversion
1 reports.
Note that the D=[variable] value should be in quotes. The Analytics code treats this as a string. The string will be
URL encoded when passed into Analytics (as you will see if viewing the request in the DigitalPulse Debugger or a
similar utility). This is normal. Adobe's servers recognize the D=[variable] construction and will copy the appropriate
value when they encounter this string.
Dynamic Variables
116
Note: When using the image request to track links, the type of link (download=lnk_d, exit=lnk_e, or custom
link=lnk_o) must be defined, as does the Link URL/Name (pev2). Links require manual implementation by
inserting code within the &lt;a href&gt; tag.
JavaScript Example
Description
s.eVar1=&quot;D=pageName&quot;
Captures the pageName value in eVar1.
s.prop1='D=v2+&quot;:&quot;+c2'
Concatenates eVar2:prop2 into prop1.
s.prop1=s.eVar1=&quot;D=g&quot;
Passes the page URL into both prop1 and eVar1.
s.eVar1=&quot;D=v0&quot;
Captures the campaign in eVar 1.
s.prop1='D=User-Agent+&quot; - &quot;+Accept-Language'
Concatenates the user agent and accept language
headers in prop1.
s.prop1=&quot;D=User-Agent&quot;
Captures the user agent in prop1,
Image Request Example
Description
/b/ss/rsid/?gn=Home&amp;D=~~&amp;c1=~~v0
/b/ss/rsid/?gn=Home&amp;D=~~&amp;c1=~~campaign
/b/ss/rsid/?gn=Home&amp;c1=D%3dv0%3d is
/b/ss/rsid/?gn=Home&amp;c1=%5b%5bv0%5d%5d%5b
Four ways to set prop1 to a campaign
/b/ss/rsid/?gn=Home&amp;D=~~&amp;c2=~~x-up-subno
Pulls the x-up-subno header into prop2
&amp;c1=D%3DUser-Agent
Makes prop1 a dynamic variable filled in with the HTTP
header User-Agent
&amp;c1=D%3D%22test%22
Makes prop1 a dynamic variable filled in with the
string&quot;test&quot;. This becomes more useful when used with
concatenation which utilizes the + operator.
&amp;c1=D%3D%22US%3A%20%22%2BUser-Agent
Makes prop1 a dynamic variable filled in with the
User-Agentprefixed by &quot;UA:&quot;
&amp;vid=D%3DX-TM-ANTID
This example searches for a uniqueheader, which in this
case is X-TM-ANTID.
Merchandising Variables
117
Merchandising Variables
When measuring the success of external campaigns or external search terms, you typically want a single value to
receive credit for any success events that occur. For example, if a customer clicks a link in an email campaign to
visit your website, all purchases made as a result should be credited to that campaign.
But what about events that are driven by internal search or by category browsing when a customer is looking for
multiple items? For example, a customer searches your site for &quot;goggles&quot; and then adds a pair to the cart:
Before checkout, the customer searches for &quot;winter coat&quot;, and then adds a down jacket to the to the cart:
Merchandising Variables
118
When this purchase is completed, assuming the allocation wasn't changed from Most Recent, you'll have an internal
search for &quot;winter coat&quot; credited with the purchase of a pair of goggles. Good for &quot;winter coat&quot;, but bad for marketing
decisions:
Internal Search Term Revenue
winter coat
$157
How merchandising variables solve this problem
Cross-category merchandising variables, or &quot;merchandising evars&quot;, let you assign the current value of an eVar to
a product at the time a success event takes place. This value remains tied to that product, even if one or more new
values are later set for that particular eVar.
If merchandising is enabled for the eVar in the previous example, the search term &quot;goggles&quot; is tied to the Fernie
Snow Goggles, and the search term &quot;winter coat&quot; is tied to the El Gordo Down Jacket. Merchandising variables
allocate revenue at the product level, so each term receives credit for the amount of revenue for the product to which
the term was associated:
Internal Search Term Revenue
winter coat
$119
goggles
$38
Implementing a Merchandising Variable
Describes how to enable and implement a merchandising variable.
Merchandising Variables
119
Enable a Merchandising Variable
Merchandising can be enabled for any custom eVar on the Admin Tools &gt; Report Suites &gt; Conversion Variables
page (you no longer need to call Adobe):
Setting
Expire After
Merchandising
Description
Determines how long merchandising values should persist.
Product Syntax: The value is set within s.products.
Conversion Variable Syntax: The value is set in the designated merchandising s.eVar.
Merchandising
Indicates when a product should be tied to the current merchandising category. Multiple events
Binding Event
may be selected by holding down Ctrl and clicking on multiple items in the list.
(Conversion
variable syntax only)
Note: When &quot;Product Syntax&quot; is selected, you can not choose an event (it is disabled,
but not grayed out).You can select an event only when the &quot;Conversion Variable Syntax&quot;
is selected.
Implementing Using Product Syntax
When Product Syntax is enabled, the merchandising category is populated directly within the products variable, so
selecting and setting a binding event is not required. This is the recommended method and should be used unless
the value is not available to set in s.products when the success event takes place.
• Syntax
s.products=&quot;category;product;quantity;price;event_incrementer;eVarN=merch_category|eVarM=merch_category2&quot;
• Example
s.events=&quot;prodView&quot;
s.products=&quot;;Fernie Snow Goggles;;;;eVar1=goggles&quot;
In
Merchandising Variables
120
The value &quot;goggles&quot; for eVar1 is assigned to the product &quot;Fernie Snow Goggles&quot;. All subsequent success events
(product adds, checkouts, purchases, and so on) that involve this product are credited to &quot;goggles&quot;.
Implementing Using Conversion Variable Syntax
Conversion Variable Syntax should be used when the eVar value is not available to set in s.products. This typically
means that your page has no context of the merchandising channel or finding method. In these cases you must set
the merchandising variable before you arrive at the product page, and the value persists until the binding event
occurs.
When the binding event selected during configuration occurs, the persisted value of the eVar is associated with the
product. For example, if prodView is specified as the binding event, the merchandising category is tied to the current
product list only at the time the event occurs. Only subsequent binding events can update a merchandising eVar
that has already been assigned to a product.
• Syntax
On the same or previous page before the binding event:
s.eVar1=&quot;merchandising_category&quot;
On the page where the binding event occurs:
s.events=&quot;prodView&quot;
s.products=&quot;category;product&quot;
• Example
Page 1 of the visit:
s.eVar1=&quot;Outdoors:Ski Goggles&quot;
Page 2 of the visit:
s.events=&quot;prodView&quot;
s.products=&quot;;Fernie Snow Goggles&quot;
The value &quot;Outdoors:Ski Goggles&quot; for eVar1 is assigned to the product &quot;Fernie Snow Goggles&quot;. All subsequent
success events (product adds, checkouts, purchases, and so on) that involve this product are credited to &quot;goggles&quot;.
Additionally, the current value of the merchandising variable is tied to all subsequent products until one of the following
conditions is met:
• eVar expires (based on the &quot;Expire After&quot; setting)
• The merchandising eVar is overwritten with a new value.
Instances on Merchandising Variables
Describes how instances are counted on merchandising variables.
Instances are not currently counted for merchandising variables that use Product Syntax. If you have selected
Product Syntax and have implemented according to these directions, you should not see instances for this variable.
If instances are being counted, it indicates that the eVar is being set in some locations outside of the products string,
which is unnecessary.
If you are using Conversion Variable Syntax, an instance is counted each time the variable is set. However, the
instance is attributed to &quot;None&quot; unless the following occurs each time the variable is set:
• A binding event is set.
Merchandising Variables
121
• The products variable is set.
• The merchandising eVar has a value.
For example, the following instance of eVar1 is allocated to &quot;Outdoors:Ski Goggles&quot;:
s.eVar1=&quot;Outdoors:Ski Goggles&quot;
s.events=&quot;prodView&quot;
s.products=&quot;;Fernie Snow Goggles&quot;
However, in the next example, the instance of eVar1 is allocated to &quot;None&quot; since all conditions are not met when
the eVar is set (there is no binding event and the products variable is not set):
Page 1 of the visit:
s.eVar1=&quot;Outdoors:Ski Goggles&quot;
Page 2 of the visit:
s.events=&quot;prodView&quot;
s.products=&quot;;Fernie Snow Goggles&quot;
Allocation to &quot;None&quot; occurs if you set a value for an eVar on a page where no binding event occurs, or if you set the
eVar value in the products string without a binding event.
Note: The current functionality for counting instances on merchandising variables is being reviewed and is
scheduled to change in an upcoming release.
The s.t() Function - Page Tracking
122
The s.t() Function - Page Tracking
The s.t() function is what compiles all the variables defined on that page into an image request and sends it to our
servers.
Properties of the Function
• Removing the s.t() call prevents any data from reaching Analytics. Multiple s.t() calls fires multiple image requests
(doubling the reported traffic on your site).
• If you wish to fire more than one image request on a single page load, using the s.tl() function is recommended.
• Triggering this function always increases pageviewsand always include the s.pageName variable.
Implementation
Upon generating code within the code manager, you are given the following at the bottom of the page code:
var s_code=s.t();if(s_code)document.write(s_code)//--&gt;&lt;/script&gt;
&lt;script language=&quot;JavaScript&quot;
type=&quot;text/javascript&quot;&gt;&lt;!--if(navigator.appVersion.indexOf('MSIE')&gt;=0)document.write(unescape('%3C')+'\!-'+'-')//--&gt;&lt;/script&gt;
&lt;noscript&gt;&lt;img src=&quot;http://yournameserver.112.2o7.net/b/ss/yourreportsuiteid/1/H.23.6--NS/0&quot;
height=&quot;1&quot; width=&quot;1&quot; border=&quot;0&quot; alt=&quot;&quot; /&gt;&lt;/noscript&gt;
Each line of code has a specific purpose:
var s_code=s.t();if(s_code)document.write(s_code)//--&gt;
This line of code is what actually fires the Javascript function. The s_code variable and it's accompanying
document.write method is for browsers that don't support image objects (Netscape browsers prior to version 3 and
Internet Explorer prior to version 4; estimated less than .5% of all internet users).
&lt;script language=&quot;JavaScript&quot;
type=&quot;text/javascript&quot;&gt;&lt;!--if(navigator.appVersion.indexOf('MSIE')&gt;=0)document.write(unescape('%3C')+'\!-'+'-')//--&gt;&lt;/script&gt;
&lt;noscript&gt;&lt;img
src=&quot;http://yournameserver.112.2o7.net/b/ss/yourreportsuiteid/1/H.23.6--NS/0&quot; height=&quot;1&quot;
width=&quot;1&quot; border=&quot;0&quot; alt=&quot;&quot; /&gt;
For any additional questions about the s.t() function, contact your organization's Account Manager. They can arrange
a meeting with an Adobe Implementation Consultant, who can provide assistance.
The s.tl() Function - Link Tracking
123
The s.tl() Function - Link Tracking
File downloads and exit links can be automatically tracked based on parameters set in the AppMeasurement for
JavaScript file.
If needed, these types of links can be manually tracked using custom link code as explained below. In addition,
custom link code can be used to track generic custom links that can be used for a variety of tracking and reporting
needs.
s.tl() Parameter Reference
Variable
this
Description
The first argument should always be set either to this (default) or true. The argument refers
to the object being clicked; when set to &quot;this,&quot; it refers to the HREF property of the link.
If you are implementing link tracking on an object that has no HREF property, you should
always set this argument to &quot;true.&quot;
Because clicking a link often takes a visitor off the current page, a 500ms delay is used to
ensure that an image request is sent to Adobe before the user leaves the page. This delay
is only necessary when leaving the page, but is typically present when the s.tl() function is
called. If you want to disable the delay, pass the keyword 'true' as the first parameter when
calling the s.tl() function.
linkType
s.tl(this,linkType,linkName, variableOverrides, doneAction)
linkType has three possible values, depending on the type of link that you want to capture.
If the link is not a download or an exit link, you should choose the Custom links option.
Type
linkType value
File Downloads
'd'
Exit Links
'e'
Custom Links
'o'
linkName
This can be any custom value, up to 100 characters. This determines how the link is displayed
in the appropriate report.
variableOverrides
(Optional, pass null if not using) This lets you change variable values for this single call, It is
similar to other AppMeasurement libraries.
useForcedLinkTracking
This flag is used to disable forced link tracking for some browsers. Forced link tracking is
enabled by default for FireFox 20+ and WebKit browsers.
Default Value
true
Example
s.useForcedLinkTracking = false
The s.tl() Function - Link Tracking
Variable
forcedLinkTrackingTimeout
124
Description
The maximum number of milliseconds to wait for tracking to finish before performing the
doneAction that was passed into s.tl . This value specifies the maximum wait time. If the
track link call completes before this timeout, the doneAction is executed immediately. If you
notice that track link calls are not completing, you might need to increase this timeout.
Default Value
250
Example
s.forcedLinkTrackingTimeout = 500
doneAction
An optional parameter to specify a navigation action to execute after the track link call
completes when useForcedLinkTracking is enabled.
Syntax
s.tl(linkObject,linkType,linkName,variableOverrides,doneAction)
doneAction : (optional) Specifies the action to take after the link track call is sent or has
timed out, based on the value specified by:
s.forcedLinkTrackingTimeout
The doneAction variable can be the string navigate, which causes the method to set
document.location to the href attribute of linkObject. The doneAction variable can also
be a function allowing for advanced customization.
If providing a value for doneAction in an anchor onClick event, you must return false after
the s.tl call to prevent the default browser navigation.
To mirror the default behavior and follow the URL specified by the href attribute, provide a
string of navigate as the doneAction .
Optionally, you can provide your own function to handle the navigation event by passing this
function as the doneAction.
Examples
&lt;a href=&quot;...&quot; onclick=&quot;s.tl(this,'o','MyLink',null,'navigate');return
false&quot;&gt;Click Here&lt;/a&gt; &lt;a href=&quot;#&quot;
onclick=&quot;s.tl(this,'o','MyLink',null,function(){if(confirm('Proceed?'))document.location=...});return
false&quot;&gt;Click Here&lt;/a&gt;
Example
The following example of an s.tl() function call uses the default 500 ms delay to ensure data is collected before
leaving the page.
s.tl(this,'o','link name');
The following example disables the 500 ms delay, if the user is not going to leave the page, or whenever the object
being clicked has no HREF.
s.tl(true,'o','link name');
The s.tl() Function - Link Tracking
125
The 500ms delay is a maximum delay. If the image requested returns in less than 500 ms, the delay stops immediately.
This allows the visitor to move onto the next page or next action within the page.
The following examples are for handling custom links on WebKit browsers:
&lt;a href=&quot;...&quot; onclick=&quot;s.tl(this,'o','MyLink',null,'navigate');return false&quot;&gt;Click Here&lt;/a&gt;
&lt;a href=&quot;#&quot; onclick=&quot;s.tl(this,'o','MyLink',null,
function(){if(confirm('Proceed?'))document.location=...});return false&quot;&gt;Click Here&lt;/a&gt;
Note: Uses of custom link code are often very specific to your Web site and reporting needs. You can contact
your Adobe Consultant or Customer Care before implementing custom link code to understand the possibilities
available to you and how best to leverage this feature based on your business needs.
The basic code to track a link using custom link code is shown in the following example:
&lt;a href=&quot;index.html&quot; onClick=&quot;s.tl(this,'o','Link Name')&quot;&gt;My Page&lt;/a&gt;
Note: The s_gi function must contain your report suite ID as a function parameter. Be sure to swap out rsid
for your unique report suite ID.
Note: If the link name parameter is not defined, the URL of the link (determined from the &quot;this&quot; object) is used
as the link name.
Analytics variables can be defined as part of custom link code.
Automatic Tracking of Exit Links and File Downloads
The JavaScript file can be configured to automatically track file downloads and exit links based on parameters that
define file download file types and exit links.
The parameters that control automatic tracking are as follows:
s.trackDownloadLinks=true
s.trackExternalLinks=true
s.linkDownloadFileTypes=&quot;exe,zip,wav,mp3,mov,mpg,avi,doc,pdf,xls&quot;
s.linkInternalFilters=&quot;javascript:,mysite.com,[more filters here]&quot;
s.linkLeaveQueryString=false
The parameters trackDownloadLinks and trackExternalLinks determine if automatic file download and exit link
tracking are enabled. When enabled, any link with a file type matching one of the values in linkDownloadFileTypes
is automatically tracked as a file download. Any link with a URL that does not contain one of the values in
linkInternalFilters is automatically tracked as an exit link.
In JavaScript H.25.4 (released February 2013), automatic exit link tracking was updated to always ignore links with
HREF attributes that start with #, about:, or javascript:.
Example 1
The file types jpg and aspx are not included in linkDownloadFileTypes above, therefore no clicks on them are
automatically tracked and reported as file downloads.
The parameter linkLeaveQueryString modifies the logic used to determine exit links.When linkLeaveQueryString=false,
exit links are determined using only the domain, path, and file portion of the link URL.When linkLeaveQueryString=true,
the query string portion of the link URL is also used to determine an exit link.
The s.tl() Function - Link Tracking
126
Example 2
With the following settings, the example below will be counted as an exit link:
//JS file
s.linkInternalFilters=&quot;javascript:,mysite.com&quot;
s.linkLeaveQueryString=false
//HTML file
&lt;a href='http://othersite.com/index.html?r=mysite.com'&gt;Visit Other Site!&lt;/a&gt;
Example 3
With the following settings, the link below is not counted as an exit link:
//JS file
s.linkInternalFilters=&quot;javascript:,mysite.com&quot;
s.linkLeaveQueryString=true
//HTML
&lt;a href='http://othersite.com/index.html?r=mysite.com'&gt;Visit Other Site&lt;/a&gt;
Note: A single link can be tracked only as a file download or exit link, with file download taking priority. If a
link is both an exit link and file download based on the parameters linkDownloadFileTypes and linkInternalFilters,
it is tracked and reported as a file download and not an exit link. The following table summarizes the automatic
tracking of file downloads and exit links.
Manual Link Tracking Using Custom Link Code
Custom link code lets file downloads, exit links, and custom links be tracked in situations where automatic tracking
is not sufficient or applicable.
Custom link code is typically implemented by adding an onClick event handler to a link or by adding code to an
existing routine. It can be implemented from essentially any JavaScript event handler or function.
Link Tracking consists of calling the AppMeasurement for JavaScript function whenever the user performs actions
that generate data you want to capture. This function, s.tl(), is either called directly in an event handler, such as
onClick or onChange, or from within a separate function. This s.tl() function has five arguments. The first three are
required:
s.tl(this,linkType,linkName, variableOverrides, doneAction)
Custom Link Tracking on FireFox and WebKit Browsers
JavaScript H.25 includes an update to ensure that link tracking completes successfully on WebKit browsers (Safari
and Chrome). JavaScript H.26 includes an update to ensure that link tracking completes successfully on FireFox
20+.
After this update, download and exit links that are automatically tracked (determined bys.trackDownloadLinksand
s.trackExternalLinks) are tracked successfully. If you are tracking custom links using manual JavaScript calls,
you need to modify how these calls are made. For example, exit and download links are often tracked using code
similar to the following:
&lt;a href=&quot;http://anothersite.com&quot; onclick=&quot;s.tl(this,'e','AnotherSite',null)&quot;&gt;
Internet Explorer executes the track link call and open the new page. Other browsers might cancel execution of the
track link call when the new page opens. This often prevents track link calls from completing.
The s.tl() Function - Link Tracking
127
To work around this behavior, H.25 (released July 2012) includes an overloaded track link method ( s.tl ) that
forces browsers with this behavior to wait for the track link call to complete. This new method executes the track link
call and handles the navigation event, instead of using the default browser action. This overloaded method requires
an additional parameter, called doneAction, to specify the action to take when the link tracking call completes.
To use this new method, update calls to s.tl with an additional doneAction parameter, similar to the following:
&lt;a href=&quot;http://anothersite.com&quot;
onclick=&quot;s.tl(this,'e','AnotherSite',null,'navigate');return false&quot;&gt;
Passing navigate as the doneAction mirrors the default browser behavior and opens the URL specified by the href
attribute when the tracking call completes.
In JavaScript H.25.4 (released February 2013), the following scope limitations were added to links tracked when
useForcedLinkTracking is enabled. The automatic forced link tracking applies only to:
• &lt;A&gt; and &lt;AREA&gt; tags.
• The tag must have an HREF attribute.
• The HREF can't start with #, about:, or javascript:.
• The TARGET attribute must not be set, or the TARGET needs to refer to the current window (_self, _top, or the value
of window.name).
Link Tracking Using an Image Request
Links can be tracked without calling the s.tl() function by constructing an image request.
Image requests are hard coded by adding the &quot;pe&quot; parameter to your image request src parameter as follows:
pe=[type]
Where [type] is replaced with the type of link you want to track:
• lnk_d = download
• lnk_e = exit
• lnk_o = custom
Additionally, a link URL can be specified by passing the URL in the pev1 parameter:
pev1=mylink.com
A link name can be specified by passing the name in the pev2 parameter:
pev2=My%20Link
For example:
&lt;img
src=&quot;http://collectiondomain.112.2o7.net/b/ss/reportsuite/1/H.25.3--NS/0?pe=lnk_e?pev1=othersite.com?pev2=Offsite%20Link&quot;
width=&quot;1&quot; height=&quot;1&quot; border=&quot;0&quot; /&gt;
Setting Additional Variables for File Downloads, Exit Links, and Custom Links
Two parameters (linkTrackVars and linkTrackEvents) control which Analytics variables are set for file downloads,
exit links, and custom links.
They are, by default, set within the JS file as follows:
s.linkTrackVars=&quot;None&quot;
s.linkTrackEvents=&quot;None&quot;
The s.tl() Function - Link Tracking
128
The linkTrackVars parameter should include each variable that you want to track with every file download, exit link,
and custom link. The linkTrackEvents parameter should include each event you want to track with every file download,
exit link, and custom link. When one of these link types occur, the current value of each variable identified is tracked.
For example to track prop1, eVar1, and event1 with every file download, exit link, and custom link, use the following
settings within the global JS file:
s.linkTrackVars=&quot;prop1,eVar1,events&quot;
s.linkTrackEvents=&quot;event1&quot;
Note: The variable pageName cannot be set for a file download, exit link, or custom link, because each of
the link types is not a page view and does not have an associated page name.
Note: If linkTrackVars (or linkTrackEvents) is null (or an empty string), all Analytics variables (or events) that
are defined for the current page are tracked. This most likely inflates instances of each variable inadvertently
and should be avoided.
Best Practices
The settings for linkTrackVars and linkTrackEvents within the JS file affect every file download, exit link, and custom
link. Instances of each variable and event can be inflated in situations where the variable (or event) applies to the
current page, but not the specific file download, exit link, or custom link.
To ensure that the proper variables are set with custom link code, Adobe recommends setting linkTrackVars and
linkTrackEvents within the custom link code, as follows:
&lt;a href=&quot;index.html&quot; onClick=&quot;
var s=s_gi('rsid');
s.linkTrackVars='prop1,prop2,eVar1,eVar2,events';
s.linkTrackEvents='event1';
s.prop1='Custom Property of Link';
s.events='event1';
s.tl(this,'o','Link Name');
&quot;&gt;My Page
The values of linkTrackVars and linkTrackEvents override the settings in the JS file and ensure only the variables
and events specified in the custom link code are set for the specific link.
Note: In the above example, the value for prop1 is set within the custom link code itself. The value of prop2
comes from the current value of the variable as set on the page.
Using Function Calls with Custom Link Code
Due to the complex nature of custom link code, you can consolidate the code into a self-contained JavaScript function
(defined on the page or in a linked JavaScript file) and make calls to the function within the onClick handler.
For example, you could insert the following two functions in your AppMeasurement.js file, just below the
s_doPlugins() function, and then use them throughout your site:
/* Set Click Interaction values (with timeout – H25 code and higher*/
function trackClickInteraction(name){
var s=s_gi('rsid');
s.linkTrackVars='prop42,prop35';
s.prop42=name;
The s.tl() Function - Link Tracking
129
s.prop35=s.pageName;
s.tl(true,'o','track interaction',null,'navigate');
}
/* Set Click Interaction values (without timeout – pre H25 code*/
function trackClickInteraction(name){
var s=s_gi('rsid');
s.linkTrackVars='prop42,prop35';
s.prop42=name;
s.prop35=s.pageName;
s.tl(true,'o','track interaction');
}
Note: If needed, you can pass the link type and link name as additional parameters for the JavaScript function.
You can use code similar to the following to call these functions:
&lt;a href=”http://www.your-site.com/some_page.php”
onclick=”trackClickInteraction('this.href');”&gt;Link Text&lt;/a&gt;
Avoiding Duplicate Link Counts
It is possible for the link to be double-counted in situations where the link is normally captured by automatic file
download or exit link tracking.
For example, if you are tracking PDF downloads automatically, the following code results in a duplicate download
count:
function trackDownload(obj) {
var s=s_gi('rsid');
s.linkTrackVars='None';
s.linkTrackEvents='None';
s.tl(obj,'d','PDF Document');
}
To ensure link double counting does not occur, use the following modified JavaScript function:
&lt;script language=JavaScript&gt;
function linkCode(obj) {
var s=s_gi('rsid');
s.linkTrackVars='None';
s.linkTrackEvents='None';
var lt=obj.href!=null?s.lt(obj.href):&quot;&quot;;
if (lt==&quot;&quot;) { s.tl(obj,'d','PDF Document'); }
}
The last two lines of the code above modify the behavior of custom link code so only the automatic tracking behavior
occurs, eliminating any possible double counting.
Popup Windows with useForcedLinkTracking
When useForcedLinkTracking is enabled, AppMeasurement overrides the default link behavior on some browsers
to prevent the track link call from being canceled when the new page opens. AppMeasurement executes the track
link call and handles the navigation event manually, instead of using the default browser action.
When tracking some links that open a popup window, the Chrome built-in popup blocker might prevent
AppMeasurement from opening a popup window that would normally be allowed. To avoid this, add a
target=&quot;_blank&quot; attribute to calls that open a window:
&lt;a href=&quot;./popup.html&quot; target=&quot;_blank&quot; onClick=&quot;&lt;a href=&quot;./popup.html&quot;
onclick=&quot;s.tl(this,'o','popup',null,'navigate');javascript:window.open('./popup.html','popup','width=550,height=450');
return false;&quot;&gt;
The s.tl() Function - Link Tracking
130
This allows the link to be tracked and the popup to load as expected.
Links from URL Shorteners
Links from URL shortener services (such as bit.ly) are typically not tracked as page views or as referrers. These
services return 301/302 redirects with the full URL to the web browser, which then sends a new, separate request
to the full URL. The original referrer is preserved since the shortener is no longer in the loop, and there isn't an
indication on the request that a redirect service was used to get the URL.
Due to the variety of services available, we recommending testing the specific scenarios in use on your site to
determine the redirect mechanism used by the service.
Link Tracking Variables in doPlugins
To help manage link tracking, these following variables are populated before the doPlugins function runs.
Inside of doPlugins, you can use the following values to modify link tracking behavior. For example, you can abort
tracking, or add additional variables to tracking requests.
Variable
linkType
Description
Impact
Contains the automatically determined link type, if any. Can If set with linkURL or linkName, a
be set to one of the following:
server call is sent as a download,
custom, or exit link.
• d (download)
• e (exit)
• o (custom/other)
This is the pe parameter in the image request.
linkName
The name that will appear in the custom, download or exit If set with linkType , an image request
link report. Truncated at 100 characters. Can be set to any will be sent as a download, custom or
string.
exit link
This is the pev2 parameter in the image request.
linkURL
linkObject
The URL of the link, which acts as the name if a linkName If set with linkType, an image request
does not exist. Can be set to any URL string.
will be sent as a download, custom or
exit link
This is the pev1 parameter in the image request.
The clicked object for reference. This is read-only.
No direct impact on measurement.
Example
function s_doPlugins(s) {
if (s.linkType == &quot;d&quot; &amp;&amp; s.linkURL.indexOf(&quot;.aspx?f=&quot;) {
//special tracking for .aspx file download script
s.eVar11 = s.linkURL.substring(s.linkURL.lastIndexOf(&quot;?f=&quot;) + 3, s.linkURL.length);
}
else if (s.linkType == &quot;o&quot; ) {
// note: linkType is set to &quot;o&quot; only if you make a custom call
// to s.tl() and set the link type to &quot;o&quot;. Automatically tracked
The s.tl() Function - Link Tracking
131
// links are set to &quot;d&quot; or &quot;e&quot; only.
s.eVar10 = s.LinkURL;
}
}
Validating File Downloads, Exit Links, and Custom Links
To fully validate download, exit, and custom links, Adobe recommends using a packet analyzer to examine the links
in real-time.
File downloads, exit links, and custom links are not page views, so the DigitalPulse Debugger tool cannot be used
to verify parameters and variable settings. You must use a Packet Analyzers to view track link data.
The s.sa() Function
132
The s.sa() Function
The s.sa() function lets you dynamically change a report suite at any time on the page, before or after an image
request fires.
If your organization wants to send data to different report suites without a page reload, using this function is strongly
recommended.
This information is suited for advanced users who are well-versed in both reporting and implementation. Do not
attempt to make any edits to your implementation without complete knowledge of its consequences. If you require
implementation changes, contact your organization's Account Manager.
Properties of the Function
Setting this function takes all previously defined variables and lets them be used in a different report suite.
Implementation Examples
Sending video data to one report suite while sending the rest to another:
// Set in the core JS file by default
var s=s_gi('prodrsid');
// Define this when a user interacts with a video
s.sa('videorsid');
s.t(); // Sends an image request
Using s.sa() and multi-suite tagging:
// Set in the core JS file by default
var s=s_gi('rsid1');
// Call the function when you wish to change report suites
s.sa('rsid1,rsid2');
s.t();
The s.clearVars() Function
133
The s.clearVars() Function
clears the following values from the instance object.
• props
• eVars
• hier
• list
• events
• eventList
• products
• productsList
• channel
• purchaseID
• transactionID
• state
• zip
• campaign
For example:
s.clearVars()
Note: clearVars() is included in About AppMeasurement for JavaScript, it is not available in H code and
previous.
The s_gi() Function
134
The s_gi() Function
The s_gi() function is used to create or find your instance of AppMeasurement by report suite ID. Internally,
AppMeasurement keeps track of every instance created, and s_gi() returns the existing instance for a report suite
if one exists. If an instance does not exist, a new instance is created and returned.
We recommend calling s_gi() before setting variables and making tracking calls throughout your page code. This
ensures that the correct object is used to make the tracking call in the case that the s variable is inadvertently
overwritten.
Using Multiple Report Suites
The object returned varies based on the report suite ID(s) passed. For example, if you make the following initial call
to s_gi():
var s=s_gi('rsid1,rsid2')
The following table outlines what is returned by subsequent calls:
Subsequent Call to s_gi
Description of Object Returned
s=s_gi('rsid1,rsid2')
The same object referenced earlier.
s=s_gi('rsid1')
A copy of the object created earlier, but not the original.
s=s_gi('rsid1,rsid3')
A copy of the object created earlier, but not the original.
s=s_gi('rsid3')
A new, empty object, with no config variables set (e.g. linkTrackVars
is empty, as is linkDownloadFileTypes).
Util.cookieRead
135
Util.cookieRead
Gets the value for a cookie.
Syntax:
s.Util.cookieRead(key)
Parameters:
Parameter
Description
key
(required) key to write value for in cookies.
Returns:
Cookie value or an empty string if the cookie is not found.
Example:
var myCookie = s.Util.cookieRead(&quot;my_cookie&quot;);
Util.cookieWrite
136
Util.cookieWrite
Writes a value to a cookie.
Syntax:
s.Util.cookieWrite(key, value [,expire])
Parameters:
Parameter
Description
key
(required) key to write value for in cookies.
value
(optional) value to write to cookies.
expire
(optional) Date object containing the expiration date for the cookie. Default is to use a session
cookie.
Returns:
Example:
//set a cookie with an expiration 6 months from now
var date = new Date();
date.setMonth(date.getMonth() + 6);
var success = s.Util.cookieWrite(&quot;my_cookie&quot;, &quot;my_value&quot;, date);
Util.getQueryParam
137
Util.getQueryParam
Returns the value of a specified query string parameter, if found in the current page URL or in the provided string.
Because important data (such as campaign tracking codes, internal search keywords, etc.) is available in the query
string on a page, getQueryParam helps capture the data into Analytics variables.
This utility replaces the getQueryParam plug-in.
Syntax:
s.Util.getQueryParam(key, [url], [delim])
Note: The syntax for the utility differs from the syntax for the plug-in.
Parameters:
Parameter
Description
key
(required) The name of the query string parameter that you want to get. This parameter is case
sensitive.
url
(optional) Default url is s.pageURL or window.location. Specifying a value for this parameter
overrides the URL from which the query parameter is retrieved to the one specified.
delim
(optional) Parameter delimiter in the URL. Default delimiter is &quot;&amp;&quot;. This lets you to specify an
alternate query-string delimiter, such as &quot;;&quot;.
Returns:
This function returns the value of the query-string variable or an empty string if it's not found.
Example:
s.doPlugins = function(s) {
s.campaign = s.Util.getQueryParam(&quot;cid&quot;);
};
Offline Tracking
138
Offline Tracking
The following variables and functions let you store measurement calls when the application is offline.
Note: To enable offline tracking, your report suite must be timestamp-enabled. If timestamps are enabled on
your report suite, your trackOffline configuration property must be true. if your report suite is not timestamp
enabled, your trackOffline configuration property must be false. If this is not configured correctly, data will
be lost. If you are not sure if a report suite is timestamp enabled, contact Customer Care.
When enabled, Offline AppMeasurement behaves in the following way:
• The application sends a server call, but the data transmission fails.
• AppMeasurement generates a timestamp for the current hit.
• AppMeasurement buffers the hit data, and backs up buffered hit data to persistent storage to prevent data loss.
At each subsequent hit, or at the interval defined by offlineThrottleDelay, AppMeasurement attempts to send
the buffered hit data, maintaining the original hit order. If the data transmission fails, it continues to buffer the hit
data (This continues while the device is offline).
Property or Method
Description
trackOffline
Default: false
Enables or disables offline tracking for the measurement library.
Examples:
s.trackOffline=true;
offlineLimit
Default: no limit
Maximum number of offline hits stored in the queue.
Examples:
s.offlineHitLimit=100;
offlineThrottleDelay
Default: 0
Specifies a cadence (or delay), in milliseconds, for sending buffered hit data when
AppMeasurement detects an active network connection. Doing so mitigates the
performance impact of sending multiple hits on the application.
For example, if offlineThrottleDelay=1000, and it takes 300ms to send the hit data,
AppMeasurement waits 700ms before sending the next buffered hit.
s.offlineThrottleDelay=1000;
forceOnline
forceOffline
Manually set the online or offline state of the measurement object. The library
automatically detects when the device is offline or online, so these methods are needed
only if you want to force measurement offline. forceOnline is used only to return to
the online state after manually going offline.
When measurement is offline:
• If trackOffline is true: hits are stored until measurement is online.
Offline Tracking
Property or Method
139
Description
• If trackOffline is false: hits are discarded.
Examples:
s.forceOffline();
s.forceOnline();
Data Collection
140
Data Collection
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. All of these cookies
are prefixed by &quot;s_&quot; like our visitor ID cookie &quot;s_vi&quot; except for out opt-out cookie
&quot;omniture_optout&quot;.
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.
Note: Implementations using dynamic variables have the option of reading in other HTTP request headers
not listed above.
Data Collection
141
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 &quot;SUCCESS&quot; or &quot;FAILURE&quot; 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.
Note: 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.
Variable Overrides
Variable overrides let you change a variable value for a single track or track link call.
To override variables, create a new object, assign variable values, and pass this object as the first parameter to
s.t(), or as the fourth parameter to s.tl():
s.eVar1=&quot;one&quot;;
s.eVar2=&quot;two&quot;;
s.eVar3=&quot;three&quot;;
overrides = new Object();
overrides.eVar1=&quot;1_one&quot;;
overrides.eVar2=&quot;&quot;;
s.t(overrides);
// values passed: eVar1=&quot;1_one&quot;, eVar2=&quot;&quot;, eVar3=&quot;three&quot;
s.linkTrackVars=&quot;eVar1,eVar2,eVar3,events&quot;;
s.eVar1=&quot;one&quot;;
s.eVar2=&quot;two&quot;;
s.eVar3=&quot;three&quot;;
overrides = new Object();
overrides.eVar1=&quot;1_one&quot;;
overrides.eVar2=&quot;&quot;;
Data Collection
142
s.tl(this,'e','AnotherSite',overrides,'navigate')
// values passed: eVar1=&quot;1_one&quot;, eVar2=&quot;&quot;, eVar3=&quot;three&quot;
Report Suite IDs - Dynamic Accounts
The .js file can be configured to automatically select a report suite ID. The .js file automatically sends the image
request to the report suite based on the URL. For example, if the URL is www.mysite.com, the image request is
automatically sent to report suite A. If the URL is www.mysite1.com, the image request is automatically sent to
report suite B.
These strings can be found within any of the following:
• Host/domain (default setting)
• Path
• Query String
• Host/domain and Path
• Path and Query String
• Full URL
For more information on configuring Analytics to automatically select a Report Suite ID, contact Adobe Live Support.
Defining the URL Segment to Match
Given the following sample URL, the portions of the URL are shown below, along with the s.dynamicAccountMatch
variable that must be set. (The default - if s.dynamicAccountMatch is not defined - is to search the Host/Domain
Name only).
Sample URL: http://www.client.com/directory1/directory2/filename.html?param1=1234&amp;param2=4321
Portion
Example (from above)
Host/Domain Name
www.client.com
Path
directory1/directory2/filename.html
Query String
param1=1234&amp;param2=4321
Host/Domain and Path
www.client.com/directory1/directory2/filename.html
Path and Query String
directory1/directory2/filename.html?param1=1234&amp;param2=4321
URL
http://www.client.com/directory1/directory2/filename.html?param1=1234&amp;param2=4321
Portion
s.dynamicAccountmatch
Host/Domain Name
Undefined
Path
window.location.pathname
Query String
(window.location.search?window.location.search:&quot;?&quot;)
Host/Domain and Path
window.location.host+window.location.pathname
Path and Query String
window.location.pathname+(window.location.search?window.location.search:&quot;?&quot;)
URL
window.location.href
Consider the following example:
• s.dynamicAccountSelection=true
Data Collection
143
• s.dynamicAccountList=&quot;devreportsuite1=qa.client.com;reportsuite2=clientdirectory;reportsuite1=client.com&quot;
• s.dynamicAccountMatch=window.location.host+window.location.pathname
Multiple Rules
If multiple rules are selected (see example above), the rules are executed from left to right. The rules stop as soon
as a match is made, as shown below (with the given set of rules).
• s.dynamicAccountSelection=true
• s.dynamicAccountList=&quot;devreportsuite1=qa.client.com;reportsuite1=client.com&quot;
The code first checks to determine if &quot;qa.client.com&quot; exists within the Host/Domain Name. If so, the report suite
&quot;devreportsuite1&quot; is selected, and the match stops. Separate multiple rules with semi-colons.
Default Report Suite
The s_account variable can be set first, and acts as a default value in case any of the specified strings cannot be
found. Below is an example:
var s_account=&quot;defaultreportsuiteid&quot;
s.dynamicAccountSelection=true
s.dynamicAccountList=&quot;devreportsuite1=qa.client.com;reportsuite1=client.com&quot;
In the case above, if the host/domain name did not contain either &quot;qa.client.com&quot; or &quot;client.com,&quot; the report suite
&quot;defaultreportsuiteid&quot; would be used.
Common Errors
Common errors in dynamic accounts are described in the following sections.
Hard Coded Account
If the desire is to always send data to a specific report suite, set s_dynamicAccountSelection to false (alternately,
the variables may be removed altogether:
var s_account=&quot;defaultreportsuiteid&quot;
REMOVE: s.dynamicAccountSelection=true
REMOVE: s.dynamicAccountList=&quot;devreportsuite1=qa.client.com;reportsuite1=client.com&quot;
In the case above, defaultreportsuiteid is always used after the other two lines are removed.
Placement of Code
Defining s_account after the lines of code does not override the dynamic account selection, as shown below.
var s_account=&quot;defaultreportsuiteid&quot;
s.dynamicAccountSelection=true
s.dynamicAccountList=&quot;devreportsuite1=qa.client.com;reportsuite1=client.com&quot;
s_account=&quot;anotherreportsuiteid&quot;
In the example above, the account &quot;anotherreportsuiteid&quot; overrides &quot;defaultreportsuiteid,&quot; but does not override any
matches that occur in s.dynamicAccountList. The function that evaluates s.dynamicAccountList is actually
executed much later in the .JS file.
Multi-Suite Tagging
Multi-suite tagging may be used in conjunction with dynamic account selection, as shown below.
s.dynamicAccountSelection=true
s.dynamicAccountList=&quot;suiteid1,suiteid2=client.com&quot;
Data Collection
144
Dynamic Account Match
Do not put the dynamic account match variables in quotes. The options are displayed below.
Host/Domain Name
None
Query String
s.dynamicAccountMatch=(window.location.search?window.location.search:&quot;?&quot;)
Host/Domain and Path
s.dynamicAccountMatch=window.location.host+window.lcation.pathname
Path and Query String
s.dynamci AccountMatch=wn
i dow.o
l cato
i n.pathname+(wn
i dow.o
l cato
i n.search?wn
i dow.o
l cato
i n.search&quot;&quot;?&quot;)
Full URL
s.dynamicAccountMatch=window.location.href
Collecting Data From Form Elements
You can capture the values of form elements, such as radio button and checkbox items, into reports. This helps you
analyze the most popular choices in your online forms.
For example, if you had a radio button letting the user specify his or her favorite genre of music (such as rock, rap,
classical, or jazz), you could capture this response in a variable to determine the overall music preferences of your
user base.
The best way to capture this data depends on how your forms are processed. It also depends on whether the form
selections you want to capture are available in the query string on the page following the form submission. Examples
in this article are given in PHP. However, you can adapt these concepts to another language, depending on your
server environment.
This information is suited for advanced users who are well-versed in both reporting and implementation. Do not
attempt to make any edits to your implementation without complete knowledge of its consequences. If you require
implementation changes, contact your organization's Account Manager.
GET Method
If your form uses a GET method to submit data, you have access to the desired data in the query string of the URL
on the page following form submission. You can use the getQueryParam plug-in to capture this data out of the
query string automatically and place it into the variable of your choosing.
POST Method
If your form uses a POST method to submit data (which is more common), you have the results for each specific
form element available to you in the $_POST superglobal. To capture this in a variable, you want to determine the
form element name in question. Using the music genre example mentioned before, part of the form element in
question look like this:
&lt;input type=&quot;radio&quot; name=&quot;music_genre&quot; value=&quot;rock&quot;&gt;
This radio button belongs to the &quot;music_genre&quot; form element. You then have access to the user's selected value by
using $_POST['music_genre']. This can be written to a variable on the page following the form submission:
s.eVar1=&quot;&lt;?=$_POST['music_genre'];?&gt;&quot;
The eVar1 variable receives a copy of whatever value was submitted to your server through the form, as specified
in the value= property.
If you need additional information regarding this custom implementation method, contact your organization's Account
Manager. They can arrange a meeting with one of our Implementation Consultants to provide the help you need.
Data Collection
145
Tracking Across Different Implementation Types
This information is intended for advanced users who are well-versed in both reporting and implementation. Do not
attempt to edit your implementation without understanding the consequences. If you require implementation changes,
contact your organization's Account Manager.
If you use more than one type of implementation (such as JavaScript and hardcoded image requests), ensure that
the following variables are specified and match each other:
• s_account
• s.visitorNamespace
• s.trackingServer
• s.trackingServerSecure (if using SSL)
If each of these do not match across implementations, users may be tracked as separate visitors.
Implementation Guidelines
Following these guidelines results in using the same cookie domains, which lets visits be tracked between various
types of implementations.
• RSID: The report suite ID
• VNS: Visitor name space, the subdomain of 2o7.net or omtrdc.net used to store the visitor ID cookie
• COOKIEDOMAIN: Your VNS + trackingServer. Depending on your data center and RDC configuration, these can
greatly vary. See Correctly populate the trackingServer and trackingServerSecure variable or contact Client Care
if you are unsure about you data collection domain.
Javascript:
var s_account=&quot;RSID&quot;
s.visitorNamespace=&quot;VNS&quot;
s.trackingServer=&quot;VNS.COOKIEDOMAIN.net&quot;
Hardcoded image request:
AppMeasurement:
var s_account=&quot;RSID&quot;
s.visitorNamespace=&quot;VNS&quot;
s.trackingServer=&quot;VNS.COOKIEDOMAIN.net&quot;
Hardcoded image request:
Hardcoded image request:
&lt;img border=&quot;0&quot; alt=&quot;&quot; src=&quot;https://VNS.COOKIEDOMAIN.net/b/ss/RSID/5?ns=VNS&quot; width=&quot;1&quot; height=&quot;1&quot;
/&gt;
&lt;!-- Note that the visitor namespace is defined twice in hardcoded image requests; once in the
http subdomain, and another using the ns= query string parameter! --&gt;
If using a first-party cookie implementation, VNS.COOKIEDOMAIN.net can be replaced with the first-party cookie
domain used. For example, first-party cookies on adobe.com would be replaced with something similar to
metrics.adobe.com.
Implementation Example
Using adobe.com as an example, the implementations described here reference the same visid cookie.
Javascript:
var s_account=&quot;omniturecom&quot;
s.visitorNamespace=&quot;omniture&quot;
s.trackingServer=&quot;omniture.112.2o7.net&quot;
Data Collection
146
Hardcoded image request:
&lt;img border=&quot;0&quot; alt=&quot;&quot; src=&quot;https://omniture.112.2o7.net/b/ss/omniturecom/5?ns=omniture&quot;
width=&quot;1&quot; height=&quot;1&quot; /&gt;
Appmeasurement:
s.account=&quot;omniturecom&quot;;
s.visitorNamespace=&quot;omniture&quot;;
s.trackingServer=&quot;omniture.112.2o7.net&quot;;
And if first-party cookies are utilized:
Javascript:
var s_account=&quot;omniturecom&quot;
s.visitorNamespace&quot;omniture&quot;
s.trackingServer=&quot;metrics.omniture.com&quot;
Hardcoded image request:
&lt;img border=&quot;0&quot; alt=&quot;&quot; src=&quot;https://metrics.omniture.com/b/ss/omniturecom/5&quot; width=&quot;1&quot; height=&quot;1&quot;
/&gt;
Appmeasurement:
s.account=&quot;omniturecom&quot;;
s.visitorNamespace=&quot;omniture&quot;;
s.trackingServer=&quot;metrics.omniture.com&quot;;
AJAX-Tracking Rich Media Applications
AJAX is an emerging concept in web design that uses multiple technologies to create and manage dynamic content
on Web pages.
The need to track user interaction with AJAX and other rich media applications is paramount to analytics success
and realization of the return on investment in the Web design. The focus of this white paper is to provide
recommendations for tracking rich Internet applications, specifically those that use AJAX.
Rich Internet Applications (RIA)
Rich Internet Applications (RIAs) are changing the face of the Web. They bridge the gap between the promise of
on-demand technologies for the masses and realistic user experiences. RIAs have been maturing for years. The
biggest leaps forward have occurred with wide-scale adoption of browsers, which support the underlying technologies
that power these applications. While RIA has many forms and supporting technologies, the most common, and
perhaps most widely adopted, are AJAX and Flash. It is important to understand that the technology is not what
defines an RIA, but its usability and application.
What to Track
One of the most commonly asked questions with RIA is how to track micro-level activity separate from macro-level
activity, and when it is appropriate to do either. For example, say you have an application that allows customers to
uniquely configure a product. The application may have significant steps the users are exposed to. Are these steps
considered page views? In addition, there are micro-level activities within each step. Should these activities be
tracked as page views?
What if you want to understand the flow between activities, or which features get the most activity? The trouble with
RIA is that each application is unique. They are designed to mimic realistic actions, and since actions are relative
to the situation, the possibilities are endless. However, most applications have a few major components: milestone
Data Collection
147
steps, features, and micro-level actions within features. So, while each application requires some consideration as
to what specifically should be measured, there are some generalizations that can be applied to RIA tracking.
Macro-Level Activity
Macro-level activity usually constitutes the loading of the application. This provides information on visits, visitors,
instances, value to future actions, and so forth. It can, and should, also represent major steps in the process. A good
rule of thumb is that if an RIA action changes the application more than 50% (or whatever is considered significantly
changing the user experience or content), then it is macro-level, and should be tracked as a page view.
Micro-Level Activity
Micro-level activity includes any changes less than 50% (or not considered as significantly changing the user
experience or content). Toggling between color selections, for instance, would be considered micro-level activity.
Adobe recommends that micro-level tracking be related to features. For example, in the case of toggling between
colors, is it really important to understand which colors were considered? Or is it more important to know that the
color selection feature was used? Perhaps both are important, and if so, capture both, but when measuring the
effectiveness of RIA, consider the feature level activity as being more valuable.
All micro-level activity should be tracked as custom links with specifics measured through associated traffic variables
(props and eVars if the use needs to be measured against success events). This ensures that page views are not
inflated by micro-level activity, and allows for path analysis through the traffic variable.
What to Analyze
It is important to understand how effectively your RIA is driving success. Success is most commonly measured
through conversions. A macro-level analysis provides insight into RIA effectiveness as a whole. Micro-level analysis
may provide insight into which features help drive conversion.
You should measure efficiency of your RIA. This is an analysis of micro-level activity relative to the RIA macro
metrics. Do users go through more steps than necessary to arrive at the same goal? Analysis metrics might include
visits/features activity; page views/feature activity, visitors/feature activity, and so forth.
Conduct analysis on path flow and fall out. Are users avoiding the RIA and finding another path to the goal? Run
fallout reports built around the site and RIA flow. Run path analysis from landing pages to gauge the true traffic
patterns. Look at barriers and incentives to guide users toward the goal.
Suggested Metrics
• RIA Visits
• RIA Visitors
• RIA Page Views
• RIA Feature Activity (Custom Links) measure click activity by feature
Suggested Analysis
• RIA Feature Activity / RIA Page Views
• RIA Feature Activity / RIA Visits • RIA Page Views / Success Metric - Conversion Ratio: measures application effectiveness
• Total RIA Activity / Success Metric - Conversion Ratio: measures application efficiency
• Feature RIA Activity / Success Metric - Conversion Ratio: measures application feature efficiency
• Path Flow to and from RIA
• Fallout Rates through RIA conversion process
Data Collection
148
Implementing with AJAX
Implementing with AJAX is exactly like deploying code on a standard HTML page.
The business has questions that need answers, the needs are assessed and variables assigned. The design is then
applied and deployed. These concepts should be familiar if you have already been through the initial stages of
implementation.
Designing the Solution
The difference when throwing AJAX into the mix is first understanding the level of detail that needs to be gathered.
The potential of content changing on the page (macro-level) or tracking attributes of the application (micro-level)
determines which variables need to be set and which method of sending data to Adobe works best.
Deploying the Code
There are two functions in the JavaScript code that allow you to send data. There are some distinct guidelines that
should be followed to know which method should be used to send data.
Collecting Macro-Data (Page)
The t() function in the Adobe code sends a standard format image request, incrementing total site page views. All
Adobe variables that have been assigned values send data. The primary focus of using this function within RIAs
revolves around the value of the pageName variable. You should use this function when:
• The new content is considered a page view for the site or is considered moving from one page to another.
• The content of the page changes more than 50% (or whatever is considered significantly changing the user
experience or content).
• The page path must be tracked for each user interaction with the RIA.
Sending Macro-Data (Page)
If an image request was previously made on the same page, you must first clear the values of the previously-set
variables. Use the clearVars() funtion in AppMeasurement for JavaScript, or write a simple JavaScript function to
clear the variables if you are using H code. Set the values appropriate for the changed content, namely the pageName
variable. After the variables are set call the t() function.
Example
Note: Before you call s.t(), you must clear any values on the s object that you do not want to persist. if you
are using AppMeasurement for JavaScript, you can call s.clearVars(). If you are using H code, write a
simple routine to set variables to an empty string.
s.clearVars();
s.pageName=&quot;New Page&quot;
s.prop1=&quot;some value&quot;
void(s.t());
The following example shows a tracking call in the done callback of the JQuery .ajax function:
$.ajax({
url: &quot;test.html&quot;,
dataType: &quot;html&quot;
})
.done(function( response ) {
$( &quot;#content&quot; ).html( response );
s.clearVars();
Data Collection
149
s.pageName = $( &quot;h1:first&quot; ).text();
s.t();
});
Collecting Micro-Data (Link)
The tl() function does not send the pageName variable and is selective in the other variables that are sent. Because
of this restrictive design, it is well-suited for tracking micro-level statistics such as button clicks, link clicks, scrolling,
and other similar events. You should use this function when:
• You do not include a new page name or inflate page view statistics for the site.
• The tracking of user interactions with buttons, links, or specific features within a page/application is desired.
• Track the interaction path of the application.
Path analysis can be enabled for traffic variables (not restricted to page pathing) which is a useful tool in analyzing
the order users interact with your page or application. For example, you see that a user interacted first with button1
and then clicked on button4 before leaving the application. This link-level path can be traced without inflating
page-level statistics by using the tl() function.
Sending Micro-Data (Link)
If an image request was previously made on the same page, clear the values of the previously-set variables. This
can be accomplished by:
• Writing a simple JavaScript function to clear the Adobe variables.
• Set the linkTrackVars and linkTrackEvents variables if you have not already done it in the s_code.js file.
• Set the values appropriate for the changed content, namely the pageName variable.
• After the variables are set, call the tl() function.
Syntax
//set linkTrackVars and linkTrackEvents&gt; (if applicable)
//set new variables
s.tl(this,'o','Link Name');
Example
s.linkTrackVars=&quot;prop1,eVar1,events&quot;; s.linkTrackEvents=&quot;event1&quot;;
s.prop1=&quot;some value&quot;; s.eVar1=&quot;another value&quot;; s.events=&quot;event1&quot;;
s.tl(this,'o','My Link Name');
Placement of Code
There are generally two places to track data with AJAX: at the time of the request or in the reply. In most cases,
macro-data (page information) should be sent at the time of reply by having the code embedded in the HTML of the
new content. For micro-data tracking (links, etc.) it is more common to use a custom links approach by inserting the
code in the onClick attribute of the link, button, etc.
External Email Tracking
Companies use Analytics to determine the success of an email campaign.
Analytics can report email campaign analysis data in several key metrics, including the following:
Metric
Description
Click-throughs
Displays the number of click-throughs tracked from the email to the landing
page.
Data Collection
150
Metric
Description
Purchases and/or Successes
Displays the number of purchases resulting from the email.
Orders
Displays the number of orders placed as a result of the email.
Yield
Displays the dollar amount per visit generated from the email.
Conversion
Displays the number of leads, registrations, or any other success event
generated from the email.
Modifications to the HTML email body and the JavaScript library are required in order to capture the key metrics
shown above.
Implementation
There are several steps to follow in order to successfully display email campaign analysis data. The steps are
described as follows:
1. Create unique tracking codes.
Often, users ask for tracking recommendations for each unique campaign. This is entirely up to them, based on
what works best. Each user is different. Adobe recommends that each user generate friendly tracking codes, as
shown in the example below:
• sc_cid=A1123A321 &gt; &quot;A&quot; flags affiliate campaign
• sc_cid=EM033007 &gt; &quot;EM&quot; flags email campaign
• sc_cid=GG987123 &gt; &quot;GG&quot; signifies Google and is a paid search campaign
Contact Adobe ClientCare for details on setting up and using tracking codes.
2. Add query string parameters to HTML email links.
In order to track a user click-through and subsequent success events, a query string parameter needs to be
added to each link within the HTML email.You can choose to track each link separately or track all links together.
Each link can have a unique tracking code, or all links can have the same tracking code. Consider the following
hypothetical link within the email to a website:
&lt;a href=&quot;http://www.mycompany.com/index.asp&quot;&gt;Visit our home page&lt;/a&gt;
The following query string parameters ?sc_cid=112233B should be added to the link above:
&lt;a href= &quot;http://www.mycompany.com/index.asp?sc_cid=112233B&quot;&gt;Visit our home page&lt;/a&gt;
3. Update the JavaScript library.
Altering code in the JavaScript file, s_code.js, lets you capture how many users (and which users) clicked-through
from the email and participated in subsequent success events. There are two steps to updating the JavaScript
library.
a. Customize s_code.js by calling getQueryParam.
The s_code.js file should be placed in a location on the Web server where each Web page can access it.
The doPlugins function within this file should be altered so it captures the query string parameters on the
email links. For example:
/* Plugin Config */
s.usePlugins=true
function s_doPlugins(s) {
/* Add calls to plugins here */
// External Campaigns
s.campaign=s.getQueryParam('source')
Data Collection
151
}
s.doPlugins=s_doPlugins
Each query string parameter that needs to be copied into a variable should have one getQueryParam call.
In the example above, the query string parameter sc_cid is copied into campaign.
Only the first call to getQueryParam is required to capture click-throughs. Contact Adobe ClientCare to
implement this function and ensure that your version of the JavaScript file contains the getQueryParam
plug-in.
b. Make sure the Code to Paste JavaScript tags are on all landing pages. This Code to Paste must reference
the version of s_code.js altered in Part A.
The following points are important to remember when updating the JavaScript library. These points are listed
below.
• The query string parameter sc_cid must be visible in the URL on the final landing page otherwise no
click-through conversion is recorded.
• The sc_cid parameter is an example of a query string parameter. Any query string parameter can be used
and captured by the getQueryParam plug-in. Make sure that the query string parameters are used only for
campaign tracking. Any time the parameters appear in a query string, their values are copied into campaign.
4. Use SAINT to classify campaign tracking codes.
The SAINT Campaign Management Tool can be used to convert tracking codes into user-friendly names. It
can also be used to summarize the success of each email campaign. Step 5, below, outlines the process required
to set up an email campaign.
5. See pathing by email campaign (optional).
Pathing analysis by email campaign can be accomplished similarly to pathing by another campaign. You can
use a variable to show pathing by campaign, as explained in the following steps:
a. Consult Adobe ClientCare about turning on pathing for a Custom Insight variable (prop)
b. On all pages, copy the page name into the designated s.prop.
c. On the email landing page, append the name of the email campaign to the prop. The result displays as shown
below:
s.prop1=&quot;Home Page : 123456&quot;
When pathing is enabled for the Custom Insight variable, you can use Path reports (such as Next Page
Flow or Fallout) to see visitor navigation from the landing page.
Implementing Adobe Opt-Outs
Some visitors to your website may prefer not to have their browsing information aggregated and analyzed by Adobe
Marketing Cloud products and services or used to provide relevant content and advertising. Adobe offers you the
ability to provide visitors to your website a means to opt out of their information being collected by the following
Adobe products:
• Adobe Analytics
• Adobe Target
• Adobe Audience Targeted Creative
• Adobe AudienceManager
• Adobe AdLens
Data Collection
152
• Adobe Experience Manager
Privacy policy recommendations
Adobe recommends that you provide your website visitors with easy-to-find and easy-to-understand information
regarding the ability to opt out of having their browsing information collected by Adobe products or services.
Visitors can learn more about how Adobe generally uses information it collects in connection with providing our
products and services to our customers in the Adobe Privacy Center. However, because you exclusively control
how to implement our services on your web sites, it is up to you to describe to your website visitors the specific ways
in which they use our products and services. You are responsible for the creation of your own privacy policy, for
complying with your privacy policy, for complying with your service agreement with Adobe, and for complying with
all applicable laws.
Opt-outs for Adobe Analytics (including marketing reports &amp; analytics, data warehouse, ad hoc analysis
and SearchCenter+)
Adobe offers two types of opt-outs for Adobe Analytics (including marketing reports &amp; analytics, data warehouse,
ad hoc analysis and SearchCenter+):
• If you implement Adobe Analytics products with your own first-party cookie, you need to develop your own customized
opt-out link for your website visitors.
• Adobe also provides an opt-out mechanism to the public for websites using cookies set from Adobe’s 2o7.net and
omtrdc.net domains. This opt-out mechanism can be accessed from the Adobe Privacy Center.
Regardless of the opt-out mechanism you choose, Adobe recommends that you clearly describe the availability of
the opt-out mechanism in your privacy policy or as otherwise required by law or recommended according to current
best practices.
Add an Opt-Out Link
Visitors to your web site may choose not to have their activity tracked in Adobe’s analytics products by visiting the
opt-out page for your data collection domain.
If a user chooses not to be tracked and an opt-out cookie is set, your JavaScript file will continue to send data to
Adobe servers but that data will not be processed or reported on.
The collection_domain section of the URL structure is the trackingServer used in your JavaScript file. The collection
domain used for your Adobe Analytics implementation can be seen in the DigitalPulse debugger in the first row of
the Adobe Analytics table, which is labeled either “First Party Cookies” or “Third Party Cookies” depending on your
implementation. The collection domain for your website may contain 2o7.net, omtrdc.net or your website domain,
such as metrics.example.com.
Visitors opt-out by clicking the link on the opt-out page, thereby causing a cookie to be set in their browser. By having
the omniture_optout cookie for the applicable tracking domain, the user's activities will not be reported by Adobe
Analytics. You can provide your own link to the opt-out cookie, or you can follow the steps below to set the opt-out
cookie.
Adobe offers opt-outs for all implementation types.You are responsible for your own privacy policy and for remaining
in compliance with your signed terms. Note that the link to the opt-out page changes based on your implementation
type, as outlined here.
If you implement Adobe Analytics products and services with cookies set on domains owned by Adobe (i.e. 207.net
or omtrdc.net), you can point your website visitors to the opt-out mechanism provided in the Adobe Privacy Center
Data Collection
153
for all sites that use Adobe cookies for Adobe Analytics products and services. The direct link to the Adobe opt-out
mechanism is http://collection_domain/optout.html.
More information about Adobe Analytics privacy practices can be found at
http://www.adobe.com/privacy/advertising-services.html.
Opt-out Page URL Structure
Your opt out page is at the following URL:
http://collection_domain/optout.html[?optional_parameters]
The optional_parameters include:
locale=[code]: Provides a translated version of the opt-out page. The following locales are supported:
• en_US (default)
• de_DE
• es_ES
• fr_FR
• jp_JP
• ko_KR
• zh_CN
• zh_TW
popup=1: Treats the page as if it were a popup, and offers a “Close Window” button.
Example Opt-Out URLs
An English web page in a full window containing a link that, when clicked, will prevent the visitor from being tracked
on metrics.example.com:
http://metrics.example.com/optout.html
A French web page in a full window, containing a link that, when clicked, will prevent the visitor from being tracked
on example.d3.sc.omtrdc.net:
http://example.d3.sc.omtrdc.net/optout.html?locale=fr_FR
A German web page, in a popup window, containing a link that, when clicked, will prevent the visitor from being
tracked on example.112.2o7.net:
http://example.112.2o7.net/optout.html?popup=1&amp;locale=de_DE
Testing and Validation
154
Testing and Validation
Testing and Validation Process
Use validation and testing to ensure data reporting accuracy.
Validation and testing should always be done on the development report suite.
Identifying the s_account Variable in the DigitalPulse Debugger
When you run the DigitalPulse Debugger, you may want to look for the s_account variable.
The following figure shows the location of the s_account variable.
JavaScript JS File
Verify that the .JS file is correctly referenced from the page. The path can be specified either relative to the current
document, or an absolute path name can be used.
&lt;script language=&quot;JavaScript&quot;
src=&quot;http://www.sampleco.com/javascript/includes/s_code.js&quot;&gt;&lt;/script&gt;
If some pages of the site are loaded in a secure protocol (https:), and reference the AppMeasurement for JavaScript
file, ensure that the reference to the file is either secure (via https:) or code the reference as shown below. This
example adopts the protocol of the current page and prevents the warning that &quot;some elements are non-secure.&quot;
&lt;script language=&quot;JavaScript&quot;
src=&quot;//www.sampleco.com/javascript/includes/s_code.js&quot;&gt;&lt;/script&gt;
Ensure that the .JS file on the web servers have permissions appropriately set so that the file may be downloaded
and executed by website visitors. If a different .JS file is used on development servers, set the &quot;read only&quot; attribute
for the .JS file on production servers to avoid an overwrite. If altered, ensure that the following settings are set
appropriately at the top of the .JS file:
/************************** CONFIG SECTION **************************/
/* You may add or alter any code config here.
*/
Testing and Validation
155
/* Link Tracking Config */
s.trackDownloadLinks=false /* true for download tracking */
s.trackExternalLinks=false /* true for exit link tracking */
s.trackInlineStats=false /* true for ClickMap support */
s.linkDownloadFileTypes=&quot;exe,zip,wav,mp3,mov,mpg,avi,doc,pdf,xls&quot;
s.linkInternalFilters=&quot;javascript:&quot;
s.linkLeaveQueryString=false
s.linkTrackVars=&quot;None&quot;
s.linkTrackEvents=&quot;None&quot;
If &quot;s_account&quot; is assigned a value at the top of the .JS file, ensure that the report suite ID (populated in the s_account
variable) is correct. Also ensure that the code in the page is not setting the Report Suite ID (s_account variable).
Examine the image request and variables to ensure that the &quot;fallback method&quot; (the third part of the &quot;split&quot; code in
the example above) is not creating the image request instead of the .JS file. This can be determined since the
&quot;fallback&quot; method only creates an image request with minimal information.
Code Modifications
Testing any modifications to the .JS file or HTML code is the responsibility of the customer. It should be completed
prior to publishing the modifications to production websites.
Ensure that the linefeeds/return characters are not stripped or altered from the code that is placed within the HTML,
or from within the .JS file. Ensure that the JavaScript executes without an error on all pages and page templates
(in Internet Explorer Internet Options, select the Advanced Tab, and click Display a Notification about Every Script
Error.
When testing for errors, paste the code into a default HTML page to determine if the error is occurring because of
other page elements/objects.
&lt;html&gt;&lt;head&gt;&lt;/head&gt;&lt;body&gt;
...paste code here to debug...
&lt;/body&gt;&lt;/html&gt;
Variables and Values
Ensure that the variables that are populated from server scripting or code cannot output any quotation marks that
interfere with the values.
For instance:
s.pageName=&quot;Article: &quot;Article Name&quot;&quot;
s.pageName='Company's Information'
Ensure that the values of the variables do not exceed their maximum limits, specified in this document. Additional
characters are cropped at the data collection servers. They may interfere with the total length, increase bandwidth
unnecessarily, and may cause other issues.
Do not use $, ™, &reg;, &copy;, or commas (,) in the products variable. Generally, these are not useful in any Analytics
variables and may interfere with the ability to interpret or export fields. The best practice is to limit characters to the
first 127 ASCII characters.
Ensure that the events variable is populated with an appropriate value (prodView, purchase, scAdd, scRemove,
scOpen, or event1-event5) whenever products is populated. Ensure that the case of all Analytics variables and
functions are maintained, as shown below.
s.pageName
s.server
s.channel
s.pageType
s.prop1 – s.prop20
Testing and Validation
156
s.campaign
s.state
s.zip
s.events
s.products
s.purchaseID
s.eVar1 – s.eVar20
var s_code=s.t();if(s_code)document.write(s_code)//--&gt;
Page names are case sensitive, and differences create additional page records. &quot;Home&quot; and &quot;home&quot; are two different
pages within Analytics.
Note: Multiple page records cannot be combined within reports.
Validate that links are reported in the Custom Links report. Ensure that the correct parameters are passed to the
tl function. For more information on custom links, see The s.tl() Function - Link Tracking.
Custom Variables
List of custom variables used in Analytics.
Variable
Description
Traffic Variables
Check the value of prop1 - 75. Here is a checklist of items to check.
• Is the correct case used? &quot;ValueA&quot; is a different record than &quot;valueA.&quot; You can use
all lowercase since a small subset of browsers convert all variables to lower case.
• Are the values less than 100 characters in length? If not, some clipping of the values
can occur.
• Are all the values in a single property variable related, or do some values look out
of place?
Conversion Variables
Econversion variables include eVar 1 - 75. Here is a list of issues to check for the
following.
• Is the correct case used? &quot;ValueA&quot; is a different record than &quot;valueA.&quot; You can use
all lowercase since a small subset of browsers convert all variables to lower case.
• Are the values less than 255 characters in length? If not, some clipping of the values
can occur.
• Are all the values in a single eVar related, or do some values look out of place?
Custom Events
Events include both standard values (prodView, scOpen, scAdd, scCheckout,
purchase), as well as custom events from event1 to event100. All events are sent
in the events variable. Multiple events on the same page should be comma-delimited
(no white space).
• For all the standard conversion events, products should also be populated with the
applicable products. For all events except purchase, the qty and price elements
are optional.
• The purchase event, must be set only once in a session after the purchase has
been completed and confirmed.
Implementation Acceptance
Implementation process steps.
The following steps outline the implementation process.
Testing and Validation
157
1. The Adobe Consultant gathers report requirements and creates a data collection plan based on those requirements.
The data collection plan includes variable definitions, required VISTA rules and custom JavaScript, data correlation,
and all settings for each report suite. The client completes the Implementation Questionnaire.
2. Technical resources on the client-side implement the code, site-specific JavaScript, and server-side variables.
3. The Adobe Consultant addresses technical issues during the implementation and assists in devising solutions
as required.
4. Technical resources on the client-side unit test the implementation.
Testers log in to Analytics and verifying all variables (page name, channel, server, events, campaign, econversion
variables, custom traffic variables, products, and all other variables).
5. The client notifies Adobe that the implementation is complete.
The client provides a validation sample (data sample) to the Adobe Consultant to validate data accuracy.
(VISTA-generated report suites are validated by comparing appropriate metrics. A client-Adobe agreement of
the metrics to be validated for such report suites shall be made in advance, at the time of the VISTA rule creation.)
6. The client faxes (or signs online) an Implementation Acceptance and Agreement for the appropriate site(s).
7. After the acceptance has been received, the Adobe Consultant enables the Adobe Best Practices - Implementation
Verification certification within the interface.
8. Optionally, the client can contract with Adobe for monitoring services for key pages of the implemented site
(generally, these are the primary templates, home page, and critical entry pages).
This monitoring software is described in a separate document, but tracks pages by loading and executing the
page, then comparing the image request to a baseline stored in a database. If any differences are detected, the
software notifies specified Adobe (AM/IE) and client personnel via email.
The following items help to ensure a successful implementation:
• A best practices document, which is client-facing and explains the processes in detail.
• The validation document that the customer uses to unit test the implementation.
• An Implementation Acceptance and Agreement form for the client to sign.
• A monitoring application that continuously validates the tags.
• A relationship with Accenture to help with implementation testing.
• Utilities and/or tools for comparison of page views and/or orders. Those comparisons can get fairly difficult.
• A method or process to quickly obtain the debug log for a given day, by report suite ID.
Data Accuracy Validation
Data accuracy validation is a process of comparing report data with known and verifiable data points.
The validation process should be completed by Adobe personnel, preferably by the Adobe Consultant (the person
most familiar with the technical implementation details).
The preferred data points for this validation, in order of preference, are listed as follows:
• (Econversion sites) Comparison of econversion orders for a single day.
• Comparison of known success events, especially logged data where IP address and other browser information
generally stored in web server logs can be compared to the data collected.
• Comparison of page views.
Note: Default pages, such as index.html, often receive automated or monitoring traffic. These pages
represent a greater difference to browser-based data collection than other visited pages.
Testing and Validation
158
All three types of validation require a debug log or data feed for the time period in question. This is generally one
day or less.
It is expected that orders or success events can be measured to within 2-3% of actual values (sometimes reaching
higher accuracy levels) using standard JavaScript-based implementations. This assumes an SSL page, since SSL
pages are cached much less frequently, and by definition they should not be cached. An implementation with fully
server-side image requests on an SSL page should come within about 0-1% of actual values. Non-secure pages
may experience higher differences, but still within 5% of actual values.
When comparing page views for a single time period, it is expected that the page views can be accounted for within
5% of actual values, not including monitoring (such as Keynote or WhatsUpGold) or automated traffic (spiders, bots,
and scripts).
Data accuracy comparisons need to take into account the following items:
• QA or other types of internal testing that may be filtered by IP addresses or VISTA rules.
• Smart tags that only generate tags for certain types of orders or traffic.
• Queries for comparison must take into account what is being measured by the website (not including returns, orders
placed by customer service personnel, or other special conditions).
• Ensure that the time zone differences between the query and the report suite match.
• Custom Keynote or similar traffic (Keynote Transaction, etc.) that measure the ordering process and may be
reflected in tags, but removed from ordering systems.
• Account for the client's de-duping processes.
• Reloads of the order page (Orders are de-duplicated based on purchaseID).
Adobe Debugger
The Adobe Debugger (previously DigitalPulse Debugger) is a free tool provided by Adobe that lets you view the
data being collected from your site on any given page.
Note: DigitalPulse debugger was recently moved from digitalpulse.omniture.com to adobetag.com. If
you are having issues using the debugger, copy the updated code from Adobe Debugger Installation and
update your bookmarklet.
When executed in your browser, it shows the image requests that transmitted data from that page into Marketing
Cloud solutions, along with any variable values or parameters that were captured.This allows you and your developers
to check the validity of your implementation on any page on your site.
The DigitalPulse Debugger is officially supported for use in all recent versions and builds of Mozilla Firefox, Google
Chrome, Microsoft Internet Explorer, and Safari.
Note: Because the Debugger functions by creating a pop-up window when you access a special bookmark
in your web browser, certain ad-blocking plug-ins and pop-up blockers might interfere with the loading of the
Debugger.
Adobe Debugger Installation
Adobe Debugger (previously DigitalPulse Debugger) is installed as a bookmarklet in your browser. Copy the provided
JavaScript code to your clipboard and then create a bookmarklet in a supported browser.
Testing and Validation
159
1. Copy the following text to your clipboard (triple-clicking might help in highlighting all the text):
javascript:void(window.open(&quot;&quot;,&quot;dp_debugger&quot;,&quot;width=600,height=600,location=0,menubar=0,status=1,toolbar=0,resizable=1,scrollbars=1&quot;).document.write(&quot;&lt;script
language='JavaScript' id=dbg
src='https://www.adobetag.com/d1/digitalpulsedebugger/live/DPD.js'&gt;&lt;/&quot;+&quot;script&gt;&quot;));
2. Complete the steps appropriate for the desired browser:
Mozilla Firefox
Instructions to create a bookmark for the Adobe Debugger (previously DigitalPulse Debugger) from within Mozilla
Firefox.
1.
2.
3.
4.
5.
Right-click the bookmarks sidebar, then click New Bookmark.
In the Name field, specify &quot;Adobe Debugger&quot; as the name for the new bookmark.
In the Location field, paste the code that you copied to your clipboard as explained in Adobe Debugger Installation.
Select Load the Bookmark in the Sidebar, if desired.
Click Add.
Google Chrome
Instructions to create a bookmark for the Adobe Debugger (previously DigitalPulse Debugger) from within Google
Chrome.
1. Right-click the Bookmarks bar (depending on your Chrome settings the Bookmarks bar might be on the New
Tab page), then click Add Page.
2. In the Name field, specify &quot;Adobe Debugger&quot; as the name for the new bookmark.
3. In the URL field, paste the code that you copied to your clipboard as explained in Adobe Debugger Installation.
4. Browse to and specify the location you want to save the bookmark.
5. Click OK.
Microsoft Internet Explorer
Instructions to create a bookmark for the Adobe Debugger (previously DigitalPulse Debugger) from within Microsoft
Internet Explorer.
1.
In the Favorites Bar, click the Add to Favorites Bar icon (
) icon.
If the Favorites Bar is hidden, right-click the browser header, then click Favorites Bar.
A new bookmark is created.
2.
3.
4.
5.
6.
Right-click the bookmark, then click Rename.
In the New Name field, specify &quot;Adobe Debugger&quot; as the name, then click OK.
Right-click the newly created bookmark again, then click Properties.
In the URL field, paste the code that you copied to your clipboard as explained in Adobe Debugger Installation.
Click OK.
Launching DigitalPulse Debugger
After installing the DigitalPulse Debugger, you are ready to use it to view the data being collected from your site.
1. From your browser, click the bookmark or bookmarklet to launch the DigitalPulse Debugger in a new window.
Testing and Validation
160
2. View the data.
Packet Analyzers
Packet analyzers let you view the data sent by your implementation to Adobe Data Collection Servers.
Simliar to the DigitalPulse Debugger, a packet monitor shows what data parameters are being passed in an image
request; however, packet monitors provide added functionality:
• View custom link tracking image requests
• View image requests using implementation methods other than JavaScript, such as hard-coded image requests
or Appmeasurement
To view Analytics requests, filter outgoing requests using &quot;b/ss&quot;.
In very rare cases, the debugger will report an image request although no request makes it to Adobe's Analytics
processing servers. Using a packet monitor is a great way to be 100% sure that a specific image request is being
fired successfully.
While Adobe does not provide an official packet monitor, there are a wide range of them on the internet. The following
are some packet monitors others have found useful.
Note: These lists are not meant to be comprehensive, but rather information on frequently used monitors. If
you have a packet monitor you successfully use and find useful, feel free to provide feedback using the
Feedback button on the right side of this window.
Testing and Validation
Firefox
161
Internet Explorer
Chrome
Standalone Programs
Observe Point (tag viewer) HttpWatch
Observe Point (tag viewer) Charles
HttpFox
Chrome Developer Tools
Fiddler
Tamper Data
Firebug Lite
Wireshark
HttpWatch
Firebug
Note: Adobe does NOT support or troubleshoot any issues you may experience with these packet monitors.
Consult the packet monitor's originating site for assistance instead.
NS_Binding_Aborted in Packet Monitors
The NS_BINDING_ABORTED message is often seen on custom link tracking image requests with packet sniffers
that sit on top of the browser, such as Tamper Data or HTTPFox .
This error occurs because the link tracking image request is designed to let the browser proceed to the next page
before waiting for a response from the Adobe data collection servers.
Adobe's response to the image request is simply a blank 1x1 transparent image, which is not relevant to the content
of the page. If you see a line item in your packet monitor from Adobe, either with a 200 OK response or an
NS_BINDING_ABORTED response, the data has reached our servers. There is no need to have the page wait any
longer.
Packet monitors integrated as a plug-in rarely see the full response.They tend to see the request as aborted because
the full response was not received. These monitors also rarely make a distinction between whether it was the request
or response that was aborted. A stand alone packet monitor typically has more detailed messages and reports the
status more accurately. For example, a user may get a message in Charles saying &quot;Client closed connection before
receiving entire response.&quot; This means the data did reach our servers, just the browser moved on to the next page
before the 1x1 pixel was received.
If an external packet sniffer is reporting that the data collection request is aborted, rather than the response, this is
a cause for concern. Adobe ClientCare can provide help in troubleshooting.
Common Syntax Mistakes
A successful implementation means drawing useful data from your website. An unsuccessful implementation can
mean spending time looking through your JavaScript code to find errors. In an attempt to save you time and prevent
frustration, some of the most common code mistakes users make when implementing are listed in the following
sections.
Putting Analytics Code in the Head Tag
Analytics code creates an image object, a non-visible image that does not show up on your page.
Note: This section applies only to the legacy s_code.js implementation. About AppMeasurement for JavaScript
supports deploying the library and page code in the &lt;head&gt; tag.
Testing and Validation
162
Previously, a common implementation practice was to place the Analytics JavaScript code between the &lt;head&gt; and
&lt;/head&gt; tags. By placing the code between these tags it prevented the 1&times;1 pixel image that was returned by the
request that sent data into Adobe servers from affecting page layout in any way. Putting code in the document head
means the code appears earlier in the code. This lets it execute sooner, which lets you count page views for partial
page loads more effectively.
Certain elements of the code require the existence of the body object. Since Web browsers execute code in the
order they receive it, if the Analytics JavaScript code is in the document head, it executes before the body object
exists. As a result, your implementation does not collect ClickMap data, and automatic tracking of file downloads
or exit links are not available. You also do not receive connection type data or visitor home page data. Putting the
code in the document head works, but the result is a very limited version of Analytics, and users may wonder why
certain reports and tools, including ClickMap, aren't recording data.
The Analytics code can be placed anywhere inside BODY tags ( &lt;BODY&gt;&lt;/BODY&gt;) of a well-formed HTML page.
Adobe recommends placing the code in a global include file at the top of the page (inside the HTML body tag). The
code can be placed anywhere on the page, except as noted below:
• If placed within a table, post the code only within the &lt;td&gt;&lt;/td&gt; tags. For example, do not place the code between
an opening &lt;tr&gt; tag and an opening &lt;td&gt; tag.
• The code that sets the variables must occur after the reference to the s_code.js file.
• Make certain that the report suite IDs in the s_account variable in the s_code.js file are set correctly. This
variable is typically set correctly when downloading code from the Code Manager for a particular report suite, or
as supplied by an Adobe Technical Consultant.
If you want to integrate Analytics with Target, the JavaScript include file must be placed at the bottom of the page.
The following example shows correct placement of the Analytics code:
&lt;html&gt;
&lt;head&gt;&lt;/head&gt;
&lt;body&gt;
&lt;!-- SiteCatalyst code version: H.20.3.
Copyright 1997-2009 Omniture, Inc. More info available at
http://www.omniture.com --&gt;
&lt;script language=&quot;JavaScript&quot; type=&quot;text/javascript&quot;
src=&quot;http://www.yourdomain.com/js/s_code.js&quot;&gt;&lt;/script&gt;
&lt;script language=&quot;JavaScript&quot; type=&quot;text/javascript&quot;&gt;&lt;!-/* You may give each page an identifying name, server, and channel on
the next lines. */
s.pageName=&quot;&quot;
s.server=&quot;&quot;
s.channel=&quot;&quot;
s.pageType=&quot;&quot;
s.prop1=&quot;&quot;
s.prop2=&quot;&quot;
s.prop3=&quot;&quot;
s.prop4=&quot;&quot;
s.prop5=&quot;&quot;
/* Conversion Variables */
s.campaign=&quot;&quot;
s.state=&quot;&quot;
s.zip=&quot;&quot;
s.events=&quot;&quot;
s.products=&quot;&quot;
s.purchaseID=&quot;&quot;
s.eVar1=&quot;&quot;
s.eVar2=&quot;&quot;
s.eVar3=&quot;&quot;
s.eVar4=&quot;&quot;
s.eVar5=&quot;&quot;
/************* DO NOT ALTER ANYTHING BELOW THIS LINE ! **************/
var s_code=s.t();if(s_code)document.write(s_code)//--&gt;&lt;/script&gt;
&lt;!-- End SiteCatalyst code version: H.20.3. --&gt;
Testing and Validation
163
&lt;/body&gt;
&lt;/html&gt;
Using s.linkTrackVars and s.linkTrackEvents
The key to a successful link tracking implementation is understanding the s.linkTrackVars and s.linkTrackEvents
variables. This lets you pass custom variable values on user actions.
If you are implementing custom link tracking and are setting custom variables and events, make sure that your
s.linkTrackVars variable contains a comma-separated list of all variables that you are passing, including the events
variable. Make sure that s.linkTrackEvents includes a comma-separated list of all events that you are passing.
Setting s.linkTrackVars and s.linkTrackEvents does not actually set these variables/events, it only prepares the
Analytics code to do so. You still need to set the variables manually, as shown in the example below:
&lt;script language=&quot;javascript&quot;&gt;
function customLinks () {
var s=s_gi('myreportsuite');
s.linkTrackVars=&quot;prop1,eVar7,products,events&quot;;
s.linkTrackEvents=&quot;event5,event9&quot;;
s.prop1=&quot;Link Click&quot;;
s.eVar7=&quot;my_page.html&quot;;
s.events=&quot;event5&quot;;
s.tl(true,'o','Custom Link Click');
}
&lt;/script&gt;
&lt;a href=&quot;my_page.html&quot; onclick=&quot;customLinks();&quot;&gt;My Page&lt;/a&gt;
Notice that events is listed in the s.linkTrackVars variable. The individual events that may be passed are included
in the s.linkTrackEvents variable and are also included within s.events later in the function. Each of the variables
that are passed are listed in s.linkTrackVars before they are populated later in the function. Also, &quot;event9 has been
included in s.linkTrackEvents, but has not been included in s.events. It is not recorded, but could be recorded if
the user had chosen to set s.events=&quot;event5,event9.&quot;
Automatic file download and Exit link tracking work differently. The s.linkTrackVars and s.linkTrackEvents are
included in the standard s_code.js file, and both are set to none. These variables are typically left set to none in
the s_code.js file so that automatic link tracking, unlike custom link tracking, uses the s.linkTrackVars and
s.linkTrackEvents values that you set in the global JavaScript file. They also pass whatever the existing values of
those variables are whenever a file download or Exit link is recorded.
Consider the example where s.channel=&quot;Home&quot; when the page loads, and where s.linkTrackVars=&quot;channel&quot; in your
s_code.js file. If a user clicks to download a file, automatic file download tracking passes data into Analytics,
including the value of s.channel that was set on page load. &quot;Home&quot; is passed a second time, leading to inflation in
page view data for this value in the Site Sections report.
Adobe strongly recommends leaving the s.linkTrackVars and s.linkTrackEvents set to &quot;none&quot; in the global
JavaScript file and setting them explicitly as necessary with your custom link tracking implementation.
Common Mistakes in the Products Variable
The s.products variable may be the most syntactically complex variable used by data collection.
Commas, semi-colons, pipes, and equals signs all play specific roles in the variable. It has no overall maximum
length, but each individual product entry cannot be longer than 100 bytes (including multi-byte characters). Mistakes
in implementation of this variable are understandable, but unfortunately for developers, s.products is often a site's
most important variable because it makes possible the tracking of revenue, units, product names, and so forth.
Here are a few extremely easy-to-make mistakes that can cause issues on any implementation.
Testing and Validation
164
Make sure that your category, product name, and revenue totals are devoid of commas and semi-colons. The
comma is used to separate entries in the s.products string. This happens when you have two products in the same
transaction, the semi-colon is used to delimit fields within an entry. If you use a comma or semi-colon in any other
way, data collection assumes that you are separating product entries. Consider the following example:
s.products=&quot;widgets;large widget, 40 x40 ;1;19.99,wugs;tiny wug;2;1,999.98&quot;;
In this implementation, the developer probably intended for data collection to read this as shown below:
Category 1: widgets
Product 1: large widget, 40 x40
Units 1: 1
Revenue 1: 19.99
Category 2: wugs
Product 2: tiny wug
Units 2: 2
Revenue 2: 1,999.98
Note the commas in the Product 1 and Revenue 2 entries. These indicate a new product entry. Data collection would
interpret the above as:
Category 1: widgets
Product 1: large widget
Category 2: 40'x40'
Product 2: 1
Units 2: 19.99
Category 3: wugs
Product 3: tiny wug
Units 3: 2
Revenue 3: 1
Category 4: 999.98
A mistake like this often results in unexpected numerical values in the Products report, because the units field is
recorded as the product name. If you see invalid product names in your Products report, review your s.products
variable implementation for misuse of reserved characters, like the comma.
Your product and category names should not contain unsupported characters. This can be especially difficult in the
s.products string, because product names are often likely to contain characters such as ™, &copy;, and &reg;. These
characters need to be stripped out of the product and category values before they are placed into s.products. You
also need to ensure that currency symbols are not included in your revenue values. Supported characters are
numbers 1-127 from the ASCII table.
If you are not passing a product category in the product string, make sure to include a semi-colon (;) where the
product category is normally displayed, as shown below:
s.products=&quot;;product name&quot;
Testing and Validation
165
In this case, the semi-colon represents a placeholder for the product category. If the semi-colon is left out of the
product string, then &quot;product name&quot; would be counted as the category, the number of units to be counted as the
product name, the revenue to be counted as the units, and so on.
Setting the PageType Variable Correctly
The pageType variable is used only to designate a 404 (Page Not Found) error page.
It has only one possible value, which is errorPage.
pageType=&quot;errorPage&quot;
On a 404 error page, the pageName variable should not be populated. The pageType variable should be set only
on a designated 404 error page. Any page containing content should never have a value in the pageType variable.
For pages containing content, you can set the variable as shown below:
pageType=&quot;&quot;
It is best to delete the variable completely from pages containing content. This practice is recommended to avoid
confusion regarding the purpose of the variable.
Using White Space in Variable Values
In HTML there are several characters that create whitespace.
These include a space, a tab, and a carriage return (or linefeed). Consider the following example:
&lt;head&gt;
&lt;title&gt;
Home Page
&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
&lt;script language=&quot;javascript&quot;&gt;
s.pageName=document.title
&lt;/script&gt;
In this case, document.title populates s.pageName, which should receive a value of &quot;Home Page.&quot; Notice the space
before &quot;Home Page.&quot; Not all browsers interpret this white space in the same way. The result may be either of two
examples below:
s.pageName=&quot;Home Page&quot;
s.pageName=&quot;
Home Page&quot;
The first value displays correctly, but the second displays white space before the text. Analytics treats these as
distinct values for the s.pageName variable. The Analytics interface strips the leading white space from the second
value. The result is a report that displays as shown below.
This implementation error causes your variable values to be fragmented across multiple line items. SAINT does not
allow leading white space in a key value. This means that it cannot be used to group multiple line items as a
Testing and Validation
166
work-around if this issue is affecting your site. The only way to fix the problem is to pre-process the desired variable
value (in this case, the document.title property) to remove any leading (or trailing) white space.
The example above uses the s.pageName variable with the document.title property. Adobe does not recommend
using document.title as the page name, nor does this issue only affect the s.pageName variable. Any variable that
has leading/trailing white space in its value can be affected.
Using Quotes
When you input values into a variable, there are a few best practices to follow.
You can use single quotes or double quotes, make sure you are consistent. If you are using single quotes, always
use single quotes. If you are using double quotes, always use double quotes. Both of the examples below are correct.
s.prop2='test' (single quotes)
s.prop2=&quot;test&quot; (double quotes)
Make sure that you have smart quotes turned off. If you are using single quotes, and you have an apostrophe in the
variable value, JavaScript interprets the apostrophe as a single quote. This means it is the end of the string. Consider
the following example:
s.pageName='John's Home Page'
In this case, JavaScript would interpret the apostrophe (which is also a single quote) in &quot;John's&quot; to be the end of the
string. Since ''s Home Page&quot; has no meaning in JavaScript, it causes an error that prevents the image request from
occurring. Either of the following examples would work:
s.pageName='John\'s Home Page'
s.pageName=&quot;John's Home Page&quot;
In the first example, you can escape the apostrophe by inserting a backslash (\) immediately before it. This tells
JavaScript that the apostrophe is not ending the string, but rather is part of it. The string then ends as intended, at
the closing single-quote.The second example uses double-quotes around the entire string. In this case, a single-quote
cannot indicate the end of the string. The same is true if a double-quote is part of the string. A value of
s.pageName=&quot;Team Says &quot;We Win!&quot;&quot; would be incorrect because of the use of double-quotes within the string, as
well as surrounding it. This would be correct if entered as s.pageName=&quot;Team Says \&quot;We Win!\&quot;&quot;.
Replacing Your Analytics Code
Adobe offers some best practices for updating your Analytics code.
Frequently, customers use the Adobe Code Manager to replace their code with the most recent version. This practice
is good to follow as long as you keep certain things in mind.
Using the Incorrect Data Collection Server ID
Occasionally, generic s_code.js files that have not been generated from Adobe Code Manager are sent to those
implementing the code on your site. As a result, the incorrect data collection server ID (as shown in the s.dc variable)
for the account is used. It is best to generate new code directly from the Code Manager for a specific report suite,
rather than reusing code from a different report suite. This is the best way to make sure the s.dc variable is populated
correctly.
Testing and Validation
167
Plug-ins
Some customers implement plug-ins to enhance their Adobe experience. When you replace your code, do not forget
that you have plug-ins as part of that code. The code created in the Code Manager does not have any plug-in code
with it, so all plug-ins need to migrate manually to the newer code base. Make a copy of your existing code just in
case something happens, and you need to revert to your previous code.
Table of Common Syntax Mistakes
The following table shows the difference between correct and incorrect code mistakes.
Incorrect
Correct
prop1
s.prop1 (uses &quot;s.&quot;)
s.evar1
s.eVar1 (uses correct capitalization)
s.pagetype='errorpage';
s.pageType='errorPage'; (uses correct capitalization)
s.tl(this,o,pageA)
s.tl(this,'o','pageA'); (correct usage of single quotes)
s.events='event1'; s.events='event2';
s.events='event1,event2'; (correct format)
s.pageName=&quot;John&quot; (smart quotes on)
s.pageName=&quot;John&quot; (smart quotes off)
s.products=&quot;shoes,UX4879,1,19.99&quot;
s.products=&quot;shoes;UX4879;1;19.99&quot; (uses semicolons,
not commas)
s.products=&quot;;MacBook Air;1;$1999.99&quot;
s.products=&quot;;MacBook Air;1;1999.99&quot; (does not use dollar
signs)
s.products=&quot;;Nikon SB-600 Speedlight Flash for Nikon
Digital SLR Cameras;1;229.9489183&quot;
s.products=&quot;;Nikon SB-600 Speedlight Flash for Nikon
Digital SLR Cameras;1;229.95&quot; (round or truncate long
prices)
var s_account=&quot;rsid1, rsid2&quot;
var s_account=&quot;rsid1,rsid2&quot; (no space between report
suite IDs when doing multi-suite tagging)
s.events=&quot;event1, event2&quot;
s.events=&quot;event1,event2&quot; (no space between event IDs
when doing multi-event tagging)
s.products=&quot;product name&quot;
s.products=&quot;;product name&quot; (semicolon used when no
product category is listed)
Additional Notes
Keep the closing HTML comment at the very end of the Adobe code (even if you are using the NOSCRIPT part of
the script).
Vulnerability Scanner
Whenever users are allowed to input values that are stored in Analytics or any other JavaScript variables, values
should be properly escaped or URIEncoded.
We highly recommend using a vulnerability scanning service to avoid injection attacks and other potential exploits
that might be present in your code.
Testing and Validation
168
Optimizing your Implementation
Analytics deployment is organized into three major steps.
1. This involves pasting a snippet of HTML code onto each page (or page template) of a website. The HTML code
snippet is very small (400 to 1,000 bytes) and contains JavaScript variables and other identifiers that facilitate
the data collection process.
2. The code snippet calls a JavaScript library file, which contains JavaScript functions specific to Analytics used
during metrics collection. If the Analytics code is implemented correctly, the time required for the browser to
execute the JavaScript library file is usually negligible.
3. The library file makes an image request to an Adobe data collection server. The server collects the data being
submitted and returns a 1x1 transparent image to the visitor's browser. This third step adds an insignificant
increment to the total page download time.
Note: Customers can take additional steps to minimize Analytics overhead.
Page Naming
The pageName variable is used to identify each page that is tracked on the website.
If the pageName variable is not populated with a defined value (such as Home), Analytics uses the URL of the page.
Because the page name is central to your reports, make sure that all parties in your organization agree on a strategy
before you implement.
Depending on the content management system your site uses, it is helpful to add content elements to your system
that can be used to populate Analytics variables. Many companies find that most Analytics variables can be populated
from existing content management elements.
Page Naming Strategies
The pageName variable should be populated with an easy-to-read, intuitive, page identifier.
You can determine the best way of populating the pageName variable by looking at the structure of your website.
The methods listed below outline various ways of populating the pageName variable.
While the pageName variable is central to identifying user behavior, Adobe recommends using multiple variables
to indicate page information. The best page naming strategies use a different variable for each level of hierarchy
within your site, as shown below:
• The channel variable can be used to indicate the site section.
• The pageName variable can be used to show content type.
• A custom insight variable (prop1) can be used for detailed content.
Levels of detail vary, depending on property, as shown below:
Variable
Level of Detail
Example
Channel
General Section
Electronics
Prop1
Sub Section
Sports : Local Sports
PageName
General Content Description
Loans : Home Mortgage : Rate Comparison
Testing and Validation
169
Variable
Level of Detail
Example
Prop2
Detailed Content Description
Electronics : Notebook PC : Detailed Specs : IBM
Thinkpad T20
The more layered your site, the more variables should be used to identify page content. Companies also find value
in allowing for overlap between variables. For example, a more detailed variable may contain information not only
about the product being viewed, but also about the site section and sub-section. This is particularly helpful when a
product or article appears in more than one section of the site.
The following page naming strategies describe how to populate the pageName variable. While it is tempting to
choose the page naming strategy that is easiest to implement, the page naming strategy largely determines the
usability of all Path and Page reports. Use good judgment when deciding how pages are named.
Unique Name for Each Page
The most valuable method of naming pages is to give each page a unique identifier that is easily understood by all
Analytics users in your organization. Examples of page names include Home Page, Electronics Department Home,
and Sports : Local Sports : High School.
Most Analytics users find that hierarchical page names are useful in both identifying where the page is found on the
site and its purpose. The following table shows some sample page names for various industries:
Conversion
Media
Finance
Home Page
Home Page
Home Page
Electronics
Technology
Home Loans
Electronics : Notebook PCs
Technology : New Gadgets
Home Loans : Rate Compare
Electronics : Notebook PCs : Product Technology : New Gadgets : Article
Page
Page
Home Loans : Rate Compare : 10
Year Fixed
File Path (Not the Full URL)
For some sites, the file path is clear and easily read. Any business user can read a URL and determine the page to
which the file path refers. If this is the case for your site, you can use a server-side variable to populate the path to
the file into the pageName variable, as shown below:
s.pageName=&quot;&lt;%= file_path %&gt;&quot;
Adobe does not recommend leaving the pageName blank, (which results in using the full URL of the page) even
though you may be tempted to do so. The following side-effects are caused by leaving the pageName variable blank
and using the pageURL as the page identifier.
• The domain and path of a page may not always be displayed identically. For example, the following four URLs
return a single page:
• http://www.mysite.com/index.jsp
• http://www.mysite.com
• http://mysite.com/index.jsp
• http://mysite.com/
If the pageName is left blank, each of these page names would occupy a separate entry in reports.
• Some pages (such as forms) post to themselves, thereby erasing any distinction between the original form and
the resulting output.
Testing and Validation
170
• When your page is translated into another language by search engines or other online tools, the URL of the page
is the URL of the search engine (not the URL of your site).
HTML (document.title)
If you have invested time into making your HTML titles readable and intuitive, you might consider using the same
title as the value in the pageName variable. Adobe recommends using a server-side variable to populate the
pageName rather than using JavaScript's document.title. Some browsers interpret the HTML title differently
than others, which may cause Analytics to receive different page names from different browsers.
The best practice for using the HTML title is to copy the existing titles for each page into a separate variable or
content management element. When you decide to make changes to the HTML title for search engine optimization
or other purposes, the Analytics page names are not affected. If a page name changes in Analytics, it becomes a
new page and is not connected with the old page name, regardless of the associated URL.
Variable Length
The length of Analytics variables can impact the size of the HTML code snippet, JavaScript library file, and image
request.
If a customer has many variables that are long (60 characters or more) the values can be replaced with shorter
identifiers. Data classifications or VISTA rules can be used to translate the identifiers to friendly names.
Note: Most Analytics variables have a maximum of 100 characters (eVars have a maximum of 255). Internet
Explorer allows an overall maximum of 2,048 characters in a GET image request URL. The image request
limit applies not only to the variables, but also to information about the browser, operating system, and browser
plug-ins (Netscape/Mozilla only).
HTML Code Snippet
Many customers have variables declared, but no value is assigned to the variable.
Removing unused variables helps to reduce the page size.
Javascript Library File
The JavaScript library file is intended to be cached in the user's browser after the initial load, which limits the amount
of data that needs to be downloaded.
Page-specific variables should be placed in the HTML snippet. All other variables should be put in the JavaScript
library file.
Caching Directives
The JavaScript library file is intended to be cached in the user's browser after the first time the user loads a page.
Adobe customers should ensure that their Web servers are set up to take advantage of this functionality. For example,
make sure that the NO-CACHE setting is set to false. Additionally, ensure that the expiration date is sufficiently long.
Make sure any proxy caches are set up with the correct configuration. The customer's Web server documentation
provides more information.
Testing and Validation
171
Tables
Many Web browsers do not start displaying the contents of a table until the browser has compiled the entire table.
If the entire contents of the page are inside one big table, the browser must compile the entire contents of the page
before anything is displayed.
Placing the call to the JavaScript library file outside table tags ensures that the call to the Analytics servers does not
impact the displaying of the page content.
Note: The file should be placed in a legal position for images and must appear between the opening &lt;body&gt;
tag and the closing &lt;/body&gt; tag.
File Compression
Customers can compress the JavaScript library file by using standards-based encoding (such as gzip).
Typical compression algorithms can reduce the size of the JavaScript file by 40-60% or more.
Note: Not all browsers support all file compression standards or interpret the compressed files in the same
manner. Adobe does not guarantee reliable file compression in all environments. Customers should test
compression in their supported browsers and configurations before deploying.
Secure Pages
Secure pages (pages loaded under https://) encrypt the image request and add to the total download time.
Secure pages can add as much as 50-75% overhead to the image request. Customers should ensure that https is
used only where necessary.
Content Delivery Services/Networks
Content Delivery Services or Content Distribution Networks (CDNs) such as Akamai and Speedera push Web content
closer to the edge of the network, keeping frequently-requested documents close to the location where they are
accessed.
Typically, this reduces access latency, bandwidth usage, and infrastructure cost.
Your AppMeasurement for JavaScript library file can be delivered via a CDN to enhance performance and delivery
of the file to the site visitor. Adobe customers need to ensure they have configured their CDN services correctly.
CDNs are a common reason for fluctuations in download times and should be considered the most probable cause
for any changes in download times.
Tag manager stores all JavaScript on a CDN.
JavaScript File Location and Concurrency
Placing the call to the JavaScript library file at the top of the page ensures that the image is among the first elements
to be downloaded.
Most Web browsers download images concurrently. Typically three to four images can be downloaded simultaneously.
Testing and Validation
172
Because most Web browsers download elements concurrently, the Status Bar of many common browsers (including
Internet Explorer) does not accurately reflect which element the browser is trying to load. For example, your Status
Bar may report that your browser is waiting for image 1 to download. The network packet tests show your browser
has already received image 1 and is currently waiting for image 2.
Note: Because third-party Internet Performance Audit providers (such as Keynote Systems) download page
image elements sequentially, not concurrently, they do not mimic the typical user experience.
Peering
Private Network Peering enables data to pass from an ISP's network to the Analytics network more efficiently.
Peering is simply the agreement to interconnect and exchange routing information without the need of the public
network. Please contact Adobe Engineering if an ISP is interested in establishing a peering relationship.
Although peering may provide some benefits to Adobe ISP customers, optimizing the HTML snippet and the Web
servers caching directives likely have a much greater impact. High-volume ISP customers realize the most benefit
from peering.
Report to Variable Mapping
The tables below display the report to variable mapping, or the reports and the variables that are used in them.
Conversion Reports
The following table lists the conversion variables that are used to populate each report:
Purchases
Conversions and Averages
s.events, s.products, s.purchaseID
Set s.events to purchase, product
detail, order number
Revenue
s.events, s.products, s.purchaseID
Set s.events to purchase, product
detail, order number
Orders
s.events, s.products, s.purchaseID
Set s.events to purchase, product
detail, order number
Units
s.events, s.products, s.purchaseID
Set s.events to purchase, product
detail, order number
Shopping Cart
Conversions and Averages
s.events, s.products, s.purchaseID
Cart
s.events
Set s.events to scOpen
Cart Views
s.events
Set s.events to scView
Cart Additions
s.events
Set s.events to scAdd
Cart Removals
s.events
Set s.events to scRemove
Checkouts
s.events
Set s.events to scCheckout
Testing and Validation
173
Custom Events
Custom Event 1
s.events
Populate with event1 - event100
…
…
Populate with event1 - event100
Custom Event 100
s.events
Populate with event1 - event100
Products
Conversions and Averages
s.events, s.products, s.purchaseID
Products
s.products, s.events
May vary depending on right column
metrics
Cross Sell
s.products, s.events, s.purchaseID
May vary depending on right column
metrics
Categories
s.products
May vary depending on right column
metrics
Campaigns
Conversions and Averages
s.products, s.events, s.campaign
Tracking Code
s.campaign
Creative Elements
N/A
Defined in Analytics
Campaigns
N/A
Defined in Analytics
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Days Before First Purchase
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Days Since Last Purchase
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Visit Number
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Daily Unique Customers
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Monthly Unique Customers
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Yearly Unique Customers
s.products, s.events, s.purchaseID
Variables set on the Order
Confirmation (Thank You!) page
Referring Domains
N/A
Automatically set by the .JS file
Original Referring Domains
N/A
Automatically set by the .JS file
Customer Loyalty
Customer Loyalty
Sales Cycle
Finding Methods
Testing and Validation
174
Finding Methods
Search Engines
N/A
Automatically set by the .JS file
Search Keywords
N/A
Automatically set by the .JS file
Top Level Domains
N/A
Automatically set by the .JS file
Languages
N/A
Automatically set by the .JS file
Time Zones
N/A
Automatically set by the .JS file
States
s.state
Variable set on the Order
Confirmation (Thank You!) page
Zip/Postal Codes
s.zip
Variable set on the Order
Confirmation (Thank You!) page
Domains
N/A
Automatically set by the .JS file
Browsers
N/A
Automatically set by the .JS file
Operating Systems
N/A
Automatically set by the .JS file
Monitor Resolutions
N/A
Automatically set by the .JS file
Visitor Profile
Technology
Site Path
Page Value
s.pageName, s.products, s.events,
s.purchaseID
Entry Pages
s.pageName
Original Entry Pages
s.pageName
Pages Per Visit
N/A
Calculated by business rules in
Analytics
Time Spent on Site
N/A
Calculated by business rules in
Analytics
Site Sections
s.channel
Same as Channel report in Traffic
reports section
Customer Variables
Custom eVar 1
s.eVar 1
Custom eVar 2
s.eVar 2
Custom eVar 3
s.eVar 3
…
Custom eVar 75
s.eVar 75
Traffic Reports
The following table lists the traffic variables that are used to populate each report:
Testing and Validation
175
Calculated Metrics
N/A
N/A
N/A
Page Views
N/A
Calculated by business rules in
Analytics
Hourly Unique Visitors
N/A
Calculated by business rules in
Analytics
Daily Unique Visitors
N/A
Calculated by business rules in
Analytics
Monthly Unique Visitors
N/A
Calculated by business rules in
Analytics
Yearly Unique Visitors
N/A
Calculated by business rules in
Analytics
Visits
N/A
Calculated by business rules in
Analytics
File Downloads
N/A
Automatically tracked by .JS file
(depends on .JS variable settings)
Referring Domains
N/A
Automatically set by the .JS file
Referrers
N/A
Automatically set by the .JS file
Search Engines
N/A
Automatically set by the .JS file
Search Keywords
N/A
Automatically set by the .JS file
Return Frequency
N/A
Calculated by business rules in
Analytics
Daily Return Visits
N/A
Calculated by business rules in
Analytics
Return Visits
N/A
Calculated by business rules in
Analytics
Visit Numbers
N/A
Calculated by business rules in
Analytics
Domains
N/A
Automatically set by the .JS file
Top Level Domains
N/A
Automatically set by the .JS file
Languages
N/A
Automatically set by the .JS file
Time Zones
N/A
Automatically set by the .JS file
Visitor Details
N/A
Automatically set by the .JS file
Last 100 Visitors
N/A
Calculated by business rules in
Analytics
Site Traffic
Finding Methods
Visitor Profile
Testing and Validation
176
Visitor Profile
User Home Page
N/A
Automatically set by the .JS file
Key Visitors
N/A
Based on visitor's IP address
Pages Viewed by Key Visitors
N/A
Based on visitor's IP address
Countries
N/A
Based on visitor's IP address
U.S. States
N/A
Based on visitor's IP address
DMA
N/A
Based on visitor's IP address
International Cities
N/A
Based on visitor's IP address
U.S. Cities
N/A
Based on visitor's IP address
Browser Types
N/A
Automatically set by the .JS file
Browsers
N/A
Automatically set by the .JS file
Mobile Devices
N/A
Automatically set by the .JS file
Browser Width
N/A
Automatically set by the .JS file
Browser Height
N/A
Automatically set by the .JS file
Operating Systems
N/A
Automatically set by the .JS file
Monitor Color Depth
N/A
Automatically set by the .JS file
Monitor Resolutions
N/A
Automatically set by the .JS file
Netscape Plug-ins
N/A
Automatically set by the .JS file
Java
N/A
Automatically set by the .JS file
JavaScript
N/A
Automatically set by the .JS file
JavaScript Version
N/A
Automatically set by the .JS file
Cookies
N/A
Automatically set by the .JS file
Connection Types
N/A
Automatically set by the .JS file
Geo Segmentation
Technology
Segmentation
Segmentation
Most Popular Pages
s.pageName
Most Popular Site Sections
s.channel
Most Popular Servers
s.server
Custom Insight
Custom Links
s.linkName
Custom Insight 1
s.prop1
Requires custom implementation
Testing and Validation
177
Custom Insight
…
…
Custom Insight 75
s.prop75
Hierarchies
Hierarchy 1
s.hier1
…
…
Hierarchy 5
s.hier5
Pathing Reports
The following table lists the pathing variables that are used to populate each report within Analytics:
Pages
Page Summary
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Page Value
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Most Popular Pages
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Reloads
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Clicks to Page
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Time Spent on Page
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Pages Not Found
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Entry Pages
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Exit Pages
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Exit Links
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Full Paths
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Longest Paths
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Entries and Exits
Complete Paths
Testing and Validation
178
Complete Paths
Path Length
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Time Spent per Visit
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Single-page Visits
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Previous Page
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Next Page
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Previous Page Flow
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Next Page Flow
s.pageName (or other pathed
variable)
Also depends on internal business
rules
PathFinder
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Fall-out
s.pageName (or other pathed
variable)
Also depends on internal business
rules
Advanced Analysis
Variable to Report Mapping
The table below displays variable to report mapping for the variables used to populate Analytics reports.
Each variable is listed with the reports that use the variable listed next to it.
Variable
s.pageName
Reports Populated
Conversion Reports &gt; Path Reports &gt; Page Value
Conversion Reports &gt; Path Reports &gt; Entry Page
Conversion Reports &gt; Path Reports &gt; Original Entry Pages
Traffic Reports &gt; Site Traffic &gt; Page Views
Traffic Reports &gt; Site Traffic &gt; Hourly Unique Visitors
Traffic Reports &gt; Site Traffic &gt; Daily Unique Visitors
Traffic Reports &gt; Site Traffic &gt; Monthly Unique Visitors
Traffic Reports &gt; Site Traffic &gt; Yearly Unique Visitors
Traffic Reports &gt; Visitor Profile &gt; Pages Viewed by Key Visitors
Traffic Reports &gt; Segmentation &gt; Most Popular Pages
Path Reports &gt; Pages &gt; Page Summary
Testing and Validation
Variable
179
Reports Populated
Path Reports &gt; Pages &gt; Page Value
Path Reports &gt; Pages &gt; Most Popular Pages
Path Reports &gt; Pages &gt; Reloads
Path Reports &gt; Pages &gt; Click to Page
Path Reports &gt; Pages &gt; Time Spent on Page
Path Reports &gt; Entries &amp; Exits &gt; Entry Pages
Path Reports &gt; Entries &amp; Exits &gt; Exit Pages
Path Reports &gt; Entries &amp; Exits &gt; Exit Links
Path Reports &gt; Complete Paths &gt; Full Paths
Path Reports &gt; Complete Paths &gt; Longest Paths
Path Reports &gt; Complete Paths &gt; Path Length
Path Reports &gt; Complete Paths &gt; Time Spent per Visit
Path Reports &gt; Complete Paths &gt; Single-page Visits
Path Reports &gt; Advanced Analysis &gt; Previous Page
Path Reports &gt; Advanced Analysis &gt; Next Page
Path Reports &gt; Advanced Analysis &gt; Previous Page Flow
Path Reports &gt; Advanced Analysis &gt; Next Page Flow
Path Reports &gt; Advanced Analysis &gt; PathFinder
Path Reports &gt; Advanced Analysis &gt; Fall-out
NOTE: In all of the Traffic Reports listed above, with the exception of the
Most Popular Pages Report, if the s.pageName variable is not set, the URL
is used.
s.server
Traffic Reports &gt; Segmentation &gt; Most Popular Servers
s.pageType
Path Reports &gt; Pages &gt; Pages Not Found
s.channel
Conversion Reports &gt; Site Path Reports &gt; Site Section
Traffic Reports &gt; Segmentation &gt; Most Popular Site Sections
s.prop1 - s.prop20
s.campaign
Traffic Reports &gt; Custom Insight &gt; Custom Insight 1-20
Conversion Reports &gt; Campaigns &gt; Conversion &amp; Averages
Conversion Reports &gt; Campaigns &gt; Tracking Code
s.state
Conversion Reports &gt; Visitor Profile &gt; States
s.zip
Conversion Reports &gt; Visitor Profile &gt; ZIP/ Postal Codes
Testing and Validation
Variable
s.events
180
Reports Populated
Conversion Reports &gt; Purchases &gt; Conversion &amp; Averages
Conversion Reports &gt; Purchases &gt; Revenue
Conversion Reports &gt; Purchases &gt; Orders
Conversion Reports &gt; Purchases &gt; Units
Conversion Reports &gt; Shopping Cart &gt; Conversion &amp; Averages
Conversion Reports &gt; Shopping Cart &gt; Carts
Conversion Reports &gt; Shopping Cart &gt; Cart Views
Conversion Reports &gt; Shopping Cart &gt; Cart Additions
Conversion Reports &gt; Shopping Cart &gt; Cart Removals
Conversion Reports &gt; Shopping Cart &gt; Checkouts
Conversion Reports &gt; Custom Events &gt; Custom Event 1-20
Conversion Reports &gt; Products &gt; Conversion &amp; Averages
Conversion Reports &gt; Products &gt; Cross Sell
Conversion Reports &gt; Products &gt; Categories
Conversion Reports &gt; Campaigns &gt; Conversion &amp; Averages
Conversion Reports &gt; Customer Loyalty &gt; Customer Loyalty
Conversion Reports &gt; Sales Cycle &gt; Days Before First Purchase
Conversion Reports &gt; Sales Cycle &gt; Days Since Last Purchase
Conversion Reports &gt; Sales Cycle &gt; Visit Number
Conversion Reports &gt; Sales Cycle &gt; Daily Unique Customers
Conversion Reports &gt; Sales Cycle &gt; Monthly Unique Customers
Conversion Reports &gt; Sales Cycle &gt; Yearly Unique Customers
Conversion Reports &gt; Site Path &gt; Page Value
s.products
Conversion Reports &gt; Purchases &gt; Conversion &amp; Averages
Conversion Reports &gt; Purchases &gt; Revenue
Conversion Reports &gt; Purchases &gt; Orders
Conversion Reports &gt; Purchases &gt; Units
Conversion Reports &gt; Shopping Cart &gt; Conversion &amp; Averages
Conversion Reports &gt; Products &gt; Conversion &amp; Averages
Conversion Reports &gt; Products &gt; Cross Sell
Conversion Reports &gt; Products &gt; Categories
Testing and Validation
Variable
181
Reports Populated
Conversion Reports &gt; Campaigns &gt; Conversion &amp; Averages
Conversion Reports &gt; Customer Loyalty &gt; Customer Loyalty
Conversion Reports &gt; Sales Cycle &gt; Days Before First Purchase
Conversion Reports &gt; Sales Cycle &gt; Days Since Last Purchase
Conversion Reports &gt; Sales Cycle &gt; Visit Number
Conversion Reports &gt; Sales Cycle &gt; Daily Unique Customers
Conversion Reports &gt; Sales Cycle &gt; Monthly Unique Customers
Conversion Reports &gt; Sales Cycle &gt; Yearly Unique Customers
Conversion Reports &gt; Site Path &gt; Page Value
s.purchaseID
Conversion Reports &gt; Purchases &gt; Conversion &amp; Averages
Conversion Reports &gt; Purchases &gt; Revenue
Conversion Reports &gt; Purchases &gt; Orders
Conversion Reports &gt; Purchases &gt; Units
Conversion Reports &gt; Shopping Cart &gt; Conversion &amp; Averages
Conversion Reports &gt; Products &gt; Conversion &amp; Averages
Conversion Reports &gt; Products &gt; Cross Sell
Conversion Reports &gt; Customer Loyalty &gt; Customer Loyalty
Conversion Reports &gt; Sales Cycle &gt; Days Before First Purchase
Conversion Reports &gt; Sales Cycle &gt; Days Since Last Purchase
Conversion Reports &gt; Sales Cycle &gt; Visit Number
Conversion Reports &gt; Sales Cycle &gt; Daily Unique Customers
Conversion Reports &gt; Sales Cycle &gt; Monthly Unique Customers
Conversion Reports &gt; Sales Cycle &gt; Yearly Unique Customers
Conversion Reports &gt; Site Path &gt; Page Value
s.eVar1 - s.eVar20
Conversion Reports &gt; Custom Variables &gt; Customer eVar 1-20
s.linkName
Traffic Reports &gt; Custom Insight &gt; Custom Links
s.hier1 - s.hier5
Traffic Reports &gt; Hierarchies &gt; Hierarchy 1-5
Implementation Plug-ins
182
Implementation Plug-ins
AppMeasurement for JavaScript plug-ins are programs or functions that perform several advanced functions.
These plug-ins extend the capabilities of your JavaScript file to give you more functionality that is not available with
a basic implementation. Adobe offers a number of other plug-ins as part of advanced solutions. Contact your Account
Manager if you want to capture data using JavaScript but are unsure how to proceed.
Calling Plug-ins with doPlugins Function
JavaScript plug-ins are usually called by the doPlugins function, which is executed when the t() function is called in
the Code to Paste.
Consequently, if you set a variable in the doPlugins function, you can overwrite a variable you set on the HTML
page. The only time the doPlugins function is not called is when the usePlugins variable is set to 'false.'
Code Example
The code example below is what the doPlugins function looks like in your JavaScript file:
AppMeasurement for JavaScript:
/* Plugin Config */
s.usePlugins=true
s.doPlugins=function(s) {
/* Add calls to plugins here */
}
H code:
/* Plugin Config */
s.usePlugins=true
function s_doPlugins(s) {
/* Add calls to plugins here */
}
s.doPlugins=s_doPlugins
Note: H code and earlier versions use a different syntax to support some very old browsers (such as IE 4
and 5).
Renaming the doPlugins Function
The doPlugins function is typically called s_doPlugins. In certain circumstances, (usually when more than one version
of code may appear on a single page) the doPlugins function name may be changed. If the standard doPlugins
function needs to be renamed to avoid conflicts, ensure that doPlugins is assigned the correct function name, as
shown in the example below.
/* Plugin Config */
s_mc.usePlugins=true
function s_mc_doPlugins(s_mc) {
/* Add calls to plugins here */
}
s_mc.doPlugins=s_mc_doPlugins
Using doPlugins
The doPlugins function provides an easy way to give default values to variables or to take values from query string
parameters on any page of the site. Using doPlugins is often easier than populating the values in the HTML page
Implementation Plug-ins
183
because only one file must be updated. Keep in mind that changes to the JavaScript file are not always immediate.
Return visitors to your site are often using cached versions of the JavaScript file. This means that updates to the
file may not be applied to all visitors for up to one month after the change is made.
The following example shows how the doPlugins function can be used to set a default value for a variable and to
get a value from the query string.
/* Plugin Config */
s.usePlugins=true
s.doPlugins=function(s) {
/* Add calls to plugins here */
// if prop1 doesn't have a value, set it to &quot;Default Value&quot;
if(!s.prop1)
s.prop1=&quot;Default Value&quot;
// if campaign doesn't have a value, get cid from the query string
if(!s.campaign)
s.campaign=s.getQueryParam('cid');
// Note: The code to read query parameters is different for
// Appmeasurement for JavaScript since a plug-in is not required:
// s.campaign=s.Util.getQueryParam('cid');
}
Installed Plug-ins
To find out whether a plug-in is included in your JavaScript file and ready for use, look in the Plugins Section of
the JavaScript file. The following example shows the getQueryParam function.
/************************** PLUGINS SECTION *************************/
/* You may insert any plugins you wish to use here.
*/
/*
* Plugin: getQueryParam 1.3 - Return query string parameter values
*/
s.getQueryParam=new Function(&quot;qp&quot;,&quot;d&quot;,&quot;&quot;
+&quot;var s=this,v='',i,t;d=d?d:'';while(qp){i=qp.indexOf(',');i=i&lt;0?qp.l&quot;
//
// ... more code below ...
//
s.abort flag
The abort flag can be set inside doPlugins to cause the current track call to not be sent.
The abort flag is reset with every tracking call, so if a subsequent tracking call also needs to be aborted the flag will
need to be set again inside doPlugins.
s.doPlugins = function(s) {
s.campaign = s.getQueryParam(&quot;cid&quot;);
if ((!s.campaign) &amp;&amp; (!s.events)) {
s.abort = true;
}
};
This lets you centralize the logic you use to identify activity that you do not want to track, such as some custom links
or external links in display ads.
Implementation Plug-ins
184
appendList
The apl (or appendList) plug-in lets you append a value to any delimited lists, with the option of a case-sensitive or
case-insensitive check to ensure that the value does not already exist in the list. The APL plug-in is referenced by
several standard plug-ins but can be used directly in a variety of situations.
This plug-in is useful for:
• Adding an event to the current events variable
• Adding a value to a list variable without duplicating a value in the list
• Adding a product to the current products variable based on some page logic
• Adding values to the parameters linkTrackVars and linkTrackEvents
Use Case 1
Scenario
Add event1 to the current events variable while ensuring
the event isn't duplicated.
s.events=&quot;scCheckout&quot;
Code
s.events=s.apl(s.events,&quot;event1&quot;,&quot;,&quot;,1)
Results
s.events=&quot;scCheckout,event1&quot;
Use Case 2
Scenario
Add the value history to the list variable prop1, with history
and History considered the same value.
s.prop1=&quot;Science,History&quot;
Code
s.prop1=s.apl(s.prop1,&quot;history&quot;,&quot;,&quot;,2)
Results
s.prop1=&quot;Science,History&quot;
history is not added because History is already in the list.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Implementation
Follow these steps to implement the APL plug-in.
1. Request the plug-in code from ClientCare or your currently assigned Adobe consultant.
2. Add call(s) to the API function as needed within the s_doPlugins function
Implementation Plug-ins
185
Here is how the code might look on your site:
/* Plugin Config */
s.usePlugins=true
function s_doPlugins(s) {
/* Add calls to plugins here */
s.events=s.apl(s.events,&quot;event1&quot;,&quot;,&quot;,1)
}
s.doPlugins=s_doPlugins
Supported Browsers
This plug-in requires that the browser supports JavaScript version 1.0.
Plug-in Information
Plug-in Information
Description
Parameters
apl((L,v,d,u)
L= source list, empty list is accepted
v = value to append
d = list delimiter
u (optional, defaults to 0) Unique value check. 0=no
unique check, value is always appended.
1=case-insensitive check, append only if value isn't in
list. 2=case-sensitive check, append only if value isn't in
list.
Return Value
original list, with appended value if added
Usage Examples
s.events=s.apl(s.events,&quot;event1&quot;,&quot;,&quot;,1);
The source list L can be an empty list, such as L=&quot;&quot;. The returned value will either be an empty list, or a list of one
value.
Plug-in Code
/********************************************************************
*
* Main Plug-in code (should be in Plug-ins section)
*
*******************************************************************/
/*
* Plugin Utility: apl v1.1
*/
s.apl=new Function(&quot;l&quot;,&quot;v&quot;,&quot;d&quot;,&quot;u&quot;,&quot;&quot;
+&quot;var s=this,m=0;if(!l)l='';if(u){var i,n,a=s.split(l,d);for(i=0;i&lt;a.&quot;
+&quot;length;i++){n=a[i];m=m||(u==1?(n==v):(n.toLowerCase()==v.toLowerCas&quot;
+&quot;e()));}}if(!m)l=l?l+d+v:v;return l&quot;);
/********************************************************************
*
Implementation Plug-ins
186
* Commented example of how to use this is doPlugins function
*
*******************************************************************/
Not Applicable - Utility function only
/********************************************************************
*
* Config variables (should be above doPlugins section)
*
*******************************************************************/
None
/********************************************************************
*
* Utility functions that may be shared between plug-ins (name only)
*
*******************************************************************/
s.split
doPlugins Function
JavaScript plug-ins are usually called by the doPlugins function, which is executed when the t() function is called
in the Code to Paste.
Consequently, if you set a variable in the doPlugins function, you may overwrite a variable you set on the HTML
page. The only time the doPlugins function is not called is when the usePlugins variable is set to false.
Code Example
The doPlugins function is typically called s_doPlugins. However, in certain circumstances (usually when more
than one version of Analytics code may appear on a single page), you can change the doPlugins function name.
If the standard doPlugins function needs to be renamed to avoid conflicts, assign doPlugins the correct function
name, as shown in the example below.
/* Plugin Config */
s_mc.usePlugins=true
function s_mc_doPlugins(s_mc) {
/* Add calls to plugins here */
}
s_mc.doPlugins=s_mc_doPlugins
Using doPlugins
This function provides an easy way to give default values to variables, or to take values from query string parameters
on any page of the site. Using doPlugins can be easier than populating the values in the HTML page, because only
one file must be updated. Changes to the JavaScript file are not always immediate. Return visitors to your site are
often using cached versions of the JavaScript file. Meaning, updates to the file may not be applied to all visitors for
up to one month after the change is made.
The following examples show how you can use the doPlugins function to set a default value for a variable and to
get a value from the query string.
/* Plugin Config */
s.usePlugins=true
function s_doPlugins(s) {
/* Add calls to plugins here */
// if prop1 doesn't have a value, set it to &quot;Default Value&quot;
if(!s.prop1)
Implementation Plug-ins
187
s.prop1=&quot;Default Value&quot;
// if campaign doesn't have a value, get cid from the query string
if(!s.campaign)
s.campaign=getQueryParam('cid');
}
s.doPlugins=s_doPlugins
Installed Plug-ins
To find out whether a plugin is included in your JavaScript file and ready for use, look in the Plugins Section of the
JavaScript file. The following example shows what the getQueryParam function looks like in the Plugins Section.
/************************** PLUGINS SECTION *************************/
/* You may insert any plugins you wish to use here. */
/*
* Plugin: getQueryParam 1.3 - Return query string parameter values
*/
s.getQueryParam=new Function(&quot;qp&quot;,&quot;d&quot;,&quot;&quot;
+&quot;vars=this,v='',i,t;d=d?d:'';while(qp){i=qp.indexOf(',');i=i&lt;0?qp.l&quot;
//
// ... more code below ...
//
getAndPersistValue
The getAndPersistValue plug-in obtains a value of your choosing and populates it into a Analytics variable for a
determined period. A common use is to see how many page views a campaign generates after a click-through,
which enables you to easily see the most common pages for each campaign.
Important: This plug-in has not been validated to be compatible with AppMeasurement for JavaScript. See
AppMeasurement Plug-in Support.
For example, you might use this plug-in to set a campaign tracking code from the campaign variable into a Custom
Traffic (s.prop) variable on each visitor's page view made for the next 30 days. This example lets you determine
how many page views the tracking code generated as a result of the original click-through.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Plug-in Code and Implementation
CONFIG SECTION: No changes required for this section.
Plug-in Configuration
Place the following code within the s_doPlugins() function, which is located in the area of the s_code.js file labeled
Plugin Config. Choose one Custom Traffic (s.prop) variable or one Custom Conversion (s.eVar) variable for use in
capturing persisted value data. This should be a variable that has been enabled using the Admin Console, but which
is not currently in use for any other purpose. You can use the following example and update it based on your
requirements.
s.prop1=s.getAndPersistValue(s.campaign,'s_getval',30);
s.getAndPersistValue has three arguments:
Implementation Plug-ins
188
1. Currently populated variable or value to persist (s.campaign shown above).
2. Cookie name, used to store the value (s_getval shown above).
3. Period of time for persistence, in days. &quot;30&quot; as shown above would cause the value to be populated into the
selected variable on every page view made by the user for the next 30 days. If omitted, the setting defaults to
session.
PLUGINS SECTION: Add the following code to the area of the s_code.js file labeled PLUGINS SECTION. Do
not make any changes to this portion of the plug-in code.
/*
* Plugin: getAndPersistValue 0.3 - get a value on every page
*/
s.getAndPersistValue=new Function(&quot;v&quot;,&quot;c&quot;,&quot;e&quot;,&quot;&quot;
+&quot;var s=this,a=new Date;e=e?e:0;a.setTime(a.getTime()+e*86400000);if(&quot;
+&quot;v)s.c_w(c,v,e?a:0);return s.c_r(c);&quot;);
Always test plug-in installations extensively to ensure that data collection is as expected before deploying in a
production environment.
getDaysSinceLastVisit
Determines the number of days since a user last visited your site, and captures this information in a Analytics variable.
This return frequency data can be used to answer the following questions:
• How frequently do users revisit my site?
• How does return frequency correlate with conversion? Do repeat buyers visit frequently or infrequently?
• Do users who click through my campaigns then return frequently?
The plug-in can also generate values used for segmentation. For example, you can create a segment to view all of
the data for only those visits that were preceded by 30 or more days of non-visitation by the user.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Plug-in Code and Implementation
CONFIG SECTION
No changes required.
Plugin Config
Place the following code within the s_doPlugins() function, which is located in the area of the s_code.js file
labeled Plugin Config. Choose one Custom Traffic (s.prop) variable and/or one Custom Converesion (s.eVar) variable
for use in capturing return frequency data. This selection should be a variable that has been enabled using the Admin
Console but is not currently in use for any other purpose. The following is given as an example, and should be
updated appropriately based on your needs.
s.prop1=s.getDaysSinceLastVisit(Cookie_Name);
PLUGINS SECTION
Add the following code to the area of the s_code.js file labeled PLUGINS SECTION. Do not make any changes
to this portion of the plug-in code.
/*
* Plugin: Days since last Visit 1.1 - capture time from last visit
*/
Implementation Plug-ins
189
s.getDaysSinceLastVisit=new Function(&quot;c&quot;,&quot;&quot;
+&quot;var s=this,e=new Date(),es=new Date(),cval,cval_s,cval_ss,ct=e.getT&quot;
+&quot;ime(),day=24*60*60*1000,f1,f2,f3,f4,f5;e.setTime(ct+3*365*day);es.s&quot;
+&quot;etTime(ct+30*60*1000);f0='Cookies Not Supported';f1='First Visit';f&quot;
+&quot;2='More than 30 days';f3='More than 7 days';f4='Less than 7 days';f&quot;
+&quot;5='Less than 1 day';cval=s.c_r(c);if(cval.length==0){s.c_w(c,ct,e);&quot;
+&quot;s.c_w(c+'_s',f1,es);}else{var d=ct-cval;if(d&gt;30*60*1000){if(d&gt;30*da&quot;
+&quot;y){s.c_w(c,ct,e);s.c_w(c+'_s',f2,es);}else if(d&lt;30*day+1 &amp;&amp; d&gt;7*day&quot;
+&quot;){s.c_w(c,ct,e);s.c_w(c+'_s',f3,es);}else if(d&lt;7*day+1 &amp;&amp; d&gt;day){s.&quot;
+&quot;c_w(c,ct,e);s.c_w(c+'_s',f4,es);}else if(d&lt;day+1){s.c_w(c,ct,e);s.c&quot;
+&quot;_w(c+'_s',f5,es);}}else{s.c_w(c,ct,e);cval_ss=s.c_r(c+'_s');s.c_w(c&quot;
+&quot;+'_s',cval_ss,es);}}cval_s=s.c_r(c+'_s');if(cval_s.length==0) retur&quot;
+&quot;n f0;else if(cval_s!=f1&amp;&amp;cval_s!=f2&amp;&amp;cval_s!=f3&amp;&amp;cval_s!=f4&amp;&amp;cval_s&quot;
+&quot;!=f5) return '';else return cval_s;&quot;);
Notes
• Always test plug-in installations extensively to ensure that data collection is as expected before deploying in a
production environment.
• The plug-in categorizes users by return frequency into the following groups:
• First Visit
• Less than 1 day
• Less than 7 days
• More than 7 days
• More than 30 days
• This plug-in relies on cookies to flag a user has having visited previously. If the browser does not accept cookies,
the plug-in returns a value of Cookies Not Supported.
getLoadTime
Gets the page load time in tenths of a second and lets you store the value in a prop, eVar, and/or a numeric event.
To use this plugin, you insert the function code, then call the function twice in your s_code.js file. Once at the
beginning of the file, and then again in the doPlugins section. This plugin is intentionally not defined as a method
of the s object. Doing so would have added to the calculated page load time.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Plug-in Code and Implementation
Add the function
Add the following definition of the s_getLoadTime function in s_code.js, anywhere before the &quot;DO NOT ALTER
ANYTHING BELOW THIS LINE&quot; section:
function s_getLoadTime(){if(!window.s_loadT){var b=new
Date().getTime(),o=window.performance?performance.timing:0,a=o?o.requestStart:window.inHeadTS||0;s_loadT=a?Math.round((b-a)/100):''}return
s_loadT}
Make the initial function call
Add a call to s_getLoadTime() near the beginning of s_code.js, outside of any function.
Make the final function call
Implementation Plug-ins
190
Add another call to s_getLoadTime() in the s_doPlugins() function, saving the returned value in a prop, eVar,
and/or a numeric event.
Usage Example 1 - Save the page load time in prop10 and eVar20:
s.eVar20=s.prop10=s_getLoadTime();
Usage Example 2 - Save the page load time in numeric event99:
if(s_getLoadTime())s.events=s.apl(s.events,'event90='+s_getLoadTime(),',',1);
(Optional) Add support for older browsers
To support older browsers that don't provide the window.performance.timing property, include the following line in
the HEAD section of the page's HTML near the beginning and prior to invoking .js, .css, or other files:
&lt;script type=&quot;text/javascript&quot;&gt;var inHeadTS=(new Date()).getTime();&lt;/script&gt;
getNewRepeat
Determines whether a visitor is a new visitor or a repeat visitor, and captures this information in a Analytics variable.
Use this plug-in to answer the following questions:
• What percentage of my visitors are new (as opposed to repeat) visitors?
• Do return visitors generate higher conversion per capita than new visitors? What is this ratio?
• Do my marketing campaigns cause persistence across visits? For example, do users who click through my
campaigns then return later?
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Plug-in Code and Implementation
CONFIG SECTION: No changes required for this section.
Plug-in Configuration
Place the following code within the s_doPlugins() function, which is located in the area of the s_code.js file labeled
Plugin Config. Choose one Custom Traffic (s.prop) variable or one Custom Conversion (s.eVar) variable for use in
capturing persisted value data. This should be a variable that has been enabled using the Admin Console, but which
is not currently in use for any other purpose. You can use the following example and update it based on your
requirements.
s.prop1=s.getNewRepeat(30,'s_getNewRepeat');
s.getNewRepeat has two optional arguments:
1. The first optional argument is the number of days that the cookie should last. The default value if this argument
is omitted is 30 days.
2. The second optional argument is the cookie name. A default value is used if this argument is omitted.
PLUGINS SECTION: Add the following code to the area of the s_code.js file labeled PLUGINS SECTION. Do
not make any changes to this portion of the plug-in code.
/*
* Plugin: getNewRepeat 1.2 - Returns whether user is new or repeat
*/
s.getNewRepeat=new Function(&quot;d&quot;,&quot;cn&quot;,&quot;&quot;
Implementation Plug-ins
191
+&quot;var s=this,e=new Date(),cval,sval,ct=e.getTime();d=d?d:30;cn=cn?cn:&quot;
+&quot;'s_nr';e.setTime(ct+d*24*60*60*1000);cval=s.c_r(cn);if(cval.length=&quot;
+&quot;=0){s.c_w(cn,ct+'-New',e);return'New';}sval=s.split(cval,'-');if(ct&quot;
+&quot;-sval[0]&lt;30*60*1000&amp;&amp;sval[1]=='New'){s.c_w(cn,ct+'-New',e);return'N&quot;
+&quot;ew';}else{s.c_w(cn,ct+'-Repeat',e);return'Repeat';}&quot;);
/*
* Utility Function: split v1.5 (JS 1.0 compatible)
*/
s.split=new Function(&quot;l&quot;,&quot;d&quot;,&quot;&quot;
+&quot;var i,x=0,a=new Array;while(l){i=l.indexOf(d);i=i&gt;-1?i:l.length;a[x&quot;
+&quot;++]=l.substring(0,i);l=l.substring(i+d.length);}return a&quot;);
Always test plug-in installations extensively to ensure that data collection is as expected before deploying in a
production environment.
getPageVisibility
Records the number of seconds your page was the active tab within the browser, and passes that value into a metric
on the next page view.
Note: This is a beta version of the plugin, and additional updates may be forthcoming.
This plug-in also records the total seconds the page was within the browser (both active and passive viewing time).
It is required to use the getPreviousValue plug-in in order to track the previous page name associated with the page
visibility events. Tracking these values helps you better understand visitor engagement and more accurately track
visitor behavior on your sites.
It is required that you use the getPreviousValue plug-in to track the previous page name associated with the page
visibility events. Tracking these values helps you better understand visitor engagement and more accurately track
visitor behavior on your sites.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics. This plug-in is compatible only with AppMeasurement tracking libraries.
Required Supporting Plug-ins
• appendList
• getPreviousValue
• getVisitStart
Plug-in Code and Implementation
Config Section
The s.pvel variable should contain the three events you wish to use:
Event
Definition
Total Page
The amount of time the page was active within the browser
Visibility Seconds
(Numeric)
Total Page
Seconds
(Numeric)
The amount of time the page was loaded in the browser, regardless of its visibility state
Implementation Plug-ins
Event
192
Definition
Total Page
The total number of times a value was recorded for the previous two events
Visibility Instances
(Counter)
Sample Calls
//Page Visibility Event List (total page visibility seconds, total page seconds, total page
visibility instances)
s.pvel='event7,event8,event9'
doPlugins Section
To initialize the plug-in, two lines of code are required in the doPlugins section of your s_code, preferably after you
have designated the s.pageName variable.
Sample Calls
/* Page Visibility */
s.eVar9 = s.getPreviousValue(s.pageName,'gpv_v9','');
designated eVar of your choice
s.getPageVisibility();
//Record the previous page name in the
Plug-ins Section
/* Page Visibility Plugin 0.1 (BETA) */
s.getPageVisibility=new Function(&quot;&quot;,&quot;&quot;
+&quot;var s=this;if(s.getVisitStart()){s.Util.cookieWrite('s_pvs','');s.U&quot;
+&quot;til.cookieWrite('s_tps','');}if(s.Util.cookieRead('s_pvs')&amp;&amp;s.pvt&lt;1&quot;
+&quot;){if(parseInt(s.Util.cookieRead('s_pvs'))&lt;=parseInt(s.Util.cookieRe&quot;
+&quot;ad('s_tps'))){s.pve=s.pvel.split(',');s.events=s.apl(s.events,s.pve&quot;
+&quot;[0]+'='+(parseInt(s.Util.cookieRead('s_pvs'))),',',2);s.Util.cookie&quot;
+&quot;Write('s_pvs','');s.events=s.apl(s.events,s.pve[1]+'='+(parseInt(s.&quot;
+&quot;Util.cookieRead('s_tps'))),',',2);s.Util.cookieWrite('s_tps','');s.&quot;
+&quot;events=s.apl(s.events,s.pve[2],',',2);}}s.pvi=setInterval(s.pvx,100&quot;
+&quot;0);s.wpvi=setInterval(s.wpvc,5000);&quot;);
s.gbp=new Function(&quot;&quot;,&quot;&quot;
+&quot;if('hidden'in document){return null;}var bp=['moz','ms','o','webkit&quot;
+&quot;'];for(var i=0;i&lt;bp.length;i++){var p=bp[i]+'Hidden';if(p in docume&quot;
+&quot;nt){return bp[i];}}return null;&quot;);
s.hp=new Function(&quot;p&quot;,&quot;&quot;
+&quot;if(p){return p+'Hidden';}else{return'hidden';}&quot;);
s.vs=new Function(&quot;p&quot;,&quot;&quot;
+&quot;if(p){return p+'VisibilityState';}else{return'visibilityState';}&quot;);
s.ve=new Function(&quot;p&quot;,&quot;&quot;
+&quot;if(p){return p+'visibilitychange';}else{return'visibilitychange';}&quot;);
s.pvx=new Function(&quot;&quot;,&quot;&quot;
+&quot;s.pvt+=1;&quot;);
s.wpvc = function(){var tempDate = Date.now();s.Util.cookieWrite('s_tps',
Math.ceil((tempDate - s.totalTime)/1000));s.Util.cookieWrite('s_pvs', s.pvt)}
document.addEventListener('visibilitychange',function(event){if(document.hidden){s.visibility
=
false;clearTimeout(s.pvi);}else{s.visibility=true;s.pvi=setInterval(s.pvx,1000);}});s.totalTime=new
Date();s.pvt=0;s.prefix=s.gbp;s.hidden=s.hp(s.prefix);s.visibility=true;s.visibilityState=s.vs(s.prefix);s.visibilityEvent=s.ve(s.prefix);
Notes
• Always test plug-in installations to ensure that data collection is as expected before deploying in a production
environment.
• Because the plug-in passes the page visibility seconds and total seconds as they are associated with the previous
page, data is not collected for the final page view of the visit.
• This plug-in relies on the ability to set cookies in the user's web browser. If the user does not accept first-party
cookies, the plug-in will not pass data into Analytics.
Implementation Plug-ins
193
• The plug-in creates its own first-party cookies named s_tps and s_pvs.
• A very small percentage of users will not pass percentage of page viewed data due to browser limitations, and
logic is contained within the plugin to ensure that the data is not skewed as a result. However, this plug-in has
been successfully tested in IE, Firefox, Chrome, and Safari.
• Due to the way the plugin measures total seconds and associates that value with the previous page name, there
will be differences between default time spent on page metrics and total seconds metrics.
• Calculated metrics can be created to aid in summarizing and understanding visitor behavior associated with these
metrics:
• Page Visibility Ratio (Total Page Visibility Seconds / Total Page Seconds)
• Total Hidden Seconds (Total Page Seconds – Total Page Visibility Seconds)
• Average Page Visibility Seconds (Total Page Visibility Seconds/Total Page Visibility Instances)
• Average Page Hidden Seconds ((Total Page Seconds - Total Page Visibility Seconds)/Total Page Visibility
Instances)
• Due to the way the plug-in rounds up the seconds, there can be a 1-2 second difference between the total page
visibility seconds and total seconds, with total seconds being higher. (To be resolved in a future update)
• Using the getVisitStart plug-in should account for visitors that have a new visit start after a period of 30+ minutes
of inactivity. This is not working as designed; however, there will likely be a workaround when we incorporate the
“total active seconds” in a future iteration of the plug-in.
Frequently Asked Questions
Will this plug-in make additional server calls?
The plugin will only record page visibility values on subsequent page view server calls. No additional server calls
are used in conjunction with it.
If I do not want to capture total page seconds or total page visibility instances, can I leave those out of the
event list?
Yes, the total page seconds and total visibility instances are optional events and can be left out of the list if desired.
Will the events captured make sense if I use them in reports other than the Previous Page Name?
Since the plugin records values on the subsequent image request only other eVars that have been captured in a
‘previous page’ context could be applied, i.e. ‘Previous Page URL’.
Will the plug-in send the visibility time on an s.tl() call, or only on an s.t() call?
The visibility time is only recorded with s.t() calls.
getPercentPageViewed
Record the portion of a page (0-100%) that the user views and pass the value into a variable on the next page view.
This plugin lets you determine how much of your content users are seeing on average, so that you can optimize
your page lengths and layouts based on user behaviors.
You can also use classifications to group percentages (such as Less than 25% or Less than 50%) so that you can
identify page-viewing trends.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Implementation Plug-ins
194
Plug-in Code and Implementation
Config Section: No changes required for this section.
Sample Calls
/*
* Add one of the following examples in s.doPlugins(), after s.pageName has been assigned:
*/
//
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IMPORTANT NOTE - PLEASE READ! &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;
//
// The getPercentPageViewed plugin returns an integer if the pageID argument is unspecified
// or is set to an empty string or evaluates to false, as shown in example 1 below. If the
// PageID is specified, the plugin returns an array as shown in example 2.
// Example 1: Get maximum percent viewed only, using s.pageName as an implicit identifier
s.prop21 = s.getPreviousValue(s.pageName,'s_ppn'); //prop21: prev page name
s.prop22 = s.getPercentPageViewed(); //prop22: max % viewed of prev page
if(!s.prop21||s.prop21=='no value')s.prop22=''; //clear max % viewed if no prev page view
//Example 2: Get entire percent page viewed array and save metrics
s.prop21 = s.getPreviousValue(s.pageName,'s_ppn'); //prop21: prev page name
var ppv = s.getPercentPageViewed(s.pageName); //get array of data on prev page % viewed
if( ppv &amp;&amp; typeof ppv=='object' &amp;&amp; ppv[0] == s.prop21 ) { //if ppv array returned and prev page
id matches prev page name
s.prop22 = ppv[1] + '|' + ppv[2]; //prop22: prev page max and initial % viewed, delimited by
&quot;|&quot;. (Use classifications to separate values)
s.prop23 = ppv[4] + 'x' + ppv[5]; //prop23: viewport width x height in CSS pixels
s.prop24 = ppv[6] + 'x' + ppv[7]; //prop24: display width x height in real pixels
s.prop25 = ppv[8]; //prop25: pixel density, i.e. number of virtual pixels per real pixel
s.prop26 = ppv[9]; //prop26: device orientation: initial and final (final only present if
rotation occurred)
}
Returns
• If there was not a previous page view in this visit, an empty string is returned
• If pid is &quot;-&quot;, or unspecified, an integer containing the last page's maximum percent viewed is returned
• Otherwise, an array is returned with the following elements:
• array[0] - Page ID
• array[1] - Maximum percent viewed
• array[2] - Initial percent viewed
• array[3] - Maximum vertical pixels viewed
• array[4] - Viewport width in CSS pixels new
• array[5] - Viewport height in CSS pixels new
• array[6] - Display width in real pixels (reflecting orientation) new
• array[7] - Display height in real pixels (reflecting orientation) new
• array[8] - Final pixel density new
• array[9] - Device orientation, set to one of the following text strings: new
• &quot;L&quot; - Landscape (rotation did not occur)
• &quot;P&quot; - Portrait (rotation did not occur)
• &quot;LP&quot; - started landscape, ended portrait
• &quot;PL&quot; - started portrait, ended landscape
Implementation Plug-ins
195
Plugins Section: Add the following code to the area of the s_code.js file labeled PLUGINS SECTION. Do not
make any changes to this portion of the plug-in code.
/*
* Plugin: getPercentPageViewed v1.71
*/
s.getPercentPageViewed=new Function(&quot;n&quot;,&quot;&quot;
+&quot;var s=this,W=window,EL=W.addEventListener,AE=W.attachEvent,E=['load&quot;
+&quot;','unload','scroll','resize','zoom','keyup','mouseup','touchend','o&quot;
+&quot;rientationchange','pan'];W.s_Obj=s;s_PPVid=(n=='-'?s.pageName:n)||s&quot;
+&quot;.pageName||location.href;if(!W.s_PPVevent){s.s_PPVg=function(n,r){v&quot;
+&quot;ar k='s_ppv',p=k+'l',c=s.c_r(n||r?k:p),a=c.indexOf(',')&gt;-1?c.split(&quot;
+&quot;',',10):[''],l=a.length,i;a[0]=unescape(a[0]);r=r||(n&amp;&amp;n!=a[0])||0;&quot;
+&quot;a.length=10;if(typeof a[0]!='string')a[0]='';for(i=1;i&lt;10;i++)a[i]=&quot;
+&quot;!r&amp;&amp;i&lt;l?parseInt(a[i])||0:0;if(l&lt;10||typeof a[9]!='string')a[9]='';&quot;
+&quot;if(r){s.c_w(p,c);s.c_w(k,'?')}return a};W.s_PPVevent=function(e){va&quot;
+&quot;r W=window,D=document,B=D.body,E=D.documentElement,S=window.screen|&quot;
+&quot;|0,Ho='offsetHeight',Hs='scrollHeight',Ts='scrollTop',Wc='clientWid&quot;
+&quot;th',Hc='clientHeight',C=100,M=Math,J='object',N='number',s=W.s_Obj|&quot;
+&quot;|W.s||0;e=e&amp;&amp;typeof e==J?e.type||'':'';if(!e.indexOf('on'))e=e.subs&quot;
+&quot;tring(2);s_PPVi=W.s_PPVi||0;if(W.s_PPVt&amp;&amp;!e){clearTimeout(s_PPVt);s&quot;
+&quot;_PPVt=0;if(s_PPVi&lt;2)s_PPVi++}if(typeof s==J){var h=M.max(B[Hs]||E[H&quot;
+&quot;s],B[Ho]||E[Ho],B[Hc]||E[Hc]),X=W.innerWidth||E[Wc]||B[Wc]||0,Y=W.i&quot;
+&quot;nnerHeight||E[Hc]||B[Hc]||0,x=S?S.width:0,y=S?S.height:0,r=M.round(&quot;
+&quot;C*(W.devicePixelRatio||1))/C,b=(D.pageYOffset||E[Ts]||B[Ts]||0)+Y,p&quot;
+&quot;=h&gt;0&amp;&amp;b&gt;0?M.round(C*b/h):0,O=W.orientation,o=!isNaN(O)?M.abs(o)%180&quot;
+&quot;:Y&gt;X?0:90,L=e=='load'||s_PPVi&lt;1,a=s.s_PPVg(s_PPVid,L),V=function(i,&quot;
+&quot;v,f,n){i=parseInt(typeof a==J&amp;&amp;a.length&gt;i?a[i]:'0')||0;v=typeof v!=&quot;
+&quot;N?i:v;v=f||v&gt;i?v:i;return n?v:v&gt;C?C:v&lt;0?0:v};if(new RegExp('(iPod|i&quot;
+&quot;Pad|iPhone)').exec(navigator.userAgent||'')&amp;&amp;o){o=x;x=y;y=o}o=o?'P'&quot;
+&quot;:'L';a[9]=L?'':a[9].substring(0,1);s.c_w('s_ppv',escape(W.s_PPVid)+&quot;
+&quot;','+V(1,p,L)+','+(L||!V(2)?p:V(2))+','+V(3,b,L,1)+','+X+','+Y+','+x&quot;
+&quot;+','+y+','+r+','+a[9]+(a[9]==o?'':o))}if(!W.s_PPVt&amp;&amp;e!='unload')W.s&quot;
+&quot;_PPVt=setTimeout(W.s_PPVevent,333)};for(var f=W.s_PPVevent,i=0;i&lt;E.&quot;
+&quot;length;i++)if(EL)EL(E[i],f,false);else if(AE)AE('on'+E[i],f);f()};v&quot;
+&quot;ar a=s.s_PPVg();return!n||n=='-'?a[1]:a&quot;);
Notes
• Always test plug-in installations to ensure that data collection is as expected before deploying in a production
environment.
• Because the plug-in passes the percentage of page viewed on the previous page, data is not collected for the final
page view of the visit. One way around this is to use a function on all exit links to call s.getPercentPageViewed().
• This plug-in relies on the ability to set cookies in the user's web browser. If the user does not accept first-party
cookies, the plug-in will not pass data into Analytics.
• The plug-in creates its own first-party cookie named s_ppv.
• A very small percentage of users will not pass percentage of page viewed data due to browser limitations. However,
this plug-in has been successfully tested in IE, Firefox, Chrome, Safari, and Opera.
getPreviousValue
Captures the value of a Analytics variable on the next page view. For example, you can use plug-in to capture the
s.pageName value from the previous page view into a Custom Traffic variable. It also has an option to capture a
previous value only when designated success events are set.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Implementation Plug-ins
196
Plug-in Code and Implementation
CONFIG SECTION: No changes required for this section.
Plug-in Configuration
Place the following code within the s_doPlugins() function, which is located in the area of the s_code.js file labeled
Plugin Config. Choose one Custom Traffic (s.prop) variable or one Custom Conversion (s.eVar) variable for use in
capturing persisted value data. This should be a variable that has been enabled using the Admin Console, but which
is not currently in use for any other purpose. You can use the following example and update it based on your
requirements.
s.prop1=s.getPreviousValue(s.pageName,'gpv_pn','event1');
s.getPreviousValue has three arguments:
1. The variable to be captured from the previous page (s.pageName above).
2. The cookie name for use in storing the value for retrieval (gpv_pn above).
3. The events that must be set on the page view in order to trigger the retrieval of the previous value (event1 above).
When left blank or omitted, the plug-in captures the previous value on all page views.
PLUGINS SECTION: Add the following code to the area of the s_code.js file labeled PLUGINS SECTION. Do
not make any changes to this portion of the plug-in code.
/*
* Plugin: getPreviousValue_v1.0 - return previous value of designated
*
variable (requires split utility)
*/
s.getPreviousValue=new Function(&quot;v&quot;,&quot;c&quot;,&quot;el&quot;,&quot;&quot;
+&quot;var s=this,t=new Date,i,j,r='';t.setTime(t.getTime()+1800000);if(el&quot;
+&quot;){if(s.events){i=s.split(el,',');j=s.split(s.events,',');for(x in i&quot;
+&quot;){for(y in j){if(i[x]==j[y]){if(s.c_r(c)) r=s.c_r(c);v?s.c_w(c,v,t)&quot;
+&quot;:s.c_w(c,'no value',t);return r}}}}}else{if(s.c_r(c)) r=s.c_r(c);v?&quot;
+&quot;s.c_w(c,v,t):s.c_w(c,'no value',t);return r}&quot;);
/*
* Utility Function: split v1.5 - split a string (JS 1.0 compatible)
*/
s.split=new Function(&quot;l&quot;,&quot;d&quot;,&quot;&quot;
+&quot;var i,x=0,a=new Array;while(l){i=l.indexOf(d);i=i&gt;-1?i:l.length;a[x&quot;
+&quot;++]=l.substring(0,i);l=l.substring(i+d.length);}return a&quot;);
Notes
• Always test plug-in installations extensively to ensure that data collection is as expected before deploying in a
production environment.
• If no value is present for the selected variable on any given page, the text no value will be set in the cookie.
• A fixed 30-minute cookie expiration is now set for each cookie, and refreshed with each page load. The plug-in
works for the length of a visit.
• Because the function must be called as part of the plug-ins section of code, the code runs each time s.t() or s.tl()
is called.
• The chosen variable should be populated with a value prior to the call to s.getPreviousValue. Because the
s_doPlugins() function is executed after the variables on the page are populated, this issue rarely occurs. It should
only be a matter of concern if the variable used with this plug-in is populated within the s_doPlugins() function and
after the call to s.getPreviousValue.
Implementation Plug-ins
197
getQueryParam
Returns the value of a specified query string parameter, if found in the current page URL. Because important data
(such as campaign tracking codes, internal search keywords, etc.) is available in the query string on a page,
getQueryParam is helps capture the data into Analytics variables.
Important: This plug-in is used by H code only. AppMeasurement for JavaScript provides this functionality
natively using Util.getQueryParam.
Once installed in your AppMeasurement for JavaScript code, the plug-in is configured by selecting a Analytics
variable to populate using data found in the query string, and specifying which query string values to capture. The
plug-in detects the specified query string, if present, and populates the chosen variable with its value. If no query
string parameter is found with that value, an empty string is returned. If a query string parameter exists but does not
have a value (such as param1 in ?param1&amp;param2=value), the word true is returned.
Note: The base code for the plug-in must be installed in your AppMeasurement for JavaScript code before
the examples below will work.
If you wanted to use s.campaign to capture campaign tracking codes available as values of the cid query parameter,
you would enter the following in the doPlugins() function in your AppMeasurement for JavaScript code:
s.campaign=s.getQueryParam('cid')
In this example, if the user arrived at a landing page on your site where the URL was
http://www.yoursite.com/index.html?cid=123456, then s.campaign would receive a value of 123456.
This could be seen using the DigitalPulse Debugger, which should show v0=123456 as part of the image request.
Note: The parameter cid and others are used here as examples. You can replace them with any query string
parameters that exist on your site.
The getQueryParam plug-in has two additional arguments (options) that can be used to capture data into Analytics
variables:
s.getQueryParam('p','d','u')
where:
p = comma-separated list of query parameters to locate (can also be a single value with no
comma)
d = delimiter for list of values (in case more than one specified parameter is found)
u = where to search for value (e.g., document.referrer); set to current page URL by default
If p is a list of query string parameters and more than one query string parameter is found in the URL, all values are
returned in a list separated by the delimiter, d, which can be a single character or a string of characters, such as &quot;
: &quot; (space-colon-space). If d is omitted, no delimiter is used between values. If one query string parameter should
take precedence over another, when both are found, use an if statement as shown below.
// cid takes precedence over iid if both exist in the query string
s.campaign=s.getQueryParam('cid');
if(!s.campaign)
s.campaign=s.getQueryParam('iid');
As of version getQueryParam v2.0, the plug-in accepts an optional third argument, u, which allows you to specify
the URL from which you would like to extract query string parameters. By default (i.e. if this third argument is omitted
Implementation Plug-ins
198
or left blank), the plug-in uses the page URL. For example, if you would like extract a query string from the referrer,
you can use the following code:
// take the query string from the referrer
s.eVar1=s.getQueryParam('pid','',document.referrer);
The flag &quot;f&quot; should be used in this third argument with frames, when the necessary query string parameter is found
in the address bar rather than the current frame's URL:
// take the query string from the parent frame
s.eVar1=s.getQueryParam('pid','',f);
When using frames and the f parameter, it is recommended that the getValOnce plug-in be used to prevent the
campaign tracking code to be sent with each page view.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Plug-in Code
/********************************************************************
*
* Main Plug-in code (should be in Plug-ins section)
*
*******************************************************************/
/*
* Plugin: getQueryParam 2.3
*/
s.getQueryParam=new Function(&quot;p&quot;,&quot;d&quot;,&quot;u&quot;,&quot;&quot;
+&quot;var s=this,v='',i,t;d=d?d:'';u=u?u:(s.pageURL?s.pageURL:s.wd.locati&quot;
+&quot;on);if(u=='f')u=s.gtfs().location;while(p){i=p.indexOf(',');i=i&lt;0?p&quot;
+&quot;.length:i;t=s.p_gpv(p.substring(0,i),u+'');if(t){t=t.indexOf('#')&gt;-&quot;
+&quot;1?t.substring(0,t.indexOf('#')):t;}if(t)v+=v?d+t:t;p=p.substring(i=&quot;
+&quot;=p.length?i:i+1)}return v&quot;);
s.p_gpv=new Function(&quot;k&quot;,&quot;u&quot;,&quot;&quot;
+&quot;var s=this,v='',i=u.indexOf('?'),q;if(k&amp;&amp;i&gt;-1){q=u.substring(i+1);v&quot;
+&quot;=s.pt(q,'&amp;','p_gvf',k)}return v&quot;);
s.p_gvf=new Function(&quot;t&quot;,&quot;k&quot;,&quot;&quot;
+&quot;if(t){var s=this,i=t.indexOf('='),p=i&lt;0?t:t.substring(0,i),v=i&lt;0?'T&quot;
+&quot;rue':t.substring(i+1);if(p.toLowerCase()==k.toLowerCase())return s.&quot;
+&quot;epa(v)}return ''&quot;);
/********************************************************************
*
* Commented example of how to use this is doPlugins function
*
*******************************************************************/
/* Plugin Example: getQueryParam 2.3
//single parameter
s.campaign=s.getQueryParam('cid');
//multiple parameters
s.campaign=s.getQueryParam('cid,sid',':');
//non-page URL example
s.campaign=s.getQueryParam('cid','',document.referrer);
//parent frame example
s.campaign=s.getQueryParam('cid','','f');
*/
/********************************************************************
*
* Config variables (should be above doPlugins section)
*
Implementation Plug-ins
199
*******************************************************************/
None
/********************************************************************
*
* Utility functions that may be shared between plug-ins (name only)
*
*******************************************************************/
None
getTimeParting
The getTimeParting plug-in populates reports with hour of day, day of week, and weekend and weekday values.
This plug-in is useful in performing analysis based on the time of day or day of week. It can help to answer the
following questions:
• Across a large date range, what is the most popular time of day for visitors to access my site?
• Are there days of the week on which conversion is higher on my site?
• How do my weekend sales compare to my weekday sales?
• Does a certain marketing campaign generate higher conversions in the morning, or in the afternoon?
This plug-in captures the date and time information available in the user's web browser. It obtains the hour of the
day and the day of the week from this information. It then converts this data to the time zone of your choosing. It
also accounts for Daylight Savings Time.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Plug-in Code
Config Section
Place the following code in the area of the s_code.js file labeled CONFIG SECTION, and make the necessary
updates as described below.
s._tpDST - an array of DST values. The array is structured in the following format: YYYY:'MM/DD,MM/DD'
//time parting configuration
//Australia
s._tpDST = {
2012:'4/1,10/7',
2013:'4/7,10/6',
2014:'4/6,10/5',
2015:'4/5,10/4',
2016:'4/3,10/2',
2017:'4/2,10/1',
2018:'4/1,10/7',
2019:'4/7,10/6'}
//US
s._tpDST = {
2012:'3/11,11/4',
2013:'3/10,11/3',
2014:'3/9,11/2',
2015:'3/8,11/1',
2016:'3/13,11/6',
2017:'3/12,11/5',
Implementation Plug-ins
200
2018:'3/11,11/4',
2019:'3/10,11/3'}
//Europe
s._tpDST = {
2012:'3/25,10/28',
2013:'3/31,10/27',
2014:'3/30,10/26',
2015:'3/29,10/25',
2016:'3/27,10/30',
2017:'3/26,10/29',
2018:'3/25,10/28',
2019:'3/31,10/27'}
Note for Northern Hemisphere clients: in the array DST values are DST start, DST end.
Note for Southern Hemisphere clients: in the array DST values are DST end, DST start.
Parameters
var tp = s.getTimeParting(h,z);
• h = (required) Hemisphere - Specify what hemisphere you are converting the time to. This is a value of 'n' or 's'.
This is used to determine how to use the DST array passed. If 'n' is passed the plugin uses the dates when DST
is on. If 's' is passed the plugin uses the dates when DST is off.
• z = (optional) Time Zone - If you would like the data to be based upon a specific time period, then that will need to
be specified as the hours different from GMT here. Note this should be the GMT during non DST. If no value is
specified, it defaults to GMT (i.e. '-5' for US Eastern Time)
Returns
Returns a concatenated value of time at minute level and day of week, for example:
8:03 AM|Monday
You can then use Classifications to group visits into time periods. For example, you could set up a rule in Classification
Rule Builder to bucket visits between 9:00 AM and 9:59 AM to &quot;9:00 AM - 10:00 AM&quot;. As an alternative to
classifications, you could provide additional client-side logic to bucket visits in JavaScript.
Example Call
var tp = s.getTimeParting('n','-7');
s.prop1 = tp;
PLUGINS SECTION
Add the following code to the PLUGINS SECTION in the s_code.js file.
/*
* Plugin: getTimeParting 3.4
*/
s.getTimeParting=new Function(&quot;h&quot;,&quot;z&quot;,&quot;&quot;
+&quot;var s=this,od;od=new Date('1/1/2000');if(od.getDay()!=6||od.getMont&quot;
+&quot;h()!=0){return'Data Not Available';}else{var H,M,D,U,ds,de,tm,da=['&quot;
+&quot;Sunday','Monday','Tuesday','Wednesday','Thursday','Friday','Saturda&quot;
+&quot;y'],d=new Date();z=z?z:0;z=parseFloat(z);if(s._tpDST){var dso=s._tp&quot;
+&quot;DST[d.getFullYear()].split(/,/);ds=new Date(dso[0]+'/'+d.getFullYea&quot;
+&quot;r());de=new Date(dso[1]+'/'+d.getFullYear());if(h=='n'&amp;&amp;d&gt;ds&amp;&amp;d&lt;de)&quot;
+&quot;{z=z+1;}else if(h=='s'&amp;&amp;(d&gt;de||d&lt;ds)){z=z+1;}}d=d.getTime()+(d.getT&quot;
+&quot;imezoneOffset()*60000);d=new Date(d+(3600000*z));H=d.getHours();M=d&quot;
+&quot;.getMinutes();M=(M&lt;10)?'0'+M:M;D=d.getDay();U=' AM';if(H&gt;=12){U=' P&quot;
+&quot;M';H=H-12;}if(H==0){H=12;}D=da[D];tm=H+':'+M+U;return(tm+'|'+D);}&quot;);
Notes
• Always test plug-in installations to ensure that data collection is as expected before deploying to production.
• Configuration variables must be set for plugin to work correctly.
Implementation Plug-ins
201
getValOnce
The getValOnce plug-in prevents a given variable from being set to the previously defined value. It uses a cookie
to determine a variable's last seen value. If the current value matches the cookie value, the variable is overwritten
with a blank string before it is sent to Adobe's processing servers.This plug-in is useful to prevent conversion variable
instance inflation caused when users refresh the page or click the Back button.
Important: This plug-in has not been validated to be compatible with AppMeasurement for JavaScript. See
AppMeasurement Plug-in Support.
Parameters
s.eVar1=s.getValOnce(variable,cookie,expiration,minute);
• Variable: The variable that will be checked. This is typically the same as the variable being defined.
• Cookie: The name of the cookie that stores the previous value to compare against. The cookie can be any value.
• (Optional) Expiration: The number of days the cookie will expire. If not set or set to 0, the default expiration is the
browser session.
• (Optional) Minute: If you set this to the string value m, the expiration value is defined in minutes instead of days.
If not set, days is the default expiration.
Properties
• This plug-in is commonly used on conversion variables. However, you can use it on any Analytics variable.
• When Javascript encounters this function, it compares the defined value to what is stored in the cookie. If the
defined value is different from the cookie value, the defined value is set. If the defined value is the same as the
cookie value, an empty string is returned.
• The cookie can only store a single value, meaning the plug-in only looks as the last defined value.
• The plug-in does not stop all values from defining the variable after it is defined. The plug-in only prevents the last
value from being set multiple times consecutively.
• If the end user blocks or rejects cookies, the original value is always returned.
• The plug-in's session is different from what Analytics defines as a session (or visit). Analytics terminates a session
after 12 hours of activity or 30 minutes of inactivity. Because the plug-in uses the browser's session definition, it is
terminated only after the user closes the tab or exits the browser.
• If a user closes your page, opens a different tab and navigates back to your site within 30 minutes, the plug-in
creates a new session while keeping the Analytics visit open.
• If a user keeps the browser window open without clicking on a link for more than 30 minutes, the Analytics visit
expires while keeping the browser session open.
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
Implementation
To implement this plug-in, place the following code within your s_code.js file
/********************************************************************
*
* Main Plug-in code (should be in Plug-ins section)
*
*******************************************************************/
/*
* Plugin: getValOnce_v1.11
*/
Implementation Plug-ins
202
s.getValOnce=new Function(&quot;v&quot;,&quot;c&quot;,&quot;e&quot;,&quot;t&quot;,&quot;&quot;
+&quot;var s=this,a=new Date,v=v?v:'',c=c?c:'s_gvo',e=e?e:0,i=t=='m'?6000&quot;
+&quot;0:86400000,k=s.c_r(c);if(v){a.setTime(a.getTime()+e*i);s.c_w(c,v,e&quot;
+&quot;==0?0:a);}return v==k?'':v&quot;);
Once the above code is implemented, define the desired variable using the getValOnce function. The following are
several examples on how it can be implemented:
Preventing the same campaign value from being defined if a duplicate value is detected within 30 days of
cookie being set:
s.campaign=s.getValOnce(s.campaign,'s_cmp',30);
Prevents the same eVar1 value from being defined if a duplicate value is detected within 30 minutes of the
cookie being set:
s.eVar1=s.getValOnce(s.eVar1,'s_ev1',30,'m');
Prevents the same eVar2 value from being defined multiple times in the same browser session:
s.eVar2=s.getValOnce(s.eVar2,'s_ev2');
Notes
• Always test plug-in installations extensively to ensure that data collection is as expected before deploying in a
production environment.
• Make sure you delete the cookie or use new, unique values during testing or variables will not be sent.
getVisitNum
The getVisitNum plug-in determines how many visits a user has made to your site and captures this number in a
Analytics variable.
Plug-in Code and Implementation
CONFIG SECTION: No changes required for this section.
Plug-in Configuration
Place the following code within the s_doPlugins() function, which is located in the area of the s_code.js file labeled
Plugin Config. Choose one Custom Traffic (s.prop) variable or one Custom Conversion (s.eVar) variable for use in
capturing visit number data. This should be a variable that has been enabled using the Admin Console, but which
is not currently in use for another purpose. You can use the following example and update it based on your
requirements.
s.prop1=s.getVisitNum();
Note: The following instructions require you to alter the data collection code on your site. This can affect data
collection on your site, and should only be done by a developer with experience using and implementing
Analytics.
PLUGINS SECTION: Add the following code to the area of the s_code.js file labeled PLUGINS SECTION. Do
not make any changes to this portion of the plug-in code.
/*
* Plugin: getVisitNum - version 3.0
*/
s.getVisitNum=new Function(&quot;tp&quot;,&quot;c&quot;,&quot;c2&quot;,&quot;&quot;
+&quot;var s=this,e=new Date,cval,cvisit,ct=e.getTime(),d;if(!tp){tp='m';}&quot;
+&quot;if(tp=='m'||tp=='w'||tp=='d'){eo=s.endof(tp),y=eo.getTime();e.setTi&quot;
Implementation Plug-ins
203
+&quot;me(y);}else {d=tp*86400000;e.setTime(ct+d);}if(!c){c='s_vnum';}if(!&quot;
+&quot;c2){c2='s_invisit';}cval=s.c_r(c);if(cval){var i=cval.indexOf('&amp;vn=&quot;
+&quot;'),str=cval.substring(i+4,cval.length),k;}cvisit=s.c_r(c2);if(cvisi&quot;
+&quot;t){if(str){e.setTime(ct+1800000);s.c_w(c2,'true',e);return str;}els&quot;
+&quot;e {return 'unknown visit number';}}else {if(str){str++;k=cval.substri&quot;
+&quot;ng(0,i);e.setTime(k);s.c_w(c,k+'&amp;vn='+str,e);e.setTime(ct+1800000);&quot;
+&quot;s.c_w(c2,'true',e);return str;}else {s.c_w(c,e.getTime()+'&amp;vn=1',e)&quot;
+&quot;;e.setTime(ct+1800000);s.c_w(c2,'true',e);return 1;}}&quot;);
s.dimo=new Function(&quot;m&quot;,&quot;y&quot;,&quot;&quot;
+&quot;var d=new Date(y,m+1,0);return d.getDate();&quot;);
s.endof=new Function(&quot;x&quot;,&quot;&quot;
+&quot;var t=new Date;t.setHours(0);t.setMinutes(0);t.setSeconds(0);if(x==&quot;
+&quot;'m'){d=s.dimo(t.getMonth(),t.getFullYear())-t.getDate()+1;}else if(&quot;
+&quot;x=='w'){d=7-t.getDay();}else {d=1;}t.setDate(t.getDate()+d);return &quot;
+&quot;t;&quot;);
Parameters
• tp = (string, optional) Tracking period. use &quot;d&quot; for day, &quot;w&quot; for week, &quot;m&quot; for month, or a number for a custom number
of days.
• If day, week, or month is selected then the visit number will reset at the end of the day/week/month.
• If a custom number of days is selected then the visit number will reset after that number of days.
• If no value is provided then &quot;m&quot; will be used.
• c = (string, optional) Specify the persistent cookie name. Default is 's_vnum'.
• c2 = (string, optional) Specify the session cookie name. Default is 's_invisit'
Returns
• returns the visit number (1,2,3,etc) of the visit. This number is incremented only on the first page of each visit.
• returns &quot;unknown visit number&quot; if the plug-in is unable to identify the visit number (cookies are blocked).
Examples
s.prop1=s.getVisitNum(365); //custom length, 365 days. Default cookie names
s.prop1=s.getVisitNum('w'); //resets weekly
s.prop1=s.getVisitNum('m','s_vmonthnum','s_monthinvisit'); //resets montly, custom cookie names
s.prop1=s.getVisitNum('d'); //resets daily
Notes
• Always test plug-in installations extensively to ensure that data collection is as expected before deploying in a
production environment.
• This plug-in relies on the ability to set cookies in the user's web browser. If the user does not accept cookies, all
visits will appear to be first visits.
trackTNT
Collects the information for the Target to Analytics integration. This plug-in is replaced by the Adobe Analytics and
Adobe target integration.
See Adobe Analytics and Adobe Target integration.
Traffic props and Conversion eVars
204
Traffic props and Conversion eVars
Custom traffic variables, also called props (s.prop) or property variables, are counters that count the number of
times each value is sent into Analytics.
Props also let you correlate custom data with specific traffic-related events. These variables are embedded in the
Analytics code on each page of your website. Through s.prop variables, Analytics lets you create custom reports,
unique to your organization, industry, and business objectives.
For example, if you are an automobile manufacturer, you may be interested in seeing &quot;Most Popular Car Model&quot; to
complement your &quot;Pages&quot; report. You can accomplish this by allocating one of your traffic properties to represent
car model. Then implement your code to pass in car model on the appropriate pages.
Note: Analytics supports up to 75 s.prop variables.
Props are used in pathing reports or in correlation reports. For example, property variables can be used to show
content type, sub-section, or template name. The resulting Custom Traffic reports show which content type,
sub-section, or template is viewed most often.
There are endless business questions that can be answered through the custom traffic variables, depending on
what you are capturing from your website. The following list contains a few common goals and objectives:
• Understanding user navigation through the website
• Understanding internal user search behavior
• Segmenting traffic by navigation or category
• Segmenting visitor behavior by demographics
eVars (or Custom Conversion Insight variables) are used to identify how well specific attributes or actions contribute
to success events on your site. For example, for a media site, eVars may be used to identify how well internal
promotions bring visitors to register. When a visitor clicks on the internal promotion, an eVar can be used to store
a unique identifier for that promotion. When the same visitor completes registration and a custom success event is
fired, the original unique identifier receives credit for the registration event.
In a conversion site, eVars may be used to track how logged-in visitors compare to non-logged in visitors in completing
a purchase. When a visitor logs in, an eVar is set to &quot;logged in.&quot; When that visitor reaches the checkout page, the
checkout event is attributed to the &quot;logged in&quot; value. When a visitor reaches the Thank You page after purchasing,
the products and purchase amounts are attributed to the &quot;logged in&quot; value. The resulting Custom eVar report shows
the total number of checkouts and orders for &quot;logged in&quot; and &quot;non-logged in&quot; visitors.
Comparing Props and eVars
There are several types of variables available in the Marketing Cloud. The two most popular types, Props and eVars,
allow your organization to report on custom dimensions to your site that standard out-of-the-box reports do not offer.
When determining which variables are assigned where, it is important to understand the differences between Prop
and eVar functionality. Understanding these differences allows your organization to decide which type of variable
is best to use.
Props vs eVars
The following are the main differences between props and eVars:
Traffic props and Conversion eVars
205
• Naming convention: Props are considered traffic variables, meaning they are used to report on popularity of
various dimensions of your site. eVars are considered conversion variables. They are used to determine which
dimensions of your site contribute the most to success events.
• Persistence: Props do not persist beyond the image request they were fired on. They cannot be associated with
other variables that are not in the same image request. eVars, however, are persistent. A back-end variable is
used to preserve the value originally fired so it can associate itself with success events later on.
• Success events: Success events, also known as conversion events, are metrics that measure the number of
times a visitor reaches a goal. This event can be anything from purchasing something on your site, to subscribing
to a newsletter. eVars are designed to report on conversion events, to show you which values are most successful
in influencing visitors to reach your goals. Traffic variables do not have this same functionality. However, you can
view participation metrics if you configure your report suite correctly.
• Pathing: Props can use pathing, which allows your organization to see a given path a user took within the context
of the variable being viewed. An Adobe representative can enable pathing, if requested. eVars cannot use pathing.
• Potentially available metrics: The metrics available between props and eVars vary widely based on the variable's
settings and data platform/version. The following list illustrates what can be enabled, not what is enabled by default.
If you want a specific metric in reporting but do not see it, have one of your organization's supported users contact
Customer Care.
• Both props and eVars:
• Instances, Page Views, Visits and Unique Visitors
• Bounces, Bounce Rate, Entries, Exits, and Total Time Spent
• Participation metrics and calculated metrics
• Props (Traffic variables):
• Average Time Spent, Average Page Depth, Reloads, and Single Access
• eVars (Conversion variables):
• All shopping cart metrics
• All purchase metrics, such as Orders, Units, and Revenue
• All custom conversion events
• Breakdowns: Props use correlations, which display page views for other traffic variables fired in the same image
request. eVars use subrelations, which provide a breakdown on other conversion variables in relation to success
events.
Using props as Counters
A counter stores (and sometimes displays) the number of times a particular event or process has occurred.
You can use a prop to count the number of times an event occurs. For example, you want to track the use of the
Real Player vs. the Windows Media Player on your site. Each page contains Code to Paste, in which you can see
s.prop variables. Use s.prop 1 to track the players. For page A, enter a value in s.prop1 to represent Real Player.
s.prop1=&quot;RealPlayer&quot;
For page B, enter a similar value in s.prop1 for Windows Media Player, as shown below.
s.prop1=&quot;WindowsMP&quot;
Note: Adobe offers up to 75 s.prop variables for you to use.
As visitors come to your site and visit the pages containing the Real Player or Windows Media Player, Analytics is
able to segment the users based on which pages they visited. The Custom Traffic report then shows the number
of visits to each page.
Traffic props and Conversion eVars
206
Note: The name of the Custom Traffic report can be customized. For example, the Custom Traffic report
can be renamed to &quot;Player Types Report.&quot;
Counting Content Hierarchies
A common usage of content hierarchies is to show the different paths visitors have taken from a certain page,
level, and so forth.
How Should I track my Content Hierarchy? You must first understand the reporting requirements for tracking
content hierarchies. If the requirements for tracking the hierarchy are very detailed, often times the hierarchy (hier)
variable is recommended. Hierarchies usually require a strict, pre-defined taxonomy where the same child node
rarely lives under multiple parent nodes. Consider the following example:
Global Hierarchy
All Sites &gt; Regions &gt; Countries &gt; Language &gt; Category
In this example, the hierarchy could begin to break down at the language level. If a requirement is to report on overall
&quot;English&quot; traffic, you can run into the problem where English appears under USA, England, Australia, and so forth.
Hierarchies allow you to only drill down. In order to slice horizontally across multiple hierarchies, the best practice
is to use a custom traffic variable (prop).
If you want to provide users with the ability to drill down through the site (similar to how users would browse the site)
and report on Unique Visitors at each level of the hierarchy, the hierarchy variable is recommended.
There are occasions when using both props and the hier variable makes sense. The following is a supported prop
for each variable type:
Props
Hierarchy
Correlations
x
x
Pathing
x
Page View
x
x
Unique Visitors
x
x
Classifications
x
What is a Predefined Event?
List of predefined events.
prodView
Success event occurs any time a visitor views a product.
scView
Success event occurs any time a shopping cart is viewed.
scOpen
Success event occurs any time a visitor opens a shopping
cart for the first time.
scAdd
Success event occurs any time a product is added to a
shopping cart.
Traffic props and Conversion eVars
207
scRemove
Success event occurs any time an item is taken out of a
shopping cart.
scCheckout
Success event occurs on the first page of a checkout.
purchase
Success event occurs on the final page of a checkout
(includes Revenue, Orders, and Units).
When any of the predefined events above occurs, an instance of the event is incremented. You can view the metrics
related to the event in several different reports. See below for an example of the code used to configure predefined
events.
s.events=&quot;scAdd&quot;
s.events=&quot;scOpen,scAdd&quot;
• In the first example above, scAdd is the value of the event. Any time an item is added to the shopping cart, the
event is incremented.
• In the second example, two values are captured at the same time. When multiple success events occur on the
same page, each event is incremented.
Detailed Product View Page
The products variable is used for tracking products and product categories (as well as purchase quantity and purchase
price).
A success event should always be set in conjunction with the products variable.
s.events=&quot;prodView&quot;
Note: While prodView is treated in implementation like an event, it does not have the same flexibility in the
interface. The prodView event is an instance of the product and is only available in the products report. Adobe
recommends you use a custom event in addition to the prodView event. This way, you can see the product
view metrics alongside other metrics in other conversion reports.
s.products=&quot;;diamond earrings (54321)&quot;
Note: The products string syntax must begin with a semi-colon. This is a legacy syntax requirement. It was
previously used to delimit the category and product, but that creates a limitation within the interface should
you ever want to change how you are classifying products. In order to have the maximum flexibility in your
reporting, it is best to leave this blank and use Classifications to set up categories.
Shopping Cart Page (scOpen, scAdd, scRemove)
s.events=&quot;scOpen,scAdd&quot;
s.products=&quot;;SKU&quot;
First Checkout Page
s.events=&quot;scCheckout&quot;
s.products=”;SKU&quot;
Confirmation Page
s.events=&quot;purchase&quot;
s.products=&quot;;SKU&quot;
Traffic props and Conversion eVars
208
Note: While using the SKU in the product string may make the products report less readable, it provides the
maximum flexibility later when you want to classify your products. You can create categories from the SKU
that indicate finish, manufacturer, category, and sub-category.
When the products variable is set in conjunction with the purchase event, the purchase quantity and total purchase
price are included in the products value as shown above.
What is a Custom Event?
Custom events let you define the success type that you want to track.
Although similar to predefined events, custom events let you define your own success metric. For example, if you
have a newsletter, your success event could be &quot;Registration.&quot; Clearly, &quot;Registration&quot; is not part of the predefined
events. By using a custom event, you can track the number of visitors who register for your newsletter. Custom
events follow the standard syntax shown below.
s.events=&quot;event3&quot;
The code above shows how to assign an event to the events variable. If you do not modify the event name in the
interface, then &quot;event3&quot; would display in the interface.
By default, success events are configured as &quot;counter&quot; events. Counter events count the number of times a success
event is set. Some success event uses require an event be incremented by some custom amount. These events
can be set either as &quot;numeric&quot; events or &quot;currency&quot; events. You can change the event type using Admin Console.
Pathing
209
Pathing
Pathing is defined as the path that users take through your site.
For example, a visitor went to page A, then page B, then page C. Pathing is one of the very powerful features of
Analytics. The tremendous insight it brings is critical to businesses looking to understand visitor traffic patterns.
Out-of-the-box Analytics provides pathing at the page level. The basic idea behind pathing is you are shown the
order of pages that users saw during their visits. This data is presented in several different reports that format the
data in different ways, depending on what you are trying to see.
Enabling Pathing on a prop
Though pathing reports are available out-of-the-box for pages, pathing can also be enabled for custom traffic
variables.
Enabling pathing on a prop can be done in the Admin Console. The following list contains few examples of a business
question that can be solved by enabling pathing for a prop.
• Where does a user go on my site after they come to my site from a campaign?
• What are the common site sections my users go to in their visits?
• How do I see page pathing by user type?
Advanced pathing is available in Ad hoc analysis. Ad hoc analysis provides segmentation on any report on the fly
without needing to enable this setting, or structure data in the prop in certain ways. It is the easiest and most optimal
way to segment your path reports as well. For more information see the Ad hoc analysis documentation.
When pathing is enabled for a prop, you get a new set of pathing reports that are found below the standard pathing
reports. Pathing reports tell you the order that it saw the pages come in for that visitor. When you enable pathing
on a prop, it does the same thing: it tells you the order of the prop values it saw come in for the user. This order of
values is displayed in different ways depending on the path report you are viewing.
Pathing by Campaign or Tracking Code
Helps you answer the question, &quot;After a user clicks into my site from a campaign, where do they go on my site?&quot;
To answer this question, you need to set aside an sprop to be used for this report. You then need to structure the
data to populate into the prop in such a way that it makes sense when pathing is enabled.
For this example, you are going to use prop1 as your campaign pathing prop. Now you want to populate this sprop
with the same value you put in the page name variable. See below:
s.prop1=s.pageName;
You should do this on all pages unless the person has clicked from a campaign. If they have clicked from a campaign
and are on the landing page of the campaign, then you populate the prop with a concatenation of the campaign and
the pagename. See below:
s.prop1=s.campaign + ‘ : ’ + s.pageName;
If the campaign they clicked was named &quot;banner1234,&quot; and the page it landed on was named &quot;Home Page,&quot; the
value in that prop would be &quot;banner1234 : Home Page.&quot; On every subsequent page you put the pagename in the
prop as shown above.
Pathing
210
When a user clicks this campaign and views four total pages in that visit, you get the following values in the sprop
in this order:
“banner1234 : Home Page” &gt; “Page 2” &gt; “Page 3” &gt; “Page 4”
With our data captured in prop1 in this way, with pathing enabled on this prop, you can now look at one of various
pathing reports to understand how they path through the site after they click from a campaign.
You can specify the start page from which to start the path report. In this case, you selected &quot;banner1234 : Home
Page&quot;, because you want to know where users went after they clicked from campaign &quot;banner 1234.&quot; This report is
only an example of one of many path reports.
Reasons Pathing may not be Recorded
List of reasons pathing information might not be recorded and displayed in reporting.
• Pathing has not been enabled for that prop in that report suite. This enablement is report suite specific.
• Data is not being passed into the correct prop.
• Pathing has been enabled and the data is in the prop, but it hasn't shown up in the reports. Though the sprop data
may show up within 10 minutes, the pathing data will not show up until the visitor's session has ended. It ends after
30 minutes of inactivity. Analytics then takes another 10 minutes to finish the processing of the path data for final
presentation in reports.
If you have checked all of these and the data is still not showing up, check with ClientCare for further debugging.
Moving from Section to Section
If you want to know how visitors move from section to section on your site, you first need to ensure that you are
tagging your sections with the channel variable.
With this data in place, you must have pathing enabled on the channel variable. If a user starts on the home page
and moves to the Sports section, then to the News section, this activity shows up in the Site Section path reports.
These reports display after pathing is enabled on this variable.
Moving from Page Template to Page Template
If your site has types of pages or page templates, you could use pathing to understand how they move from type to
type.
You need to first capture the page type or template in a prop set aside for only that purpose. Then have Adobe
ClientCare enable pathing on that prop. You can now view your page template pathing reports to understand how
users move from template to template on your site.
Segmenting Paths by User Type
Segmenting paths by user type is a common request for trying to understand how specific user types path on your
site.
You can concatenate the user type and page name into a sprop and enable pathing on the sprop.
Pathing
211
For example, let's say you have two user types: &quot;Registered&quot; users and &quot;Non-Registered&quot; users. You need to
distinguish between these two user types on each page and put these values into your designated sprop. When
you populate the prop, it should display as shown below:
s.prop1=”Registered : “ + s.pageName;
If the user is a registered user and visited the home page, the value in the prop displays as follows:
“Registered : Home Page”
If they click to another page named &quot;Page 2&quot;, the value on that page displays as follows:
“Registered : Page 2”
With Pathing turned on, you see those two values in succession. If you want to know how registered users move
from the home page, find the value &quot;Registered : Home Page&quot; in one of the path reports and see the next pages
they visited. In this case, they next went to &quot;Page 2.&quot;
Purchase Events
212
Purchase Events
For the purchase event, Analytics variables are used to capture specific purchase information. The s.purchaseID
variable is used to serialize (de-duplicate) the event.
The purchaseID is limited to 20 characters. The purchaseID variable serializes all events passed in the variable
s.events, and overrides any serialization value for events. If purchaseID is left blank, each instance of the purchase
event, even page reloads, is counted.
If a purchase event is called without a purchaseID, a unique one is automatically generated based on the s.products
and s.events variables. This automatically generated purchaseID is stored locally as a cookie value within the
visitor's browser, and is not sent to any report suite tables. Manually defined purchaseIDs on the other hand are
sent to a backend table within the report suite. The last five purchases made by a visitor (with or without purchaseID)
are stored in the local cookie.
When a visitor makes any purchase, the following checks are made:
• Does the purchaseID match any of the five cookie values? If so, the image request is considered a duplicate
purchase. All conversion variables, including the purchase event, do not appear in reporting.
• If purchaseID is defined, does it match any value in the report suite's backend table? If so, the image request is
considered a duplicate purchase. All conversion variables, including the purchase event, do not appear in reporting.
• If the purchaseID is unique to both the last 5 stored values in the cookie and the report suite's purchaseID table,
the image request is unique and included in reporting. If five purchases are already included in the local cookie,
the oldest one is overwritten.
Specific server-side code can be used to generate the unique number (alphanumeric value) embedded in the HTML
source. Usually the Order ID, or similar alphanumeric value, is used for this purpose. This value should not change
if the user refreshes the page. The following is a short example (note the purchaseID code in bold):
Syntax
s.products=&quot;Category;ProductName;Qty;total_price [,Category2;ProductName2;Qty;total_price]&quot;
s.state=&quot;XX&quot;
s.zip=&quot;00000&quot;
s.purchaseID=&quot;&lt;%=getPurchaseID()%&gt;&quot;
s.events=&quot;purchase&quot;
Examples
s.products=&quot;Footwear;Hiking Boots (1234);1;170.00&quot;
s.state=&quot;UT&quot;
s.zip=&quot;84097&quot;
s.purchaseID=&quot;12341234&quot;
s.events=&quot;purchase&quot;
Additional Notes
• Be sure to use server-side code to generate the unique identifier for the event. Do not use a JavaScript randomization
function to generate a number, which generates unique numbers each time the page is loaded (each
instance/pageview counts).
• The unique identifiers are applicable to all users across all sessions. Therefore, ensure the identifier is unique
across users and sessions. For instance, if the Order ID repeats after 30 days, append the date of the order to
make the Order ID sufficiently unique.
• The serialization value may be alphanumeric values up to 20 characters in length. This is identical to the limitations
of s.purchaseID (replace s. with s_ for G Code).
• The s.purchaseID variable serializes all events passed in the variable s.events, and overrides any serialization
value for events. Do not use Event serialization for any events if the s.purchaseID variable is used on the current
page (replace s. with s_ for G Code).
Event Serialization
213
Event Serialization
Event serialization is the process of implementing measures to prevent duplicate events from entering Analytics
reporting. This can commonly occur when a user refreshes the page multiple times, navigates to a certain page
multiple times, or saves the web page to their computer (for example, if a customer saves a purchase confirmation
page to their computer, every time they view it orders and revenue would be counted again if event serialization
was not in place).
Event serialization is useful in the following instances:
• A page may be reloaded or refreshed and repeatedly send an event. Event serialization prevents events from
being recounted by using a serial number for each event.
• The user saves the page to his/her machine for later review.This scenario is quite common on purchase confirmation
pages to review purchase receipts. Event serialization prevents the subsequent page reloads from re-counting
the events.
Note: Data Sources does not support event serialization or de-duplication.
This document describes the process to implement Event serialization for conversion and custom events. To
use Event serialization, you must first contact Adobe Live Support to have it enabled.
Default Behavior
The default behavior is to count each instance of an event. An event is set for each pageviewthat is counted, even
on page reloads or page refreshes. The s.purchaseID variable is used in order to uniquely identify each order
(purchase). This allows a user to reload the order page without recounting the order, revenue, or products. A similar
feature is available for all events. This includes pre-defined events such as prodView and scCheckout, as well as
all custom events.
Methods of Event Serialization
There are two methods of keeping events from counting more than once.
There are three different settings an event can be set to. These settings are not client-facing, and as such can only
be enabled by an Adobe representative.
Always record event: This is the default behavior of all events when initially enabled. All events included in image
requests will be sent directly to SiteCatalyst, including page reloads.
Record once per visit: An event with this setting enabled will only track the first instance of that event in a given visit.
Once a new visit starts, each event with this setting enabled can be tracked again. This is an effective way to mitigate
duplicate events via browser refreshes.
Use event ID: This setting allows the capability to associate each event with a unique ID. If SiteCatalyst sees an
eventID it has already seen before with that variable, it will not be counted in reporting.
The only event that cannot have event serialization enabled is the purchase event, as this uses the s.purchaseID
variable. All other eCommerce events and custom events can have these settings enabled.
• Use a unique identifier to let an event fire once per unique ID.
• Send multiple events, then use configure Analytics to let an event fire once per visit.
To implement Event serialization, provide a unique ID for the event, for example event1:1234ABCD.
Event Serialization
214
Event Serialization - Once per Unique ID
Once Event serialization is implemented, and Analytics receives a duplicate number, it ignores the event. An event
is counted only once per unique value. If the number is unique, another event instance is counted, as shown in the
following example:
User Name
Description
Event Syntax
Analytics Total Event1
Count
John
User views page for the first time.
event1:1000
1
John
User reloads the page (a form submit may fail, event1:1000
and cause the page to reload).
1
Stacy
User views page for the first time.
event1:1001
2
Stacy
User reloads the page (a form submit may fail, event1:1001
and cause the page to reload).
2
Jill
User views page for the first time, enters
information correctly, and moves on to next
page.
event1:1002
3
Jamie
User views page for the first time
event1
4
Jamie
User forgets to fill in the last name field on the event1
form. The form is displayed again with the
missing information highlighted.
5
s.events Syntax
Use the following syntax for serializing events. In the first example, event1 is serialized, while event2 is not serialized
(an instance is counted for each pageview or page reload).
s.events=&quot;[event]:[serial number]&quot;
Samples:
s.events=&quot;event1:12341234&quot;
s.events=&quot;event1:12341234,event2&quot;
s.events=&quot;purchase,event1:12341234&quot;
Serializing a counter event with a value other than 1
Add the serial number after the event value similar to the following:
s.events=&quot;event1=100:12341234&quot;
Note the following when selecting serialization IDs:
• Serialization IDs must be 20 characters or less.
• Serialization IDs must be alphanumeric characters.
• Serialization IDs are separate for each success event. Therefore, you can use the same ID for multiple success
events if needed, just not for the same success event.
• Serialization IDs are tied to the report suite, so if you are using multi-suite tagging to send data to multiple report
suites, keep this in mind.
• Serialization IDs never expire, so even if the same ID is used years later, the success event will not be counted
again.
• Cookie deletion does not prevent Event ID serialization because serialization IDs are stored on Adobe servers and
are not cookie-based.
• The one success event with which it is not possible to use Event ID serialization is the Purchase event, which uses
a special s.purchaseID variable for serialization.
Event Serialization
215
Event Serialization - Once per Visit
Analytics offers a feature to let an event only fire once per visit. Give the name of the report suite and event name
to Adobe Live Support to enable the event.
Serializing eVars
The same functionality used to keep an event from being fired more than once per visit can be applied to evar
instances. When enabled for an evar, click-throughs and instances are only counted once per visit for a specific
evar. This is not counting once per value, but once per evar. This means that if an evar or campaign variable is set
to record once per visit, only the first value seen in a visit shows a click-through or instance. However, if the evar
is set to allocate credit to the most recent value, then the most recent value still receives credit, even if it does not
have an instance. The following example helps to illustrate this point.
If s.campaign is set to Record once per visit, and within a single visit 20, pages are viewed. First, there are 10
pages where s.campaign is set to &quot;abc,&quot; then 10 pages are viewed where s_campaign is set to &quot;xyz.&quot; On all 20
pages, event1 is fired. The following screen shot illustrates the results. Notice that there are no instances or
Click-throughs associated with &quot;xyz,&quot; but it does receive credit for all events fired.
Identifying Unique Visitors
216
Identifying Unique Visitors
Adobe uses a cookie to track unique browsers/devices.
Analytics Visitor ID Order
Adobe Analytics provides several mechanisms to identify visitors. The following table lists the different ways a visitor
can be identified in Analytics (in order of preference):
Order Query Parameter (collection method)
Used
Present When
vid (s.visitorID)
s.visitorID is set
aid (s_vi cookie)
Visitor had an existing s_vi cookie before you deployed the
Visitor ID service, or you have a visitor ID grace period
configured.
mid (AMCV_ cookie set by Marketing Cloud Visitor's browser accepts cookies (first-party)
Visitor ID service)
fid (fallback cookie on H.25.3 or newer, or
AppMeasurement for JavaScript)
Visitor's browser accepts cookies (first-party)
IP Address, User Agent, Gateway IP
Address
Visitor's browser does not accept cookies.
In many scenarios you might see 2 or 3 different IDs on a call, but Analytics will use the first ID present from the
previous table as the official visitor ID. For example, if you are setting a custom visitor ID (included in the &quot;vid&quot; query
parameter), that ID will be used before other IDs that might be present on that same hit.
Note: Each Analytics visitor ID is associated with a visitor profile on Adobe servers. Visitor profiles are deleted
after 1 year of inactivity regardless of any visitor ID cookie expiration.
Custom Visitor ID
You can implement a custom method to identify visitors by setting the s.visitorID variable.
A custom Visitor ID can be used on sites where you have unique way to identify visitors. An example of this is an
ID generated when a user logs in to web site using a user name and password.
Should you have the ability to derive and manage the visitor IDs of your users, you can use the following methods
to set the ID:
Method
Description
s.visitorID variable
If JavaScript is used on the browser, or if you are using any other AppMeasurement library,
you can set the visitor ID in a data collection variable.
Query string
parameter on the
image request
This lets you pass the visitor ID to Adobe via the vid query string parameter on a
hard-coded image request.
Data Insertion API
On devices using wireless protocols that don't accept JavaScript, you can send an XML
post containing the &lt;visitorid/&gt; XML element to Adobe collection servers from your servers.
Identifying Unique Visitors
217
Method
Description
URL re-writing and
VISTA
Some deployment architectures provide support for using URL re-writing to maintain session
state when a cookie cannot be set. In such cases, Adobe engineering services can implement
a VISTA rule that would look for the session value in the URL of the page, then format and
place into the visid values.
Marketing Cloud Visitor ID Service
The Marketing Cloud Visitor ID service replaces the legacy Analytics visitor ID mechanism, and is required by
heartbeat video measurement, Analytics for Target, and future Marketing Cloud integrations.
See Marketing Cloud Visitor ID Service.
Analytics Visitor ID
When a user visits your site, a persistent cookie is set by the Adobe web server by including it in the HTTP response
to the browser. This cookie is set on the specified data collection domain.
When a request is sent to the Adobe data collection server, the header is checked for the visitor ID cookie (s_vi).
If this cookie is in the request, it is used to identify the visitor. If the cookie is not in the request, the server generates
a unique visitor ID, sets it as a cookie in the HTTP response header, and sends it back with the request. The cookie
is stored in the browser and is sent back to the data collection server during subsequent visits the site, which enables
the visitor to be identified across visits.
Third-Party Cookies and CNAME records
Some browsers, such as Apple Safari, no longer store cookies that are set in the HTTP header from domains that
do not match the domain of the current website (this is a cookie used in a third-party context, or a third-party cookie).
For example, if you are on mysite.com and your data collection server is mysite.omtrdc.net, the cookie that is
returned in the HTTP header from mysite.omtrdc.net might be rejected by the browser.
To avoid this, many customers have implemented CNAME records for their data collection servers as part of a
first-party cookie implementation. If a CNAME record is configured to map a hostname on the customer's domain
to the data collection server (for example, mapping metrics.mysite.com to mysite.omtrdc.net), the visitor ID
cookie is stored since the data collection domain now matches the domain of the website.This increases the likelihood
that the visitor ID cookie will be stored, but it introduces some overhead as you need to configure CNAME records
and maintain SSL certificates for data collection servers.
Cookies on Mobile Devices
When mobile devices are tracked using cookies, there are some settings you can use to modify how measurement
occurs. Cookie default lifetime is 5 years, but you can use the CL query param variable (s.cookieLifetime) to
change this default. To set the cookie location for cname implementations, use the CDP query string
s.cookieDomainPeriods. The default is 2 if no value is specified. and the default location is domain.com. For
implementations that do not use CNAME, the visitor ID cookie location is at the 207.net domain.
Identifying Unique Visitors
218
Fallback ID Methods
If other visitor ID methods fail, Adobe sets a fallback cookie or uses a combination of IP address and user agent to
identify the visitor.
Fallback Visitor Identification Method
AppMeasurement for JavaScript 1.x and JavaScript H.25.3 (released January 2013) contain a new fallback visitor
identification method for visitors whose browser blocks the cookie set by Adobe’s data collection servers (called
s_vi). Previously, if a cookie could not be set, visitors were identified using a combination of the IP address and
user agent string during data collection.
With this update, if the standard s_vi cookie is unavailable, a fallback cookie is created on the domain of the website
with a randomly generated unique ID. This cookie, named s_fid, is set with a 2 year expiration and is used as the
fallback identification method going forward. This change should result in increased accuracy in visit and visitor
counts in situations where the primary cookie (AMCV_ or s_vi) cannot be set.
Visits total includes all visitors that are identified by the s_vi cookie or by using a fallback method.
IP Address, User Agent, Gateway IP Address
. If the AMCV_ or s_vi and the s_fid cookies cannot be set, visitors are identified using a combination of IP address
and User Agent.
Identifying Mobile Devices
Most mobile devices accept browser cookies. However, in cases when devices do not accept cookies, another
method is used to uniquely identify wireless devices.
Adobe has identified a number of HTTP subscriber ID headers that uniquely identify a majority of mobile devices.
Those headers often include the device phone number (or a hashed version of the number), or other identifiers. The
majority of current devices have one or more of the headers that uniquely identify the device, and all Adobe data
collection servers automatically use those headers in place of a Visitor ID.
In a typical image request, a '1' in the path (/b/ss/rsid/1) causes Adobe servers to return a gif image and to
attempt to set a persistent visitor ID cookie (AMCV_ or s_vi). However, if the device is recognized as a mobile device
based on the HTTP headers, a '5' is passed in place of the '1', which indicates that a wbmp format image should be
returned and that our list of recognized wireless headers (not a cookie) should be used to identify the device.
The following table lists out the order of the ID methods used based on the return image type value ('1' or '5') in the
path:
Setting
/1/
ID method order
Default:
• Custom visitor ID
• Cookie
• Subscriber ID Header
• IP Address-UserAgent-Gateway IP Address
Identifying Unique Visitors
219
Setting
ID method order
/5/ /5.1/
/5.5/
Device was identified as a wireless device, or /5/ was manually sent in the image request:
• Custom visitor ID
• Subscriber ID Header
• Cookie
• IP Address-User Agent-Gateway IP Address
You can also pass a '1' or a '5' in manual image requests, but be aware that these codes are mutually-exclusive,
therefore always passing '5' does not leverage a cookie when it is supported.You can incorporate your own mechanism
to determine if a device supports cookies, and if so, pass a '1' in the image rather than a '5'. The accuracy improvement
in this situation is limited to the number of mobile devices supporting cookies.
Subscriber ID Headers
The subscriber ID method is generally more reliable than a cookie for user identification because of cookie deletion,
cookie acceptance issues, and gateway cookie management issues.
You can improve changes of identifying a visitor by being added to the white list for the carrier that your mobile
visitors use. To get access to the carrier's visitor ID, contact the carrier to add your domain to their white list. If you
are on a carrier's white list, you also have access to subscriber ID headers that you may not otherwise be able to
access.
The following list of headers is used to identify wireless devices. The algorithm for processing the headers is to
1.
2.
3.
4.
extract the HTTP header key (the name of the header, such as,&quot;X-Up-Calling-Line-ID&quot;)
trim out all non alpha (A-Z and a-z) characters
convert the header key to lowercase
compare the end of the key to the ones in the following table to find a match:
Header
Type
Example
callinglineid
ID
X-Up-Calling-Line-ID: 8613802423312
subno
ID
x-up-subno: swm_10448371100_vmag.mycingular.net
clientid
ID
ClientID: [email protected]
uid
ID
x-jphone-uid: a2V4Uh21XQH9ECNN
clid
ID
X-Hts_clid: 595961714786
deviceid
ID
rim-device-id: 200522ae
forwardedfor
ID or IP Address
X-Forwarded-For: 127.0.0.1
msisdn
ID or IP Address
X-Wap-msisdn: 8032618185
clientip
IP Address
Client-ip: 10.9.41.2
wapipaddr
IP Address
X-WAPIPADDR: 10.48.213.162
huaweinasip
IP Address
x-huawei-NASIP: 211.139.172.70
userip
IP Address
UserIP: 70.214.81.241
ipaddress
IP Address
X-Nokia-ipaddress: 212.97.227.125
subscriberinfo
IP Address
X-SUBSCRIBER-INFO: IP=10.103.132.128
Identifying Unique Visitors
220
For example &quot;callinglineid&quot; would match &quot;X-Up-Calling-Line-ID&quot; and &quot;nokia-callinglineid.&quot; The header type tells us
what to expect in the header. The order of header priority is listed here (if a &quot;callinglineid&quot; header is present it is used
instead of &quot;subno&quot;).
You can use Dynamic Variables to extract specific values from a header.
Cross-Device Visitor Identification
221
Cross-Device Visitor Identification
Cross-device visitor identification helps you connect visitors across multiple devices.
This feature works by associating the visitor profiles across each device where a user is uniquely identified. After
association, the visitor profile records are merged and visits from each device are considered to be from the same
user. This feature allows campaigns from one device, such as a mobile device, to receive credit from conversion
events made from another device, such as a desktop. This feature is commonly referred to as 'visitor stitching'.
Important: Cross-Device Visitor Identification fundamentally alters how Adobe Analytics identifies unique
visitors and attributes success events. Read this section throughly to fully understand the impacts to determine
if this functionality is right for your unique implementation and business requirements.
Benefits of Cross-Device Visitor Identification
• A uniquely identified user is a single visitor profile across each device.
• Attribute success events to first-touch channels cross-device and browsers.
• Gain a more complete, unified view of your customers.
Limitations of Cross-Device Visitor Identification
• Some data is not persisted across authentication from the unauthenticated profile to the authenticated, including:
• eVars or campaign variables with an expiration set to 'Visit'.
• eVars or campaign with longer expirations on a new authentication on a second, third, etc device.
• In some cases marketing channel values, geo-segmentation, and technology reports are affected.
• When initially implemented, Unique Visitor counts are inflated on a visit when authentication first occurs.
• Longer term, Unique Visitor counts will be driven down as users are authenticated across devices.
• Also longer term, Visits will be driven down to a small degree when an authenticated user switches devices within
30 minutes.
How Visitors are Counted without Cross-Device Visitor Identification
With the increasing number of devices used by the same visitor, it can be difficult to accurately gauge unique visitors
and correctly attribute first-touch marketing channels. For example, a potential customer clicks a link in a marketing
email and views your site for the first time:
This customer is considered a unique visitor and the first-touch email channel is incremented. The next day, this
same customer visits your site from a laptop at his office:
Cross-Device Visitor Identification
222
Since the device is new, the customer is considered a unique visitor and the first-touch direct channel is incremented.
A few days later, this same customer visits from a mobile device:
The customer is again treated as a unique visitor.
Connecting Users Across Devices
Cross-device visitor identification uses the visitor ID variable, s.visitorID, to associate a user across devices.
When you provide a visitor ID variable with a hit, the system checks for any other visitor profiles that have a matching
visitor ID. If one exists, the visitor profile that is already in the system is used from that point forward and the previous
visitor profile is no longer used.
The visitor ID is typically set after authentication, or after a visitor performs some other action that enables you to
uniquely identify them independently of the device that is used. We recommend creating a hash of the username
or an internal ID that does not contain any personally identifiable information.
In the previous example, after the customer signs on from each device, they are all associated with the same user
profile. If the visitor later signs out on a device, stitching continues to work since the visitor IDs that are stored in a
cookie on each device are already associated with the same visitor profile. We recommend populating the s.visitorID
variable whenever possible in case the visitor ID cookie is deleted.
Unique Visitor and Visits Counts
Consider the following connection sequence for two devices:
Cross-Device Visitor Identification
223
On the first data connection
• Visitor de-duplication is not retroactive.
After authentication on the laptop, hits with either visitor ID (nv1 or cust1) will be considered the same individual by
Adobe Analytics. However, visitor de-duplication is not retroactive, so 2 unique visitors are counted.
On the first data connection on the mobile device the customer is not recognized so a new unique visitor is counted.
Once the user is authenticated (cust1) on the mobile device, Adobe Analytics maps cust1 back to the visitor ID
provided on the main site, so no more unique visits are incremented.
Each new device or browser authenticated will add 1 unique visitor.
On subsequent data connections
On subsequent data connections to authenticated devices unique visitors are not incremented.
Data Impact of Cross-Device Visitor Identification
Overview of how enabling cross-device visitor identification affects the data that you see in reports.
Cross-Device Visitor Identification
224
To understand how this feature affects data collection, it is useful to understand the visitor data fields in a visitor
profile:
Data Field
Description
Visitor ID cookie
ID generated automatically on the first visit from a device or browser and stored
in the s_vi cookie.
Visitor ID variable
Optional visitor ID that is set using the s.visitorID variable. This value is
populated after a user authenticates and might match an ID that your company
uses to track a user across multiple digital marketing channels.
Effective Visitor ID
The effective visitor ID is the actual ID for the user profile. This value is set to
the visitor ID cookie, or to the visitor ID variable if one is provided.
Example Visit
Example containing a sample of server calls sent in a common customer interaction.
Server Call
Action
1
Visitor ID
Cookie
Visitor ID
Variable
Effective
Visitor ID
Visit Page
Number
Visit Number
A visitor clicks 1
a link in a
marketing
email and visits
your site from
home
computer. This
visitor has
visited your
site 7 other
times in the
past.
-
1
1
8
2-8
Visits 7
1
additional
pages on your
site.
-
1
2-8
8
9
Authenticates
on home
computer.
1
CID1
CID1
1
1
10
Visits 1
additional
page.
1
CID1
CID1
2
1
11
Opens site
from laptop at
office. This
visitor has not
visited your
site before
using this
device.
2
-
2
1
1
Cross-Device Visitor Identification
225
Server Call
Action
Visitor ID
Cookie
Visitor ID
Variable
Effective
Visitor ID
Visit Page
Number
Visit Number
12
Authenticates
on laptop.
2
CID1
CID1
1
9
13
Views 1
additional
page.
2
CID1
CID1
2
9
Visitors
Analytics counts each unique effective visitor ID as a unique visitor.
If you look at the previous table, this occurred 3 times: at hits 1, 9, and 10. This occurs because the effective visitor
ID is the same for both server calls, and occurs even though the visits might be several hours apart and on different
devices.
This can increase the number of unique visitors you see when cross-device visitor identification is enabled. The
visitor might be counted twice on the same visit: once for the initial visit and again after the user is authenticated.
When a new visitor views your site, the s_vi cookie is populated and stored. On the data collection server, a new
visitor profile is created for this visitor ID, and the effective visitor ID on the profile is set to match the cookie.
When cross-device visitor identification is enabled, if a visitor ID variable is provided in a subsequent hit (for example,
after authentication), the effective visitor ID is updated to match the custom value. This can cause the effective
visitor ID to change directly after authentication, resulting in multiple visitor counts.
After the initial association, visit counts return to normal because the visitor is associated through the visitor ID
cookie. If the visitor later views your site and then authenticates, the visitor count is not inflated because the effective
visitor ID doesn't change after authentication.
Cross-Device Visitor Identification
226
Visits
Analytics counts a visit each time a server call occurs with a Visit Page Number equal to 1.
If you look at the previous table, this occurred 4 times: at hits 1, 9, 10, and 11. Similar to visitors, this value returns
to normal after the initial association because the Visit Page Number is not reset back to 1 due to a change in the
effective visitor ID.
Segments
You can create a segment whenever an association occurs for a given visitor ID cookie.
Based on the previous table, if you created a segment where visit number equals 9, it would include server calls 11
and 12. Even through server call 10 was technically part of the same visit, the historical data for that server call is
not altered and the visit number remains unchanged.
Geo-Segmentation Data
Geo-Segmentation data is recorded based on the first hit of the visit, and does not change for a single visit regardless
of the device used.
If a customer browses your site from his or her home computer, and then from a mobile device within 30 minutes,
the Geo-Segmentation data is not changed. If you are using VISTA to populate an eVar with Geo-Segmentation
data, it is based on the IP address in each hit. This could result in multiple Geo-Segmentation data values if the IP
address changes for the same visit.
Attribution and Persistence
When visitor profiles are merged after being associated with the same visitor ID variable, attribution is not changed
in the historical data set.
• When the variable s.visitorID is set and sent on a hit, the system checks for any other visitor profiles that have
a matching visitor ID.
• If a profile exists, the visitor profile that is already in the system is used from that point forward and the previous
visitor profile is no longer used.
• If no matching visitor ID is found, a new profile is created.
Cross-Device Visitor Identification
227
When an un-authenticated customer first arrives at your site, that customer is assigned a visitor profile by Adobe
Analytics. As shown in Unique Visitor and Visits Counts, on authentication a new profile is created. When the new
profile is created, one visit ends and another visit starts.
On the first data connection
The example below is a representation of how data is sent to Adobe Analytics when a customer authenticates for
the first time, on the first device:
• eVar16 has an expiration of 1 day and evar17 expires on visit.
• The post_visitor_id column represents the profile maintained by Adobe Analytics.
• The post_evar16 and post_evar17 columns show shows the persistence of eVars.
• cust_visid represents a value set in s.visitorID.
• Each row is one 'hit', a single request sent to Adobe Analytics data collection servers.
On the first data connection containing a previously unrecognized s.visitorID value (u999 above), the new profile
is created. Persistent values from the previous profile are transferred to the new profile.
• eVars set to expire on the visit are not copied to the authenticated profile. Note the value car above is not persisted.
• eVars set to expire by other measures will be copied to the authenticated profile. Note the value apple is persisted.
• For the eVars that are persisted, no Instance metric is recorded. This means when using cross-device visitor
identification, it is possible to see reports where the Unique Visits metric for an eVar value is larger than the Instance
metric.
On subsequent data connections
The example below is a representation of how data is sent to Adobe Analytics when a customer authenticates on
a new device, after having previously authenticated on a different device:
When the customer authenticates his or her id is matched to the previous 'authenticated' profile - 2947539300. The
profile used at the start of this visit (5477766334477) is no longer used and no data persists from the file.
Cross-Device Visitor Identification
228
• Geo-Segmentation data is recorded based on the first hit of the visit and does not change for a single visit regardless
of the device used. This means on a subsequent data connection on a new device, geo-Segmentation data is
generally not included.
• Technology columns such as browser, operating system, and color depth are recorded on the first hit of a visit.
Like Geo-Segmentation values, they will not be copied to the stitched profile.
• A Marketing Channel such as Direct or Internal which is commonly set up to not overwrite another channel will
overwrite other channels on a subsequent data connection containing a first authentication for that device, such
as the first authentication shown in Unique Visitor and Visits Counts.
Special cases
In some other cases data is not persisted from the unauthenticated to the authenticated profile.
• If a user is new to your site (has never visited before on this device) AND that user authenticates within approximately
3 minutes of arriving, no values will persist to the authenticated profile.
Visitor Migration
229
Visitor Migration
Visitor migration is a process where the visitor ID cookie is migrated from one domain to another.
Visitor migration lets you preserve visitor identification cookies when changing data collection domains. Data collection
domains might change for the following reasons:
• Moving from 2o7.net to omtrdc.net (Regional Data Collection).
• You are implementing the Marketing Cloud Visitor ID Service and are moving from a CNAME/first-party data
collection domain to 2o7.net or omtrdc.net (Regional Data Collection)
• Moving from 2o7.net or omtrdc.net to a cname/first-party data collection (First-Party Cookies).
• Moving from one CNAME to another (changing domains).
After visitor migration is configured, when a user visits the new domain without a visitor ID cookie, the server redirects
to the previous data collection hostname, retrieves any available visitor ID cookies, and then redirects back to the
new domain. If a Visitor ID is not found on the previous hostname, a new ID is generated. This occurs only once
per visitor.
Visitor Migration Process
The following table lists the tasks required for visitor migration:
Task
Description
To get started: Contact Customer Care
with the domain(s) you want to migrate,
and the migration period you would like to
enable (30, 60, or 90 days). Make sure you
include the non-secure and secure
domains.
Create a list with the exact syntax for the domains you want to migrate
to and migrate from.
• example.112.2o7.net &gt; metrics.example.com
• example.102.112.2o7.net &gt; smetrics.example.com
The migration host names are configured on Adobe Data collection
server. Customer Care will let you know when the change is made so
you can plan for the next step.
6+ hours after configuration change:
After you make this change, use a Packet Analyzer to verify that the
Update the s.trackingServer and
Analtyics image request is going to the updated data collection server.
s.trackingServerSecure variables in
your Analytics JavaScript code to use the
new data collection servers.
Immediately after updating your
Analytics code: Test your site to verify
that the redirect to the previous data
collection domain is occurring.
Use a Packet Analyzer to verify that when you access your site for the
first time, or after clearing cookies, you see three 302 (redirect) HTTP
status codes before the 200 (OK) HTTP status code. If any of these
redirects fail, contact Customer Care immediately to ensure that the
migration is configured correctly.
For the entire migration period: Keep
The previous hostname must resolve through DNS or the cookie
the DNS record for the previous hostname migration will not occur.
active.
Visitor Migration
230
Deprecated visitorMigrationKey and visitorMigrationServer Variables
As of March 2013, the visitorMigrationKey, visitorMigrationServer, and visitorMigrationServerSecure
data collection variables are deprecated and no longer used. The data previously contained in these variables are
now stored on Adobe servers for increased security.
Redirects and Aliases
231
Redirects and Aliases
Redirects point the browser to a new location without user interaction. They are executed at either the web browser
(client-side redirect) or at the web server (server-side redirect).
Because redirects do not require any user interaction, redirects are often executed without the user ever noticing.
The only thing that indicates a redirect has occurred is the browser's address bar. The address bar displays a URL
that is different from the link the browser initially requested.
Although there are only two types of redirects, they can be implemented in numerous ways. For example, client-side
redirects can occur because the web page to which a user has pointed his or her browser contains scripting or
special HTML code that redirects the browser to another URL. Server-side redirects can occur because the page
contains server-side scripting or because the web server has been configured to point the user to another URL.
Analytics and Redirects
Analytics gathers some of its data from the browser, and relies upon certain browser properties. Two of those
properties, the &quot;Referring URL&quot; (or &quot;referrer&quot;) and the &quot;Current URL&quot; can be changed by a server-side redirect.
Because the browser is aware that one URL has been requested, but a different URL has been returned, it clears
the Referring URL. The result is the referring URL is blank, and Analytics might report that no referrer existed for
the page.
The following examples illustrate how browsing is affected without and with redirects:
• Example: Browsing Without Redirects
• Example: Browsing With Redirects
Example: Browsing Without Redirects
Consider the following hypothetical scenario in which the user does not encounter a redirect:
1. User points his or her browser to www.google.com, and types, &quot;discount airline tickets&quot; into the search field,
and then clicks the Search button.
2. The browser displays the search results including a link to your site, http://www.flywithus.com/. After
displaying the search results, the browser's address bar displays the search terms that the user entered in the
search field (http://www.google.com/search?hl=en&amp;ie=UTF-8&amp;q=discount+airline+tickets). Notice that
the search terms are included in the URL query string parameters that follow http://www.google.com/search?.
3. The user clicks the link to your hypothetical site http://www.flywithus.com/. When the user clicks this
link and lands on the flywithus.com website, Analytics uses JavaScript to collect the referring URL
(http://www.google.com/search?hl=en&amp;ie=UTF-8&amp;q=discount+airline+tickets) as well as the
current URL (http://www.flywithus.com/).
4. Analytics reports the information collected during this interaction in various reports, such as Referring Domains,
Search Engines, and Search Keywords.
Example: Browsing With Redirects
Redirects can cause the browser to blank out the true referring URL. Consider the following scenario:
1. User points his or her browser to www.google.com, and types, &quot;discount airline tickets&quot; into the search field,
and then clicks the Search button.
Redirects and Aliases
232
2. The browser window's address bar displays the search terms that the user typed into the search field
(http://www.google.com/search?hl=en&amp;ie=UTF-8&amp;q=discount+airline+tickets). Notice that the
search terms are included in the URL query string parameters that follow &quot;http://www.google.com/search?&quot;.
The browser also displays a page that contains the search results including a link to one of your domain names:
http://www.flytohawaiiforfree.com/. This vanity domain is configured to redirect the user to
http://www.flywithus.com/.
3. The user clicks on the link http://www.flytohawaiiforfree.com/ and is redirected by the server to your
main site, http://www.flywithus.com. When the redirection occurs, the data that is important to Analytics
data collection is lost because the browser clears the referring URL. Thus, the original search information used
in the Analytics reports (for example, Referring Domains, Search Engines, Search Keywords) is lost.
Implementing Redirects discusses how to leverage Analytics variables to capture the data lost in the redirect.
Specifically, the section discusses how to fix the &quot;discount airline tickets&quot; situation described above.
Implementing Redirects
In order to capture Analytics data from redirects, four minor alterations need to be made to the code that creates
the redirect and the AppMeasurement for JavaScript file.
Completing the following steps will retain the information that the original referrer (for example,
http://www.google.com/search?hl=en&amp;ie=UTF-8&amp;q=discount+airline+tickets in the scenario
above) passes to your site:
Configure Referrer Override JavaScript Code
Adobe ClientCare can provide you with a JavaScript file that contains code that will override the default functionality
Analytics uses to capture the referrer from the HTTP header.
The code snippet below shows two JavaScript variables, s_referrer and s_pageURL. This code is placed on the
ultimate landing page of the redirect.
&lt;script language=&quot;JavaScript&quot;
src=&quot;//INSERT-DOMAIN-AND-PATH-TO-CODE-HERE/AppMeasurement.js&quot;&gt;&lt;/script&gt;
&lt;script language=&quot;JavaScript&quot;&gt;&lt;!-/* You may give each page an identifying name, server, and channel on
the next lines. */
s.pageName=&quot;&quot;
s.server=&quot;&quot;
s.campaign=&quot;&quot;
s.referrer=&quot;&quot;
s.pageURL=&quot;&quot;
Redirects using getQueryParam
While the getQueryParam is an easy way to populate Analytics variables with query string values, it must be
implemented in connection with a temporary variable so that legitimate referrers are not overwritten when the query
string is empty. The best way to use getQueryParam is in connection with the getValue plug in as outlined with the
following pseudo-code, which should be added to the &quot;doPlugins()&quot; function within the &quot;s_code_remote.js&quot; or
&quot;s_code.js&quot; file as shown below.
// AppMeasurement 1.x
/* Plugin Config */
s.usePlugins=true
s.doPlugins = function(s) {
var tempVar=s.Util.getQueryParam('origref')
if(tempVar)
Redirects and Aliases
233
s.referrer=tempVar;
}
// H Code
/* Plugin Config */
s.usePlugins=true
s.doPlugins = function(s) {
/* Add calls to plugins here */
// Copy original referrer into s.referrer if it exists
var tempVar=s.getQueryParam('origref')
if(tempVar)
s.referrer=tempVar;
}
Modify the Redirect Mechanism
Modify the Redirect Mechanism XE &quot;Redirect Mechanism&quot;
Because the browser strips referring URL, you must configure the mechanism that handles the redirect (for example,
the web server, server-side code, client-side code) to pass along the original referrer information. If you would also
like to record the alias link URL, this must also be passed along to the ultimate landing page. Use the s_pageURL
variable to override the current URL.
Because there are many ways to implement a redirect, you should check with your web operations group or your
online advertising partner to identify the specific mechanisms that execute redirects on your website.
Capture the Original Referrer
Capture the Original Referrer XE &quot;Original Referrer&quot;
Normally, Analytics will obtain the referring URL from the browser's document.referrer property, and the current
URL from the document.location property. By passing values to the referrer and pageURL variables, you can
override the default processing. By passing a value to the referrer variable, you are telling Analytics to ignore the
referrer information in the document.referrer property and to use an alternative value that you define.
Therefore, the final version of the landing page would need to contain the following code to correct the issues
introduced in the &quot;discount airline tickets&quot; scenario.
&lt;script language=&quot;JavaScript&quot;
src=&quot;http://INSERT-DOMAIN-AND-PATH-TO-CODE-HERE/AppMeasurement.js&quot;&gt;&lt;/script&gt;
&lt;script language=&quot;JavaScript&quot;&gt;&lt;!-/* You may give each page an identifying name, server, and channel on
the next lines. */
s.pageName=&quot;&quot;
s.server=&quot;&quot;
s.campaign=&quot;&quot;
s.referrer=http://www.google.com/search?hl=en&amp;ie=UTF-8&amp;q=discount+airline+tickets
// Setting the s.pageURL variable is optional.
s.pageURL=&quot;http://www.flytohawaiiforfree.com&quot;
Verify the Referrer with the Adobe Debugger
Run a test to verify that the referrer, originating URL (s_server) and campaign variables are being captured.
These variables will be represented as the following parameters in the Adobe Debugger.
Redirects and Aliases
234
URL or Query String Value
Value as Shown in the DigitalPulse
Debugger
Original Referrer
http://www.google.com/search%3F
hl%3Den %26ie%3DUTF826q%3
Ddiscount%2Bairline%2Btickets
r=http:/ref=www.google.com/search?hl=en&amp;ie=UTF
-8&amp;q=discount+airline+tickets
Page URL
http://www.flytohawaiiforfree.com g=http://www.flytohawaiiforfree.com
This value will appear in the
DigitalPulse Debugger if the pageURL
variable is used.
Ultimate Landing Page URL http://www.flywithus.com
This value will NOT appear in the
DigitalPulse Debugger if the pageURL
variable is used.
The text that the debugger displays should correspond to the following example:
Image
http://flywithuscom.112.2o7.net/b/ss/flywithuscom/1/JS-1.4/s61944015791667?[AQB]
ndh=1
t=4/8/2014 13:34:28 4 360
pageName=Welcome to FlyWithUs.com
r=http://ref=www.google.com/search?hl=en&amp;ie=UTF-8&amp;q=discount+airline+tickets
cc=USD
g=http://www.flytohawaiiforfree.com
s=1280x1024
c=32
j=1.3
v=Y
k=Y
bw=1029
bh=716
ct=lan
hp=N
[AQE]
After verifying that the Adobe Debugger displays these variables, it is always helpful to confirm that the search terms
and the original referring domain (prior to the redirect) are registering traffic in reports.
FAQ
235
FAQ
Common implementation questions and links to more information.
Question
Summary
How can I change colleted Use processing rules simplify data collection and manage content as it is sent to
data, based on defined
reporting. learn more
conditions of my own?
Which is the latest version This section contains a release history for AppMeasurement libraries across web and
of s_code file?
mobile platforms. The latest version of each library can be downloaded in Marketing
Reports &amp; Analytics &gt; Admin Tools &gt; Code Manager. learn more
How to debug s_code file? The Adobe Debugger (previously DigitalPulse Debugger) is a free tool provided by
Adobe that lets you view the data being collected from your site on any given page.
learn more
How to track different link
types?
File downloads and exit links can be automatically tracked based on parameters set
in the AppMeasurement for JavaScript file. learn more
How to track video ?
JavaScript can be used to track a wide variety of players. To track using JavaScript,
you add code to the web page that contains your player and track the player using
event handlers. learn more
How to track a mobile
App?
Acquisition links with unique tracking codes can be generated in Adobe Mobile services.
When a user downloads and runs an app from the Apple App Store after clicking on
the generated link, the SDK automatically collects and sends the acquisition data to
Adobe Mobile services. iOS Android
Implementation of video
tracking?
You can track media players by creating functions attached to the video player event
handlers This lets you call Media.open, Media.play, Media.stop, and Media.close at
the appropriate times. learn more
Setting up First Party
Cookie?
Analytics uses cookies to provide information on variables and components that do not
persist between image requests and browser sessions. These harmless cookies
originate from a domain hosted by Adobe, known as third-party cookies. learn more
How to get an SSL
certificate?
Determine if your site uses https:// protocol. If it does, requesting a CSR and purchasing
an SSL certificate is required. Note: An SSL certificate is not required if you do not
have any secure pages or content. This entire step may be skipped if you use only
http:// protocol on your site. learn more
Information about
Certification expiration
notice?
SSL certificates expire each year, meaning that Adobe requires an updated certificate
request each time this happens. The FPC specialist provides sufficient warning when
this occurs, however, it is recommended to be proactive in monitoring the expiration
and providing Adobe with this updated certificate. learn more
Information about plugins? AppMeasurement for JavaScript plug-ins are programs or functions that perform several
advanced functions. These plug-ins extend the capabilities of your JavaScript file to
give you more functionality that is not available with a basic implementation. Adobe
offers a number of other plug-ins as part of advanced solutions. Contact your Account
Manager if you want to capture data using JavaScript but are unsure how to proceed.
learn more
Information about data
insertion API?
Adobe has created multiple ways to send data into Analytics. learn more
What is 500 error?
Information about the internal server error which caused a &quot;500 Query Error&quot; status.
Insight query API pageType variable
Contact and Legal Information
236
Contact and Legal Information
Information to help you contact Adobe and to understand the legal issues concerning your use of this product and
documentation.
Help &amp; Technical Support
The Adobe Marketing Cloud Customer Care team is here to assist you and provides a number of mechanisms by
which they can be engaged:
• Check the Marketing Cloud help pages for advice, tips, and FAQs
• Ask us a quick question on Twitter @AdobeMktgCare
• Log an incident in our customer portal
• Contact the Customer Care team directly
• Check availability and status of Marketing Cloud Solutions
Service, Capability &amp; Billing
Dependent on your solution configuration, some options described in this documentation might not be available to
you. As each account is unique, please refer to your contract for pricing, due dates, terms, and conditions. If you
would like to add to or otherwise change your service level, or if you have questions regarding your current service,
please contact your Account Manager.
Feedback
We welcome any suggestions or feedback regarding this solution. Enhancement ideas and suggestions for the
Analytics suite can be added to our Customer Idea Exchange.
Legal
&copy;
2015 Adobe Systems Incorporated. All Rights Reserved.
Published by Adobe Systems Incorporated.
Terms of Use | Privacy Center
Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries. A trademark symbol (&reg;, ™, etc.) denotes an Adobe trademark.
All third-party trademarks are the property of their respective owners. Updated Information/Additional Third Party
Code Information available at http://www.adobe.com/go/thirdparty.
">
Hello! I am an AI chatbot specifically trained to assist you with the Adobe Adobe Analytics Implementation Guide. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!
Show related prompts
Assistant typing
Assistant is out of keyboard. Please, try again later.
Key features

Collects data from website visitors
Reports on website activity
Helps businesses understand their audience
Provides insights into marketing campaign effectiveness
Allows for optimization of website experiences
Integrates with other Adobe products
Frequently asked questions

To set up Adobe Analytics, you need to install the Adobe Analytics tracking code on your website. This code will collect data from your visitors and send it to your Adobe Analytics account. You can find instructions on how to install the tracking code in the Adobe Analytics documentation.
Adobe Analytics collects a variety of data from your website visitors, including their IP address, browser type, operating system, and the pages they visit. You can customize the data that Adobe Analytics collects to meet your specific business needs. See the Adobe Analytics documentation for details.
Adobe Analytics provides a variety of reports and tools that you can use to analyze the data collected from your website visitors. You can use this data to understand your audience, measure the effectiveness of your marketing campaigns, and optimize your website experiences.
How do I set up Adobe Analytics on my website?

What kind of data does Adobe Analytics collect?

How do I use the data collected by Adobe Analytics?

Related

Adobe Analytics Implementation Guide

Adobe Analytics Implementation Guide

Adobe Analytics Implementation Guide

Adobe Marketing Channels User Guide

Adobe AppMeasurement for Flash, Flex, and AIR Implementation Guide

Mobile Device Measurement Implementation Guide

Adobe Reports and Analytics User Guide

Omniture DataSources User Guide

Adobe Analytics User Manual

Adobe AppMeasurement for Microsoft Platforms Guide | AI Chat & PDF

Adobe Activity Map User Manual

Adobe AppMeasurement for iOS User Manual + AI Chat
