EventStore data guide

This article provides a summary of event-level data points made available through EventStore.

How it works

EventStore provides the most efficient way for collecting and exporting event-level data from your site.

Here’s how it works:

  1. The Tealium Collect tag captures the live event feed on your site and feeds the events to EventStore, which allows you to view and download the underlying data.

  2. The captured data is then 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.

    If you send your event data (event feeds), to another location, such as your S3 bucket or server, the feeds are not displayed in EventStore.

  3. After the S3 bucket reaches a size of 100 MB (uncompressed) or after 1 hour has elapsed, whichever comes first, the data is compressed and prepared for Redshift.

  4. The compressed data is then copied and imported into the Redshift database for your account.

Tealium Collect tag data

The Tealium Collect tag sends several predefined variables and data from the page, as described in the following sections.

Ignore legacy values prefixed by _t in your data log files.

Default variables

Variable Description
visitorid The unique ID of the visitor.
eventid An alphanumeric identifier unique to the event.
eventtime The UNIX/epoch timestamp of the event, based on UTC time zone.
useragent 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 The Uniform Resource Identifier (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 parameter, there is a data point that contains the parameter key and value.
pageurl_full_url The URL of the HTML document without querystring parameters.

Referrer URL variables

Variable Description
referrerurl_scheme The 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 parameter, there is a data point that contains the parameter key and value.
referrerurl_full_url The entire URL of the referring page.

Tags executed

Variable Description
  • The profile and tag that successfully executed.
  • Each successful tag trigger includes its own entry.

Environment detail variables

Variable Description
ut.account Tealium iQ account.
ut.profile Tealium iQ profile.
ut.env The publish environment associated with the utag.js file.

Tealium built-in variables

A full list of Tealium built-in variables is provided in the Built-In Data Layer Variables article.

Variable Description
ut.event The name of the event being tracked, such as a view or link.
ut.version The utag.js version number, followed by the publish timestamp.
ut.domain The top-level domain of the currently loaded web page.
tealium_session_number A duplicate of the existing value in cp.utag_main__sn.
tealium_session_event_number A new cookie value in cp.utag_main__se that counts the number of calls in the current session (visit) Useful for Single Page Apps (SPAs) where there is always ‘one page’ and many events on that page

First-party Tealium cookies

Variable Description
_ses_id A unique identifier for the session. Requires utag.js version 4.27 and later.
_st The time at which the visitor session expires if the visitor does nothing more. This is the visitor’s “now” time, plus the session timeout time. This timeout period is normally 30 minutes (1800000 milliseconds) unless configured otherwise. The value of utag.cfg.session_timeout, which can be overridden by changing this variable using 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 indicating the start of session. Values are 0 or 1. Requires utag.js version 4.26 and later.
_pn The page number value. Starts over at 1 with each new session and increments each 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 visits. Starts as “1” for the first visit.
_dc_event Keeps count of page views. Starts as “1” for the first page view of a visit.
_dc_region The AudienceStream region where the visit session resides.

Additional variables

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

  • Data points defined in your data layer. The maximum character length for any one value is 255 characters.
  • Webpage elements, such as metadata, cookie parameters, and JavaScript page variables.
  • Performance timing metrics for gathering Real User Monitoring (RUM) data. This data can be used to understand a user’s experience. For example, the browser time to DOM interactive state for pages on your site.
Peformance timing variable Description
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.domainLookupStart
timing.connect t.connectStart
timing.response t.responseStart
timing.dom_loading_to_interactive t.domInteractive minus t.domLoading
timing.dom_interactive_to_complete t.domComplete minus t.domInteractive
timing.load t.loadEventEnd minus t.loadEventStart
timing.time_to_first_byte t.responseStart minus t.connectEnd
timing.front_end t.loadEventStart minust.responseEnd
timing.fetch_to_response t.responseStart minus t.fetchStart
timing.fetch_to_complete t.domComplete minus t.fetchStart
timing.fetch_to_interactive t.domInteractive minus t.fetchStart

If the value of a data point equals zero (0), no timing information was captured. You can ignore the zero values when reporting or averaging.

Calculate visitor timezone

The timezone for a visitor is not sent in the EventStore data. You can calculate the timezone by viewing the difference between EventTime and _ses_id on the record where _ss is 1, since that record is the start of the session.

If utag.cfg.session_timeout is known, you can calculate the current local time for the user by subtracting utag.cfg.session_timeout from _st, and then calculating the timezone by looking at the difference between the current time and EventTime. This approach can be used for any record.

Versions of utag.js

For detailed information about individual utag versions, see the utag.js Release Notes.

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",

Performance timing metrics

For additional information about performance timing metrics, see the following:

Was this page helpful?

This page was last updated: January 7, 2023