Cumulative release notes for Clickstream data feeds.
There is now a user interface for data feeds and job management. Until now, Data Feed administrators had to rely on Adobe Customer Care to get a status update on their Data Feed jobs. This is no longer the case. The Data Feed user interface is now available to all Adobe Analytics administrators.
With this release, the name of the service has changed from Clickstream Data Feeds to Analytics Data Feed.
The following sections contain legacy history information from the Clickstream Data Feeds service.
The following data feed column sizes will increase in a future release:
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 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.
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.
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.
Expand the following columns to store a 255 character string:
Expand the following columns to store a 32-bit unsigned integer:
|post_browser_height||post_browser_width||browser (Feb 20, 2014)|
|os (Feb 20, 2014)||resolution||visit_search_engine|
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.
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 Feed Information.
Format of post_product_list column when events are present but product is empty
In post_product_list, If events are contained on the event list for a given hit but there is no product in the product list, the post_product_list contains four semicolons:
or in rare cases as semicolon, semicolon, zero, semicolon, zero, semicolon:
If you are performing a check for an empty product list you should update your ETL to handle both formats.
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.
post_mvvar1 – post_mvvar3