Adobe Marketing Cloud ClickStream Data Feeds

(1)

(2)

Clickstream Data Feeds Help...3

What's New...4

Best Practices...8

Configuring Data Feeds...9

Data Feed Contents...12

Clickstream Data Column Reference...15

Page Event Lookup...46

Hit Source Lookup...47

Calculating Metrics...49

Identifying Visitors...52

Pre and Post Columns...54

Special Characters...55

Troubleshooting...57

Contact and Legal Information...58

ClickStream Data Feeds Last updated 6/1/2016

(3)

Clickstream Data Feeds Help

Important: See What's New to learn about an upcoming column expansion that impacts all data feeds customers. Raw clickstream data that is collected from web sites, mobile apps, or is uploaded using web service APIs or data sources, is processed and stored in Adobe's Data Warehouse. This raw clickstream data forms the data set that is used by Adobe Analytics. As a service, Adobe can deliver this raw data to the customer in a batched manner on a recurring daily or hourly delivery schedule. This service is called the "raw clickstream data feed", or just "data feed." Each data feed comprises the clickstream data for a single report suite.

To get started with clickstream data feeds, see Configuring Data Feeds.

(4)

What's New

Cumulative 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 additional lookup 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 column added.

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 expand the fields used to store lookup file keys, as these are increasing in size as well. Note that the column expansions that were previously scheduled for April 2014 have been postponed, and an announcement will be included in the release 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 your ETL 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_action click_tag ip2 pagename post_page_event_var2 page_event_var2 channel post_pagename_no_url post_pagename t_time_info user_server post_channel first_hit_pagename domain post_t_time_info post_transactionid transactionid visit_start_pagename ref_domain post_prop1-75 prop1-75 plugins geo_zip code_ver 4 What's New

(5)

ct_connect_type c_color accept_language post_ page_type page_type ip s_resolution post_purchaseid purchaseid visit_keywords ua_pixels ua_color geo_city stats_server post_keywords state j_jscript geo_region post_zip zip post_state post_currency currency namespace ua_os Integer expansion

Expand the following columns to store a 32-bit unsigned integer:

search_engine browser_width browser_height browser (Feb 20, 2014) post_browser_width post_browser_height language country color visit_search_engine resolution os (Feb 20, 2014) search_page_num post_search_engine geo_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 a modification 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 Video solution event numbers are different for each report suite. The event lookup file delivered with each report suite should 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 load on both origination and destination servers. See Configuring Data Feeds.

February 14, 2013

(6)

In post_product_list, If events are contained on the event list for a given hit but there is no product in the product list, 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 to receive the entire URL of each page and tracked link, which might contain long query strings or other values that were previously truncated at 255 characters.

After this change, the page_url and page_event_var1 length will increase from 255 bytes to 64 kilobytes. Update any 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 large enough 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 single large monolithic file. The multiple file package is particularly useful for report suites with very high traffic volumes and 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 maintain compatibility with your current ETL processes, existing data feeds will not be altered unless requested to Customer Care 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 6 What's New

(7)

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

(8)

Best Practices

Following are some best practices for optimizing data feed delivery time. You should:

• Ensure that you communicate any anticipated traffic spikes ahead of time. Any upstream latency has a direct impact on 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 inadvertently run out of disk space.

• When changing FTP credentials, please ensure that the credentials are current in Adobe's data feed system. Notify Adobe 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.

8 Best Practices

(9)

Configuring Data Feeds

Data 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 Adobe does not delete any 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 an Amazon S3 bucket. Amazon will automatically encrypt the data at rest (on the Amazon servers). When you download the 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, an Access 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 of the 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 objects in other buckets. If userA creates a bucket, say bucketA, he or she can create a bucket policy that explicitly allows userB to create objects in bucketA even though the user doesn't own the bucket. This can be advantageous because it doesn't require that userA and userB to exchange credentials. Instead, userB provides userA with their account number, 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 an object to userA's bucket, userB still "owns" that object, and by default, userA is not granted any permissions to that object even though userA owns the bucket—objects do not inherit permissions from the parent bucket. UserB must explicitly grant userA permissions because userB is still the object's owner. For this cross-account upload, AWS provides a BucketOwnerFullControl ACL by specifying that the use of this ACL by the bucket owner (userA) and is granted full permissions to the object (read, write, delete, etc), even though the object is "owned" by userB.

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 each containing 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. You receive 24 separate deliveries for each day, with each file delivered after the data for that hour is processed.

