Version 14 Report Descriptions
U. S State
State name or ID, to be used on the order confirmation (Thank You) page, in conjunction with the purchase event
state*
Visitor Zip and Postal Codes Report
Zip code, to be used on the order confirmation (Thank You) page, in
zip*
conjunction with the purchase or other event
File Downloads Report
Optionally used to identify the name of a link when sending in custom, download, or exit link data.
linkName
Custom Links Report Exit Links Report File Downloads Report
Used to identify the type of link: Custom, Download, or Exit
linkType
Custom Links Report Exit Links Report
Multiple List variables are a delimited list of
values that are passed into a variable,
List Props
and then reported as individual line items for reporting.
Multiple Similar to how List Props function, List
Vars allow multiple values within the same image request.
List Variable (list var)
Version 15 only.
ClickMap A ClickMap variable used to uniquely
identify links on a page
s_objectID
Pages Not Found Report
Used on 404-Page Not Found error pages
pageType
Pages Report
Optionally used to override the URL of the page as recorded in Analyitcs
pageURL
Paths Reports
Finding Methods Report
Optionally used to override a page's referrer as recorded in Analyitcs
referrer
N/A Integration Data Sources utilize a
transaction ID to tie offline data to an
transactionID
online transaction (like a lead or purchase generated online)
N/A Visitors may be identified by the
visitorID variable, or by IP address/User Agent
visitorID
Configuration Variables
Configuration variables, which control data collection, are contained in the .js file, but they are not considered data collection elements. Configuration variables are not included in marketing reports, but they may affect the data, or the appearance of the reports. Configuration variables include the following.
Reports Populated Description
Implementation Variable
N/A Report suite IDs. The account(s) that the page
view is reported in.
s_account
N/A The character set used on the page. The default is assumed to be ISO-8859-1. A list of available character sets is available from Adobe.
charSet
Revenue Report
The currency code used in the s.products and s.events variables. The default is assumed to be
currencyCode
All conversion reports showing revenue or monetary values
USD (U.S. dollars). A list of supported currency codes is available from Adobe.
Affects multiple reports as it controls how the visitor ID is stored and handled.
The number of sections in a domain on which the visitor ID cookie is set.
cookieDomainPeriods
N/A The number of sections in a domain on which
cookies are set by the JavaScript file. This
fpCookieDomainPeriods
overrides the value of cookieDomainPeriods for JavaScript cookies.
See Implementing First-Party Cookies
Establishes the lifetime of the visitor cookie (s.vixxxx). Configuration of this variable is completed by Adobe and should not be modified by clients.
cookieLifetime
The doPlugins variable is a reference to the
The function that should be called before data is sent to Analytics.
doPlugins
s_doPlugins function, and allows the s_doPlugins
function to be called at the appropriate location within the JavaScript file.
N/A Set to "true" if "s.dynamicAccountList"
contains a list of domain/report suite ID pairs to
dynamicAccountSelection
be used to dynamically select the report suite ID based on domain, host, or directory name.
N/A A list of domains and which report suite ID should be used for each (such as "abc.com=reportabc").
dynamicAccountList
N/A The section of the URL that all filters in
dynamicAccountList are applied to
dynamicAccountMatch
N/A Set to "true" to track clicks on links that have
extension names listed in s.linkDownloadFileTypes.
trackDownloadLinks
N/A Set to "true" to track clicks on links that are
external. External links are domains not listed in s.linkInternalFilters.
ClickMap Set to "true" to capture data for ClickMap
reporting.
trackInlineStats
File Downloads Report
The list of download file types.
linkDownloadFileTypes
Exit Links Report
Determines which links on your site are exit links, which is any link that takes a visitor away from
linkInternalFilters
your site. It is a comma-separated list of filters that represent the links that are part of the site.
Exit Links Report
The list of all domains which should be considered external. This is used to limit the number of
linkExternalFilters
external links that will be used, not to specify specific links as external.
File Downloads Report
Whether or not the query string of exit links and download links should be included for tracking purposes.
linkLeaveQueryString
Exit Links Report
Any The variables that should be sent on custom links, download links, and external links. By default, this
linkTrackVars
variable is set to "None" so that variables set on the page are not recounted by link clicks.
Conversion The events to be sent on custom links, download
links, and external links. By default, this variable
linkTrackEvents
is set to "None" that variables set on the page are not recounted by link clicks.
N/A If set to "true", s_doPlugins() will be called by the .JS code prior to creating the image request.
usePlugins
Automatic Variables
Automatic variables are obtained by the .JS code either automatically, or they are populated in the .JS file as a result of the control variables explained above. The names of these variables are defined only within the query string of the image request. There is no equivalent HTML-based variable. The automatic variables include the following.
Description Automatic Variable
The referring URL as defined by the browser. This value includes all query string parameters for the referring URL, including search strings and other information. r (Referring URL)
The current page's URL. This value may include all query string parameters, depending upon the account settings and configuration.
Various information about the page ID, link clicked, including destination URL, link number, etc.
ClickMap data (various)
The time and date that the event request occurred, in local time. t
Whether Java is enabled (Y/N). v
The version of JavaScript supported by the browser. j
The width and height of the browser window. bw, bh
The width and height of the screen (the physical monitor). s
Monitor depth (number of available colors). c
Connection type, including LAN, modem, etc. ct
Netscape plug-ins (if running Netscape, the list of plug-ins installed in the browser) p
Cookies enabled (whether or not cookies are enabled in the browser based on a test cookie)
k
Whether the current page is set as the browser's Home page hp
Direct Variables
Direct variables are those set directly by the browser in the HTTP header of the image request sent to Analytics. These variables are set in each request that is made for any content on the Internet and include some of the most basic user information. The variables are reported directly or indirectly in a number of marketing reports. Direct variables include the following.
Description Direct Variable
The IP address is the Internet Protocol address of the user's browser or machine. That IP addresses may be pooled among multiple users, and that a single user may also use more than one IP address from page to page.
IP address
The user's IP address is resolved to geographic location based on data provided by Digital Envoy through a partnership with Adobe.
The domain from which the user is requesting data. In many cases, this is a company or an Internet Service Provider (ISP) such as AOL.
domain
The user agent string indicates the browser and version, and the Operating System used. In some cases, it may also contain major plug-in or customization features (i.e., .NET). user agent string
The Browser, Browser Version, and Operating System reports are based on the user agent string.
The preferred language setting of the browser. language
The names and values of all cookies that have been set. cookies
Data Warehouse
Data warehouse refers to the copy of raw, unprocessed data for storage and custom reports, which you can run by filtering the data.You can request reports to display advanced data relationships from raw data based on your unique questions. Data warehouse reports are emailed or sent via FTP, and may take up to 72 hours to process. Processing time depends on the complexity of the query and the amount of data requested.
Adobe enables Data Warehouse for administrator-level users only, for specific report suites. (It can be enabled for global and children report suites, but not for rollup report suites.) The administrator can create a group that has access to data warehouse, and then associate non-administrator level users to that group.
Data Warehouse automatically zips any file that exceeds 1 MB in size. The maximum email attachment size is 10 MB.
Data Warehouse can process an unlimited number of rows in a single request for individual scheduled and downloaded reports.
Note: As of October 15, 2015, a change was made to column case sensitivity in Data Warehouse. Data
Warehouse now reports the first value encountered in the reporting period. (Previously, it reported versions of case-insensitive variables that were not encountered in the data at all.)
Data Warehouse Requests Descriptions
This table describes the fields and options on the Data Warehouse Request tab.
Description Element
Identifies the request.
Request Name
The date and granularity of the request.
Reporting Date
• Custom: A date range you configure in the calendar.
• Preset: A preset range. The preset range is relative to the report date.
• Granularity: The time granularity. Valid values are None, Hour, Day, Week, Month, Quarter, and Year.
Lets you select the part of the visitor population you want to examine and generate complex segments. You can load pre-configured segments, create new segments, and store segment components in a library to use in building additional segments.
Available Segments
You can now stack segments. When selecting multiple segments, the preview area, the Request Manager, and the Request Detail popup show a comma-separated list of names (e.g., Segment1, Segment2).
See Segmentation for more information.
Note: You cannot include both a segment filter and a breakdown on the same
segment, in the same Data Warehouse report. Doing so will result in an error.
Lets you categorize data using breakdowns. Segments and breakdowns differ in that a segment filters data out of a data set, while a breakdown compartmentalizes data across all valid values for the breakdown.
Description Element
You can also break down a report by one or more segments. However, you cannot include both a segment filter and a breakdown on the same segment, in the same Data Warehouse report. Doing so will result in an error.
For example, use segments to remove a gender from the data set, and use a breakdown to see data separated by gender.
When a Data Warehouse request is submitted with multiple multi-value dimensions (e.g., various Mobile Reports), an exponential number of rows can be generated from a single hit. The number of rows that can be output from a single hit is capped at 100 (previously 1,000).
Lets you add metrics on which you want to report.
Metrics
Provides ranked breakdown reports, sorted by descending metric value, similar to what is displayed in the Reports & Analytics user interface, Data Workbench, etc.
More...
Metrics Sort
Lets you schedule requests for automatic delivery at selected intervals, or as a one-time report. If you use the default format, the report arrives in an email as a .csv file.
Schedule Delivery
To add the date range, include %R in the filename. This value represents the date values requested in the report. For example, if you request data from May 1, 2013 through May 7, 2013, the %R shows a filename including the date range of 20130501 - 20130507.
Data Warehouse Release Notes
Cumulative release notes for data warehouse.For more recent data warehouse release notes, please refer to the Marketing Cloud Release Notes. •Data Warehouse (10/16/2014) •Data Warehouse (09/18/2014) •Data Warehouse (08/21/2014) •Data Warehouse (07/17/2014) •Data Warehouse (06/19/2014) •Data Warehouse (05/22/2014) •Data Warehouse (04/17/2014) •Data Warehouse (03/13/2014) •Data Warehouse (02/20/2014) •Data Warehouse (01/16/2014) •Data Warehouse (11/14/2013) •Data Warehouse (10/17/2013) •Data Warehouse (09/12/2013) •Data Warehouse (08/15/2013) •Data Warehouse (07/18/2013) •Data Warehouse (06/20/2013) •Data Warehouse (05/23/2013)
•Data Warehouse (04/18/2013) •Data Warehouse (03/21/2013) •Data Warehouse (02/21/2013) •Data Warehouse (11/08/2012) •Data Warehouse (10/18/2012) •Data Warehouse (9/21/2012) •Data Warehouse (8/16/2012) •Data Warehouse (7/19/2012) •Data Warehouse (4/26/2012) •Data Warehouse (3/29/2012) •Data Warehouse (1/19/2012) •Data Warehouse (11/03/2011) •Data Warehouse (10/07/2011) •Data Warehouse (9/20/2011) •Data Warehouse (8/2012) •Data Warehouse (7/2011) •Data Warehouse (5/2011) •Data Warehouse (4/2011) •Data Warehouse (1/2011) •Data Warehouse (11/2010) Data Warehouse (10/16/2014)
No fixes or new features were released at this time.
Data Warehouse (09/18/2014)
No fixes or new features were released at this time.
Data Warehouse (08/21/2014) New Features
Description Feature
Data warehouse now supports "“matches"” and "“does not match”" in segment definitions. (Reports & Analytics and Ad Hoc Analysis already support this.) Support for "matches" and
"does not match" in data warehouse segments
Segments that were previously incompatible with data warehouse because data warehouse did not support "“matches"” and "“does not match”" will become compatible after the release (assuming this was the only reason the segment was incompatible.) Additional segments may appear in the data warehouse segment list after the release.
Fixes
• Referrer report was incorrectly reporting internal referrers.
• Running a data warehouse report on a currency metric with a visit-level breakdown resulted in incorrect data.
Data Warehouse (07/17/2014)
Data Warehouse (06/19/2014) New Features
Description Feature
Data warehouse now supports 'Event Exists' rules outside of Hit containers. New rules in data
warehouse
Data warehouse now supports containers of equal scope to be embedded directly within one another.
Nested containers in data warehouse
Fixes
• When using the same segment in both reports & analytics and data warehouse for the Entry Page Report, the results were different.
• Data warehouse was not reporting Search Keywords – Paid.
• Users were unable to see the variable Page URL from the data warehouse API.
• Segments with multiple nested Visit or Visitor containers were incompatible with data warehouse.
Data Warehouse (05/22/2014) New Features
Description Feature
Segments are now created, managed, and used across Analytics user interfaces and across report suites.
Unified segmentation management and creation across Analytics
A new Segment Builder interface lets you build simple, nested, and sequential segments. You can now apply multiple segments to a single report to prevent duplicating logic in multiple segments.
A new Segment Manager lets you easily manage, approve, share, and tag segments. Segments can be published to the Marketing Cloud for Analytics-powered targeting. See Unified Segmentation Transition Guide.
Fixes
• Fixed an issue that caused Referring Domain dimension to not match reports & analytics in some circumstances. • Using Revenue Participation metric resulted in data returning different revenue results when pulled at different
dates/times.
• Non-Admin user was able to cancel scheduled data warehouse requests. • Trying to access data warehouse caused a network acceleration timeout.
• Data warehouse re-added classifications of post_tnt (Campaign, Recipe, and Campaign > Recipe) for reporting and segmentation.
Note: Data warehouse access from Version 14 has been removed in this release.Learn more
Data Warehouse (04/17/2014) Fixes
• Added the Marketing Cloud Visitor ID as a single breakdown column for reporting and segmenting. The column is called Marketing Cloud Visitor ID in the user interface.
• Fixed an issue that caused Referrer Type metrics, and segments that are based on Referrer Type, to not match reports & analytics.
• Fixed an issue in visitor container segments that caused some visitors to not be correctly included when visits are processed out-of-order. This might occur when offline data is enabled in a mobile app and a hits from an earlier visit are sent in after subsequent visits have already been collected.
• Fixed an issue that caused some report requests to fail when they contained multiple referrer type breakdowns. • Fixed an issue that caused the contains one of segment operator to not return data when applied to multi-valued
dimensions (for example, list variables).
• Fixed an issue that caused negative decimal values in events to be rounded incorrectly. Reporting for these events now matches reports & analytics.
• Fixed an issue that caused some large reports that have no metrics to not generate.
• Fixed an issue that caused invalid values to appear in reports when displaying participation on non-string values. • Fixed an issue that caused dash characters in scheduled report names to be changed to an underscore. These
reports now correctly contain dashes.
Note: Data warehouse access from Version 14 will be removed in an upcoming release.Learn more
Data Warehouse (03/13/2014) Fixes
• Fixed an issue causing the audit log to show Complete, but no report was sent.
• Fixed an issue causing the evaluator to not return data consistently between data warehouse and ad hoc analysis. • Fixed an issue causing segment rules using contains one or all of to not correctly process.
• Fixed a search keyword issue causing ::empty:: to display instead of keyword unavailable.
• Fixed data discrepancy issues between ad hoc analysis and data warehouse requests. These issues occurred in participation revenue reporting and in the Customer Loyalty report.
Note: Data warehouse access from Version 14 will be removed in an upcoming release.Learn more
Data Warehouse (02/20/2014) New Features
Description Feature
Hourly reports that contain the previous hour of data can now be scheduled in data warehouse.
Data warehouse hourly reports
Fixes
• Fixed an issue that caused some Japanese characters to display incorrectly when the UI language was set to English.
Data Warehouse (01/16/2014) New Features
Description Feature
The following search engine reports are now available in data warehouse: New search engine reports
in data warehouse
• Search Engines - Paid • Search Engines - Natural
Description Feature
• Search Keywords - Paid • Search Keywords - Natural
The following data warehouse reports were updated to match the logic used by marketing reports & analytics and ad hoc analysis:
Updated data warehouse reports
• Referrers
• Referring domains • Referrer type • Search Engines - All • Search Keywords - All
• These updated reports work with past date ranges, and all scheduled reports will be automatically switched over to use the new logic.
In conjunction with the change described in Updated data warehouse reports, you must use new elements in your data warehouse web services API requests to report Updated breakdowns in the
data warehouse web
services API breakdowns that match the logic used by marketing reports & analytics and ad hoc analysis. See data warehouse API on Developer Connection.
Data warehouse can now export data in Tableau TDE format. To request a report in Tableau format:
Tableau Integration with data warehouse
1. In the Schedule Delivery section of a Data Warehouse Request, click Advanced
Delivery Options.
2. Select Tableau Format (TDE) as the Report Format.
Fixes
• Transactional data sources data (offline data uploaded using a transaction ID) is no longer included in the Visits-All Visitors and Visitors metrics. This was changed to match marketing reports & analytics.
• Case sensitivity for page name-based dimensions (next page, previous page, and so on) now use the same