adobe marketing cloud clickstream data feeds · pdf fileclickstream (legacy) data feeds help...
TRANSCRIPT
Adobe® Experience Cloud
ClickStream Data Feeds
Contents
Clickstream (Legacy) Data Feeds Help..................................................................3
What's New...............................................................................................................4
Best Practices and General Information...............................................................8
Configuring Data Feeds..........................................................................................9
Data Feed Contents...............................................................................................12
Clickstream Data Column Reference...................................................................15
Page Event Lookup...............................................................................................................50
Hit Source Lookup.................................................................................................................51
Calculating Metrics................................................................................................53
Identifying Visitors.................................................................................................56
Pre and Post Columns..........................................................................................58
Special Characters................................................................................................59
Troubleshooting.....................................................................................................61
Contact and Legal Information.............................................................................63
ClickStream Data FeedsLast updated 4/17/2018
Clickstream (Legacy) Data Feeds Help
Important: On February 16, 2017, Clickstream Data Feeds was replaced by Analytics Data Feed. Pleaserefer to its documentation instead of this legacy documentation.
Raw clickstream data that is collected from web sites, mobile apps, or is uploaded using web service APIs or datasources, is processed and stored in Adobe's Data Warehouse. This raw clickstream data forms the data set that isused by Adobe Analytics.
As a service, Adobe can deliver this raw data to the customer in a batched manner on a recurring daily or hourlydelivery schedule.This service is called the "raw clickstream data feed", or just "data feed." Each data feed comprisesthe clickstream data for a single report suite.
To get started with clickstream data feeds, see Configuring Data Feeds.
For column reference for an existing feed, see Clickstream Data Column Reference.
3Clickstream (Legacy) Data Feeds Help
What's NewCumulative release notes for Clickstream data feeds.
Data Feed Column Expansion (expected soon)
The following data feed column sizes will increase in a future release:
• geo_zip field - column size will increase from 16 to 50 bytes• geo_region field - column size will increase from 32 to 255 bytes• geo_city field - column size will increase from 32 to 255 bytes
New OS Types Lookup File
Clickstream data feed customers that are currently receiving the os column will automatically receive an additionallookup file for OS types starting June 19, 2014.
Mobile Carrier Column Now Available
Mobile carrier data is now available in clickstream data feeds (this data is currently displayed on the Visitor Profile> Technology > Mobile Carrier report in marketing reports & analytics). Contact customer care to have this columnadded.
Data Feed Column Expansion
Adobe is currently evaluating an increase to the size of many data feed fields. Before these field sizes are increased,you need to expand the data fields in your ETL system to accommodate these new sizes.You also need to expandthe fields used to store lookup file keys, as these are increasing in size as well. Note that the column expansionsthat were previously scheduled for April 2014 have been postponed, and an announcement will be included in therelease notes when these expansions are rescheduled.
Note: You can download a sample data feed with expanded columns and lookup files to test your ETL process.We recommend all customers test processing of this sample feed to prepare for the upcoming expansion.
Lookup file key expansion
The column used to store each lookup file key value should be expanded to store a 32-bit unsigned integer.
Note that additional lookup files could be added to the data feed when additional columns added, If possible yourETL system should be designed to accommodate the addition of new lookup files without impacting processing.
String expansion
Expand the following columns to store a 255 character string:
click_actionclick_tagip2
pagenamepost_page_event_var2page_event_var2
channelpost_pagename_no_urlpost_pagename
t_time_infouser_serverpost_channel
first_hit_pagenamedomainpost_t_time_info
post_transactionidtransactionidvisit_start_pagename
4What's New
ref_domainpost_prop1-75prop1-75
pluginsgeo_zipcode_ver
ct_connect_typec_coloraccept_language
post_ page_typepage_typeip
s_resolutionpost_purchaseidpurchaseid
visit_keywordsua_pixelsua_color
geo_citystats_serverpost_keywords
statej_jscriptgeo_region
post_zipzippost_state
post_currencycurrencynamespace
ua_os
Integer expansion
Expand the following columns to store a 32-bit unsigned integer:
search_enginebrowser_widthbrowser_height
browser (Feb 20, 2014)post_browser_widthpost_browser_height
languagecountrycolor
visit_search_engineresolutionos (Feb 20, 2014)
search_page_numpost_search_enginegeo_dma
October 17, 2013
Social, Mobile, and Video solution variables are now available
You can now receive solution variables in data feeds, which currently includes Social, Mobile, and Video metrics.
To update your data feed definition to add solution variables, contact Customer Care.
Event lookup file now included in data feed download
Starting October 17, 2013, an additional event lookup file will be added to all data feeds.Your ETL might require amodification to consider this file.
This new lookup file provides a map for all events, including shopping cart events, instance events, custom events,mobile-specific events, social-specific events, and so on. Be aware that the map for Mobile, Social, and Videosolution event numbers are different for each report suite. The event lookup file delivered with each report suiteshould be considered specific to that report suite.
May 23, 2013
Hourly Data Feeds
Hourly data feeds provide customers raw Analytics data in hourly increments instead of the normal daily increments.By splitting the data into hourly increments, the data can be delivered in a more timely manner with less peak loadon both origination and destination servers. See Configuring Data Feeds.
5What's New
February 14, 2013
Format of post_product_list column when events are present but product is empty
In post_product_list, If events are contained on the event list for a given hit but there is no product in the productlist, the post_product_list contains four semicolons:
;;;;
or in rare cases as semicolon, semicolon, zero, semicolon, zero, semicolon:
;;0;0;
If you are performing a check for an empty product list you should update your ETL to handle both formats.
January 22, 2013
Expansion of page_url and page_event_var1 Columns
These columns were expanded to store URLs that are longer that 255 characters. This change enables you toreceive the entire URL of each page and tracked link, which might contain long query strings or other values thatwere previously truncated at 255 characters.
After this change, the page_url and page_event_var1 length will increase from 255 bytes to 64 kilobytes. Updateany applications or scripts that you are using to process the data feed to use a 64Kb variable to store these strings.If you are storing the data feed in a database, make sure that the page_url and page_event_var1 columns are largeenough to contain a string up to 64Kb. Alternatively, if your systems require the truncated versions of these columns,please make certain your ETL handles truncation appropriately.
This change does not impact the post_page_url or post_page_event_var1 columns, which remain at 255 characters.
June 21, 2012
• You may now opt to receive clickstream data feed data as a once-daily package of multiple files rather than a singlelarge monolithic file. The multiple file package is particularly useful for report suites with very high traffic volumesand has several advantages:
• Improved delivery consistency, especially during days with traffic spikes.• Better parallel data processing. Using the multiple file package can significantly reduce the time required to
compress and extract large data sets.
• The following additional optional columns are now available for inclusion in your data feed. In order to maintaincompatibility with your current ETL processes, existing data feeds will not be altered unless requested to CustomerCare through your Supported User.
• post_event_list
post_ page_event
post_page_event_var1
post_page_event_var2
post_ page_type
post_page_url
post_pagename
post_pagename_no_url
post_product_list
6What's New
post_channel
post_mvvar1 – post_mvvar3
post_purchaseid
post_referrer
post_state
post_hier1-post_hier5
post_currency
post_partner_plugins
visit_keywords
post_transactionid
post_page_event_var3
va_instance_event
va_new_engagement
post_prop1-post_prop75
tnt_post_vista
7What's New
Best Practices and General InformationFollowing are some best practices for data feed processing and delivery.You should:
• Expect data feeds to be delivered within 12 hours after the end of a given time period 95% of the time.
For example, if you have an hourly feed, the data feed request for the 3 a.m. to 4 a.m. hour should be deliveredby 4 p.m. 95% of the time. Data feeds for report suites with high traffic volume can take longer to process anddeliver, particularly if they are configured as daily feeds rather than hourly feeds.
• Ensure that you communicate any anticipated traffic spikes ahead of time. Any upstream latency has a direct impacton how quickly the data feed process can get started.
• Ensure that you have ample room on your FTP site. Clean it out on a regular basis so that you don’t inadvertentlyrun out of disk space.
• When changing FTP credentials, please ensure that the credentials are current in Adobe's data feed system. NotifyAdobe Customer Care of the credential changes.
• Use hourly delivery if possible. It makes the files smaller and faster to produce/transmit.• Consider using “multiple-file” delivery (typically done with large daily feeds.) Multiple-file delivery breaks the single
monolithic file into smaller files and delivers them all at the same time. Again, smaller files make it faster to create,zip/unzip, and transmit the data.
• If you are using sFTP as the delivery method, do not read and do not delete files with a “.part” suffix. The “.part”suffix indicates the file is partially transferred, it is not complete. Once the file has been transferred, the file will berenamed without the “.part” suffix.
• Build your ETL process with the assumption that, occasionally, a file may be transferred more than once. Otherwise,you may end up with duplicate data.
8Best Practices and General Information
Configuring Data FeedsData feeds are enabled by Customer Care and delivered using FTP or Amazon S3.
This section provides an overview of data feed options and the one-time configuration process.
FTP File Delivery
Data feed data can be delivered to an Adobe or customer hosted FTP location.
If you select to have data uploaded to your FTP server, you must provide Adobe with the appropriate username,password, and upload path.You must implement your own process to manage disk space on the server, as Adobedoes not delete any data from the server.
sFTP File Delivery
Data feed data can be delivered to an Adobe or customer hosted sFTP location.
If you select to have data uploaded to your FTP server, you must provide Adobe with the appropriate username andupload path.You must implement your own process to manage disk space on the server, as Adobe does not deleteany data from the server.
Amazon S3 File Delivery
If you don't want to worry about managing disk space or encrypting your data, you can now upload your files to anAmazon S3 bucket. Amazon will automatically encrypt the data at rest (on the Amazon servers).When you downloadthe data, it gets decrypted automatically.
If you select to have data uploaded via Amazon S3, you must provide Adobe Client Care with a Bucket name, anAccess Key ID, a Secret Key and a folder name.
BucketOwnerFullControl setting for Amazon S3 data feeds
The common use case for Amazon S3 is that the Amazon Web Services (AWS) account owner creates a bucket,then creates a user that has permission to create objects in that bucket, and then provides credentials for that user.In this case, the objects of a user belongs to the same account, and the account owner implicitly has full control ofthe object (read, delete, etc). This is similar to how FTP delivery works.
AWS also makes it possible for a user to create objects in a bucket that belong to a completely different user account.For example, if two AWS users, userA and userB, do not belong to the same AWS account but want to create objectsin other buckets. If userA creates a bucket, say bucketA, he or she can create a bucket policy that explicitly allowsuserB to create objects in bucketA even though the user doesn't own the bucket.This can be advantageous becauseit doesn't require that userA and userB to exchange credentials. Instead, userB provides userA with their accountnumber, and userA creates a bucket policy that essentially says "let userB create objects in bucketA".
BucketOwnerFullControl provides cross-account rights to create objects in other buckets. If userB uploads anobject to userA's bucket, userB still "owns" that object, and by default, userA is not granted any permissions to thatobject even though userA owns the bucket—objects do not inherit permissions from the parent bucket. UserB mustexplicitly grant userA permissions because userB is still the object's owner. For this cross-account upload, AWSprovides a BucketOwnerFullControl ACL by specifying that the use of this ACL by the bucket owner (userA) and isgranted full permissions to the object (read, write, delete, etc), even though the object is "owned" by userB.
9Configuring Data Feeds
Delivery Formats and Contents
Daily: Data for each day is delivered after it is processed in a single zipped file, or in multiple zipped files eachcontaining approximately 2 GB of uncompressed data.You receive a single delivery for each day.
Hourly: Data for each hour is delivered in a single zipped file that contains all data received during that hour.Youreceive 24 separate deliveries for each day, with each file delivered after the data for that hour is processed.
Note: Due to the potential size of data feed zip files, make sure your ETL process uses a 64-bit zip utility.
Hourly Data Feeds
It is important to understand that the term “hourly” describes the time frame of the data that is sent with each individualdata export, and not the time frame in which the delivery occurs. Hourly data feeds are processed and delivered ina best-effort fashion. However, there are several factors that can impact the delivery time of an hourly data feedincluding:
• Report suite latency (i.e. unannounced spike in traffic)• Upstream processing• Peek and non-peak hours• Internet connection speeds
For hourly data feeds the expectation is that 95% of the time the feed will deliver within 12 hours of the close of thathour’s worth of data. Data feeds for report suites with high traffic volume may take longer to process and deliver.
Receiving an hourly data feed is different then receiving daily feed with multiple file delivery. When receiving hourlydata feeds the data for each day is split into 24 files based on the data collected during that hour, and each file isdelivered as soon as it is available. A daily feed that is delivered in multiple files is delivered once per day after theprevious day's data is processed, and is spilt into 2GB increments based on the amount of data collected.
Data Backfills for Hourly Data Feeds
If you request data for earlier dates when setting up a new hourly data feed, data for dates more than 60 days agomight be delivered in daily format instead of hourly.
In this case, you will not receive 24 separate deliveries for these days, instead, you will receive a single deliverywith a midnight timestamp that contains all of the data for that day. If you are requesting this type of backfill, Makesure your ETL is configured to process daily deliveries.
Multiple File Delivery
You can select single file or multiple file delivery when the data feed is created. When setting up a daily feed, werecommend selecting multiple file delivery, due to the significant performance increases gained when compressingand uncompressing files that are larger than 2 GB. Multiple file delivery makes it easier to process data in parallel.Data files are always split on a complete record and can be easily concatenated after extraction.
One Time Configuration Process
DescriptionPerformed ByTask
Review the clickstream data columns and determinethe data you would like to receive. Adobe also providesa recommended column set that can be selected.
CustomerSelect data columns
10Configuring Data Feeds
DescriptionPerformed ByTask
Select an FTP location where Adobe should deliverdata feed files. Adobe can provide FTP hosting for thefiles if preferred.
Customer(FTP only) Select FTP location
Purchase an S3 bucket from Amazon
Contact Customer Care through your Supported Userand provide:
CustomerContact Adobe Customer Care toconfigure the data feed.
• The report suite that contains the data you want in thefeed.
• The columns you want in the data set.• Daily or hourly data delivery. If Daily, select single file
or multiple file delivery (multiple recommended).• (FTP only) FTP hostname, credentials, and path.• (Amazon S3 only) bucket name, access key ID, secret
key, and folder name.
Delivery Process
DescriptionPerformed ByTask
Server calls are collected and processed in Adobe DataCollection servers.
AdobeData collection
After data is processed for the delivery period (previoushour or previous day), the data is exported to the data
AdobeFeed generation
feed. The feed is stored in delimited format andcompressed.
The compressed data is transferred to either AmazonS3 or a customer-hosted or Adobe-hosted FTP site.
AdobeDelivery to customer
When complete, a manifest file (or .fin file for olderfeeds) is transferred indicating that the delivery iscomplete.
The customer monitors S3 or the FTP for the manifestfile. This file contains details on all files that weredelivered.
CustomerData download
The manifest file is read and each listed file isdownloaded.
CustomerManifest file processing
Downloaded files are uncompressed and processed.CustomerData is uncompressed and processed
After you have configured your data feed, continue to Data Feed Contents to understand what files you will receive.
11Configuring Data Feeds
Data Feed ContentsThis section describes the files found in a data feed delivery.
Manifest File
The manifest file contains the following details about each file that is part of the uploaded data set:
• file name• file size• MD5 hash• number of records contained in the file
The manifest file follows the same format as a Java JAR manifest file.
The manifest file is always delivered last as a separate .txt file, so that its existence indicates that the completedata set for that request period has already been delivered. Manifest files are named according to the following:
<report_suite_id>_YYYY_MM_DD.txt
A typical manifest file contains data similar to the following:
Datafeed-Manifest-Version: 1.0 Lookup-Files: 1 Data-Files: 1 Total-Records: 611
Lookup-File: bugzilla_2012-09-09-lookup_data.tar.gz MD5-Digest: af6de42d8b945d4ec1cf28360085308 File-Size: 63750
Data-File: 01-bugzilla_2012-09-09.tsv.gz MD5-Digest: 9c70bf783cb3d0095a4836904b72c991 File-Size: 122534 Record-Count: 611
Every manifest file contains a header, indicating the total number of lookup files, data files, and total number ofrecords in all data files. This header is followed by multiple sections containing information for each file included inthe data feed delivery.
Some feeds are configured to receive a rsid_YYYY-MM-DD.fin file instead of a .txt manifest. The .fin indicatesthat the upload is complete, but it contains no metadata about the upload.
Lookup Files
Lookup files do not contain hit data, these are supplemental files that provide the column headers for the hit data,and lookup files to translate the IDs found in the data feed to actual values. For example, a value of "497" in thebrowser column indicates that the hit came from "Microsoft Internet Explorer 8".
Note that the column_headers.tsv and event_list.tsv are specific to the data feed and report suite. Other files,such as browser.tsv, are generic.
The lookup files are delivered together in a compressed zip named according to the following:
<report_suite_id>_<YYYY-mm-dd>-<HHMMSS>-lookup_data.<compression_suffix>
• column_headers.tsv (customized for this data feed)• browser.tsv• browser_type.tsv• color_depth.tsv• connection_type.tsv
12Data Feed Contents
• country.tsv• javascript_version.tsv• languages.tsv• operating_systems.tsv• plugins.tsv• resolution.tsv• referrer_type.tsv• search_engines.tsv• event.tsv (customized for this data feed)
For hourly delivery, lookup files are delivered only with the data for the first hour of each day.
Hit Data Files
Hit data is provided in a hit_data.tsv file. The amount of data in this file is determined by the delivery format(hourly or daily, and single or multiple files). This file contains only hit data. The column headers are deliveredseparately with the lookup files. Each row in this file contains a single server call.
Delivery Contents
Note: The files are encoded using ISO-8859-1.
The actual files delivered by Adobe vary based on the type of data feed that you have configured. Find the configurationthat matches your data feed in the following table for a description of the delivered files.
The time (HHMMSS) indicated in a file name always indicates the beginning of the date range for the data in thefile, regardless of when the file was produced or uploaded.
DescriptionDelivery Format
After data is collected for a day, you will receive a delivery that contains the following:Daily, single file
• a single compressed data file.• A manifest file.
The data file is delivered with the following name:
<report_suite>_<YYYY-mm-dd>.<compression_suffix>
Where <compression_suffix> is either tar.gz or zip.
When extracted, the data file contains a single hit_data.tsv file with all data for that day, aswell as the compressed lookup files described above.
The hit data file size varies greatly depending on the number of variables actively used andamount of traffic on the report suite. However, on average, a row of data is approximately 500B(compressed) or 2KB (uncompressed). Multiplying this by the number of server calls can providea rough estimate on how large a data feed file will be.
After data is collected for a day, you will receive a delivery that contains the following:Daily, multiple file
• One or more compressed data files, broken into 2 GB chunks.• A manifest file.
13Data Feed Contents
DescriptionDelivery Format
Each data file is delivered with the following name:
<index>-<report_suite>_<YYYY-mm-dd>.<compression_suffix>
Where <index> is an incrementing file index from 1 to n, given n files, and <compression_suffix>is either tar.gz or zip.
When extracted, each data file contains a single hit_data.tsv that contains approximately 2GB of uncompressed data, as well as the compressed lookup files described above.
After data is collected for an hour, you will receive a delivery that contains the following:Hourly, single file
• a single data file.• A manifest file.
The data file is delivered with the following name:
<report_suite>_<YYYY-mm-dd>-<HHMMSS>.<compression_suffix>
Where <compression_suffix> is either tar.gz or zip.
When extracted, the data file contains a single hit_data.tsv file with all data for that hour.The compressed lookup files described above are delivered only with the data for the first hourof each day.
After data is collected for an hour, you will receive a delivery that contains the following:Hourly, multiplefile
• One or more compressed data files, broken into 2 GB chunks.• A manifest file.
Each data file is delivered with the following name:
<index>-<report_suite>_<YYYY-mm-dd>-<HHMMSS>.tsv.<compression_suffix>
Where <index> is an incrementing file index from 1 to n, given n files, and <compression_suffix>is either gz or zip
When extracted, each data file contains a single hit_data.tsv that contains approximately 2GB of uncompressed data. The compressed lookup files described above are delivered onlywith the data for the first hour of each day.
14Data Feed Contents
Clickstream Data Column ReferenceTable data describing the columns in the data feed.
• Columns, Descriptions, and Data Types• Events Lookup for Solution Variables
Columns, Descriptions, and Data Types
Note: For any given column (for instance, one that is defined as 255 characters), a data feed may sendadditional characters due to the addition of characters escaping values in a string.
Example lookupData typeColumn descriptionColumn name
en-us, ja;q=0.62, deString (255 characters)The accept language headerfrom the browser.
accept_language
See Browser Lookup andBrowser Type Lookup Key:FK
32-bit unsigned integerThe browser ID (has lookuptable) actually used for the hit.See pre_browser.
browser
806 Key: FK32-bit unsigned integerHeight in pixels of browserwindow.
browser_height
128032-bit unsigned integerWidth in pixels of browserwindow.
browser_width
32String (255 characters)Color depth as generated fromJavaScript.
c_color
[Custom]String (255 characters)The campaign value passed inon the hit. May not end up being
campaign
the value that gets passed to theinterface (see post_campaign).
String (100); MediaOptimizer solution variable
mobile carrier (requries lookupfile)
carrier
[Custom]String (100 characters)Custom traffic variable for sitesections (channels).
channel
http://www.adobe.comString (255 characters)Visitor click map information.This information is what is
click_action
contained in the address of thelink the user clicked on (URL /JS function, etc.)
08-bit unsigned integerVisitor click map information.The type of link clicked on.
click_action_type
homepageString (255 characters)Visitor click map information.This is the pagename (or URL
click_context
if no pagename is declared) forthe page on which the link clickoccurred
08-bit unsigned integerVisitor click map information.The type of click_context
click_context_type
15Clickstream Data Column Reference
(indicates whether thepagename or URL was used)
39632-bit unsigned integerVisitor click map information.This is the numeric ID for the
click_sourceid
location on the page where thelink is located
AString (255 characters)Visitor click map information.The type of link or form elementthat was clicked on.
click_tag
G.7-pD-SString (255 characters)The version of code in the JSfile creating the image request.
code_ver
See Color Depth LookupKey: FK
32-bit unsigned integerColor depth ID (has lookuptable) that we ended up usingfor the hit. See pre_color.
color
08-bit unsigned integerConnection type ID (has lookuptable).
connection_type
Ystring (1 character)Specifies whether JavaScriptsession cookie is accepted.
cookies
See Country Lookup Key:FK
32-bit unsigned integerCountry ID (has lookup table).country
modemString (255 characters)Connection type of the browserscomputer.
ct_connect_type
28-bit unsigned integerHow the currency rate is stored.curr_factor
1Decimal (24 significantdigits,12 digits after thedecimal point )
Current exchange rate when thetransaction occurred.
curr_rate
USDString (3 characters)Type of currency for thetransaction.
currency
110275071632-bit unsigned integer(timestamp-enabled reportsuites only) The timestamp sent
cust_hit_time_gmt
with the hit. This "timestamp" isin Unix time (number of secondssince Jan 1, 1970.)
UserID123ABCString (255 characters)A visitor ID passed in with thehit to be used as the visitor ID
cust_visid
for the hit (instead of usingvisid_high and visid_low)
08-bit unsigned integerA flag to determine if current hitis a new daily visitor.
daily_visitor
YYYY-MM-DD HH:MM:SS(this is not in Unix time.)
datetimeThe time in readable format inTime Zone specified by ReportSuite ID. Set by Adobe servers.
date_time
Adobe servers combinepost_cust_hit_time_gmt and thereport suite's time zone to create
16Clickstream Data Column Reference
date_time. hit_time is in thetimezone of the report suite
example.comString (255 characters)Domain of users ISP.domain
[Custom]String (255 characters)Lists each event that wascounted as a duplicate.
duplicate_events
08-bit unsigned integerA flag indicating that thepurchase event for this hit
duplicate_purchase
should be ignored because it isa duplicate.
(rsid)String (40 bytes)The Report suite from which thehit was duplicated
duplicated_from
String (255 characters),AMO solution variable
ef_id for Media Optimizeref_id
[Custom]String (255 characters)Custom variable 1 - 250.evar1-250
For event ID to namemapping, see the event.tsv
String (64k characters)Comma separated list ofnumeric IDs representing eventspassed in from the customer.
event_list
file that is delivered with thedata feed.
See Exclude Lookup Key:FK
Hits that have a value otherthan 0 for this column are
8-bit unsigned integerHit excluded by client rule.exclude_hit
not used by Analyticsreports and should beignored when calculatedmetrics.
Note that visit_num is notincremented for excludedhits
http://www.adobe.comString (255 characters)The original entry page URL.first_hit_page_url
homepageString (255 characters)The original entry pagepagename.
first_hit_pagename
http://www.yahoo.comString (255 characters)The referring domain of the hit(based on referrer).
first_hit_ref_domain
8-bit unsigned integerInteger representing the type ofreferral for the hit. Lookup
first_hit_ref_type
values can be obtained fromreferrer_type.csv lookup table.
http://www.yahoo.comString (255 characters)Original referrer - referrer of firsthit ever for the visitor.
first_hit_referrer
110275071632-bit unsigned integerTimestamp of the first hit inGMT.
first_hit_time_gmt
los angelesString (255 characters)City from Digital Envoy.geo_city
17Clickstream Data Column Reference
usaString (255 characters)Country from Digital Envoy.geo_country
[Custom]32-bit unsigned integerDMA from Digital Envoy.geo_dma
caString (255 characters)Region / State from DigitalEnvoy.
geo_region
84103String (255 characters)Zip code based on IP-addresslookup
geo_zip
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values aspassed in on the image request.
hier1-5
The delimiter is chosen by theclient during implementation.
See Hit Source Lookup8-bit unsigned integerA flag for the back-endprocessing to know what type ofhit the data is.
hit_source
109661412232-bit unsigned integerSet by Adobe servers, this is thetimestamp used for
hit_time_gmt
non-timestamped report suites.This "timestamp" is in Unix time(number of seconds since Jan1, 1970.)
64-bit unsigned integerUsed to uniquely identify a hit.The combination of hitid_low
hitid_high1. 14988E+15 Key: PRI
and hitid_high creates a uniqueID for the row.
64-bit unsigned integerUsed to uniquely identify a hit.The combination of hitid_low
hitid_low1. 50367E+16 Key: PRI
and hitid_high creates a uniqueID for the row.
Nstring (1 character)Homepage flag, whether or notthis page was the user'shomepage
homepage
08-bit unsigned integerA flag to determine if current hitis a new hourly visitor.
hourly_visitor
String (255 characters)IP address of user's computer,from users ISP.
ip1. 112.89.14
String (255 characters)A second IP address to be usedby VISTA to determine validityof hits.
ip2
String (255 characters)Version of JavaScript supportedby browser.
j_jscript1. 3
Ystring (1 character)Flag indicating whether or notjava is enabled.
java_enabled
See Javascript VersionLookup Key: FK
8-bit unsigned integerVersion of Javascript.javascript
See Languages LookupKey: FK
32-bit unsigned integerLanguage ID (has lookup table).language
18Clickstream Data Column Reference
110275196532-bit unsigned integerTimestamp of the previous hit inGMT
last_hit_time_gmt
032-bit unsigned integerThe purchase number of theprevious purchase.
last_purchase_num
032-bit unsigned integerThe time of the previouspurchase.
last_purchase_time_gmt
String (255 characters)Experience Cloud audiencesmc_audiences
String (255 characters)Experience Cloud Visitor ID TheExperience Cloud Visitor ID is a
mcvisid1. 64983E+37
128-bit number that consists of2 signed, positive, 64-bitnumbers in base 10, bothpadded to 19 zeros, and thenconcatenated.
Mobile solution variables. SeeMobile Solution Variables
mobile*
2332-bit unsigned integerThe ID of the mobile devicewhich passed the hit intomarketing reports.
mobile_id
08-bit unsigned integerA flag to determine if current hitis a new monthly visitor.
monthly_visitor
String (64k characters)Mvvars are multi-value fieldsprovided to allow customers to
mvvar1-3
implement custom multi-valueprojects. Also known as "listvariables" in Adobe MarketingReports & Analytics.
String (255 characters)Not currently populated;reserved for future release.
namespace
08-bit unsigned integerA flag that determines if thecurrent hit is a new visit.
new_visit
See Operating SystemsLookup Key: FK
32-bit unsigned integerOperating system ID (haslookup table).
os
String (64k characters)List of plugins available to thebrowser.
p_plugins
0 See Page Event Lookup8-bit unsigned integerPage event ID, the type of hitthat is sent in the request.
page_event
Look-ups provided for type ofevent (normal,download, exit,custom)
http://www.adobe.comString (64k characters)Related to the page_eventcolumn. It is the URL of the
page_event_var1
download link, exit link orcustom link clicked.
19Clickstream Data Column Reference
homepage_buyString (255 characters)If you have individually namedyour link, this column containsthe link name.
page_event_var2
String (64k characters)Used for both Survey and Mediamodule, and serves as the
page_event_var3
pre-version for both modules.(This column contains the valuepassed in on the hit for the pageevent.)
errorPageString (255 characters)page type variable (only usedfor error page).
page_type
http://www.adobe.com/search/search_results.htmString (64k characters)The URL of the pageview. Theaddress of the page in theaddress bar of the browser.
page_url
search_resultsString (100 characters)The name of the page (if set).pagename
18-bit unsigned integerA (1/0) flag that determines if thehit was used for paid searchtracking.
paid_search
String (255 characters)Not usable by customers. Thisis a comma-separated list of
partner_plugins
plungin_ids (usually about 5characters each) for plugins thatpartners have registered withus.
YString (1 character)A flag indicating if 3rd partycookies and/or persistentcookies are enabled.
persistent_cookie
See Plugins Lookup Key:FK
String (255 characters)List of plugin IDs available to thebrowser (has lookup table) Thisis the post value.
plugins
60032-bit unsigned integerHeight in pixels of the browserwindow.
post_browser_height
86832-bit unsigned integerWidth in pixels of the browserwindow.
post_browser_width
[Custom]String (255 characters)Persisting value of campaign.post_campaign
[Custom]String (100 characters)Custom traffic variable for sitesections (channels).
post_channel
Ystring (1 character)Specifies whether JavaScriptsession cookie is accepted.
post_cookies
USDString (3 characters)Type of currency for thetransaction.
post_currency
110275071632-bit unsigned integerTimestamp actually used for thehit, this is cust_hit_time_gmt for
post_cust_hit_time_gmt
timestamp-enabled reportsuites, or hit_time_gmtotherwise.
20Clickstream Data Column Reference
String (255 characters)Post version of the cust_visidfield. What we ended up usingfor the hit.
post_cust_visid
String (255 characters);AMO solution variable
post verion of ef_idpost_ef_id
[Custom]String (255 characters)Persisting value of evar1-250.post_evar1-250
For event ID to namemapping, see the events.tsv
String (64k characters)Comma separated list ofnumeric IDs representing eventspassed in from the customer.
post_event_list
that is delivered with thedata feed. Key: FK
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values aspassed in on the image request.
post_hier1-5
The delimiter is chosen by theclient during implementation.
Ystring (1 character)Flag indicating whether or notjava is enabled.
post_java_enabled
my keywordString (100 characters)The keywords that were actuallyused for the hit.
post_keywords
String (255 characters)Experience Cloud audiencespost_mc_audiences
Mobile solution variables. SeeMobile Solution Variablespost_mobile*
String (64k characters)Post-processed mvvars. "Whatwe ended up using for the hit."
Data in the post_mvvar columnswill be separated by a6-character delimiter:
--**--
post_mvvar1-3
The delimiter in column mvvarwill be replaced in post_mvvarby
--**--
0 See Page Event Lookup8-bit unsigned integerPage event ID, the type of hitthat is sent in the request.
post_page_event
http://www.adobe.comString (100 characters)Related to the page_eventcolumn. It is the URL of the
post_page_event_var1
download link, exit link orcustom link clicked.
homepage_buyString (100 characters)If you have individually namedyour link, this column containsthe link name.
post_page_event_var2
String (64k characters)Used for both Survey and Mediamodule, and serves as the
post_page_event_var3
pre-version for both modules.(This column contains the value
21Clickstream Data Column Reference
passed in on the hit for the pageevent.)
errorPageString (100 characters)page type variable (only usedfor error page).
post_ page_type
http://www.adobe.com/search/search_results.htmString (255 characters)The URL of the pageview. Theaddress of the page in theaddress bar of the browser.
post_page_url
search_resultsString (100 characters)The name of the page (if set). Ifno page is specified the URL isplaced in this value.
post_pagename
search_resultsString (100 characters)The name of the page (if set). Ifno page is specified this valueis left empty.
post_pagename_no_url
String (100 characters)List of partner plugins availableto the browser (has lookuptable).
post_partner_plugins
Ystring (1 character)Flag indicating if 3rd partycookies and/or persistentcookies are enabled.
post_persistent_cookie
Format is comma separatedlist of: category; product;
String (64k characters)The product list as passed inthrough the JavaScript.
post_product_list
quantity; cost;custEventsDecValues;merchandisingValues
Computers;HPPavillion;1;1000;200|201,OfficeSupplies
[Custom]String (100 characters)Custom traffic variables 1 - 75.post_prop1-75
1584A9646GString (100 characters)Unique identifer for a purchase.Identifies a duplicate purchase(see duplicate_purchase).
post_purchaseid
String (244 characters)Page prior to the current page.post_referrer
String (255 characters);AMO solution variable
post version of s_kwcidpost_s_kwcid
Search Engine Lookup32-bit unsigned integerThe numeric ID of the searchengine that was actually usedand stored.
post_search_engine
Social solution variables. SeeSocial Solution Variablespost_social*
AZString (100 characters)Geographical region (i.e.Arizona, Utah, Saxony [German
post_state
Region]) passed in onJavaScrip. Normally only set ona purchase page.
22Clickstream Data Column Reference
3826-0-0--**--3826-1-1--**--3826-2-0String (64k characters)Post column for the marketingreports and Survey integration.
post_survey
Processed based onpage_event_var3.
12/11/2004 4:23:31 1 +420String (100 characters)Raw time info from JavaScript.Used to determine the visitor'stimezone.
post_t_time_info
String (64k characters)Post column for Analytics andTarget integration.
post_tnt
String (64k characters)Post column for Analytics andTarget integration.
post_tnt_action
A1B2C3D4String (100 characters)A unique identifier where variousdata points can be uploadedlater via Data Sources.
post_transactionid
Video solution variables. SeeVideo Solution Variablespost_video*
64-bit unsigned integerThe visid_high value that weended up using for the hit.
post_visid_high
64-bit unsigned integerThe visid_low value that weended up using for the hit.
post_visid_low
0=Custom VisitorID (Acustom visitor ID was set inthe code using s.visitorID)
8-bit unsigned integerPost version of the visid_typecolumn. What we ended upusing for the hit.
post_visid_type
1=IP&UA fallback (cookieswere rejected by browser)
2=Wireless (HTTP MobileSubscriber Header identifiedas mobile carrier)
3=Adobe (server generated,stored in s_vi on client)Default method.
4=Fallback cookie (newfallback ID, JavaScriptgenerated, stored in s_fidon client, added in H25.3)
5=ID Service
See Identifying UniqueVisitors.
String (100 characters)Post version of the zip field.What we use for the hit.
post_zip
032-bit unsigned integerThe page id of the previouspage. This is an internal
prev_page
23Clickstream Data Column Reference
identifier and not useful to thecustomer.
Format is comma separatedlist of: category; product;
String (64k characters)The product list as passed inthrough the JavaScript.
product_list
quantity; cost;custEventsDecValues;merchandisingValues
Computers;HPPavillion;1;1000;200|201,OfficeSupplies
Replaced by post_product_listas of April 2011. Contains data
product_merchandising
for Merchandising evars as theyrelate to products.
[Custom]String (100 characters)Custom traffic variables 1 - 75.prop1-75
1584A9646GString (20 characters)Unique identifier for a purchase.Identifies a duplicate purchase(see duplicate_purchase).
purchaseid
[Custom]8-bit unsigned integerA flag to determine if current hitis a new quarterly visitor.
quarterly_visitor
String (255 characters)The referring domain of the hit(based on referrer).
ref_domain
8-bit unsigned integerInteger representing the type ofreferral for the hit. Lookup
ref_type
values can be obtained fromreferrer_type.csv lookup table.
String (255 characters)Page prior to the current page.referrer
See Resolution Lookup Key:FK
32-bit unsigned integerResolution id (has lookup table).resolution
String (255 characters);AMO solution variable
s_kwcid for Media Optimizers_kwcid
1024x768String (255 characters)Screen resolution as passed infrom JavaScript.
s_resolution
Nstring (1 character)A (Y/N) field if the hit was used(sampled) or not for ad hocanalysis.
sampled_hit
See Search Engine LookupKey: FK
32-bit unsigned integerSearch engine ID, has lookuptable
search_engine
132-bit unsigned integerThe page number of searchresults that the keywords wereon from the search engine.
search_page_num
08-bit unsigned integerUsed to track secondary hits.Secondary hits are charged at
secondary_hit
24Clickstream Data Column Reference
a rate of 50% of the normalcosts.
ssString (2 characters)Deprecated. pe or ss - type ofhit coming through. The
service
page_event column gives thesame information but in moredetail.
String (255 characters)social account and app idssocialaccountandappids
Social solution variables. SeeSocial Solution Variables
social*
32-bit unsigned integerAdobe proprietary columninformation
sourceid
AZString (255 characters)Geographical region (i.e.Arizona, Utah, Saxony [German
state
Region]) passed in onJavaScript. Normally only set ona purchase page.
www263.omniture.comString (255 characters)Adobe internal server thatprocessed the hit.
stats_server
26/11/2013 4:23:31 1 420String (255 characters)Raw time information fromJavaScript. Used to determinethe visitor's timezone.
t_time_info
String (64k characters)Pre column for Analytics andTarget integration.
tnt
String (64k characters)Pre column for Analytics andTarget integration.
tnt_action
52060:81:1 or
52060:81:1,13234:23:0,9132:12:1
String (64k characters)Same information as the tnt fieldbut with any modifications madeby Vista Rules, etc.
tnt_post_vista
A1B2C3D4String (255 characters)A unique identifier where variousdata points can be uploadedlater via Data Sources.
transactionid
NString (1 character)A (Y/N) field that determines ifthe query string of the hit wastruncated or not. i.e.
truncated_hit
String (255 characters)Screen color depth. Stands forUser Agent Color. From HTTPheader sent by older browsers.
ua_color
String (255 characters)Screen color depth. Stands forUser Agent Operating System.
ua_os
From HTTP header sent byolder browsers.
String (255 characters)Screen color depth. Stands forUser Agent Pixels. From HTTPheader sent by older browsers.
ua_pixels
25Clickstream Data Column Reference
String (64k characters)User agent as found in theHTTP header sent from thebrowser.
user_agent
375724966432-bit unsigned integerThe hash on the report suite ID.user_hash
[Custom]String (255 characters)Custom traffic variable forservers.
user_server
64461432-bit unsigned integerThe numeric ID for the reportsuite ID (normally seen in thename of DW files).
userid
adobeString (255 characters)The report suite ID.username
String (255 characters)Detail for last-touch value inMarketing Channels reports.
va_closer_detail
8-bit unsigned integerID for [first/last] -touchvalue in Marketing Channels
va_closer_id
reports. ID labels are found intheMarketing Channel Manager.
String (255 characters)Detail for first-touch value in theMarketing Channels Report.
va_finder_detail
8-bit unsigned integerID for [first/last] -touchvalue in Marketing Channels
va_finder_id
reports. ID labels are found intheMarketing Channel Manager.
1=A channel instance(displayed as "Click
8-bit unsigned integerInstance event for last-touchvalue in Marketing Channelsreports
va_instance_event
Throughs" in the reportinginterface). Otherwise, thevalue is 0.
8-bit unsigned integerNew engagement for first-touchvalue in Marketing Channelsreports
va_new_engagement
Video solution variables. SeeVideo Solution Variables
video*
64-bit unsigned integerPart 1 of the visitorID. Thecombination of two visitor IDs
visid_high1. 70E+18
(visid_high and visid_low)creates a unique visitor ID.
64-bit unsigned integerPart 2 of the visitorID. Thecombination of two visitor IDs
visid_low1. 21E+17
(visid_high and visid_low)creates a unique visitor ID.
string (1 character)Indicates whether this is anewly-generated visitorID. Only
visid_new
available if visid_type=3(Example: a new s_vi cookiewas generated).
26Clickstream Data Column Reference
32-bit unsigned integerIf the visitorID was generated byus (visid_type=3), this is the
visid_timestamp
timestamp for when the ID wasoriginally created.
0=Custom VisitorID (Acustom visitor ID was set inthe code using s.visitorID)
8-bit unsigned integerInteger that specifies how thevisitorID was calculated (basedon a lookup).
visid_type
1=IP&UA fallback (cookieswere rejected by browser)
2=Wireless (HTTP MobileSubscriber Header identifiedas mobile carrier)
3=Adobe (server generated,stored in s_vi on client)Default method.
4=Fallback cookie (newfallback ID, JavaScriptgenerated, stored in s_fidon client, added in H25.3)
5=ID Service
See Identifying UniqueVisitors.
my keywordString (255 characters)Keywords used to find the site.visit_keywords
1
Note that visit_num is notincremented for excluded
32-bit unsigned integerThe number of the current visit(Incremented each time a visitorreturns to the site).
visit_num
hits (hits whereexclude_hit column > 0).
1732-bit unsigned integerThe page sequence number inthe current visit.
visit_page_num
String (255 characters)The referring domain of the visit(based on referrer).
visit_ref_domain
8-bit unsigned integerInteger representing the type ofreferral for the visit. Lookup
visit_ref_type
values can be obtained fromreferrer_type.csv lookup table.
http://www.google.comString (255 characters)The referrer to the visit.visit_referrer
032-bit unsigned integerThe search engine used to findthe site.
visit_search_engine
http://www.adobe.comString (255 characters)The start page for the visit.visit_start_page_url
27Clickstream Data Column Reference
homepageString (255 characters)The pagename the visit startedon.
visit_start_pagename
110275071632-bit unsigned integerThe GMT timestamp of the firstpageview in this visit.
visit_start_time_gmt
[Custom]8-bit unsigned integerA flag to determine if current hitis a new weekly visitor.
weekly_visitor
08-bit unsigned integerA flag to determine if current hitis a new yearly visitor.
yearly_visitor
84604String (255 characters)Zip code (i.e. 84604,85381)passed in by JavaScript, or
zip
populated by GeoSegmentationdata.
Events Lookup for Solution Variables
Solution variable events appear as numeric codes in the event_list and post_event_list, and are custom toeach report suite.You must use the events.tsv file that is delivered with each data feed to decode the eventnumbers in the post_event_list.
This applies to columns in the following sections:
• App Store Solution Variables• Mobile Solution Variables• Social Solution Variables• Video Solution Variables
App Store Solution Variables
Events LookupTypeDescriptionVariable/Event
Solution variable events appearas numeric codes in the
Contained in event_listThe number of mobile applicationdownloads.
AppStoreDownloads
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listThe number of in app purchases.AppStorePurchases
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the event
28Clickstream Data Column Reference
numbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listUsed to calculate the averageapp ranking. This calculated
AppStore Rank
event_list andmetric is defined using thefollowing formula: post_event_list, and are
custom to each report suite.You[AppStore Rank] / [AppStore
Rank (divisor)]must use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listUsed to calculate the averageapp ranking. This calculated
AppStore RankDivisor
event_list andmetric is defined using thefollowing formula: post_event_list, and are
custom to each report suite.You[AppStore Rank] / [AppStore
Rank (divisor)]must use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listThe amount of in app revenue.AppStore In-AppRevenue
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listThe amount of revenueassociated with the purchase ofan app.
AppStore One-offRevenue
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
29Clickstream Data Column Reference
Solution variable events appearas numeric codes in the
Contained in event_listThe amount of in app revenueminus amount retained by appstore.
AppStore In-AppRoyalties
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listThe amount of one off revenueminus amount retained by appstore.
AppStore One-offRoyalties
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listUsed to calculate the averageapp ranking. This calculated
AppStore Rating
event_list andmetric is defined using thefollowing formula: post_event_list, and are
custom to each report suite.You[AppStore Rating] /
[AppStore Rating (divisor)]must use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listUsed to calculate the averageapp ranking. This calculated
AppStore RatingDivisor
event_list andmetric is defined using thefollowing formula: post_event_list, and are
custom to each report suite.You[AppStore Rating] /
[AppStore Rating (divisor)]must use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
30Clickstream Data Column Reference
Mobile Solution Variables
Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_".
Events LookupTypeDescriptionVariable/Event
Solution variable events appearas numeric codes in the
string (255 characters)Populated from thea.action context dataautomatically passed in
mobileaction
event_list andwhen trackAction is calledin the SDK. Allows for post_event_list, and areautomatic action pathingin the app.
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listAction Time In Appmobileactioninapptime
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listAction Time Totalmobileactiontotaltime
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)App Id. Stores theApplication name and
mobileappid
event_list andversion in the followingformat: post_event_list, and are
custom to each report suite.You[AppName]
[BundleVersion]must use the events.tsv filethat is delivered with each data
For example, myapp 1.1 feed to decode the event
31Clickstream Data Column Reference
numbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Mobile Campaign Contentmobilecampaigncontent
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Mobile Campaign Mediummobilecampaignmedium
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Mobile Campaign Namemobilecampaignname
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Mobile Campaign Sourcemobilecampaignsource
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
32Clickstream Data Column Reference
Solution variable events appearas numeric codes in the
string (255 characters)Mobile Campaign Termmobilecampaignterm
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listCrashes. Triggered whenthe application does notexit gracefully. Event is
mobilecrashes
event_list andsent on application startafter crash (the application post_event_list, and areis considered to crash ifquit is not called).
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Day of Week. Number ofthe week day the app waslaunched.
mobiledayofweek
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Days Since First Use.Number of days since firstrun.
mobiledayssincefirstuse
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
33Clickstream Data Column Reference
Solution variable events appearas numeric codes in the
string (255 characters)Days Since Last Use.Number of days since lastuse.
mobiledayssincelastuse
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Device Name. Stores thedevice name.
mobiledevice
event_list andOn iOS, this is acomma-separated 2 digit post_event_list, and are
custom to each report suite.Youstring that Identifies themust use the events.tsv fileiOS device. The firstthat is delivered with each datanumber typicallyfeed to decode the eventrepresents the devicenumbers in thepost_event_list.
generation, and thesecond number typicallyversions differentmembers of the devicefamily.
Solution variable events appearas numeric codes in the
string (255 characters)Hour of Day. Measuresthe hour the app was
mobilehourofday
event_list andlaunched. 24 hournumerical format. Used for post_event_list, and aretime parting to determinepeak usage times.
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)First Launch Date. Date offirst launch afterinstallation. MM/DD/YYYY
mobileinstalldate
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the event
34Clickstream Data Column Reference
numbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listFirst Launches. Triggeredon first run afterinstallation (orre-installation).
mobileinstalls
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listLaunches. Triggered onany run that is not aninstall or an upgrade. This
mobilelaunches
event_list andalso triggers when theapplication is brought outof the background.
post_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Launch Number. Numberof times the application
mobilelaunchnumber
event_list andwas launched or broughtout of the background. post_event_list, and are
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
String (255 characters);Mobile solution variable
Mobile message idmobilemessageid
String (255 characters);Mobile solution variable
mobile message onlinemobilemessageonline
Solution variable events appearas numeric codes in the
string (255 characters)Operating SystemVersion.
mobileosversion
event_list and
35Clickstream Data Column Reference
post_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listPrevious Session Length.Aggregated total PreviousSession Length.
mobileprevsessionlength
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Example:booleanIndicates whether or not a
user has opted in for pushmessaging
mobilepushoptin
1
Example:StringIdentifier for a pushmessage that has beenclicked-through by theuser
mobilepushpayloadid
"83659238-7428-0174-7538-056718462846"
Solution variable events appearas numeric codes in the
string (255 characters)Resolution.Width x Heightin actual pixels.
mobileresolution
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Lifetime Value (evar)mobileltv
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the event
36Clickstream Data Column Reference
numbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listLifetime Value (event)mobileltvtotal
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listUpgrades. Triggered onfirst run after upgrade(anytime the versionnumber changes).
mobileupgrades
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Point of Interest Namepointofinterest
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Distance to Point ofInterest Center
pointofinterestdistance
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
37Clickstream Data Column Reference
Stringpost version ofmobileactionpost_mobileaction
Stringpost version ofmobileappidpost_mobileappid
Stringpost version ofmobilecampaigncontentpost_mobilecampaigncontent
Stringpost version ofmobilecampaignmediumpost_mobilecampaignmedium
Stringpost version ofmobilecampaignnamepost_mobilecampaignname
Stringpost version ofmobilecampaignsourcepost_mobilecampaignsource
Stringpost version ofmobilecampaigntermpost_mobilecampaignterm
Stringpost version ofmobiledayofweekpost_mobiledayofweek
Stringpost version ofmobiledevicepost_mobiledevice
Stringpost version ofmobiledayssincelastusepost_mobiledayssincelastuse
Stringpost version ofmobiledayssincefirstusepost_mobiledayssincefirstuse
Stringpost version ofmobilehourofdaypost_mobilehourofday
Stringpost version ofmobileinstalldatepost_mobileinstalldate
Stringpost version ofmobilelaunchnumberpost_mobilelaunchnumber
String (255 characters);Mobile solution variable
post version ofmobilemessageidpost_mobilemessageid
String (255 characters);Mobile solution variable
post version ofmobilemessageonlinepost_mobilemessageonline
Stringpost version ofmobileosversionpost_mobileosversion
booleanpost version ofmobilepushoptin
post_mobilepushoptin
Stringpost version ofmobilepushpayloadid
post_mobilepushpayloadid
Stringpost version ofmobileresolutionpost_mobileresolution
Stringpost version of mobileltvpost_mobileltv
38Clickstream Data Column Reference
string (255 characters)post version ofpointofinterest
pointofinterest
string (255 characters)post version ofpointofinterestdistance
pointofinterestdistance
Social Solution Variables
Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_".
Events LookupTypeDescriptionVariable/Event
Solution variable eventsappear as numeric codes in
255Social Campaign Variablesocialassettrackingcode
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
textAuthors.socialauthor
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Not in use.socialaveragesentiment
Solution variable eventsappear as numeric codes in
textSocial Platforms /Properties.
socialcontentprovider
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
Contained in event_listFacebook Interactions.socialfbstories
39Clickstream Data Column Reference
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
Contained in event_listPeople Talking About This.socialfbstorytellers
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
String (255 characters)social interaction countsocialinteractioncount
String (255 characters)social interaction typesocialinteractiontype
Solution variable eventsappear as numeric codes in
textLanguage.sociallanguage
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
textLatitude / Longitude.sociallatlong
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
40Clickstream Data Column Reference
Solution variable eventsappear as numeric codes in
Contained in event_listLike Adds.sociallikeadds
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Not in use.sociallink
Solution variable eventsappear as numeric codes in
textMention.socialmentions
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
String (255 characters)social owned definitioninsight typesocialowneddefinitioninsighttype
String (255 characters)social owned definitioninsight valuesocialowneddefinitioninsightvalue
String (255 characters)social owned definitionmetricsocialowneddefinitionmetric
String (255 characters)social owned definitionproperty vs postsocialowneddefinitionpropertyvspost
String (255 characters)social owned post IDssocialownedpostids
String (255 characters)social owned property idsocialownedpropertyid
String (255 characters)social owned propertynamesocialownedpropertyname
String (255 characters)socialownedpropertypropertyvsapp
Solution variable eventsappear as numeric codes in
Contained in event_listSocial Property Views.socialpageviews
the event_list andpost_event_list, and arecustom to each report suite.
41Clickstream Data Column Reference
You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
Contained in event_listPost Views.socialpostviews
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Not in use.socialproperty
Solution variable eventsappear as numeric codes in
Contained in event_listComments.socialpubcomments
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
Contained in event_listPosts.socialpubposts
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
String (255 characters)
Contained in event_list
Recommends.socialpubrecommends
the event_list andpost_event_list, and arecustom to each report suite.
42Clickstream Data Column Reference
You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
Contained in event_listFollowers.socialpubsubscribers
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Solution variable eventsappear as numeric codes in
Social Listening Query,hashed value
socialterm
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
Not in use.socialtermslist
Solution variable eventsappear as numeric codes in
Contained in event_listSentiment.socialtotalsentiment
the event_list andpost_event_list, and arecustom to each report suite.You must use theevents.tsv file that isdelivered with each data feedto decode the event numbersin the post_event_list.
String (255 characters)post version ofsocialaccountandappidspost_socialaccountandappids
String (255 characters)post_socialassettrackingcode
String (255 characters)post_socialauthor
43Clickstream Data Column Reference
String (255 characters)post_socialcontentprovider
String (255 characters)post_socialfbstories
String (255 characters)post_socialfbstorytellers
String (255 characters)post version ofsocialinteractioncountpost_socialinteractioncount
String (255 characters)post version ofsocialinteractiontypepost_socialinteractiontype
String (255 characters)post_sociallanguage
String (255 characters)post_sociallatlong
String (255 characters)post_sociallikeadds
String (255 characters)post_socialmentions
String (255 characters)post version ofsocialowneddefinitioninsighttypepost_socialowneddefinitioninsighttype
String (255 characters)post version ofsocialowneddefinitioninsightvaluepost_socialowneddefinitioninsightvalue
String (255 characters)post version ofsocialowneddefinitionmetricpost_socialowneddefinitionmetric
String (255 characters)post version ofsocialowneddefinitionpropertyvspostpost_socialowneddefinitionpropertyvspost
String (255 characters)post version ofsocialownedpostidspost_socialownedpostids
String (255 characters)post version ofsocialownedpropertyidpost_socialownedpropertyid
String (255 characters)post version ofsocialownedpropertynamepost_socialownedpropertyname
String (255 characters)post version ofsocialownedpropertypropertyvsapppost_socialownedpropertypropertyvsapp
String (255 characters)post version ofsocialpageviewspost_socialpageviews
String (255 characters)post version ofsocialpostviewspost_socialpostviews
String (255 characters)post version ofsocialpubcommentspost_socialpubcomments
String (255 characters)post version ofsocialpubpostspost_socialpubposts
String (255 characters)post version ofsocialpubrecommendspost_socialpubrecommends
44Clickstream Data Column Reference
String (255 characters)post version ofsocialpubsubscriberspost_socialpubsubscribers
String (255 characters)post version of socialtermpost_socialterm
String (255 characters)post version ofsocialtotalsentimentpost_socialtotalsentiment
Video Solution Variables
Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_".
Events LookupTypeDescriptionVariable/Event
Solution variable events appearas numeric codes in the
string (255 characters)Video namevideo
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Ad namevideoad
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listAd Completes. Indicatesthat a user has viewed acomplete video or ad.
videoadcomplete
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
45Clickstream Data Column Reference
Solution variable events appearas numeric codes in the
string (255 characters)Ad in Pod positionvideoadinpod
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Ad Player Namevideoadplayername
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Ad Podvideoadpod
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listAd Views. Indicates that avisitor has viewed someportion of an ad. However,
videoadstart
event_list andit does not provide anyinformation about how post_event_list, and aremuch, or what part, of avideo the visitor viewed.
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
46Clickstream Data Column Reference
Solution variable events appearas numeric codes in the
Contained in event_listAd Time Viewed. Total timespent viewing the ad.
videoadtime
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Channelvideochannel
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
string (255 characters)Chapter namevideochapter
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listVideo Completes. Indicatesthat a user has viewed acomplete video or ad.
videocomplete
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
47Clickstream Data Column Reference
Solution variable events appearas numeric codes in the
string (255 characters)Content Type. Content typeis set to "Video"automatically for all videoviews.
videocontenttype
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
String (100 Bytes)videopath
Solution variable events appearas numeric codes in the
string (255 characters)Player Namevideoplayername
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Video quality evarvideoqoebitrateaverageevar
Video quality evarvideoqoebitratechangecountevar
Video quality evarvideoqoebuffercountevar
Video quality evarvideoqoebuffertimeevar
Video quality evarvideoqoedroppedframecountevar
Video quality evarvideoqoeerrorcountevar
Video quality evarvideoqoetimetostartevar
Solution variable events appearas numeric codes in the
string (255 characters)Segmentvideosegment
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listVideo Segment Views. Senton all close events, whichoccur on video complete or
videosegmentviews
48Clickstream Data Column Reference
event_list andpost_event_list, and are
when the users stopsviewing at some pointbefore the complete occurs.
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listVideo Views. Indicates thata visitor has viewed someportion of a video. However,
videostart
event_list andit does not provide anyinformation about how post_event_list, and aremuch, or what part, of avideo the visitor viewed.
custom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
Solution variable events appearas numeric codes in the
Contained in event_listVideo Time Viewed. Totaltime spent viewing thevideo.
videotime
event_list andpost_event_list, and arecustom to each report suite.Youmust use the events.tsv filethat is delivered with each datafeed to decode the eventnumbers in thepost_event_list.
string (255 characters)post version of videopost_video
string (255 characters)post version of videoadpost_videoad
string (255 characters)post version ofvideoadinpod
post_videoadinpod
string (255 characters)post version ofvideoadlength
post_videoadlength
string (255 characters)post version ofvideoadname
post_videoadname
string (255 characters)post version ofvideoadplayername
post_videoadplayername
string (255 characters)post version of videoadpodpost_videoadpod
string (255 characters)post version ofvideochannel
post_videochannel
49Clickstream Data Column Reference
string (255 characters)post version ofvideochapter
post_videochapter
string (255 characters)post version ofvideocontenttype
post_videocontenttype
string (255 characters)post version of videolengthpost_videolength
string (255 characters)post version of videonamepost_videoname
string (255 characters)post version of videopathpost_videopath
string (255 characters)post version ofvideoplayername
post_videoplayername
string (255 characters)post version ofvideoqoebitrateaverageevar
post_videoqoebitrateaverageevar
string (255 characters)post version ofvideoqoebitratechangecountevar
post_videoqoebitratechangecountevar
string (255 characters)post version ofvideoqoebuffercountevar
post_videoqoebuffercountevar
string (255 characters)post version ofvideoqoebuffertimeevar
post_videoqoebuffertimeevar
string (255 characters)post version ofvideoqoedroppedframecountevar
post_videoqoedroppedframecountevar
string (255 characters)post version ofvideoqoeerrorcountevar
post_videoqoeerrorcountevar
string (255 characters)post version ofvideoqoetimetostartevar
post_videoqoetimetostartevar
string (255 characters)post version ofvideosegment
post_videosegment
Page Event Lookup
Lookup table to determine the type of a hit based on the page_event value.
post_page_event valuepage_event valueHit type
0 for all page views (s.t() calls)same as postPage views
0 for trackState calls from the mobile SDKs.
100 for "other link"10 for "other link"Link tracking
100 for trackAction and lifecycle calls from theMobile SDKs.
10 for trackAction and lifecycle callsfrom the Mobile SDKs.
101 for "download link"11 for "download link"
102 for "external or exit link"12 for "external or exit link"
76 - Media start event31 – Media start eventMilestone Video
50Clickstream Data Column Reference
post_page_event valuepage_event valueHit type
77 - Media update only event (doesn't perform anyeVar or any other variable processing)
32 – Media update only event (doesn’tperform any eVar or any other variableprocessing)
78 - Media + other variable update event (includeseVar and other variable processing)33 – Media + other variable update
event (includes eVar and othervariable processing)
50 = (non-Primetime) Media Stream Startsame as post
Heartbeat Video
51 = (non-Primetime) Media Stream Close(Complete/Finish)
52 = (non-Primetime) Media Stream Scrubbing
53 = (non-Primetime) Media Stream Keep Alive(internal only, will not appear in data feed)
54 = (non-Primetime) Media Stream Ad Start
55 = (non-Primetime) Media Stream Ad Close(Complete/Finish)
56 = (non-Primetime) Media Stream Ad Scrubbing
60 = Primetime Media Stream Start
61 = Primetime Media Stream Close(Complete/Finish)
62 = Primetime Media Stream Scrubbing
63 = Primetime Media Stream Keep Alive (internalonly, will not appear in data feed)
64 = Primetime Media Stream Ad Start
65 = Primetime Media Stream Ad Close(Complete/Finish)
66 = Primetime Media Stream Ad Scrubbing
8040Survey
70 - Indicates a hit that includes TargetActivity data.This is 70 for hits that are
Analytics for Target
and are not associated with anAnalytics call.
Hit Source Lookup
Lookup table to determine the source of a hit based on the page_event value.
51Clickstream Data Column Reference
Hit sourceID
Page view or tracked link with no timestamp passed in (non-timestamped report suites)1
Page view or tracked link with timestamp passed in (timestamped report suites)2
Live log file (not historical log file) with hit timestamps3
not used4
"generic" (sometimes known as ecommerce) data source (like current data source)5
full (historical) log file (not live log file)6
transactionid/customerid data source file7
SCM (SearchCenter+) data sources8
Adobe Social summary metrics9
52Clickstream Data Column Reference
Calculating MetricsDescribes how to calculate common metrics using clickstream data feeds.
Pre vs. Post column
Bots
Bots are excluded from data feeds according to the bot rules defined for your report suite.
Date filtering
Include rows from the date range you want included by filtering the date_time field. The date_time field is humanreadable (for example, YYYY-MM-DD HH:MM:SS) and is adjusted to the time zone of the report suite. For example,date_time starts with "2013-12" includes hits from December 2013.
Event string
The event string in event_list and post_event_list contains a comma-delimited list of events, which may havea value and/or a unique ID.We recommend doing all processing on the post_event_list because it is de-duplicatedand has already applied logic to remove duplicate events with the same ID (see Event Serialization).
For event ID to name mapping, see the event lookup delivered with your data feed.
For more information on events, see Events.
Formulas for common metrics
The following table contains instructions to calculate several common metrics.
How to calculateMetric
Page views can be calculated by counting when there is either a value in post_pagename orpost_page_url.
Page Views
You can use similar logic to count custom links:
• post_page_event = 100 to count custom links.• post_page_event = 101 to count download links.• post_page_event = 102 to count exit links.
Visits1. Exclude all rows where exclude_hit > 0.2. Exclude all rows with hit_source = 5,7,8,9. 5, 8, and 9 are summary rows uploaded using
data sources. 7 represents transaction ID data source uploads that should not be includedin visit and visitor counts. See Hit Source Lookup.
3. Combine post_visid_high, post_visid_low, visit_num, and visit_start_time_gmt*.Count unique number of combinations.
*In rare circumstances, internet irregularities, system irregularities, or the use of custom visitorIDs can result in duplicate visit_num values for the same visitor ID that are not the same visit.To avoid resulting issues, also include visit_start_time_gmt when counting visits.
Visitors1. Exclude all rows where exclude_hit > 0.
53Calculating Metrics
How to calculateMetric
2. Exclude all rows with hit_source = 5,7,8,9. 5, 8, and 9 are summary rows uploaded usingdata sources. 7 represents transaction ID data source uploads that should not be includedin visit and visitor counts. See Hit Source Lookup
3. Combine post_visid_high with post_visid_low. Count unique number of combinations.
When an event is set on a hit, post_event_list contains the event. The post_event_list isde-duplicated and is recommended to determine event instances.
Event instances
For example:
post_event_list = 1,200
Indicates an instance of purchase and event1.
1. Exclude all rows where exclude_hit > 0.2. Exclude all rows with hit_source = 5,8,9. These are summary rows uploaded using data
sources. See Hit Source Lookup.3. Count the number of times the event lookup value appears in post_event_list.
When an eVar is set on a hit, event_list contains an instance of that eVar.eVar instances
For example:
post_event_list = 100,101,106
Indicates an instance of eVar1, eVar2, and eVar7.This means that a value for these three eVarswas set on the hit.
To calculate instances for eVars, use the same logic explained in Event instances above, butcount the number of times the eVar lookup appears in the post_event_list.
To calculate time spent, you must group hits by visit, then order them according to the hit numberwithin the visit.
Time Spent
1. Exclude all rows where exclude_hit > 0.2. Group hits for a visit by concatenating visid_high, visid_low, and visit_num.3. Order hits for each visit by visit_page_num.4. Using page_event, filter the types of hits you want.5. Find hits where the value you want to track time spent is set. For example:
hit 1: post_prop1=redhit 2: post_prop1=blue
6. Subtract the post_cust_hit_time for hit 1 from the post_cust_hit_time for hit 2 todetermine the seconds between these two hits. The result is the time spent forpost_prop1=red. If this results in a negative number, it indicates that the hit was receivedout-of-order and the calculation should be discarded.
This logic can be extended to calculate time spent for other values.When calculating time spent,Analytics calculates time spent based on the time the value was set in a track (page_event=0)or trackLink (page_event=10|11|12) call, to the time of the next page view (track call).
When reporting time spent for a specific period, marketing reports & analytics and ad hoc analysisevaluate hits beyond the reporting period to determine time spent for values within the reporting
54Calculating Metrics
How to calculateMetric
period, except when the start and/or end date of the time period is on a monthly boundary. Dueto the complexity of these calculations, it might be difficult to match the time spent metricsexactly. Data warehouse does not evaluate hits beyond the reporting period.
Currency conversion is applied to the post_product_list according to the settings for thereport suite, so using that column is recommended.
Revenue, orders,units
1. Exclude all rows where exclude_hit > 0.2. Exclude all rows with hit_source = 5,8,9. 5-9 represent summary rows uploaded using
data sources. See Hit Source Lookup.3. Ignore purchase data for rows where duplicate_purchase = 1. This flag indicates that the
purchase is a duplicate (meaning that a hit with the same purchaseID was already recorded).4. The post_product_list uses the same syntax as s.products, so you can parse this string
to calculate metrics. For example:
;Cross Trainers;1;69.95,;Athletic Socks;10;29.99
By parsing this string, you can determine that 1 pair of cross trainers were purchased for$69.95, and that total revenue from this purchase was $99.94.
Note: Analytics allows currency events that contain product revenue to be passed inthrough the events string, so you might need to account for revenue that is not in theproducts string. See Numeric/Currency Events in s.events.
55Calculating Metrics
Identifying Visitors
Analytics provides several mechanisms by which visitors can be identified (listed in Analytics Visitor IDs). Regardlessof the method used to identify a visitor, in data feeds the final visitor ID used by Analytics is split across thepost_visid_high and post_visid_low columns, even when using the Experience Cloud ID Service.
To identify unique visitors:
1. Exclude all rows where exclude_hit > 0.2. Exclude all rows with hit_source = 5,7,8,9. 5, 8, and 9 are summary rows uploaded using data sources. 7
represents transaction ID data source uploads that should not be included in visit and visitor counts. See HitSource Lookup
3. Combine post_visid_high with post_visid_low. All hits across all dates that contain this combination ofpost_visid_high and post_visid_low can be considered as coming from same visitor.
If you would like to determine which mechanism was used to determine the visitor ID value (for example, to calculatecookie acceptance), the post_visid_type contains a lookup key that indicates which ID method was used. Thelookup keys are listed along with the visitor ID mechanisms in the table below.
Experience Cloud Visitor ID
The Experience Cloud Visitor ID is reported in a separate column, mcvisid. Because this ID is reported in its owncolumn, it can be unclear if Analytics is using this ID or a different ID to identify a visitor.
If the Experience Cloud Visitor ID was used to identify the visitor, the ID will be contained in the post_visid_highand post_visid_low columns and the post_visid_type will be set to 5. When calculating metrics, you should usethe value from the post_visid_high and post_visid_low columns since these columns will always contain thefinal visitor ID.
Tip: When using the Adobe Analytics visitor ID as a key for other systems, always use post_visid_high andpost_visid_low. These fields are the only visitor ID fields guaranteed to have a value with every row in the datafeed.
Analytics Visitor IDs
There are several ways a visitor can be identified in Analytics (listed in the following table in order of preference):
Present Whenpost_visid_typecolumnvalue
Query Parameter (collection method)OrderUsed
s.visitorID is set.0vid (s.visitorID)
Visitor had an existing s_vi cookie before youdeployed the ID Service, or you have a VisitorID grace period configured.
3aid (s_vi cookie)
Visitor's browser accepts cookies (first-party),and the Experience Cloud ID Service isdeployed.
5mid (AMCV_ cookie set by ExperienceCloud ID Service)
Visitor's browser accepts cookies (first-party).4fid (fallback cookie on H.25.3 or newer, orAppMeasurement for JavaScript)
Device is recognized as a mobile device.2HTTP Mobile Subscriber header
56Identifying Visitors
Present Whenpost_visid_typecolumnvalue
Query Parameter (collection method)OrderUsed
Visitor's browser does not accept cookies.1IP Address, User Agent, Gateway IPAddress
In many scenarios you might see 2 or 3 different IDs on a call, but Analytics will use the first ID present from thatlist as the official visitor ID, and split that value across the post_visid_high and post_visid_low columns. Forexample, if you are setting a custom visitor ID (included in the "vid" query parameter), that ID will be used beforeother IDs that might be present on that same hit.
57Identifying Visitors
Pre and Post ColumnsThe pre column contains the data as it was sent to data collection.The post column contains the value after processing.
For example, variable persistence, processing rules, VISTA rules, and currency conversion might change the finalvalue recorded for a variable that appears in the post column. For most calculations you want to use the post columnunless you are applying custom business logic (for example, applying a custom formula to determine attribution).
If a column does not contain a pre or a post version (for example, visit_num), then the column can be considereda post column. Columns prefixed with "pre_" typically contain data that was populated by Adobe and not sent byyour implementation. For example, pre_browser is populated by Adobe, but evar1 is populated by yourimplementation. Both of these columns have a "post_" column (post_browser, post_evar1), which contains thevalue used by reporting.
Case Sensitivity in Values
Most Analytics variables are considered as case-insensitive for reporting purposes, meaning different case variationsare considered to be the same value ("snow", "Snow", "SNOW", and "sNow" are all considered to be the samevalue). However, for display purposes, case sensitivity is preserved since most customers prefer to be able to sendin mixed case characters to display in reports.
When processing the data feed, you can lowercase values for comparison purposes, though you'll likely want topreserve case for display purposes.
If you see different case variations of the same value between the pre and post columns (for example, "snow" in thepre column, and "Snow" in the post column), it indicates that you are passing in both uppercase and lowercaseversions of the same value across your site. The case variation in the post column was previously passed in and isstored in the virtual cookie, or was processed around the same time for that report suite. For example:
Hit 1: s.list1="Tabby,Persian,Siamese”;
Hit 2: s.list1=“tabby,persian,siamese”;
When hit 2 is reported in the data feed, the pre column will contain the exact casing passed in (tabby,persian,siamese),but the value from hit 1 is likely persisted for that visit and will be reported in the post column (which will beTabby,Persian,Siamese) since hit 1 and 2 contain the exact same value when a case-insensitive comparison isperformed.
58Pre and Post Columns
Special CharactersInformation about special characters used in the Clickstream data feed.
• Special characters in the hit_data file• Special characters in multi-valued variables (events_list, products_list, mvvars)• Sample workflow
Special characters in the hit_data file
The following characters have a special meaning in the hit_data file:
DescriptionMeaningCharacter
Marks the end of a data field.End of column\t (tab character)
Marks the end of a data row.End of row\n (newline character)
Escapes tab, newline, and backslash when the characterwas part of the value sent during data collection.
Escape character\ (backslash character)
When any of the special characters are preceded by a backslash, they represent a literal character.
DescriptionMeaningCharacter
Literal tab character. This character was part of the valuesent in during data collection.
Tab\\t
Literal newline. This character was part of the value sent induring data collection.
Newline\\n
Literal backslash character. This character was part of thevalue sent in during data collection.
Backslash\\
Special characters in multi-valued variables (events_list, products_list, mvvars)
The following characters have a special meaning in multi-valued variables:
DescriptionMeaningCharacter
Separates product strings, event IDs, or other values inmulti-valued variables.
End of value, (comma character)
Separates values associated with an individual product inthe product_list.
End of sub-valuewithin an individualproduct value
; (semicolon character)
Assigns a value to an event in the event_list.Value assignment= (equals character)
When any of the special characters are preceded by a caret, they represent a literal character.
59Special Characters
DescriptionMeaningCharacter
Literal comma character.This character was part of the valuesent in during data collection.
Comma^,
Literal semicolon character. This character was part of thevalue sent in during data collection.
Semicolon^;
Literal equals character.This character was part of the valuesent in during data collection.
Equals^=
Literal caret character. This character was part of the valuesent in during data collection.
Caret^^
Sample workflow
If some of the columns in your data feed contain user-submitted data, you should check for special characters beforeseparating the data by column or row using split or readLine, or similar.
Consider the following data:
prop1eVar1Browser HeightBrowser Width
ensearch\nstring10501680
ensearch\tstring600800
During export, the newline and tab characters in the eVar1 values are escaped.The data feed for these rows appearsas follows:
1680\t1050\tsearch\\nstring\ten\n800\t600\tsearch\\tstring\ten\n
Calling readLine() on the first row returns the following partial string:
800\t600\tsearch\
Calling split("\t") on the second row returns the following string array:
800600search\stringen
To avoid this, use a solution similar to the following:
1. Starting at the beginning of the file, read until you locate a tab, newline, backslash or caret character.2. Perform an action based on the special character encountered:
• Tab - insert the string up that point into a data store cell and continue.• Newline - complete the data store row.• Backslash - read the next character, insert the appropriate string literal, and continue.• Caret - read the next character, insert the appropriate string literal, and continue.
60Special Characters
Troubleshooting
Transfer Failures
In the event of an FTP transfer failure (login denied, lost connection, out of quota, etc), Adobe attempts to automaticallyconnect and send the data up to three separate times. If the failures persist, the feed is marked as failed and anemail notification is sent.
When contacting Customer Care to correct delivery failures, be sure to give the agent your data feed ID. This feedID was provided by Customer Care when the data feed was initially created. If the feed ID is not available, providethe report suite ID and FTP destination.
Resend Options
If you need data for a delivery period resent, contact Customer Care. Adobe stores the generated data feed files forthe previous 7 days, so if the request is made within this period data feed files can be resent without being regenerated.
Daylight Savings impact on Hourly Data Feeds
For certain time zones the time will change twice a year due to daylight saving time (DST) definitions. Data feedshonor the time zone for which the report suite is configured. If the time zone for the report suite is one that does notuse DST, file delivery will continue normally like any other day. If the time zone of the report suite is one that doesuse DST, file delivery will be altered for the hour in which the time change occurs (usually 2:00 am).
When making STD -> DST time transitions (“Spring Forward”), the customer will only get 23 files. The hour that isskipped in the DST transition is simply omitted. For example, if the transition occurs at 2 AM, they’ll get a file for the1:00 hour, and will get a file for the 3:00 hour. There will be no 2:00 file, since at 2:00 STD, it becomes 3:00 DST.
When making DST -> STD transitions, (“Fall Back”), the customer will get 24 files. However, the hour of transitionwill actually include 2 hours’ worth of data. For example, if the transition occurs at 2:00 am, the file for 1:00 will bedelayed by one hour, but will contain data for two hours. It will contain data from 1:00 DST to 2:00 STD (which wouldhave been 3:00 DST). The next file will begin at 2:00 STD.
No Data for a Time Period
You can optionally configure a data feed to deliver a manifest file if no data is collected for a specific period. If youenable this option, you'll receive a manifest file similar to the following:
Datafeed-Manifest-Version: 1.0 Lookup-Files: 0 Data-Files: 0 Total-Records: 0
No Domain Info for Domain Reporting
Some mobile carriers (such as T-Mobile and O1) are no longer providing domain info for reverse-DNS lookups.Therefore, that data is not available for domain reporting.
Data Processing Overview
Before processing hourly or daily data, data feeds waits until all the hits that entered data collection within thetimeframe (day or hour) have been written out to data warehouse. After that occurs, data feeds collects the datawith timestamps that fall within the timeframe, compresses it, and sends it via FTP. For hourly feeds, files are typicallywritten out to data warehouse within 15-30 min after the hour, but there is no set time period. If there was no data
61Troubleshooting
with timestamps that fall within the timeframe, then the process tries again the next timeframe. The current datafeed process uses the date_time field to determine which hits belong to the hour. This field is based on the timezone of the report suite.
62Troubleshooting
Contact and Legal InformationInformation to help you contact Adobe and to understand the legal issues concerning your use of this product anddocumentation.
Help & Technical Support
The Adobe Experience Cloud Customer Care team is here to assist you and provides a number of mechanisms bywhich they can be engaged:
• Check the Experience Cloud help pages for advice, tips, and FAQs• Ask us a quick question on Twitter @AdobeExpCare• Log an incident in our customer portal• Contact the Customer Care team directly• Check availability and status of Experience Cloud Solutions
Service, Capability & Billing
Dependent on your solution configuration, some options described in this documentation might not be available toyou. As each account is unique, please refer to your contract for pricing, due dates, terms, and conditions. If youwould 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 can beadded to our Customer Idea Exchange.
Legal
© 2018 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 theUnited States and/or other countries. A trademark symbol (®, ™, etc.) denotes an Adobe trademark.
All third-party trademarks are the property of their respective owners. Updated Information/Additional Third PartyCode Information available at http://www.adobe.com/go/thirdparty.
63Contact and Legal Information