(10)

Hourly Data Feeds

It is important to understand that the term “hourly” describes the time frame of the data that is sent with each individual data export, and not the time frame in which the delivery occurs. Hourly data feeds are processed and delivered in a best-effort fashion. However, there are several factors that can impact the delivery time of an hourly data feed including:

• 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 that hour’s worth of data.

Receiving an hourly data feed is different then receiving daily feed with multiple file delivery. When receiving hourly data feeds the data for each day is split into 24 files based on the data collected during that hour, and each file is delivered as soon as it is available. A daily feed that is delivered in multiple files is delivered once per day after the previous 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 ago might 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 delivery with a midnight timestamp that contains all of the data for that day. If you are requesting this type of backfill, Make sure 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, we recommend selecting multiple file delivery, due to the significant performance increases gained when compressing and 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

Description Performed By

Task

Review the clickstream data columns and determine the data you would like to receive. Adobe also provides a

recommended column set that can be selected. Customer

Select data columns

Select an FTP location where Adobe should deliver data feed files. Adobe can provide FTP hosting for the files if preferred. Customer

(FTP only) Select FTP location Purchase an S3 bucket from Amazon

Contact Customer Care through your Supported User and provide:

Customer Contact Adobe Customer Care to

configure the data feed.

• The report suite that contains the data you want in the feed. • The columns you want in the data set.

10 Configuring Data Feeds

(11)

Task

• 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

Task

Server calls are collected and processed in Adobe Data Collection servers.

Adobe Data collection

After data is processed for the delivery period (previous hour or previous day), the data is exported to the data feed. The feed is stored in delimited format and compressed. Adobe

Feed generation

The compressed data is transferred to either Amazon S3 or a customer-hosted or Adobe-hosted FTP site. When complete, Adobe

Delivery to customer

a manifest file (or .fin file for older feeds) is transferred indicating that the delivery is complete.

The customer monitors S3 or the FTP for the manifest file. This file contains details on all files that were delivered. Customer

Data download

The manifest file is read and each listed file is downloaded. Customer

Manifest file processing

Downloaded files are uncompressed and processed. Customer

Data is uncompressed and processed

(12)

Data Feed Contents

This 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 complete data 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 of records in all data files. This header is followed by multiple sections containing information for each file included in the data feed delivery. Some feeds are configured to receive a rsid_YYYY-MM-DD.fin file instead of a .txt manifest. The .fin indicates that 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 the browser 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 •country.tsv 12 Data Feed Contents

(13)

•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 delivered separately 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 configuration that 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 the file, regardless of when the file was produced or uploaded.

Description Delivery 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, as well as the compressed lookup files described above.

The hit data file size varies greatly depending on the number of variables actively used and amount 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 provide a 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:

(14)

Description Delivery 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 2 GB 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 hour of each day. After data is collected for an hour, you will receive a delivery that contains the following:

Hourly, 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:

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 2 GB of uncompressed data. The compressed lookup files described above are delivered only with the data for the first hour of each day.

14 Data Feed Contents

(15)

Clickstream Data Column Reference

Table data describing the columns in the data feed.

•Columns, Descriptions, and Data Types •Events Lookup for Solution Variables

Columns, Descriptions, and Data Types

Example lookup Data type Column description Column name en-us, ja;q=0.62, de String (255 characters)

The accept language header from the browser.

accept_language

See Browser Lookup and Browser Type Lookup Key: FK 32-bit unsigned integer

The browser ID (has lookup table) actually used for the hit. See pre_browser.

browser

806 Key: FK 32-bit unsigned integer

Height in pixels of browser window.

browser_height

1280 32-bit unsigned integer

Width in pixels of browser window. browser_width

32 String (255 characters)

Color depth as generated from JavaScript.

c_color

[Custom] String (255 characters)

The campaign value passed in on the hit. May not end up being the campaign

value that gets passed to the interface (see post_campaign).

String (100); Media Optimizer solution variable

mobile carrier (requries lookup file) carrier

Custom traffic variable for site sections (channels).

channel

http://www.adobe.com String (255 characters)

Visitor click map information. This information is what is contained in click_action

the address of the link the user clicked on (URL / JS function, etc.)

Visitor click map information. The type of link clicked on.

