EventStore Data Guide

EventStore Data Guide

by on ‎08-27-2015 10:53 AM - edited on ‎05-18-2017 04:30 PM by Community Manager (2,145 Views)
Table of Contents Placeholder


A summary of the event-level data points that are made available through EventStore.

EventStore provides the most efficient way for collecting and exporting event-level data from your site. It all begins with the Tealium Collect Tag, which captures the live feed of events on your site. Streaming those events to EventStore allows you to view and download the underlying data. The data is compressed into a flattened JSON file and made available for download from Tealium’s Amazon S3 bucket. Each JSON object in the file may contain one or more rows of name-value pairs associated with the event.

Please note that if you send your event data (i.e. Streams) elsewhere, such as your own S3 bucket or server, you will not see any Streams show up in EventStore.

Data Collected

The Collect Tag captures a mix of pre-defined data variables and data from the page. These are summarized below.

In your data log files, please ignore any legacy values prefixed by "_t". 

Default Variables

  • Visitor ID: This is the unique ID of the visitor.
  • Event ID: This is an alphanumeric identifier unique to the event.
  • Event Time: This is the unix/epoch timestamp (based on UTC time zone) of the event.
  • User Agent: This is the user-agent header.

DOM Variables

Variable Description
dom_domain Domain of the site
dom_pathname Pathname of the URL
dom_query_string Querystring portion of the URL following the "?" character
dom_url The entire URL of the HTML document
dom_title Title of the HTML document
dom_viewport_width Device screen width
dom_viewport_height Device screen height

Page URL Variables

Variable Description
pageurl_scheme URI protocol such as "http" or"https"
pageurl_domain Domain of the site
pageurl_path Pathname of the URL
pageurl_querystring Querystring portion of the URL following the "?" character
pageurl_query_params_key For each querystring parameters, a data point will exist containing the parameter key and value
pageurl_full_url The URL of the HTML document without querystring parameters

Referrer URL Variables  

Variable Description
referrerurl_scheme URI protocol of referring URL such as "http" or"https"
referrerurl_domain Domain of the referring URL site
referrerurl_path Pathname of the referring URL
referrerurl_querystring Querystring portion of the referring URL following the "?" character
referrerurl_query_params_key For each querystring parameters, a data point will exists containing the paramter key and value
referrerurl_full_url The entire URL of the referring page

Tags Executed

Variable Description
tags_profile_tag-uid_executed The profile and tag that successfully executed. Each successfully tag trigger will include its own entry.

Environment Detail Variables   

Variable Description
Account (ut.account) Tealium iQ account
Profile (ut.profile) Tealium iQ profile
Environment (ut.env) The publish environment associated with the utag.js file.

Tealium Built-in Variables

Variable Description
Event (ut.event) The name of the event being tracked. (view, link, etc.)
Version (ut.version) The utag.js version number followed by the timestamp of its publish
Domain (ut.domain) The top-level domain of the currently-loaded web page

First-Party Tealium Cookies 

Variable Description
_ses_id The timestamp that logs the time spent by a visitor on your site. It is based on the local timezone set in the visitor's computer.
- Requires utag.js version 4.27 and later
_st The time at which the visitor's session will expire, if the visitor does nothing more. It is the visitor's "now" time, plus the session timeout time. This timeout period is normally 30 minutes (1800000 milliseconds), unless it has been configured differently. It is the value of utag.cfg.session_timeout, and can be over-ridden by changing this same variable, using for example a JavaScript Extension.
- Requires utag.js version 4.26 and later
_v_id The ID value unique to the visitor
- Requires utag.js version 4.26 and later
_ss A flag value (0 or 1) indicating the start of session
- Requires utag.js version 4.26 and later
_pn The page number value which starts over at 1 with each new session and increments every time utag.js loads
- Requires utag.js version 4.28 and later
_sn The session count
- Requires utag.js version 4.28 and later
_dc_visit Keeps count of the visits, starting as "1" for the first visit
_dc_event Keep count of the page views, starting as "1" for the first page view of a visit
_dc_region The AudienceStream Region in which the visit session resides


Refer utag.js release notes for individual utag versions.

The visitor's timezone is not sent in the Managed S3 for Events data. However, it is possible to work it out it by looking at the difference between EventTime and _ses_id, on the record where _ss is 1, since that record is the start of the session. Alternatively, if utag.cfg.session_timeout is known, it is possible to work out the user's local "now" time by substracting utag.cfg.session_timeout from _st, and then to work out the timezone by looking at the difference between this "now" time and EventTime. This approach can be used on any record.

