Adobe ® Marketing Cloud ClickStream Data Feeds
Dec 08, 2015
Adobe® Marketing Cloud
ClickStream Data Feeds
Contents
Clickstream Data Feeds Help.................................................................................3
What's New...............................................................................................................4
Configuring Data Feeds..........................................................................................8
Data Feed Contents...............................................................................................11
Clickstream Data Column Reference...................................................................14
Page Event Lookup...............................................................................................................30
Hit Source Lookup.................................................................................................................31
Calculating Metrics................................................................................................32
Pre and Post Columns..........................................................................................35
Special Characters................................................................................................36
Troubleshooting.....................................................................................................38
Contact and Legal Information.............................................................................39
ClickStream Data FeedsLast updated 8/18/2014
Clickstream Data Feeds Help
Important: See What's New to learn about an upcoming column expansion that impacts all data feedscustomers.
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 Data Feeds Help
What's NewCumulative release notes for Clickstream data feeds.
New OS Types Lookup File coming June 19, 2014
Clickstream data feed customers that are currently receiving the os column will automatically receive an additionallookup file for OS types starting June 19, 2014. Before this date, ensure that your processing system is prepared toreceive this additional lookup file.
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
ref_domainpost_prop1-75prop1-75
pluginsgeo_zipcode_ver
ct_connect_typec_coloraccept_language
post_ page_typepage_typeip
4What's New
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.
February 14, 2013
Format of post_product_list column when events are present but product is empty
5What's New
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
post_channel
post_mvvar1 – post_mvvar3
6What's New
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
Configuring Data FeedsData feeds are enabled by Customer Care and delivered using FTP.
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.
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.
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 six hours of the close of thathour’s worth of data.
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.
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.
8Configuring Data Feeds
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
Select an FTP location where Adobe should deliverdata feed files. Adobe can provide FTP hosting for thefiles if preferred.
CustomerSelect FTP location
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 hostname, credentials, and path.
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 customer-hostedor Adobe-hosted FTP site. When complete, a manifest
AdobeDelivery to customer
file (or .fin file for older feeds) is transferred indicatingthat the delivery is complete.
The customer monitors the FTP for the manifest file.This file contains details on all files that were delivered.
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
9Configuring Data Feeds
After you have configured your data feed, continue to Data Feed Contents to understand what files you will receive.
10Configuring 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
11Data Feed Contents
• country.tsv• javascript_version.tsv• languages.tsv• operating_systems.tsv• plugins.tsv• resolution.tsv• referrer_type.tsv• search_engines.tsv• event_lookup.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
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.
Each data file is delivered with the following name:
<index>-<report_suite>_<YYYY-mm-dd>.<compression_suffix>
12Data Feed Contents
DescriptionDelivery Format
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.
13Data Feed Contents
Clickstream Data Column ReferenceTable data describing the columns in the data feed.
Example lookupData typeColumn descriptionColumn name
en-us, ja;q=0.62, deString (255 characters)The accept language header fromthe browser.
accept_language
See Browser Lookup andBrowser Type Lookup Key:FK
32-bit unsigned integerThe browser ID (has lookup table)actually used for the hit. Seepre_browser.
browser
806 Key: FK32-bit unsigned integerHeight in pixels of browser window.browser_height
128032-bit unsigned integerWidth in pixels of browser window.browser_width
32String (255 characters)Color depth as generated fromJavaScript.
c_color
1123String (255 characters)The campaign value passed in onthe hit. May not end up being the
campaign
value that gets passed to theinterface (see post_campaign).
[Custom]String (255 characters)Custom traffic variable for sitesections (channels).
channel
http://www.adobe.comString (255 characters)Visitor click map information. Thisinformation is what is contained in
click_action
the address of the link the userclicked on (URL / JS function, etc.)
08-bit unsigned integerVisitor click map information. Thetype of link clicked on.
click_action_type
homepageString (255 characters)Visitor click map information. Thisis the pagename (or URL if no
click_context
pagename is declared) for the pageon which the link click occurred
08-bit unsigned integerVisitor click map information. Thetype of click_context (indicates
click_context_type
whether the pagename or URL wasused)
39632-bit unsigned integerVisitor click map information. Thisis the numeric ID for the location onthe page where the link is located
click_sourceid
AString (255 characters)Visitor click map information. Thetype of link or form element that wasclicked on.
click_tag
G.7-pD-SString (255 characters)The version of code in the JS filecreating the image request.
code_ver
See Color Depth LookupKey: FK
32-bit unsigned integerColor depth ID (has lookup table)that we ended up using for the hit.See pre_color.
color
14Clickstream Data Column Reference
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 (255 characters)Type of currency for the transaction.currency
110275071632-bit unsigned integer(timestamp-enabled report suitesonly) The timestamp sent with the
cust_hit_time_gmt
hit. This "timestamp" is in Unix time(number of seconds since Jan 1,1970.)
UserID123ABCString (255 characters)A visitor ID passed in with the hit tobe used as the visitor ID for the hit
cust_visid
(instead of using visid_high andvisid_low)
08-bit unsigned integerA flag to determine if current hit isa new daily visitor.
daily_visitor
YYYY-MM-DD HH:MM:SS(this is not in Unix time.)
datetimeThe time in readable format in TimeZone specified by Report Suite ID.Set by Adobe servers. Adobe
date_time
servers combinepost_cust_hit_time_gmt and thereport suite's time zone to createdate_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 was countedas a duplicate.
duplicate_events
08-bit unsigned integerA flag indicating that the purchaseevent for this hit should be ignoredbecause it is a duplicate.
duplicate_purchase
[Custom]String (255 characters)Custom commerce variable 1 - 75.evar1-75
For event ID to namemapping, see the
textComma separated list of numericIDs representing events passed infrom the customer.
event_list
event_lookup.tsv that isdelivered with the data feed.
15Clickstream Data Column Reference
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 page pagename.first_hit_pagename
http://www.yahoo.comString (255 characters)Original referrer - referrer of first hitever for the visitor.
first_hit_referrer
110275071632-bit unsigned integerTimestamp of the first hit in GMT.first_hit_time_gmt
los angelesString (255 characters)City from Digital Envoy.geo_city
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 Digital Envoy.geo_region
84103String (255 characters)Zip code based on IP-addresslookup
geo_zip
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values as passedin on the image request. The
hier1-5
delimiter is chosen by the clientduring implementation.
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values as passedin on the image request. The
hier3
delimiter is chosen by the clientduring implementation.
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values as passedin on the image request. The
hier4
delimiter is chosen by the clientduring implementation.
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values as passedin on the image request. The
hier5
delimiter is chosen by the clientduring implementation.
See Hit Source Lookup8-bit unsigned integerA flag for the back-end processingto know what type of hit 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
16Clickstream Data Column Reference
"timestamp" is in Unix time (numberof seconds since Jan 1, 1970.)
64-bit unsigned integerUsed to uniquely identify a hit. Thecombination of hitid_low and
hitid_high1. 14988E+15 Key: PRI
hitid_high creates a unique ID forthe row.
64-bit unsigned integerUsed to uniquely identify a hit. Thecombination of hitid_low and
hitid_low1. 50367E+16 Key: PRI
hitid_high creates a unique ID forthe row.
Nstring (1 character)Homepage flag, whether or not thispage was the user's homepage
homepage
08-bit unsigned integerA flag to determine if current hit isa new hourly visitor.
hourly_visitor
String (255 characters)IP address of user's computer, fromusers ISP.
ip1. 112.89.14
String (255 characters)A second IP address to be used byVISTA to determine validity of hits.
ip2
String (255 characters)Version of JavaScript supported bybrowser.
j_jscript1. 3
Ystring (1 character)Flag indicating whether or not javais 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
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 previous purchase.last_purchase_time_gmt
String (255 characters)Marketing Cloud Visitor ID TheMarketing Cloud Visitor ID is a
mcvisid1. 64983E+37
128-bit number that consists of 2signed, positive, 64-bit numbers inbase 10, both padded to 19 zeros,and then concatenated.
Mobile solution variables. SeeMobile Solution Variables
mobile*post_mobile*
2332-bit unsigned integerThe ID of the mobile device whichpassed the hit into marketingreports.
mobile_id
08-bit unsigned integerA flag to determine if current hit isa new monthly visitor.
monthly_visitor
17Clickstream Data Column Reference
textMvvars 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; reservedfor future release.
namespace
08-bit unsigned integerA flag that determines if the currenthit is a new visit.
new_visit
See Operating SystemsLookup Key: FK
32-bit unsigned integerOperating system ID (has lookuptable).
os
textList of plugins available to thebrowser.
p_plugins
0 See Page Event Lookup8-bit unsigned integerPage event ID, the type of hit thatis sent in the request. Look-ups
page_event
provided for type of event(normal,download, exit, custom)
http://www.adobe.comtextRelated to the page_event column.It is the URL of the download link,exit link or custom link clicked.
page_event_var1
homepage_buyString (255 characters)If you have individually named yourlink, this column contains the linkname.
page_event_var2
textUsed for both Survey and Mediamodule, and serves as the
page_event_var3
pre-version for both modules. (Thiscolumn contains the value passedin on the hit for the page event.)
errorPageString (255 characters)page type variable (only used forerror page).
page_type
http://www.adobe.com/search/search_results.htmtextThe URL of the pageview. Theaddress of the page in the addressbar of the browser.
page_url
search_resultsString (255 characters)The name of the page (if set).pagename
18-bit unsigned integerA (1/0) flag that determines if the hitwas used for paid search tracking.
paid_search
String (255 characters)Not usable by customers. This is acomma-separated list of plungin_ids
partner_plugins
(usually about 5 characters each)for plugins that partners haveregistered with us.
Ystring (1 character)A flag indicating if 3rd party cookiesand/or persistent cookies areenabled.
persistent_cookie
18Clickstream Data Column Reference
See Plugins Lookup Key:FK
String (255 characters)List of plugin IDs available to thebrowser (has lookup table) This isthe post value.
plugins
0 See Page Event Lookup8-bit unsigned integerPage event ID, the type of hit thatis sent in the request.
post_ page_event
errorPageString (255 characters)page type variable (only used forerror page).
post_ page_type
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 (255 characters)Custom traffic variable for sitesections (channels).
post_channel
Ystring (1 character)Specifies whether JavaScriptsession cookie is accepted.
post_cookies
USDString (255 characters)Type of currency for the transaction.post_currency
110275071632-bit unsigned integerTimestamp actually used for the hit,this is cust_hit_time_gmt for
post_cust_hit_time_gmt
timestamp-enabled report suites, orhit_time_gmt otherwise.
8-bit unsigned integerPost version of the cust_visid field.What we ended up using for the hit.
post_cust_visid
[Custom]String (255 characters)Persisting value of evar1-75.post_evar1-75
For event ID to namemapping, see the
textComma separated list of numericIDs representing events passed infrom the customer.
post_event_list
event_lookup.tsv that isdelivered with the data feed.Key: FK
[CUSTOM],[CUSTOM],[CUSTOM]String (255 characters)Delimited list of values as passedin on the image request. The
post_hier1-5
delimiter is chosen by the clientduring implementation.
Ystring (1 character)Flag indicating whether or not javais enabled.
post_java_enabled
my keywordString (255 characters)The keywords that were actuallyused for the hit.
post_keywords
textPost-processed mvvars. "What weended up using for the hit."
post_mvvar1-3
http://www.adobe.comString (255 characters)Related to the page_event column.It is the URL of the download link,exit link or custom link clicked.
post_page_event_var1
homepage_buyString (255 characters)If you have individually named yourlink, this column contains the linkname.
post_page_event_var2
19Clickstream Data Column Reference
textUsed for both Survey and Mediamodule, and serves as the
post_page_event_var3
pre-version for both modules. (Thiscolumn contains the value passedin on the hit for the page event.)
http://www.adobe.com/search/search_results.htmString (255 characters)The URL of the pageview. Theaddress of the page in the addressbar of the browser.
post_page_url
search_resultsString (255 characters)The name of the page (if set). If nopage is specified the URL is placedin this value.
post_pagename
search_resultsString (255 characters)The name of the page (if set). If nopage is specified this value is leftempty.
post_pagename_no_url
String (255 characters)List of partner plugins available tothe browser (has lookup table).
post_partner_plugins
Ystring (1 character)Flag indicating if 3rd party cookiesand/or persistent cookies areenabled.
post_persistent_cookie
Format is comma separatedlist of: category; product;
textThe product list as passed inthrough the JavaScript.
post_product_list
quantity; cost;custEventsDecValues;merchandisingValues
Computers;HPPavillion;1;1000;200|201,OfficeSupplies
[Custom]String (255 characters)Custom traffic variables 1 - 75.post_prop1-75
1584A9646GString (255 characters)Unique identifer for a purchase.Identifies a duplicate purchase (seeduplicate_purchase).
post_purchaseid
String (255 characters)Page prior to the current page.post_referrer
Search Engine Lookup32-bit unsigned integerThe numeric ID of the search enginethat was actually used and stored.
post_search_engine
AZString (255 characters)Geographical region (i.e. Arizona,Utah, Saxony [German Region])
post_state
passed in on JavaScrip. Normallyonly set on a purchase page.
3826-0-0--**--3826-1-1--**--3826-2-0textPost column for the marketingreports and Survey integration.
post_survey
Processed based onpage_event_var3.
12/11/2004 4:23:31 1 +420String (255 characters)Raw time info from JavaScript.post_t_time_info
textPost column for Analytics andTarget integration.
post_tnt
20Clickstream Data Column Reference
textPost column for Analytics andTarget integration.
post_tnt_action
A1B2C3D4String (255 characters)A unique identifier where variousdata points can be uploaded latervia Data Sources.
post_transactionid
64-bit unsigned integerThe visid_high value that we endedup using for the hit.
post_visid_high
64-bit unsigned integerThe visid_low value that we endedup 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 up usingfor the hit.
post_visid_type
1=IP&UA fallback (cookieswere rejected by browser)
2=Wireless (HTTP MobileSubscriber Headeridentified as 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=Visitor ID Service
See Identifying UniqueVisitors.
String (255 characters)Post version of the zip field. Whatwe use for the hit.
post_zip
032-bit unsigned integerThe page id of the previous page.This is an internal identifier and notuseful to the customer.
prev_page
Format is comma separatedlist of: category; product;
textThe product list as passed inthrough the JavaScript.
product_list
quantity; cost;custEventsDecValues;merchandisingValues
Computers;HPPavillion;1;1000;200|201,OfficeSupplies
21Clickstream Data Column Reference
Replaced by post_product_list asof April 2011. Contains data for
product_merchandising
Merchandising evars as they relateto products.
[Custom]String (255 characters)Custom traffic variables 1 - 75.prop1-75
1584A9646GString (255 characters)Unique identifier for a purchase.Identifies a duplicate purchase (seeduplicate_purchase).
purchaseid
[Custom]8-bit unsigned integerA flag to determine if current hit isa 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 values
ref_type
can be obtained fromreferrer_type.csv lookup table.
String (255 characters)Page prior to the current page.referrer
See Resolution LookupKey: FK
32-bit unsigned integerResolution id (has lookup table).resolution
1024x768String (255 characters)Screen resolution as passed in fromJavaScript.
s_resolution
Nstring (1 character)A (Y/N) field if the hit was used(sampled) or not for ad hoc analysis.
sampled_hit
See Search Engine LookupKey: FK
32-bit unsigned integerSearch engine ID, has lookup tablesearch_engine
132-bit unsigned integerThe page number of search resultsthat the keywords were on from thesearch engine.
search_page_num
08-bit unsigned integerUsed to track secondary hits.Secondary hits are charged at a rateof 50% of the normal costs.
secondary_hit
ssString (2 characters)Deprecated. pe or ss - type of hitcoming through. The page_event
service
column gives the same informationbut in more detail.
Social solution variables. See SocialSolution Variables
social*
post_social*
32-bit unsigned integerAdobe proprietary columninformation
sourceid
AZString (255 characters)Geographical region (i.e. Arizona,Utah, Saxony [German Region])
state
passed in on JavaScript. Normallyonly set on a purchase page.
22Clickstream Data Column Reference
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.
t_time_info
textPre column for Analytics and Targetintegration.
tnt
textPre column for Analytics and Targetintegration.
tnt_action
A1B2C3D4String (255 characters)A unique identifier where variousdata points can be uploaded latervia Data Sources.
transactionid
Nstring (1 character)A (Y/N) field that determines if thequery string of the hit was truncatedor not. i.e.
truncated_hit
String (255 characters)Screen color depth. Stands for UserAgent Color. From HTTP headersent by older browsers.
ua_color
String (255 characters)Screen color depth. Stands for UserAgent Operating System. From
ua_os
HTTP header sent by olderbrowsers.
String (255 characters)Screen color depth. Stands for UserAgent Pixels. From HTTP headersent by older browsers.
ua_pixels
textUser agent as found in the HTTPheader sent from the browser.
user_agent
375724966432-bit unsigned integerThe hash on the report suite ID.user_hash
[Custom]String (255 characters)Custom traffic variable for servers.user_server
64461432-bit unsigned integerThe numeric ID for the report suiteID (normally seen in the name ofDW 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 last-touch value in MarketingChannels reports.
va_closer_id
String (255 characters)Detail for first-touch value in theMarketing Channels Report.
va_finder_detail
8-bit unsigned integerID for first-touch value in MarketingChannels reports
va_finder_id
8-bit unsigned integerInstance event for first-touch valuein Marketing Channels reports
va_instance_event
8-bit unsigned integerNew engagement for first-touchvalue in Marketing Channels reports
va_new_engagement
23Clickstream Data Column Reference
Video solution variables. See VideoSolution Variables
video*
post_video*
64-bit unsigned integerPart 1 of the visitorID. Thecombination of two visitor IDs
visid_high1. 70E+18
(visid_high and visid_low) createsa 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) createsa 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 cookie was generated).
32-bit unsigned integerIf the visitorID was generated by us(visid_type=3), this is the timestamp
visid_timestamp
for when the ID was originallycreated.
0=Custom VisitorID (Acustom visitor ID was set inthe code using s.visitorID)
8-bit unsigned integerInteger that specifies how thevisitorID was calculated (based ona lookup).
visid_type
1=IP&UA fallback (cookieswere rejected by browser)
2=Wireless (HTTP MobileSubscriber Headeridentified as 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=Visitor 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).
24Clickstream Data Column Reference
1732-bit unsigned integerThe page sequence number in thecurrent visit.
visit_page_num
http://www.google.comString (255 characters)The referrer to the visit.visit_referrer
032-bit unsigned integerThe search engine used to find thesite.
visit_search_engine
http://www.adobe.comString (255 characters)The start page for the visit.visit_start_page_url
homepageString (255 characters)The pagename the visit started on.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 hit isa new weekly visitor.
weekly_visitor
08-bit unsigned integerA flag to determine if current hit isa new yearly visitor.
yearly_visitor
84604String (255 characters)Zip code (i.e. 84604,85381) passedin by JavaScript, or populated byGeoSegmentation data.
zip
App Store Solution Variables
TypeDescriptionVariable/Event
Contained in event_listThe number of mobile application downloads.AppStore Downloads
Contained in event_listThe number of in app purchases.AppStore Purchases
Contained in event_listUsed to calculate the average app ranking.Thiscalculated metric is defined using the followingformula:
AppStore Rank
[AppStore Rank] / [AppStore Rank
(divisor)]
Contained in event_listUsed to calculate the average app ranking.Thiscalculated metric is defined using the followingformula:
AppStore Rank Divisor
[AppStore Rank] / [AppStore Rank
(divisor)]
Contained in event_listThe amount of in app revenue.AppStore In-App Revenue
Contained in event_listThe amount of revenue associated with thepurchase of an app.
AppStore One-off Revenue
Contained in event_listThe amount of in app revenue minus amountretained by app store.
AppStore In-App Royalties
25Clickstream Data Column Reference
Contained in event_listThe amount of one off revenue minus amountretained by app store.
AppStore One-off Royalties
Contained in event_listUsed to calculate the average app ranking.Thiscalculated metric is defined using the followingformula:
AppStore Rating
[AppStore Rating] / [AppStore Rating
(divisor)]
Contained in event_listUsed to calculate the average app ranking.Thiscalculated metric is defined using the followingformula:
AppStore Rating Divisor
[AppStore Rating] / [AppStore Rating
(divisor)]
Video Solution Variables
Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_".
TypeDescriptionVariable/Event
string (255 characters)Video namevideo
string (255 characters)Ad namevideoad
string (255 characters)Segmentvideosegment
string (255 characters)Content Type. Content type is set to "Video"automatically for all video views.
videocontenttype
string (255 characters)Ad Podvideoadpod
string (255 characters)Ad in Pod positionvideoadinpod
string (255 characters)Player Namevideoplayername
string (255 characters)Channelvideochannel
string (255 characters)Ad Player Namevideoadplayername
Contained in event_listVideo Time Viewed. Total time spent viewingthe video.
videotime
Contained in event_listVideo Views. Indicates that a visitor has viewedsome portion of a video. However, it does notprovide any information about how much, orwhat part, of a video the visitor viewed.
videostart
26Clickstream Data Column Reference
Contained in event_listVideo Completes. Indicates that a user hasviewed a complete video or ad.
videocomplete
Contained in event_listVideo Segment Views. Sent on all close events,which occur on video complete or when theusers stops viewing at some point before thecomplete occurs.
videosegmentviews
Contained in event_listAd Views. Indicates that a visitor has viewedsome portion of an ad. However, it does notprovide any information about how much, orwhat part, of a video the visitor viewed.
videoadstart
Contained in event_listAd Completes. Indicates that a user has vieweda complete video or ad.
videoadcomplete
Contained in event_listAd Time Viewed. Total time spent viewing thead.
videoadtime
Mobile Solution Variables
Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_".
TypeDescriptionVariable/Event
string (255 characters)First Launch Date. Date of first launch afterinstallation. MM/DD/YYYY
mobileinstalldate
string (255 characters)App Id. Stores the Application name andversion in the following format:
mobileappid
[AppName] [BundleVersion]
For example, myapp 1.1
string (255 characters)Launch Number. Number of times theapplication was launched or brought out of thebackground.
mobilelaunchnumber
string (255 characters)Days Since First Use. Number of days sincefirst run.
mobiledayssincefirstuse
string (255 characters)Days Since Last Use. Number of days sincelast use.
mobiledayssincelastuse
string (255 characters)Hour of Day. Measures the hour the app waslaunched. 24 hour numerical format. Used fortime parting to determine peak usage times.
mobilehourofday
string (255 characters)Day of Week. Number of the week day the appwas launched.
mobiledayofweek
27Clickstream Data Column Reference
string (255 characters)Device Name. Stores the device name.
On iOS, this is a comma-separated 2 digitstring that Identifies the iOS device. The first
mobiledevice
number typically represents the devicegeneration, and the second number typicallyversions different members of the devicefamily.
string (255 characters)Operating System Version.mobileosversion
string (255 characters)Resolution. Width x Height in actual pixels.mobileresolution
string (255 characters)Mobile Campaign Sourcemobilecampaignsource
string (255 characters)Mobile Campaign Mediummobilecampaignmedium
string (255 characters)Mobile Campaign Termmobilecampaignterm
string (255 characters)Mobile Campaign Contentmobilecampaigncontent
string (255 characters)Mobile Campaign Namemobilecampaignname
counterPoint of Interest Namepointofinterest
counterDistance to Point of Interest Centerpointofinterestdistance
string (255 characters)Lifetime Value (evar)mobileltv
Contained in event_listFirst Launches. Triggered on first run afterinstallation (or re-installation).
mobileinstalls
Contained in event_listUpgrades. Triggered on first run after upgrade(anytime the version number changes).
mobileupgrades
Contained in event_listLaunches. Triggered on any run that is not aninstall or an upgrade. This also triggers whenthe application is brought out of thebackground.
mobilelaunches
Contained in event_listCrashes. Triggered when the application doesnot exit gracefully. Event is sent on applicationstart after crash (the application is consideredto crash if quit is not called).
mobilecrashes
Contained in event_listPrevious Session Length. Aggregated totalPrevious Session Length.
mobileprevsessionlength
Contained in event_listAction Time Totalmobileactiontotaltime
28Clickstream Data Column Reference
Contained in event_listAction Time In Appmobileactioninapptime
Contained in event_listLifetime Value (event)mobileltvtotal
Social Solution Variables
Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_".
TypeDescriptionVariable/Event
textSocial Platforms / Properties.socialcontentprovider
textAuthors.socialauthor
textLanguage.sociallanguage
textLatitude / Longitude.sociallatlong
textMention.socialmentions
Contained in event_listFollowers.socialpubsubscribers
Contained in event_listSentiment.socialtotalsentiment
Contained in event_listLike Adds.sociallikeadds
Contained in event_listSocial Property Views.socialpageviews
Contained in event_listPost Views.socialpostviews
Contained in event_listPeople Talking About This.socialfbstorytellers
Contained in event_listFacebook Interactions.socialfbstories
Contained in event_listRecommends.socialpubrecommends
Contained in event_listComments.socialpubcomments
Contained in event_listSubscribers.socialpubsubscribers
Contained in event_listPosts.socialpubposts
29Clickstream Data Column Reference
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
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)
30Clickstream Data Column Reference
post_page_event valuepage_event valueHit type
64 = Primetime Media Stream Ad Start
65 = Primetime Media Stream Ad Close(Complete/Finish)
66 = Primetime Media Stream Ad Scrubbing
8040Survey
Hit Source Lookup
Lookup table to determine the source of a hit based on the page_event value.
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
31Clickstream 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 Views1. 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. Sum the remaining rows that have post_page_event = 0, which indicates a normal page
view. See Page Event Lookup.
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, and visit_num. Count unique number ofcombinations.
Visitors1. Exclude all rows where exclude_hit > 0.
32Calculating 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
33Calculating 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.
34Calculating Metrics
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.
35Pre 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.
36Special 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.
37Special 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.
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
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 datawith 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.
38Troubleshooting
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 Marketing Cloud Customer Care team is here to assist you and provides a number of mechanisms bywhich they can be engaged:
• Check the Marketing Cloud help pages for advice, tips, and FAQs• Ask us a quick question on Twitter @AdobeMktgCare• Log an incident in our customer portal• Contact the Customer Care team directly• Check availability and status of Marketing Cloud Solutions
Service, Capability & 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 for AdobeAnalytics can be added to our Customer Idea Exchange.
Legal
© 2014 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.
All third-party trademarks are the property of their respective owners.
39Contact and Legal Information