click_action_type

homepage String (255 characters)

Visitor click map information. This is the pagename (or URL if no click_context

pagename is declared) for the page on which the link click occurred

Visitor click map information. The type of click_context (indicates click_context_type

whether the pagename or URL was used)

Visitor click map information. This is the numeric ID for the location click_sourceid

on the page where the link is located

(16)

A String (255 characters)

Visitor click map information. The type of link or form element that was clicked on.

click_tag

G.7-pD-S String (255 characters)

The version of code in the JS file creating the image request. code_ver

See Color Depth Lookup Key: FK

32-bit unsigned integer Color depth ID (has lookup table)

that we ended up using for the hit. See pre_color.

color

Connection type ID (has lookup table).

connection_type

Y string (1 character)

Specifies whether JavaScript session cookie is accepted.

cookies

See Country Lookup Key: FK 32-bit unsigned integer

Country ID (has lookup table). country

modem String (255 characters)

Connection type of the browsers computer.

ct_connect_type

How the currency rate is stored. curr_factor

1 Decimal (24 significant

digits,12 digits after the decimal point ) Current exchange rate when the

transaction occurred. curr_rate

USD String (3 characters)

Type of currency for the transaction.

currency

(timestamp-enabled report suites only) The timestamp sent with the cust_hit_time_gmt

hit. This "timestamp" is in Unix time (number of seconds since Jan 1, 1970.)

UserID123ABC String (255 characters)

A visitor ID passed in with the hit to be used as the visitor ID for the cust_visid

hit (instead of using visid_high and visid_low)

A flag to determine if current hit is a new daily visitor.

daily_visitor

YYYY-MM-DD HH:MM:SS (this is not in Unix time.) datetime

The time in readable format in Time Zone specified by Report Suite ID. Set by Adobe servers. date_time

Adobe servers combine

post_cust_hit_time_gmt and the report suite's time zone to create date_time. hit_time is in the timezone of the report suite

example.com String (255 characters)

Domain of users ISP. domain

Lists each event that was counted as a duplicate.

duplicate_events

A flag indicating that the purchase event for this hit should be ignored because it is a duplicate.

duplicate_purchase

16 Clickstream Data Column Reference

(17)

(rsid) Report suite that the hit was

duplicated from duplicated_from

String (255 characters), AMO solution variable

ef_id for Media Optimizer ef_id

Custom variable 1 - 250. evar1-250

For event ID to name mapping, see the event.tsv file that is delivered with the data feed. String (64k characters)

Comma separated list of numeric IDs representing events passed in from the customer.

event_list

See Exclude Lookup Key: FK Hits that have a value other than 0 for this column are not 8-bit unsigned integer

Hit excluded by client rule. exclude_hit

used by Analytics reports and should be ignored when calculated metrics. Note that visit_num is not incremented for excluded hits http://www.adobe.com String (255 characters)

The original entry page URL. first_hit_page_url

The original entry page pagename. first_hit_pagename

http://www.yahoo.com String (255 characters)

Original referrer - referrer of first hit ever for the visitor.

first_hit_referrer

Timestamp of the first hit in GMT. first_hit_time_gmt

los angeles String (255 characters)

City from Digital Envoy. geo_city

usa String (255 characters)

Country from Digital Envoy. geo_country

[Custom] 32-bit unsigned integer

DMA from Digital Envoy. geo_dma

ca String (255 characters)

Region / State from Digital Envoy. geo_region

Zip code based on IP-address lookup

geo_zip

[CUSTOM],[CUSTOM],[CUSTOM] String (255 characters)

Delimited list of values as passed in on the image request. The delimiter hier1-5

is chosen by the client during implementation.

See Hit Source Lookup 8-bit unsigned integer

A flag for the back-end processing to know what type of hit the data is.

hit_source

Set by Adobe servers, this is the timestamp used for

hit_time_gmt

non-timestamped report suites. This "timestamp" is in Unix time (number of seconds since Jan 1, 1970.)

64-bit unsigned integer Used to uniquely identify a hit. The

combination of hitid_low and hitid_high

(18)

hitid_high creates a unique ID for the row.

64-bit unsigned integer Used to uniquely identify a hit. The

combination of hitid_low and hitid_low

1. 50367E+16 Key: PRI hitid_high creates a unique ID for

the row.

N string (1 character)