Additional Data Variables

The Tag also collects a variety of other data from the page, including:

  • Data points defined in your Data Layer.
    •   The maximun character length for any one value is 255 characters. 
  • Webpage elements like meta data, cookie parameters, and JavaScript page variables 
  • Performance Timing metrics for gathering RUM (Real User Monitoring) data. This data can be used to understand a user's experience (i.e. the Browser's time to DOM Interactive state) for your site's pages.
    • "timing.domain" = The domain where the timing data was collected
    • "timing.pathname" = The path name (web page) where the timing data was collected
    • "timing.query_string" = The query string value in URL where the timing data was collected
    • "timing.timestamp" = The date/time when the timing data was collected (epoch time of client's web browser)
    • "timing.dns" = t.domainLookupEnd - t.domainLookupStart
    • "timing.connect" = t.connectEnd - t.connectStart
    • "timing.response" = t.responseEnd - t.responseStart
    • "timing.dom_loading_to_interactive" = t.domInteractive - t.domLoading
    • "timing.dom_interactive_to_complete" = t.domComplete - t.domInteractive
    • "timing.load" = t.loadEventEnd - t.loadEventStart
    • "timing.time_to_first_byte" = t.responseStart - t.connectEnd
    • "timing.front_end" = t.loadEventStart - t.responseEnd
    • "timing.fetch_to_response" = t.responseStart - t.fetchStart
    • "timing.fetch_to_complete" = t.domComplete - t.fetchStart
    • "timing.fetch_to_interactive" = t.domInteractive - t.fetchStart 

    If the value of a data point equals "0" it simply means that no timing information was captured. Please ignore it when reporting or averaging.

References for Performance Timing metrics:

Sample JSON Object

    "visitorid": "014fb34a718e001ad754191d58ff1c074003a06c00c48",
    "eventid": "65f61a4b-54ca-4adf-b757-657e1711f6e7",
    "eventtime": 1441822083000,
    "useragent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/8.0.8 Safari/600.8.9",
    "dom_domain": "",
    "dom_pathname": "/products/audiencestream/",
    "dom_query_string": "",
    "dom_url": "",
    "dom_title": "AudienceStream | Real-time Data Action Engine | Tealium",
    "dom_viewport_width": "1670",
    "dom_viewport_height": "1059",
    "pageurl_scheme": "http",
    "pageurl_domain": "",
    "pageurl_path": "/products/audiencestream/",
    "pageurl_querystring": "",
    "pageurl_full_url": "",
    "referrerurl_scheme": "https",
    "referrerurl_domain": "",
    "referrerurl_path": "",
    "referrerurl_querystring": "",
    "referrerurl_full_url": "",
    "tags_tiq_as_3_executed": true,
    "tags_tiq_as_1_executed": true,
    "udo_ut_account": "tealium",
    "udo_ut_profile": "main",
    "udo_ut_env": "prod",
    "udo_ut_event": "view",
    "udo_ut_version": "ut4.39.201509091709",
    "udo_ut_domain": "",
    "firstpartycookies_utag_main_ses_id": "1441822044558",
    "firstpartycookies_utag_main__st": "1441823881730",
    "firstpartycookies_utag_main_v_id": "014fb34a718e001ad754191d58ff1c074003a06c00c48",
    "firstpartycookies_utag_main__ss": "0",
    "firstpartycookies_utag_main__pn": "2",
    "firstpartycookies_utag_main__sn": "1",
    "firstpartycookies_utag_main_dc_visit": "1",
    "firstpartycookies_utag_main_dc_event": "2",
    "firstpartycookies_utag_main_dc_region": "us-west-1",
    "firstpartycookies__gat": "1",
    "firstpartycookies__ga": "GA1.2.2095105468.1441822080",
    "js_page.is_mobile": "false",
    "js_page.is_tablet": "false",
    "device_type": "desktop",
    "udo_page_name": "AudienceStream | Real-time Data Action Engine | Tealium",
    "udo_site_name": "Tealium",
    "udo_site_description": "Tag Management and Audience Segmentation",
    "udo_page_type": "page",
    "udo_post_author": "tealium",
    "udo_post_date": "2014/11/26",