Analytics Clickstream

Adobe® Marketing CloudClickStream 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 Last updated 8/18/2014 ClickStream Data Feeds Clickstream Data Feeds Help 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. For column reference for an existing feed, see Clickstream Data Column Reference. Before this date. If possible your ETL system should be designed to accommodate the addition of new lookup files without impacting processing. and an announcement will be included in the release notes when these expansions are rescheduled. Note that the column expansions that were previously scheduled for April 2014 have been postponed. 2014 Clickstream data feed customers that are currently receiving the os column will automatically receive an additional lookup file for OS types starting June 19. String expansion Expand the following columns to store a 255 character string: ip2 click_tag click_action page_event_var2 post_page_event_var2 pagename post_pagename post_pagename_no_url channel post_channel user_server t_time_info post_t_time_info domain first_hit_pagename visit_start_pagename transactionid post_transactionid prop1-75 post_prop1-75 ref_domain code_ver geo_zip plugins accept_language c_color ct_connect_type ip page_type post_ page_type . Contact customer care to have this column added. 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). 2014. New OS Types Lookup File coming June 19. Note that additional lookup files could be added to the data feed when additional columns added. ensure that your processing system is prepared to receive this additional lookup file. We recommend all customers test processing of this sample feed to prepare for the upcoming expansion.What's New 4 What's New Cumulative release notes for Clickstream data feeds. Before these field sizes are increased. as these are increasing in size as well. you need to expand the data fields in your ETL system to accommodate these new sizes. Data Feed Column Expansion Adobe is currently evaluating an increase to the size of many data feed fields. You also need to expand the fields used to store lookup file keys. Note: You can download a sample data feed with expanded columns and lookup files to test your ETL process. Lookup file key expansion The column used to store each lookup file key value should be expanded to store a 32-bit unsigned integer. and Video metrics. 2014) resolution visit_search_engine geo_dma post_search_engine search_page_num October 17. 2013. February 14. contact Customer Care. the data can be delivered in a more timely manner with less peak load on both origination and destination servers. which currently includes Social.What's New 5 purchaseid post_purchaseid s_resolution ua_color ua_pixels visit_keywords post_keywords stats_server geo_city geo_region j_jscript state post_state zip post_zip namespace currency post_currency ua_os Integer expansion Expand the following columns to store a 32-bit unsigned integer: browser_height browser_width search_engine post_browser_height post_browser_width browser (Feb 20. Your ETL might require a modification to consider this file. The event lookup file delivered with each report suite should be considered specific to that report suite. Mobile. See Configuring Data Feeds. 2013 Social. social-specific events. This new lookup file provides a map for all events. 2013 Hourly Data Feeds Hourly data feeds provide customers raw Analytics data in hourly increments instead of the normal daily increments. an additional event lookup file will be added to all data feeds. Event lookup file now included in data feed download Starting October 17. Be aware that the map for Mobile. Social. instance events. By splitting the data into hourly increments. 2013 Format of post_product_list column when events are present but product is empty . and Video solution variables are now available You can now receive solution variables in data feeds. 2014) color country language os (Feb 20. including shopping cart events. May 23. Mobile. To update your data feed definition to add solution variables. and so on. custom events. and Video solution event numbers are different for each report suite. mobile-specific events. the post_product_list contains four semicolons: . If events are contained on the event list for a given hit but there is no product in the product list.. the page_url and page_event_var1 length will increase from 255 bytes to 64 kilobytes. semicolon: . or in rare cases as semicolon. The multiple file package is particularly useful for report suites with very high traffic volumes and has several advantages: • Improved delivery consistency. In order to maintain compatibility with your current ETL processes. 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. Alternatively. which might contain long query strings or other values that were previously truncated at 255 characters.0. semicolon. January 22.0.. zero.. especially during days with traffic spikes. please make certain your ETL handles truncation appropriately. If you are storing the data feed in a database. zero. Update any applications or scripts that you are using to process the data feed to use a 64Kb variable to store these strings. After this change. semicolon.What's New 6 In post_product_list. • The following additional optional columns are now available for inclusion in your data feed. If you are performing a check for an empty product list you should update your ETL to handle both formats. existing data feeds will not be altered unless requested to Customer Care through your Supported User. • Better parallel data processing. This change enables you to receive the entire URL of each page and tracked link. June 21. This change does not impact the post_page_url or post_page_event_var1 columns. • 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 . Using the multiple file package can significantly reduce the time required to compress and extract large data sets. 2013 Expansion of page_url and page_event_var1 Columns These columns were expanded to store URLs that are longer that 255 characters.. which remain at 255 characters. if your systems require the truncated versions of these columns. make sure that the page_url and page_event_var1 columns are large enough to contain a string up to 64Kb. What'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 7 . 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. Data files are always split on a complete record and can be easily concatenated after extraction. You must implement your own process to manage disk space on the server. Hourly data feeds are processed and delivered in a best effort fashion. 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. Multiple File Delivery You can select single file or multiple file delivery when the data feed is created. When receiving hourly data feeds the data for each day is split into 24 files based on the data collected during that hour. FTP File Delivery Data feed data can be delivered to an Adobe or customer hosted FTP location. there are several factors that can impact the delivery time of an hourly data feed including: • Report suite latency (i. and each file is delivered as soon as it is available. you must provide Adobe with the appropriate username.e. Receiving an hourly data feed is different then receiving daily feed with multiple file delivery. as Adobe does not delete any data from the server. This section provides an overview of data feed options and the one-time configuration process. or in multiple zipped files each containing approximately 2 GB of uncompressed data. You receive 24 separate deliveries for each day. . Multiple file delivery makes it easier to process data in parallel. and is spilt into 2GB increments based on the amount of data collected. due to the significant performance increases gained when compressing and uncompressing files that are larger than 2 GB. Delivery Formats and Contents Daily: Data for each day is delivered after it is processed in a single zipped file. password. we recommend selecting multiple file delivery. However.Configuring Data Feeds 8 Configuring Data Feeds Data feeds are enabled by Customer Care and delivered using FTP. If you select to have data uploaded to your FTP server. 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. A daily feed that is delivered in multiple files is delivered once per day after the previous day's data is processed. and upload path. with each file delivered after the data for that hour is processed. When setting up a daily feed. Adobe also provides a recommended column set that can be selected. Feed generation Adobe After data is processed for the delivery period (previous hour or previous day). credentials. • FTP hostname. Adobe can provide FTP hosting for the files if preferred. Data download Customer The customer monitors the FTP for the manifest file. Select FTP location Customer Select an FTP location where Adobe should deliver data feed files. Delivery Process Task Performed By Description Data collection Adobe Server calls are collected and processed in Adobe Data Collection servers. • The columns you want in the data set. the data is exported to the data feed. This file contains details on all files that were delivered. a manifest file (or .fin file for older feeds) is transferred indicating that the delivery is complete. Manifest file processing Customer The manifest file is read and each listed file is downloaded. The feed is stored in delimited format and compressed. select single file or multiple file delivery (multiple recommended). • Daily or hourly data delivery. Data is uncompressed and processed Customer Downloaded files are uncompressed and processed. Delivery to customer Adobe The compressed data is transferred to customer-hosted or Adobe-hosted FTP site. Customer Contact Customer Care through your Supported User and provide: • The report suite that contains the data you want in the feed. When complete. . Contact Adobe Customer Care to configure the data feed.Configuring Data Feeds 9 One Time Configuration Process Task Performed By Description Select data columns Customer Review the clickstream data columns and determine the data you would like to receive. and path. If Daily. continue to Data Feed Contents to understand what files you will receive.Configuring Data Feeds 10 After you have configured your data feed. . tsv. but it contains no metadata about the upload. so that its existence indicates that the complete data set for that request period has already been delivered.fin indicates that the upload is complete. Some feeds are configured to receive a rsid_YYYY-MM-DD. The lookup files are delivered together in a compressed zip named according to the following: <report_suite_id>_<YYYY-mm-dd>-<HHMMSS>-lookup_data. The . The manifest file is always delivered last as a separate .tsv • connection_type.tsv • browser_type. and total number of records in all data files. Lookup Files Lookup files do not contain hit data. indicating the total number of lookup files.txt file.Data Feed Contents 11 Data Feed Contents This section describes the files found in a data feed delivery.tar. these are supplemental files that provide the column headers for the hit data. such as browser.gz MD5-Digest: af6de42d8b945d4ec1cf28360085308 File-Size: 63750 Data-File: 01-bugzilla_2012-09-09. This header is followed by multiple sections containing information for each file included in the data feed delivery.fin file instead of a .gz MD5-Digest: 9c70bf783cb3d0095a4836904b72c991 File-Size: 122534 Record-Count: 611 Every manifest file contains a header.tsv are specific to the data feed and report suite. data files. 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.<compression_suffix> • column_headers.tsv.tsv .0 Lookup-Files: 1 Data-Files: 1 Total-Records: 611 Lookup-File: bugzilla_2012-09-09-lookup_data. a value of "497" in the browser column indicates that the hit came from "Microsoft Internet Explorer 8".tsv • color_depth.tsv and event_list.txt A typical manifest file contains data similar to the following: Datafeed-Manifest-Version: 1.tsv (customized for this data feed) • browser. Note that the column_headers. Manifest files are named according to the following: <report_suite_id>_YYYY_MM_DD. For example. Other files.txt manifest. are generic. and lookup files to translate the IDs found in the data feed to actual values. tsv • operating_systems. However.tsv • javascript_version. as well as the compressed lookup files described above. on average.gz or zip. Each data file is delivered with the following name: <index>-<report_suite>_<YYYY-mm-dd>. Multiplying this by the number of server calls can provide a rough estimate on how large a data feed file will be.tsv • referrer_type. The time (HHMMSS) indicated in a file name always indicates the beginning of the date range for the data in the file.tsv • resolution.Data Feed Contents 12 • country. Each row in this file contains a single server call. multiple file After data is collected for a day. The amount of data in this file is determined by the delivery format (hourly or daily. Daily. lookup files are delivered only with the data for the first hour of each day.tsv • plugins. The data file is delivered with the following name: <report_suite>_<YYYY-mm-dd>. Find the configuration that matches your data feed in the following table for a description of the delivered files. the data file contains a single hit_data. single file After data is collected for a day. Delivery Format Description Daily. you will receive a delivery that contains the following: • a single compressed data file.tsv • event_lookup. • A manifest file. The hit data file size varies greatly depending on the number of variables actively used and amount of traffic on the report suite. you will receive a delivery that contains the following: • One or more compressed data files.tsv • languages.tsv • search_engines.tsv file. This file contains only hit data. broken into 2 GB chunks. Hit Data Files Hit data is provided in a hit_data. a row of data is approximately 500B (compressed) or 2KB (uncompressed).tsv file with all data for that day. When extracted. regardless of when the file was produced or uploaded.<compression_suffix> . The column headers are delivered separately with the lookup files.<compression_suffix> Where <compression_suffix> is either tar. • A manifest file. Delivery Contents The actual files delivered by Adobe vary based on the type of data feed that you have configured. and single or multiple files).tsv (customized for this data feed) For hourly delivery. tsv file with all data for that hour. single file After data is collected for an hour. given n files. The compressed lookup files described above are delivered only with the data for the first hour of each day.tsv that contains approximately 2 GB of uncompressed data. The data file is delivered with the following name: <report_suite>_<YYYY-mm-dd>-<HHMMSS>. the data file contains a single hit_data. The compressed lookup files described above are delivered only with the data for the first hour of each day. and <compression_suffix> is either gz or zip When extracted. as well as the compressed lookup files described above.<compression_suffix> Where <index> is an incrementing file index from 1 to n. When extracted. . Hourly. • A manifest file.tsv that contains approximately 2 GB of uncompressed data. and <compression_suffix> is either tar. When extracted.Data Feed Contents 13 Delivery Format Description Where <index> is an incrementing file index from 1 to n. multiple file After data is collected for an hour.gz or zip. Hourly.tsv. given n files. each data file contains a single hit_data. • A manifest file. each data file contains a single hit_data. Each data file is delivered with the following name: <index>-<report_suite>_<YYYY-mm-dd>-<HHMMSS>.<compression_suffix> Where <compression_suffix> is either tar.gz or zip. broken into 2 GB chunks. you will receive a delivery that contains the following: • a single data file. you will receive a delivery that contains the following: • One or more compressed data files. ) http://www. de browser The browser ID (has lookup table) actually used for the hit. This String (255 characters) is the pagename (or URL if no pagename is declared) for the page on which the link click occurred homepage click_context_type Visitor click map information. String (255 characters) en-us. ja.Clickstream Data Column Reference 14 Clickstream Data Column Reference Table data describing the columns in the data feed. A code_ver The version of code in the JS file creating the image request. This String (255 characters) information is what is contained in the address of the link the user clicked on (URL / JS function. String (255 characters) 1123 channel Custom traffic variable for site sections (channels).adobe. The type of link clicked on.62. See pre_color. 32-bit unsigned integer 806 Key: FK browser_width Width in pixels of browser window. See pre_browser. The String (255 characters) type of link or form element that was clicked on. String (255 characters) G. The 8-bit unsigned integer type of click_context (indicates whether the pagename or URL was used) 0 click_sourceid Visitor click map information.com click_action_type Visitor click map information. 32-bit unsigned integer See Color Depth Lookup Key: FK 8-bit unsigned integer . 32-bit unsigned integer See Browser Lookup and Browser Type Lookup Key: FK browser_height Height in pixels of browser window.q=0. String (255 characters) [Custom] click_action Visitor click map information. May not end up being the value that gets passed to the interface (see post_campaign). 0 click_context Visitor click map information. String (255 characters) 32 campaign The campaign value passed in on the hit. Column name Column description Data type Example lookup accept_language The accept language header from the browser.7-pD-S color Color depth ID (has lookup table) that we ended up using for the hit. 32-bit unsigned integer 1280 c_color Color depth as generated from JavaScript. This 32-bit unsigned integer is the numeric ID for the location on the page where the link is located 396 click_tag Visitor click map information. etc. For event ID to name mapping. String (255 characters) example.) domain Domain of users ISP. String (255 characters) USD cust_hit_time_gmt (timestamp-enabled report suites 32-bit unsigned integer only) The timestamp sent with the hit. 8-bit unsigned integer 2 curr_rate Current exchange rate when the transaction occurred. This "timestamp" is in Unix time (number of seconds since Jan 1. 32-bit unsigned integer See Country Lookup Key: FK ct_connect_type Connection type of the browsers computer. string (1 character) Y country Country ID (has lookup table). Adobe servers combine post_cust_hit_time_gmt and the report suite's time zone to create date_time. String (255 characters) [Custom] event_list Comma separated list of numeric IDs representing events passed in from the customer.75. 0 date_time The time in readable format in Time datetime Zone specified by Report Suite ID.) 1102750716 cust_visid A visitor ID passed in with the hit to String (255 characters) be used as the visitor ID for the hit (instead of using visid_high and visid_low) UserID123ABC daily_visitor A flag to determine if current hit is a new daily visitor.tsv that is delivered with the data feed. Decimal (24 significant digits.Clickstream Data Column Reference 15 connection_type Connection type ID (has lookup table). 1970. text . 0 evar1-75 Custom commerce variable 1 . see the event_lookup. hit_time is in the timezone of the report suite YYYY-MM-DD HH:MM:SS (this is not in Unix time. Set by Adobe servers. 8-bit unsigned integer 0 cookies Specifies whether JavaScript session cookie is accepted.12 digits after the decimal point ) 1 currency Type of currency for the transaction.com duplicate_events Lists each event that was counted as a duplicate. String (255 characters) modem curr_factor How the currency rate is stored. String (255 characters) [Custom] 8-bit unsigned integer duplicate_purchase A flag indicating that the purchase 8-bit unsigned integer event for this hit should be ignored because it is a duplicate. This 1096614122 .[CUSTOM] hit_source A flag for the back-end processing 8-bit unsigned integer to know what type of hit the data is. Note that visit_num is not incremented for excluded hits first_hit_page_url The original entry page URL. String (255 characters) http://www. String (255 characters) [CUSTOM].Clickstream Data Column Reference exclude_hit Hit excluded by client rule. String (255 characters) [CUSTOM].referrer of first hit String (255 characters) ever for the visitor. String (255 characters) usa geo_dma DMA from Digital Envoy. String (255 characters) los angeles geo_country Country from Digital Envoy. this is the 32-bit unsigned integer timestamp used for non-timestamped report suites. 16 8-bit unsigned integer See Exclude Lookup Key: FK Hits that have a value other than 0 for this column are not used by Analytics reports and should be ignored when calculated metrics.adobe. String (255 characters) [CUSTOM].[CUSTOM] hier3 Delimited list of values as passed in on the image request.com first_hit_pagename The original entry page pagename.[CUSTOM] hier4 Delimited list of values as passed in on the image request. String (255 characters) homepage first_hit_referrer Original referrer .com first_hit_time_gmt Timestamp of the first hit in GMT. http://www. The delimiter is chosen by the client during implementation. String (255 characters) ca geo_zip Zip code based on IP-address lookup String (255 characters) 84103 hier1-5 Delimited list of values as passed in on the image request.[CUSTOM]. String (255 characters) [CUSTOM]. See Hit Source Lookup hit_time_gmt Set by Adobe servers. The delimiter is chosen by the client during implementation.[CUSTOM]. The delimiter is chosen by the client during implementation. The delimiter is chosen by the client during implementation.[CUSTOM] hier5 Delimited list of values as passed in on the image request. 32-bit unsigned integer 1102750716 geo_city City from Digital Envoy.yahoo.[CUSTOM].[CUSTOM]. 32-bit unsigned integer [Custom] geo_region Region / State from Digital Envoy. mobile* post_mobile* Mobile solution variables. The 64-bit unsigned integer combination of hitid_low and hitid_high creates a unique ID for the row. homepage Homepage flag. 8-bit unsigned integer 0 1. from String (255 characters) users ISP.Clickstream Data Column Reference 17 "timestamp" is in Unix time (number of seconds since Jan 1. 112. ip2 A second IP address to be used by String (255 characters) VISTA to determine validity of hits. and then concatenated. See Mobile Solution Variables mobile_id The ID of the mobile device which passed the hit into marketing reports. j_jscript Version of JavaScript supported by String (255 characters) browser. 14988E+15 Key: PRI 1. java_enabled Flag indicating whether or not java string (1 character) is enabled. whether or not this string (1 character) page was the user's homepage N hourly_visitor A flag to determine if current hit is a new hourly visitor. 50367E+16 Key: PRI 1. 8-bit unsigned integer 1. 64-bit numbers in base 10. 32-bit unsigned integer 23 monthly_visitor A flag to determine if current hit is a new monthly visitor. 1970. 32-bit unsigned integer 0 last_purchase_num The purchase number of the previous purchase.14 1. positive. 64983E+37 .) hitid_high Used to uniquely identify a hit. 0 ip IP address of user's computer. hitid_low Used to uniquely identify a hit. both padded to 19 zeros. Y javascript Version of Javascript. The 64-bit unsigned integer combination of hitid_low and hitid_high creates a unique ID for the row.89. 32-bit unsigned integer See Languages Lookup Key: FK last_hit_time_gmt Timestamp of the previous hit in GMT 32-bit unsigned integer 1102751965 32-bit unsigned integer 0 last_purchase_time_gmt The time of the previous purchase. 3 mcvisid Marketing Cloud Visitor ID The String (255 characters) Marketing Cloud Visitor ID is a 128-bit number that consists of 2 signed. 8-bit unsigned integer See Javascript Version Lookup Key: FK language Language ID (has lookup table). text page_event Page event ID. 32-bit unsigned integer See Operating Systems Lookup Key: FK p_plugins List of plugins available to the browser. (This column contains the value passed in on the hit for the page event. Look-ups provided for type of event (normal.com page_event_var2 If you have individually named your String (255 characters) link. text namespace Not currently populated. custom) 8-bit unsigned integer page_event_var1 Related to the page_event column. exit link or custom link clicked. String (255 characters) new_visit A flag that determines if the current 8-bit unsigned integer hit is a new visit.) page_type page type variable (only used for error page).Clickstream Data Column Reference 18 mvvar1-3 Mvvars are multi-value fields provided to allow customers to implement custom multi-value projects. htp:/www.adobe.com/search/search_results. String (255 characters) String (255 characters) 0 See Page Event Lookup errorPage 1 Y .download. search_results paid_search A (1/0) flag that determines if the hit 8-bit unsigned integer was used for paid search tracking. The text address of the page in the address bar of the browser. exit. text It is the URL of the download link. page_url The URL of the pageview. Also known as "list variables" in Adobe Marketing Reports & Analytics. http://www. This is a String (255 characters) comma-separated list of plungin_ids (usually about 5 characters each) for plugins that partners have registered with us.adobe. reserved for future release. persistent_cookie A flag indicating if 3rd party cookies string (1 character) and/or persistent cookies are enabled. 0 os Operating system ID (has lookup table). partner_plugins Not usable by customers.htm pagename The name of the page (if set). homepage_buy page_event_var3 Used for both Survey and Media text module. and serves as the pre-version for both modules. the type of hit that is sent in the request. this column contains the link name. 32-bit unsigned integer 868 post_campaign Persisting value of campaign. Y post_keywords The keywords that were actually used for the hit. String (255 characters) [CUSTOM]. string (1 character) Y post_currency Type of currency for the transaction. this column contains the link name. text For event ID to name mapping. homepage_buy . 32-bit unsigned integer 600 post_browser_width Width in pixels of the browser window. String (255 characters) [Custom] post_channel Custom traffic variable for site sections (channels). String (255 characters) It is the URL of the download link.Clickstream Data Column Reference 19 plugins List of plugin IDs available to the browser (has lookup table) This is the post value. String (255 characters) post_cust_hit_time_gmt Timestamp actually used for the hit. 8-bit unsigned integer What we ended up using for the hit.com post_page_event_var2 If you have individually named your String (255 characters) link. the type of hit that is sent in the request. String (255 characters) [Custom] post_cookies Specifies whether JavaScript session cookie is accepted. "What we text ended up using for the hit. String (255 characters) See Plugins Lookup Key: FK post_ page_event Page event ID. 8-bit unsigned integer 0 See Page Event Lookup post_ page_type page type variable (only used for error page). The delimiter is chosen by the client during implementation. my keyword post_mvvar1-3 Post-processed mvvars. Key: FK post_hier1-5 Delimited list of values as passed in on the image request.[CUSTOM]. see the event_lookup.adobe." String (255 characters) post_page_event_var1 Related to the page_event column. http://www. String (255 characters) [Custom] post_event_list Comma separated list of numeric IDs representing events passed in from the customer. USD 1102750716 post_cust_visid Post version of the cust_visid field. post_evar1-75 Persisting value of evar1-75.tsv that is delivered with the data feed. String (255 characters) errorPage post_browser_height Height in pixels of the browser window. or hit_time_gmt otherwise. 32-bit unsigned integer this is cust_hit_time_gmt for timestamp-enabled report suites. exit link or custom link clicked.[CUSTOM] post_java_enabled Flag indicating whether or not java string (1 character) is enabled. text 3826-0-0--**--3826-1-1--**--3826-2-0 post_t_time_info Raw time info from JavaScript. Arizona. Normally only set on a purchase page. Saxony [German Region]) passed in on JavaScrip.1000.HP Pavillion. quantity. search_results post_partner_plugins List of partner plugins available to the browser (has lookup table). (This column contains the value passed in on the hit for the page event. Processed based on page_event_var3. Utah.adobe.200|201. Search Engine Lookup post_state Geographical region (i. text . If no String (255 characters) page is specified this value is left empty.) post_page_url The URL of the pageview. String (255 characters) post_purchaseid Unique identifer for a purchase. merchandisingValues The product list as passed in through the JavaScript. htp:/www. [Custom] 1584A9646G String (255 characters) post_search_engine The numeric ID of the search engine 32-bit unsigned integer that was actually used and stored.com/search/search_results. text Computers. custEventsDecValues. product. String (255 characters) post_persistent_cookie Flag indicating if 3rd party cookies string (1 character) and/or persistent cookies are enabled. cost. search_results post_pagename_no_url The name of the page (if set).75. String (255 characters) AZ post_survey Post column for the marketing reports and Survey integration. and serves as the pre-version for both modules. post_referrer Page prior to the current page.htm post_pagename The name of the page (if set). String (255 characters) 12/11/2004 4:23:31 1 +420 post_tnt Post column for Analytics and Target integration. If no String (255 characters) page is specified the URL is placed in this value.Clickstream Data Column Reference 20 post_page_event_var3 Used for both Survey and Media text module.1. String (255 characters) Identifies a duplicate purchase (see duplicate_purchase). The String (255 characters) address of the page in the address bar of the browser. Y post_product_list Format is comma separated list of: category.Office Supplies post_prop1-75 Custom traffic variables 1 .e. Office Supplies . What we ended up using for the hit.visitorID) 1=IP&UA fallback (cookies were rejected by browser) 2=Wireless (HTTP Mobile Subscriber Header identified as mobile carrier) 3=Adobe (server generated. merchandisingValues Computers. stored in s_fid on client. 4=Fallback cookie (new fallback ID. text post_transactionid A unique identifier where various data points can be uploaded later via Data Sources. What we use for the hit. product.3) 5=Visitor ID Service See Identifying Unique Visitors. String (255 characters) post_visid_high The visid_high value that we ended 64-bit unsigned integer up using for the hit. post_visid_low The visid_low value that we ended 64-bit unsigned integer up using for the hit. post_zip Post version of the zip field. 8-bit unsigned integer A1B2C3D4 0=Custom VisitorID (A custom visitor ID was set in the code using s. quantity.1. stored in s_vi on client) Default method. JavaScript generated. added in H25. post_visid_type Post version of the visid_type column.Clickstream Data Column Reference 21 post_tnt_action Post column for Analytics and Target integration. product_list The product list as passed in through the JavaScript. custEventsDecValues. cost. String (255 characters) prev_page The page id of the previous page.200|201.HP Pavillion. 32-bit unsigned integer This is an internal identifier and not useful to the customer.1000. text 0 Format is comma separated list of: category. String (255 characters) ref_type Integer representing the type of referral for the hit. String (255 characters) resolution Resolution id (has lookup table). 8-bit unsigned integer referrer Page prior to the current page.e. Lookup values can be obtained from referrer_type. 0 service Deprecated. pe or ss . String (255 characters) [Custom] purchaseid Unique identifier for a purchase. Saxony [German Region]) passed in on JavaScript.Clickstream Data Column Reference 22 product_merchandising Replaced by post_product_list as of April 2011. 1584A9646G quarterly_visitor A flag to determine if current hit is a new quarterly visitor. The page_event column gives the same information but in more detail. 8-bit unsigned integer [Custom] ref_domain The referring domain of the hit (based on referrer).csv lookup table. 8-bit unsigned integer Secondary hits are charged at a rate of 50% of the normal costs. Arizona. ss social* Social solution variables.75. 1024x768 sampled_hit A (Y/N) field if the hit was used string (1 character) (sampled) or not for ad hoc analysis. See Social Solution Variables post_social* sourceid Adobe proprietary column information 32-bit unsigned integer state Geographical region (i. Contains data for Merchandising evars as they relate to products.type of hit String (2 characters) coming through. 1 secondary_hit Used to track secondary hits. N search_engine Search engine ID. String (255 characters) Identifies a duplicate purchase (see duplicate_purchase). Normally only set on a purchase page. prop1-75 Custom traffic variables 1 . 32-bit unsigned integer s_resolution Screen resolution as passed in from String (255 characters) JavaScript. has lookup table 32-bit unsigned integer See Search Engine Lookup Key: FK See Resolution Lookup Key: FK search_page_num The page number of search results 32-bit unsigned integer that the keywords were on from the search engine. Utah. String (255 characters) AZ . Stands for User String (255 characters) Agent Pixels. va_finder_detail Detail for first-touch value in the Marketing Channels Report.e. tnt_action Pre column for Analytics and Target text integration. String (255 characters) www263. truncated_hit A (Y/N) field that determines if the string (1 character) query string of the hit was truncated or not. ua_pixels Screen color depth. From HTTP header sent by older browsers.omniture. text user_hash The hash on the report suite ID. Stands for User String (255 characters) Agent Operating System. 644614 username The report suite ID. From HTTP header sent by older browsers. String (255 characters) 26/11/2013 4:23:31 1 420 tnt Pre column for Analytics and Target text integration. String (255 characters) va_closer_id ID for last-touch value in Marketing 8-bit unsigned integer Channels reports. va_finder_id ID for first-touch value in Marketing 8-bit unsigned integer Channels reports String (255 characters) String (255 characters) va_instance_event Instance event for first-touch value 8-bit unsigned integer in Marketing Channels reports va_new_engagement New engagement for first-touch 8-bit unsigned integer value in Marketing Channels reports A1B2C3D4 N 3757249664 . String (255 characters) [Custom] userid The numeric ID for the report suite 32-bit unsigned integer ID (normally seen in the name of DW files). transactionid A unique identifier where various data points can be uploaded later via Data Sources. Stands for User String (255 characters) Agent Color. ua_color Screen color depth. 32-bit unsigned integer user_server Custom traffic variable for servers. user_agent User agent as found in the HTTP header sent from the browser.Clickstream Data Column Reference 23 stats_server Adobe internal server that processed the hit. ua_os Screen color depth. From HTTP header sent by older browsers. String (255 characters) adobe va_closer_detail Detail for last-touch value in Marketing Channels reports. i.com t_time_info Raw time information from JavaScript. 21E+17 0=Custom VisitorID (A custom visitor ID was set in the code using s. JavaScript generated. 64-bit unsigned integer visid_low Part 2 of the visitorID. Only available if visid_type=3 (Example: a new s_vi cookie was generated). . 4=Fallback cookie (new fallback ID. visid_type Integer that specifies how the 8-bit unsigned integer visitorID was calculated (based on a lookup).Clickstream Data Column Reference video* post_video* 24 Video solution variables. this is the timestamp for when the ID was originally created. visit_keywords Keywords used to find the site. stored in s_fid on client. The combination of two visitor IDs (visid_high and visid_low) creates a unique visitor ID.3) 5=Visitor ID Service See Identifying Unique Visitors. stored in s_vi on client) Default method. The combination of two visitor IDs (visid_high and visid_low) creates a unique visitor ID. 64-bit unsigned integer visid_new Indicates whether this is a string (1 character) newly-generated visitorID.visitorID) 1=IP&UA fallback (cookies were rejected by browser) 2=Wireless (HTTP Mobile Subscriber Header identified as mobile carrier) 3=Adobe (server generated. String (255 characters) my keyword visit_num The number of the current visit (Incremented each time a visitor returns to the site). 32-bit unsigned integer 1 Note that visit_num is not incremented for excluded hits (hits where exclude_hit column > 0). 1. added in H25. visid_timestamp If the visitorID was generated by us 32-bit unsigned integer (visid_type=3). See Video Solution Variables visid_high Part 1 of the visitorID. 70E+18 1. Contained in event_list The amount of revenue associated with the purchase of an app. or populated by GeoSegmentation data.Clickstream Data Column Reference 25 visit_page_num The page sequence number in the 32-bit unsigned integer current visit. 84604. Contained in event_list . Contained in event_list The number of in app purchases.com String (255 characters) visit_start_pagename The pagename the visit started on. http://www.com String (255 characters) visit_search_engine The search engine used to find the 32-bit unsigned integer site. http://www.e.85381) passed String (255 characters) in by JavaScript.google. String (255 characters) homepage visit_start_time_gmt The GMT timestamp of the first pageview in this visit. 84604 App Store Solution Variables Variable/Event AppStore Downloads AppStore Purchases AppStore Rank Description Type The number of mobile application downloads. 8-bit unsigned integer [Custom] yearly_visitor A flag to determine if current hit is a new yearly visitor.adobe. 32-bit unsigned integer 1102750716 weekly_visitor A flag to determine if current hit is a new weekly visitor. This Contained in event_list calculated metric is defined using the following formula: [AppStore Rank] / [AppStore Rank (divisor)] AppStore Rank Divisor Used to calculate the average app ranking. 17 visit_referrer The referrer to the visit. This Contained in event_list calculated metric is defined using the following formula: [AppStore Rank] / [AppStore Rank (divisor)] AppStore In-App Revenue AppStore One-off Revenue AppStore In-App Royalties The amount of in app revenue. 8-bit unsigned integer 0 zip Zip code (i. 0 visit_start_page_url The start page for the visit. Contained in event_list The amount of in app revenue minus amount retained by app store. Contained in event_list Used to calculate the average app ranking. This Contained in event_list calculated metric is defined using the following formula: [AppStore Rating] / [AppStore Rating (divisor)] Video Solution Variables Note that pre* and post* versions of these variables are available. Total time spent viewing the video.Clickstream Data Column Reference AppStore One-off Royalties AppStore Rating The amount of one off revenue minus amount retained by app store. or what part. string (255 characters) string (255 characters) string (255 characters) string (255 characters) string (255 characters) string (255 characters) string (255 characters) string (255 characters) string (255 characters) Contained in event_list . 26 Contained in event_list Used to calculate the average app ranking. However. videostart Video Views. it does not Contained in event_list provide any information about how much. The post versions are prepended with "post_". Variable/Event Description Type video Video name videoad Ad name videosegment Segment videocontenttype Content Type. videoadpod Ad Pod videoadinpod Ad in Pod position videoplayername Player Name videochannel Channel videoadplayername Ad Player Name videotime Video Time Viewed. of a video the visitor viewed. This Contained in event_list calculated metric is defined using the following formula: [AppStore Rating] / [AppStore Rating (divisor)] AppStore Rating Divisor Used to calculate the average app ranking. Content type is set to "Video" automatically for all video views. Indicates that a visitor has viewed some portion of a video. Clickstream Data Column Reference 27 videocomplete Video Completes. Day of Week. Stores the Application name and version in the following format: string (255 characters) [AppName] [BundleVersion] For example. videoadstart Ad Views. Contained in event_list Contained in event_list Contained in event_list Mobile Solution Variables Note that pre* and post* versions of these variables are available. videoadtime Ad Time Viewed. Days Since First Use. Number of the week day the app string (255 characters) was launched. Indicates that a user has viewed a complete video or ad. Number of days since first run.1 mobilelaunchnumber mobiledayssincefirstuse mobiledayssincelastuse mobilehourofday mobiledayofweek Launch Number. Measures the hour the app was string (255 characters) launched. 24 hour numerical format. Sent on all close events. it does not provide any information about how much. or what part. Number of times the string (255 characters) application was launched or brought out of the background. Used for time parting to determine peak usage times. of a video the visitor viewed. Variable/Event Description Type mobileinstalldate First Launch Date. Total time spent viewing the ad. The post versions are prepended with "post_". videosegmentviews Video Segment Views. Number of days since last use. MM/DD/YYYY string (255 characters) mobileappid App Id. Indicates that a user has viewed Contained in event_list a complete video or ad. Date of first launch after installation. videoadcomplete Ad Completes. myapp 1. However. string (255 characters) Hour of Day. Indicates that a visitor has viewed some portion of an ad. . string (255 characters) Days Since Last Use. Contained in event_list which occur on video complete or when the users stops viewing at some point before the complete occurs. and the second number typically versions different members of the device family. string (255 characters) On iOS. mobileprevsessionlength Previous Session Length. Triggered on first run after installation (or re-installation). mobilelaunches Launches. Triggered on any run that is not an install or an upgrade. This also triggers when Contained in event_list the application is brought out of the background. this is a comma-separated 2 digit string that Identifies the iOS device. Width x Height in actual pixels. Triggered when the application does not exit gracefully.Clickstream Data Column Reference mobiledevice 28 Device Name. mobilecrashes Crashes. mobileupgrades Upgrades. Resolution. Event is sent on application Contained in event_list start after crash (the application is considered to crash if quit is not called). Aggregated total Previous Session Length. Triggered on first run after upgrade Contained in event_list (anytime the version number changes). The first number typically represents the device generation. Stores the device name. mobileosversion mobileresolution Operating System Version. string (255 characters) string (255 characters) mobilecampaignsource Mobile Campaign Source mobilecampaignmedium Mobile Campaign Medium mobilecampaignterm Mobile Campaign Term mobilecampaigncontent Mobile Campaign Content mobilecampaignname Mobile Campaign Name pointofinterest Point of Interest Name pointofinterestdistance Distance to Point of Interest Center mobileltv Lifetime Value (evar) mobileinstalls First Launches. mobileactiontotaltime Action Time Total string (255 characters) string (255 characters) string (255 characters) string (255 characters) string (255 characters) counter counter string (255 characters) Contained in event_list Contained in event_list Contained in event_list . socialpubsubscribers Subscribers. The post versions are prepended with "post_". socialpubrecommends Recommends. socialtotalsentiment Sentiment. sociallanguage Language. socialfbstorytellers People Talking About This. socialpubcomments Comments. Type text text text text text Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list Contained in event_list . socialpubsubscribers Followers. socialpubposts Posts. socialmentions Mention. sociallatlong Latitude / Longitude. socialpageviews Social Property Views. socialpostviews Post Views. socialfbstories Facebook Interactions.Clickstream Data Column Reference 29 mobileactioninapptime Action Time In App mobileltvtotal Lifetime Value (event) Contained in event_list Contained in event_list Social Solution Variables Note that pre* and post* versions of these variables are available. socialauthor Authors. sociallikeadds Like Adds. Variable/Event Description socialcontentprovider Social Platforms / Properties. Milestone Video 11 for "download link" 101 for "download link" 12 for "external or exit link" 102 for "external or exit link" 31 – Media start event 76 . Mobile SDKs.Media update only event (doesn't perform any perform any eVar or any other variable eVar or any other variable processing) processing) 78 . Link tracking 10 for "other link" 100 for "other link" 10 for trackAction and lifecycle calls 100 for trackAction and lifecycle calls from the from the Mobile SDKs.Media + other variable update event (includes 33 – Media + other variable update eVar and other variable processing) event (includes eVar and other variable processing) Heartbeat Video same as post 50 = (non-Primetime) Media Stream Start 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 (internal only.Clickstream Data Column Reference 30 Page Event Lookup Lookup table to determine the type of a hit based on the page_event value.Media start event 32 – Media update only event (doesn’t 77 .t() calls) 0 for trackState calls from the mobile SDKs. will not appear in data feed) . Hit type page_event value Page views same as post post_page_event value 0 for all page views (s. ID Hit source 1 Page view or tracked link with no timestamp passed in (non-timestamped report suites) 2 Page view or tracked link with timestamp passed in (timestamped report suites) 3 Live log file (not historical log file) with hit timestamps 4 not used 5 "generic" (sometimes known as ecommerce) data source (like current data source) 6 full (historical) log file (not live log file) 7 transactionid/customerid data source file 8 SCM (SearchCenter+) data sources 9 Adobe Social summary metrics .Clickstream Data Column Reference Hit type page_event value 31 post_page_event value 64 = Primetime Media Stream Ad Start 65 = Primetime Media Stream Ad Close (Complete/Finish) 66 = Primetime Media Stream Ad Scrubbing Survey 40 80 Hit Source Lookup Lookup table to determine the source of a hit based on the page_event value. These are summary rows uploaded using data sources. date_time starts with "2013-12" includes hits from December 2013. 8. Exclude all rows where exclude_hit > 0. Exclude all rows where exclude_hit > 0. which may have a value and/or a unique ID. Combine post_visid_high. 2. . 7 represents transaction ID data source uploads that should not be included in visit and visitor counts.8. Sum the remaining rows that have post_page_event = 0. The date_time field is human readable (for example. 3. Pre vs. Count unique number of combinations. Post column Bots Bots are excluded from data feeds according to the bot rules defined for your report suite. Visits Visitors 1.9. 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. For event ID to name mapping. Exclude all rows where exclude_hit > 0. 5. Exclude all rows with hit_source = 5. Formulas for common metrics The following table contains instructions to calculate several common metrics.8. See Hit Source Lookup. • post_page_event = 102 to count exit links. Event string The event string in event_list and post_event_list contains a comma-delimited list of events. For example. 1. See Page Event Lookup. Metric Page Views How to calculate 1.7. see Events. See Hit Source Lookup.9. We recommend doing all processing on the post_event_list because it is de-duplicated and has already applied logic to remove duplicate events with the same ID (see Event Serialization). post_visid_low. 3. see the event lookup delivered with your data feed. Exclude all rows with hit_source = 5. which indicates a normal page view. For more information on events. 2. and visit_num. YYYY-MM-DD HH:MM:SS) and is adjusted to the time zone of the report suite. and 9 are summary rows uploaded using data sources.Calculating Metrics 32 Calculating Metrics Describes how to calculate common metrics using clickstream data feeds. Date filtering Include rows from the date range you want included by filtering the date_time field. Subtract the post_cust_hit_time for hit 1 from the post_cust_hit_time for hit 2 to determine the seconds between these two hits. If this results in a negative number. and 9 are summary rows uploaded using data sources. This logic can be extended to calculate time spent for other values. and visit_num. Using page_event. Combine post_visid_high with post_visid_low. post_event_list contains the event. This means that a value for these three eVars was set on the hit. For example: hit 1: post_prop1=red hit 2: post_prop1=blue 6. eVar instances When an eVar is set on a hit. For example: post_event_list = 1. Exclude all rows where exclude_hit > 0.8. Group hits for a visit by concatenating visid_high. 5. When calculating time spent.8. 1. and eVar7. Count the number of times the event lookup value appears in post_event_list.Calculating Metrics Metric 33 How to calculate 2. event_list contains an instance of that eVar. filter the types of hits you want. but count the number of times the eVar lookup appears in the post_event_list. marketing reports & analytics and ad hoc analysis evaluate hits beyond the reporting period to determine time spent for values within the reporting . 3. Exclude all rows with hit_source = 5. Exclude all rows with hit_source = 5. See Hit Source Lookup. Find hits where the value you want to track time spent is set. When reporting time spent for a specific period. then order them according to the hit number within the visit. eVar2. For example: post_event_list = 100. 8. to the time of the next page view (track call). visid_low.101. 1. 2. use the same logic explained in Event instances above. 5. it indicates that the hit was received out-of-order and the calculation should be discarded. Event instances When an event is set on a hit. 4. The result is the time spent for post_prop1=red. 3. See Hit Source Lookup 3. you must group hits by visit.106 Indicates an instance of eVar1.200 Indicates an instance of purchase and event1. Order hits for each visit by visit_page_num. The post_event_list is de-duplicated and is recommended to determine event instances.7. Time Spent To calculate time spent.9.9. 2. To calculate instances for eVars. 7 represents transaction ID data source uploads that should not be included in visit and visitor counts. 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. These are summary rows uploaded using data sources. Count unique number of combinations. Exclude all rows where exclude_hit > 0. 4. 1. so you might need to account for revenue that is not in the products string. Ignore purchase data for rows where duplicate_purchase = 1. See Hit Source Lookup.69.Calculating Metrics Metric 34 How to calculate period.products.Athletic Socks.29. Exclude all rows with hit_source = 5.. 5-9 represent summary rows uploaded using data sources. and that total revenue from this purchase was $99. 3.95.94. For example: . . Currency conversion is applied to the post_product_list according to the settings for the units report suite.9. it might be difficult to match the time spent metrics exactly.8.10. Data warehouse does not evaluate hits beyond the reporting period.1. orders. Revenue. 2. The post_product_list uses the same syntax as s. so using that column is recommended.99 By parsing this string. This flag indicates that the purchase is a duplicate (meaning that a hit with the same purchaseID was already recorded). Due to the complexity of these calculations. Exclude all rows where exclude_hit > 0.95. Note: Analytics allows currency events that contain product revenue to be passed in through the events string.Cross Trainers. See Numeric/Currency Events in s. so you can parse this string to calculate metrics. you can determine that 1 pair of cross trainers were purchased for $69.events. except when the start and/or end date of the time period is on a monthly boundary. visit_num). and currency conversion might change the final value recorded for a variable that appears in the post column. the pre column will contain the exact casing passed in (tabby. which contains the value used by reporting. applying a custom formula to determine attribution). .list1="Tabby.siamese”. Case Sensitivity in Values Most Analytics variables are considered as case-insensitive for reporting purposes. For example. For example. VISTA rules. though you'll likely want to preserve case for display purposes.Persian. processing rules. then the column can be considered a post column. but evar1 is populated by your implementation.Siamese”. you can lowercase values for comparison purposes.Pre and Post Columns 35 Pre and Post Columns The pre column contains the data as it was sent to data collection.Persian.persian. variable persistence. For most calculations you want to use the post column unless you are applying custom business logic (for example. "Snow". but the value from hit 1 is likely persisted for that visit and will be reported in the post column (which will be Tabby. Both of these columns have a "post_" column (post_browser. for display purposes. pre_browser is populated by Adobe. Hit 2: s. For example: Hit 1: s. meaning different case variations are considered to be the same value ("snow". If a column does not contain a pre or a post version (for example. If you see different case variations of the same value between the pre and post columns (for example.Siamese) since hit 1 and 2 contain the exact same value when a case-insensitive comparison is performed.The post column contains the value after processing. and "Snow" in the post column). and "sNow" are all considered to be the same value). Columns prefixed with "pre_" typically contain data that was populated by Adobe and not sent by your implementation. post_evar1). However. case sensitivity is preserved since most customers prefer to be able to send in mixed case characters to display in reports.persian. "SNOW". The case variation in the post column was previously passed in and is stored in the virtual cookie.list1=“tabby. "snow" in the pre column.siamese). it indicates that you are passing in both uppercase and lowercase versions of the same value across your site. When processing the data feed. or was processed around the same time for that report suite. When hit 2 is reported in the data feed. When any of the special characters are preceded by a caret. event IDs. Literal backslash character. they represent a literal character. This character was part of the value sent in during data collection. mvvars) The following characters have a special meaning in multi-valued variables: Character Meaning Description . products_list. Character Meaning \\t Tab \\n Newline \\ Backslash Description Literal tab character. This character was part of the value sent in during data collection. Escapes tab. (comma character) End of value . Assigns a value to an event in the event_list. This character was part of the value sent in during data collection. or other values in multi-valued variables. newline. products_list. mvvars) • Sample workflow Special characters in the hit_data file The following characters have a special meaning in the hit_data file: Character Meaning \t (tab character) End of column \n (newline character) End of row \ (backslash character) Escape character Description Marks the end of a data field. they represent a literal character. • Special characters in the hit_data file • Special characters in multi-valued variables (events_list. Literal newline. and backslash when the character was part of the value sent during data collection. Marks the end of a data row. product value = (equals character) Value assignment Separates product strings. When any of the special characters are preceded by a backslash. . Special characters in multi-valued variables (events_list. (semicolon character) End of sub-value within an individual Separates values associated with an individual product in the product_list.Special Characters 36 Special Characters Information about special characters used in the Clickstream data feed. Special Characters 37 Character Meaning ^. backslash or caret character. Sample workflow If some of the columns in your data feed contain user-submitted data. newline. The data feed for these rows appears as follows: 1680\t1050\tsearch\\nstring\ten\n 800\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: 800 600 search\ string en To avoid this.complete the data store row.read the next character. insert the appropriate string literal.read the next character. and continue. read until you locate a tab. Starting at the beginning of the file. use a solution similar to the following: 1. This character was part of the value sent in during data collection. • Backslash . Literal equals character.insert the string up that point into a data store cell and continue. • Caret . This character was part of the value sent in during data collection. the newline and tab characters in the eVar1 values are escaped. This character was part of the value sent in during data collection. you should check for special characters before separating the data by column or row using split or readLine. insert the appropriate string literal. • Newline . . 2. Comma ^. Consider the following data: Browser Width Browser Height eVar1 prop1 1680 1050 search\nstring en 800 600 search\tstring en During export. This character was part of the value sent in during data collection. Literal caret character. Semicolon ^= Equals ^^ Caret Description Literal comma character. or similar. Literal semicolon character. Perform an action based on the special character encountered: • Tab . and continue. the hour of transition will actually include 2 hours’ worth of data. If you enable this option. if the transition occurs at 2:00 am. After that occurs. It will contain data from 1:00 DST to 2:00 STD (which would have been 3:00 DST). When making STD -> DST time transitions (“Spring Forward”). compresses it. out of quota. For example. so if the request is made within this period data feed files can be resent without being regenerated. Adobe attempts to automatically connect and send the data up to three separate times. For example. the customer will only get 23 files. This field is based on the time zone of the report suite. the customer will get 24 files.Troubleshooting 38 Troubleshooting Transfer Failures In the event of an FTP transfer failure (login denied. Resend Options If you need data for a delivery period resent. the file for 1:00 will be delayed by one hour. . If there was no data with timestamps that fall within the timeframe. Data feeds honor the time zone for which the report suite is configured. There will be no 2:00 file. The current data feed process uses the date_time field to determine which hits belong to the hour. If the time zone for the report suite is one that does not use DST. but will contain data for two hours. you'll receive a manifest file similar to the following: Datafeed-Manifest-Version: 1. The hour that is skipped in the DST transition is simply omitted. contact Customer Care. and will get a file for the 3:00 hour. (“Fall Back”). files are typically written out to data warehouse within 15-30 min after the hour. data feeds waits until all the hits that entered data collection within the timeframe (day or hour) have been written out to data warehouse. However. it becomes 3:00 DST. 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. The next file will begin at 2:00 STD. file delivery will be altered for the hour in which the time change occurs (usually 2:00 am). If the time zone of the report suite is one that does use DST. the feed is marked as failed and an email notification is sent. For hourly feeds. if the transition occurs at 2 AM. then the process tries again the next timeframe. When making DST -> STD transitions. but there is no set time period. they’ll get a file for the 1:00 hour.0 Lookup-Files: 0 Data-Files: 0 Total-Records: 0 Data Processing Overview Before processing hourly or daily data. and sends it via FTP. If the failures persist. etc). 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. since at 2:00 STD. Adobe stores the generated data feed files for the previous 7 days. data feeds collects the data with timestamps that fall within the timeframe. lost connection. file delivery will continue normally like any other day. or if you have questions regarding your current service. please contact your Account Manager. . Help & Technical Support The Adobe Marketing Cloud Customer Care team is here to assist you and provides a number of mechanisms by which they can be engaged: • Check the Marketing Cloud help pages for advice. some options described in this documentation might not be available to you. Terms of Use | Privacy Center Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. All third-party trademarks are the property of their respective owners. Capability & Billing Dependent on your solution configuration. Published by Adobe Systems Incorporated. Feedback We welcome any suggestions or feedback regarding this solution. Enhancement ideas and suggestions for Adobe Analytics can be added to our Customer Idea Exchange. due dates. Legal © 2014 Adobe Systems Incorporated. If you would like to add to or otherwise change your service level. and conditions. terms. tips. As each account is unique. please refer to your contract for pricing.Contact and Legal Information 39 Contact and Legal Information Information to help you contact Adobe and to understand the legal issues concerning your use of this product and documentation. All Rights Reserved. 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.