Homepage flag, whether or not this page was the user's homepage homepage

A flag to determine if current hit is a new hourly visitor.

hourly_visitor

String (255 characters) IP address of user's computer, from

users ISP. ip

1. 112.89.14 String (255 characters)

A second IP address to be used by VISTA to determine validity of hits. ip2

String (255 characters) Version of JavaScript supported by

browser. j_jscript

1. 3 Y string (1 character)

Flag indicating whether or not java is enabled.

java_enabled

See Javascript Version Lookup Key: FK

8-bit unsigned integer Version of Javascript.

javascript

See Languages Lookup Key: FK 32-bit unsigned integer

Language ID (has lookup table). language

Timestamp of the previous hit in GMT

last_hit_time_gmt

The purchase number of the previous purchase.

last_purchase_num

The time of the previous purchase. last_purchase_time_gmt

String (255 characters) Marketing Cloud Visitor ID The

Marketing Cloud Visitor ID is a mcvisid

1. 64983E+37 128-bit number that consists of 2

signed, positive, 64-bit numbers in base 10, both padded to 19 zeros, and then concatenated.

Mobile solution variables. See Mobile Solution Variables mobile* post_mobile*

The ID of the mobile device which passed the hit into marketing reports.

mobile_id

A flag to determine if current hit is a new monthly visitor.

monthly_visitor

String (64k characters) Mvvars are multi-value fields

provided to allow customers to mvvar1-3

implement custom multi-value projects. Also known as "list variables" in Adobe Marketing Reports & Analytics.

(19)

String (255 characters) Not currently populated; reserved

for future release. namespace

A flag that determines if the current hit is a new visit.

new_visit

See Operating Systems Lookup Key: FK

32-bit unsigned integer Operating system ID (has lookup

table). os

String (64k characters) List of plugins available to the

browser. p_plugins

0 See Page Event Lookup 8-bit unsigned integer

Page event ID, the type of hit that is sent in the request. Look-ups page_event

provided for type of event (normal,download, exit, custom)

http://www.adobe.com String (64k characters)

Related to the page_event column. It is the URL of the download link, exit link or custom link clicked. page_event_var1

homepage_buy String (255 characters)

If you have individually named your link, this column contains the link name.

page_event_var2

String (64k characters) Used for both Survey and Media

module, and serves as the page_event_var3

pre-version for both modules. (This column contains the value passed in on the hit for the page event.)

errorPage String (255 characters)

page type variable (only used for error page).

page_type

http://www.adobe.com/search/search_results.htm String (64k characters)

The URL of the pageview. The address of the page in the address bar of the browser.

page_url

search_results String (100 characters)

The name of the page (if set). pagename

A (1/0) flag that determines if the hit was used for paid search tracking.

paid_search

String (255 characters) Not usable by customers. This is a

comma-separated list of partner_plugins

plungin_ids (usually about 5 characters each) for plugins that partners have registered with us.

Y String (1 character)

A flag indicating if 3rd party cookies and/or persistent cookies are enabled.

persistent_cookie

See Plugins Lookup Key: FK String (255 characters)

List of plugin IDs available to the browser (has lookup table) This is the post value.

plugins

0 See Page Event Lookup 8-bit unsigned integer

Page event ID, the type of hit that is sent in the request.

(20)

errorPage String (100 characters)

page type variable (only used for error page).

post_ page_type

Height in pixels of the browser window.

post_browser_height

Width in pixels of the browser window.

post_browser_width

Persisting value of campaign. post_campaign

Custom traffic variable for site sections (channels).

post_channel

Specifies whether JavaScript session cookie is accepted.

post_cookies

USD String (3 characters)

Type of currency for the transaction.

post_currency

Timestamp actually used for the hit, this is cust_hit_time_gmt for post_cust_hit_time_gmt

timestamp-enabled report suites, or hit_time_gmt otherwise.

8-bit unsigned integer Post version of the cust_visid field.

What we ended up using for the hit. post_cust_visid

String (255 characters); AMO solution variable

post verion of ef_id post_ef_id

Persisting value of evar1-250. post_evar1-250

For event ID to name mapping, see the event_lookup.tsv that String (64k characters)

Comma separated list of numeric IDs representing events passed in from the customer.

post_event_list

is delivered with the data feed. Key: FK

[CUSTOM],[CUSTOM],[CUSTOM] String (255 characters)

Delimited list of values as passed in on the image request. The delimiter post_hier1-5

is chosen by the client during implementation.

Flag indicating whether or not java is enabled.

post_java_enabled

my keyword String (100 characters)

The keywords that were actually used for the hit.

post_keywords String post_mobileaction String post_mobileappid String post_mobilecampaigncontent String post_mobilecampaignmedium String post_mobilecampaignname 20 Clickstream Data Column Reference

(21)

String post_mobilecampaignsource String post_mobilecampaignterm String post_mobiledayofweek String post_mobiledayssincefirstuse String post_mobiledayssincelastuse String post_mobiledevice String post_mobilehourofday String post_mobileinstalldate String post_mobilelaunchnumber String post_mobileltv

String (255 characters); Mobile solution variable

post version of mobilemessageid post_mobilemessageid

String (255 characters); Mobile solution variable post version of mobilemessageonline post_mobilemessageonline String post_mobileosversion String post_mobileresolution String (64k characters) Post-processed mvvars. "What we

ended up using for the hit." Data in the post_mvvar columns will be separated by a 6-character delimiter:

--**--post_mvvar1-3

The delimiter in column mvvar will be replaced in post_mvvar by

--**--post_page_event

Related to the page_event column. It is the URL of the download link, exit link or custom link clicked. post_page_event_var1

(22)

homepage_buy String (100 characters)

If you have individually named your link, this column contains the link name.

post_page_event_var2

String (64k characters) Used for both Survey and Media

module, and serves as the post_page_event_var3

pre-version for both modules. (This column contains the value passed in on the hit for the page event.)

String post_page_type

http://www.adobe.com/search/search_results.htm String (255 characters)

The URL of the pageview. The address of the page in the address bar of the browser.

post_page_url

The name of the page (if set). If no page is specified the URL is placed in this value.

post_pagename

The name of the page (if set). If no page is specified this value is left empty.

post_pagename_no_url

String (100 characters) List of partner plugins available to

the browser (has lookup table). post_partner_plugins

Flag indicating if 3rd party cookies and/or persistent cookies are enabled.

post_persistent_cookie

Format is comma separated list of: category; product; quantity; String (64k characters)

The product list as passed in through the JavaScript. post_product_list cost; custEventsDecValues; merchandisingValues Computers;HP Pavillion;1;1000;200|201,Office Supplies [Custom] String (100 characters)

Custom traffic variables 1 - 75. post_prop1-75

1584A9646G String (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

post version of s_kwcid post_s_kwcid

Search Engine Lookup 32-bit unsigned integer

The numeric ID of the search engine that was actually used and stored.

post_search_engine

AZ String (100 characters)

Geographical region (i.e. Arizona, Utah, Saxony [German Region]) post_state

passed in on JavaScrip. Normally only set on a purchase page.

(23)

3826-0-0--**--3826-1-1--**--3826-2-0 String (64k characters)

Post column for the marketing reports and Survey integration. post_survey

Processed based on page_event_var3.

12/11/2004 4:23:31 1 +420 String (100 characters)

Raw time info from JavaScript. Used to determine the visitor's timezone.

post_t_time_info

String (64k characters) Post column for Analytics and

Target integration. post_tnt

String (64k characters) Post column for Analytics and

Target integration. post_tnt_action

A1B2C3D4 String (100 characters)

A unique identifier where various data points can be uploaded later via Data Sources.

post_transactionid

64-bit unsigned integer The visid_high value that we ended

up using for the hit. post_visid_high

64-bit unsigned integer The visid_low value that we ended

up using for the hit. post_visid_low

0=Custom VisitorID (A custom visitor ID was set in the code using s.visitorID) 8-bit unsigned integer

Post version of the visid_type column. What we ended up using for the hit.

post_visid_type

1=IP&UA fallback (cookies were rejected by browser) 2=Wireless (HTTP Mobile Subscriber Header identified as mobile carrier)

3=Adobe (server generated, stored in s_vi on client) Default method. 4=Fallback cookie (new fallback ID, JavaScript generated, stored in s_fid on client, added in H25.3) 5=Visitor ID Service

See Identifying Unique Visitors. String (100 characters)

Post version of the zip field. What we use for the hit.

post_zip

The page id of the previous page. This is an internal identifier and not useful to the customer.

prev_page

Format is comma separated list of: category; product; quantity; String (64k characters)

The product list as passed in through the JavaScript. product_list

(24)

cost; custEventsDecValues; merchandisingValues Computers;HP Pavillion;1;1000;200|201,Office Supplies Replaced by post_product_list as of April 2011. Contains data for product_merchandising

Merchandising evars as they relate to products.

Custom traffic variables 1 - 75. prop1-75

1584A9646G String (255 characters)

Unique identifier for a purchase. Identifies a duplicate purchase (see duplicate_purchase).

purchaseid

A flag to determine if current hit is a new quarterly visitor.

quarterly_visitor

String (255 characters) The referring domain of the hit

(based on referrer). ref_domain

8-bit unsigned integer Integer representing the type of

referral for the hit. Lookup values ref_type

can be obtained from

referrer_type.csv lookup table.

String (255 characters) Page prior to the current page.

referrer

See Resolution Lookup Key: FK

32-bit unsigned integer Resolution id (has lookup table).

resolution

s_kwcid for Media Optimizer s_kwcid

1024x768 String (255 characters)

Screen resolution as passed in from JavaScript.

s_resolution

N string (1 character)

A (Y/N) field if the hit was used (sampled) or not for ad hoc analysis.

sampled_hit

See Search Engine Lookup Key: FK

32-bit unsigned integer Search engine ID, has lookup table

search_engine

The page number of search results that the keywords were on from the search engine.

search_page_num

Used to track secondary hits. Secondary hits are charged at a rate of 50% of the normal costs. secondary_hit

ss String (2 characters)

Deprecated. pe or ss - type of hit coming through. The page_event service

column gives the same information but in more detail.

String (255 characters) social account and app ids

socialaccountandappids

(25)

Social solution variables. See Social Solution Variables

social* post_social*

32-bit unsigned integer Adobe proprietary column

information sourceid

AZ String (255 characters)

Geographical region (i.e. Arizona, Utah, Saxony [German Region]) state

passed in on JavaScript. Normally only set on a purchase page.

www263.omniture.com String (255 characters)

Adobe internal server that processed the hit.

stats_server

26/11/2013 4:23:31 1 420 String (255 characters)

Raw time information from JavaScript. Used to determine the visitor's timezone.

t_time_info

String (64k characters) Pre column for Analytics and

Target integration. tnt

String (64k characters) Pre column for Analytics and

Target integration. tnt_action

52060:81:1 or

52060:81:1,13234:23:0,9132:12:1 String (64k characters)

Same information as the tnt field but with any modifications made by Vista Rules, etc.

tnt_post_vista

A1B2C3D4 String (255 characters)

A unique identifier where various data points can be uploaded later via Data Sources.

transactionid

N String (1 character)

A (Y/N) field that determines if the query string of the hit was

truncated or not. i.e. truncated_hit

String (255 characters) Screen color depth. Stands for User

Agent Color. From HTTP header sent by older browsers.

ua_color

Agent Operating System. From ua_os

HTTP header sent by older browsers.

Agent Pixels. From HTTP header sent by older browsers.

ua_pixels

String (64k characters) User agent as found in the HTTP

header sent from the browser. user_agent

The hash on the report suite ID. user_hash

Custom traffic variable for servers. user_server

The numeric ID for the report suite ID (normally seen in the name of DW files).

userid

adobe String (255 characters)

The report suite ID. username

(26)

String (255 characters) Detail for last-touch value in

Marketing Channels reports. va_closer_detail

8-bit unsigned integer ID for last-touch value in

Marketing Channels reports. va_closer_id

String (255 characters) Detail for first-touch value in the

Marketing Channels Report. va_finder_detail

8-bit unsigned integer ID for first-touch value in

Marketing Channels reports va_finder_id

8-bit unsigned integer Instance event for first-touch value

in Marketing Channels reports va_instance_event

8-bit unsigned integer New engagement for first-touch

value in Marketing Channels reports

va_new_engagement

Video solution variables. See Video Solution Variables

video* post_video*

64-bit unsigned integer Part 1 of the visitorID. The

combination of two visitor IDs visid_high

1. 70E+18 (visid_high and visid_low) creates

a unique visitor ID.

64-bit unsigned integer Part 2 of the visitorID. The

combination of two visitor IDs visid_low

1. 21E+17 (visid_high and visid_low) creates

a unique visitor ID.

string (1 character) Indicates whether this is a

newly-generated visitorID. Only visid_new

available if visid_type=3 (Example: a new s_vi cookie was generated).

32-bit unsigned integer If the visitorID was generated by us

(visid_type=3), this is the visid_timestamp

timestamp for when the ID was originally created.

0=Custom VisitorID (A custom visitor ID was set in the code using s.visitorID) 8-bit unsigned integer

Integer that specifies how the visitorID was calculated (based on a lookup).

visid_type

1=IP&UA fallback (cookies were rejected by browser) 2=Wireless (HTTP Mobile Subscriber Header identified as mobile carrier)

3=Adobe (server generated, stored in s_vi on client) Default method.

(27)

4=Fallback cookie (new fallback ID, JavaScript generated, stored in s_fid on client, added in H25.3) 5=Visitor ID Service

See Identifying Unique Visitors. my keyword

String (255 characters) Keywords used to find the site.

visit_keywords

1

Note that visit_num is not

incremented for excluded hits 32-bit unsigned integer

The number of the current visit (Incremented each time a visitor returns to the site).

visit_num

(hits where exclude_hit

column > 0). 17

32-bit unsigned integer The page sequence number in the

current visit. visit_page_num

http://www.google.com String (255 characters)

The referrer to the visit. visit_referrer

The search engine used to find the site.

visit_search_engine

The start page for the visit. visit_start_page_url

The pagename the visit started on. visit_start_pagename

The GMT timestamp of the first pageview in this visit.

visit_start_time_gmt

A flag to determine if current hit is a new weekly visitor.

weekly_visitor

A flag to determine if current hit is a new yearly visitor.

yearly_visitor

Zip code (i.e. 84604,85381) passed in by JavaScript, or populated by GeoSegmentation data.

zip

Events Lookup for Solution Variables

Solution variable events appear as numeric codes in the event_list and post_event_list, and are custom to each report suite. You must use the event_lookup.tsv file that is delivered with each data feed to decode the event numbers in the

post_event_list.

This applies to columns in the following sections: •App Store Solution Variables

•Video Solution Variables •Mobile Solution Variables •Social Solution Variables

App Store Solution Variables

Events Lookup Type

Description Variable/Event

(28)

Solution variable events appear as numeric codes in the event_list

Contained in event_list

The number of mobile application downloads.

AppStore Downloads

and post_event_list, and are

custom to each report suite. You must use the

event_lookup.tsv file that is delivered with each data feed to decode the event numbers in the

post_event_list.

The number of in app purchases. AppStore Purchases

and post_event_list, and are custom to each report suite. You must use the

post_event_list.

Used to calculate the average app ranking. This calculated metric is defined using the following formula: AppStore Rank

and post_event_list, and are custom to each report suite. You

[AppStore Rank] / [AppStore

Rank (divisor)] must use the

post_event_list.

Used to calculate the average app ranking. This calculated metric is defined using the following formula: AppStore Rank

Divisor

[AppStore Rank] / [AppStore

Rank (divisor)] must use the

post_event_list.

The amount of in app revenue. AppStore In-App

Revenue

event_lookup.tsv file that is 28 Clickstream Data Column Reference

(29)

delivered with each data feed to decode the event numbers in the

post_event_list.

The amount of revenue associated with the purchase of an app. AppStore One-off

Revenue

post_event_list.

The amount of in app revenue minus amount retained by app store. AppStore In-App

Royalties

post_event_list.

The amount of one off revenue minus amount retained by app store. AppStore One-off

Royalties

post_event_list.

Used to calculate the average app ranking. This calculated metric is defined using the following formula: AppStore Rating

[AppStore Rating] /

[AppStore Rating (divisor)] must use the

(30)

Used to calculate the average app ranking. This calculated metric is defined using the following formula: AppStore Rating

Divisor

custom to each report suite. You

[AppStore Rating] /

[AppStore Rating (divisor)] must use the

post_event_list.

Video Solution Variables

Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_". Events Lookup Type

string (255 characters) Video name

video

post_event_list.

string (255 characters) Ad name

videoad

post_event_list.

string (255 characters) Segment

videosegment

post_event_list.

(31)

string (255 characters) Content Type. Content type is set to

"Video" automatically for all video views.

videocontenttype

post_event_list.

string (255 characters) Ad Pod

videoadpod

post_event_list.

string (255 characters) Ad in Pod position

videoadinpod

post_event_list.

string (255 characters) Player Name

videoplayername

post_event_list.

string (255 characters) Channel

videochannel

(32)

delivered with each data feed to decode the event numbers in the

post_event_list.

string (255 characters) Ad Player Name

videoadplayername

post_event_list.

Video Time Viewed. Total time spent viewing the video.

videotime

post_event_list.

Video Views. Indicates that a visitor has viewed some portion of a video. However, it does not provide any videostart

and post_event_list, and are information about how much, or

what part, of a video the visitor viewed.

post_event_list.

Video Completes. Indicates that a user has viewed a complete video or ad.

videocomplete

post_event_list.

Video Segment Views. Sent on all close events, which occur on video complete or when the users stops videosegmentviews

(33)

custom to each report suite. You viewing at some point before the

complete occurs.

must use the

post_event_list.

Ad Views. Indicates that a visitor has viewed some portion of an ad. However, it does not provide any videoadstart

information about how much, or what part, of a video the visitor viewed.

post_event_list.

Ad Completes. Indicates that a user has viewed a complete video or ad. videoadcomplete

post_event_list.

Ad Time Viewed. Total time spent viewing the ad.

videoadtime

post_event_list. videopath

Mobile Solution Variables

Note that pre* and post* versions of these variables are available. The post versions are prepended with "post_". Events Lookup Type

(34)

string (255 characters) First Launch Date. Date of first

launch after installation.

MM/DD/YYYY

mobileinstalldate

custom to each report suite. You must use the event_lookup.tsv

file that is delivered with each data feed to decode the event numbers in the post_event_list.

string (255 characters) App Id. Stores the Application name

and version in the following format: mobileappid

[AppName] [BundleVersion]

custom to each report suite. You

For example, myapp 1.1 _{must use the}_{event_lookup.tsv}

string (255 characters) Populated from the a.action context

data automatically passed in when trackAction is called in the SDK. mobileaction

and post_event_list, and are Allows for automatic action pathing

in the app. custom to each report suite. You

must use the event_lookup.tsv

string (255 characters) Launch Number. Number of times

the application was launched or brought out of the background. mobilelaunchnumber

and post_event_list, and are custom to each report suite. You must use the event_lookup.tsv

string (255 characters) Days Since First Use. Number of

days since first run. mobiledayssincefirstuse

(35)

string (255 characters) Days Since Last Use. Number of

days since last use. mobiledayssincelastuse

string (255 characters) Hour of Day. Measures the hour the

app was launched. 24 hour numerical format. Used for time mobilehourofday

and post_event_list, and are parting to determine peak usage

times.

string (255 characters) Day of Week. Number of the week

day the app was launched. mobiledayofweek

string (255 characters) Device Name. Stores the device

name. mobiledevice

and post_event_list, and are On iOS, this is a comma-separated

2 digit string that Identifies the iOS custom to each report suite. You must use the event_lookup.tsv

device. The first number typically

file that is delivered with each data represents the device generation,

feed to decode the event numbers in the post_event_list.

and the second number typically versions different members of the device family.

string (255 characters) Operating System Version.

mobileosversion

(36)

string (255 characters) Resolution. Width x Height in

actual pixels. mobileresolution

string (255 characters) Mobile Campaign Source

mobilecampaignsource

string (255 characters) Mobile Campaign Medium

mobilecampaignmedium

string (255 characters) Mobile Campaign Term

mobilecampaignterm

string (255 characters) Mobile Campaign Content

mobilecampaigncontent

(37)

string (255 characters) Mobile Campaign Name

mobilecampaignname

string (255 characters) Lifetime Value (evar)

mobileltv

First Launches. Triggered on first run after installation (or

re-installation). mobileinstalls

Upgrades. Triggered on first run after upgrade (anytime the version number changes).

mobileupgrades

Launches. Triggered on any run that is not an install or an upgrade. This also triggers when the application is brought out of the background. mobilelaunches

(38)

Crashes. Triggered when the application does not exit gracefully. Event is sent on application start mobilecrashes

after crash (the application is considered to crash if quit is not called).

Previous Session Length.

Aggregated total Previous Session Length.

mobileprevsessionlength

Action Time Total mobileactiontotaltime

Action Time In App mobileactioninapptime

Lifetime Value (event) mobileltvtotal