Back

EventStore (legacy) is the Tag that allows you to log your website's traffic data directly for Event Store.
NOTE: This Tag has been deprecated and, therefore, NOT available in the Tag Marketplace anymore. However, any instances of this Tag added prior to deprecation are still supported and renamed 'EventStore Legacy'.

Configuring the EventStore Legacy Tag

To edit the settings of an existing EventStore (legacy) Tag:

1. Go to the Tags tab in Tealium iQ and click on this Tag. Then click on 'Edit'.

2. The Server field is automatically populated with "//uconnect.tealiumiq.com/ulog/youraccount.yourprofile". The 'youraccount' and 'yourprofile' values indicate the account and profile to which this Tag has been added.

NOTE: Do not modify this field unless you want to set it to a custom path. Please contact your Account Manager before making any changes.

3. From the 'Require Mapping' list choose whether or not you want to map data sources.
The default of " No" will automatically send all data points in your Data Layer.
Setting it to " Yes" will ONLY send the data points you specify via Data Mappings tab (more on this below).

4. Enter any suitable notes (optional) and proceed to the Load Rules tab.

5. Leave the 'Load on All Pages' Rule selected.

6. If you selected "Yes" for mapping in step #3, proceed to the Data Mappings tab. Otherwise, click Finish.

7. Perform a Save/Publish

configure_eventstore.png

Back to top

How EventStore Legacy Works

When a browser loads your web site it also loads Tealium's code which contains the EventStore Tag. When EventStore loads, it acts like a traditional pixel request and sends a GET request to the webserver(s) you specified for an invisible 1x1 pixel. Tealium attaches various data sources to this GET request. When the webserver receives the GET request, it also receives the data attached to that request. The webserver then responds to the request by sending a 1x1 pixel to the browser. Because EventStore uses a GET request, there may be a limit to the number of characters you can send with the request. The HTTP protocal doesn't specify a limit, but web browsers can impose a character limit, such as some versions of Internet Explorer setting the limit at 2,083 characters.

Data Points Captured by EventStore Legacy

The browser's GET request automatically includes all of the variables contained in your Universal Data Object (UDO). However, if the names of the variables in your UDO contain a period, for example 'page.name', then Tealium will not automatically send them. You must map those data sources manually, as described below.

In addition to your UDO, there are a number of additional data points sent. Here are the data points captured by default:

Default Data Points

Data Point Name Description
_cb Cache Busting This variable is used for cache busting purposes. A random value is assigned for this purpose.
_cs Current Session ID This is the session ID for the current session (or visit). This number is the same as “_fs" ONLY during the visitor's first session and will be different otherwise.
_dr Referring URL This is the referring URL (or previous page) associated with the event. This data can be used for clickstream or path analysis based on the data.
_du Page URL This indicates the URL of the page being viewed.
_ec Event Count This indicates the total number of events (not just views). In cases where the only event type being used is “view" then this number will be the same as the _evc count.
_et Event Type This is the type of event passed through. Example event types include:
    • view
    • link
    • impression
    • video
    • conversion
    • custom
These are defined using the utag calls (such as utag.view). Event types are defined as "view" unless specifically set otherwise by the customer during the implementation process.
_evc Event View Count This integer indicates the total number of views for the current session. For example, the first view of the session will have an “_evc" value of “1".
_fs First Session ID This is the session ID assigned to the visitor's first session. This data can be used when using EventStore to conduct cross-session analysis.
_nv New Visitor Flag This value is set to “1" if a new visitor and “0" if otherwise.
_sc Session Count This integer shows the number of visits or sessions associated with the visitor. For example, a value of “1" means it's the visitor's fist visit, while a value of “4" indicates the fourth visit.
_sd Session Referring Domain This variable is populated with the referring domain on the first event of the session.
_sr Session Referring URL This variable is populated with the referring URL on the first event of the session.
_ss Session Start Flag Potential values are “0" or “1". The value “1" means that the event or the record is the first record in the session (typically landing page). A value of “0" means that the event is not the first event in the session.
_vd Visitor Referring Domain The referring domain associated with the visitor's first session. For first- time visitors, this value will be the same of the “_sd" variable.
_vi Visitor ID Visitor ID is a random ID assigned to the visitor. It is tied to the visitor using a cookie and will persist unless the cookie is deleted. Use Visitor ID in order to look at the person's behavior across multiple sessions. For example, you can use the visitor ID to see if a visitor who responded to an internal promotion in a given session ended up making a transaction in the next.
_vr Visitor Referring URL This variable indicates the referring URL associated with the visitor's first session. For first-time visitors, this value will be the same as the “_sr" variable.

 

Data Points Not Automatically Captured

This Tag does NOT automatically capture the following data:

  • JavaScript variables located on your web page, but outside of the UDO.
  • Variables that are inside your UDO, but have a period in the name.
  • DOM data, such as the URL, document title, querystring, meta tag information, and cookie values.

To log this data, you must manually map them as described below.

Mapping Data Sources

There are a few reasons you may want to map data:

  • To map a data source that is not located in the UDO.
  • To map a data source that is contained in the UDO, but has a period in its name.
  • To truncate, or shorten, the name of a data source in order to avoid going over any browser-imposed character limits on the GET request.

There are no pre-built destination variables for EventStore, so you must create the destination for the data source you want to map.

To map a data source in EventStore Legacy:

1. In Tealium iQ, navigate to the Tags tab and expand the EventStore (Legacy) Tag.

2. Click the 'Edit' button in the Data Mappings section.

3. Select the data source you want to map.

4. Click the Select Destination button. There is no Mapping Toolbox for this Tag. Instead, the data source will appear below without a value in the text field.

5. Enter a value in the text field to identify the data source. This value is how you can identify the new data source. Choose something short to avoid exceeding any browser-imposed character limits on GET requests. Try to stick to the naming convention that default data sources use. For example, if you map the page_name data source, enter "_pn" into the text field. Not only does this remain consistent, but you also minimize the number of characters sent with the GET request.

eventstream_mapping.png

Back to top

Delivering Data to Your Own Servers

Prerequisites

If you prefer to send the data collected by this Tag to your own webservers instead of Tealium's, there are a few pre-requisites you need to meet.

  • You must have your own webserver set up to collect the data.
  • The webserver must have logging enabled.
  • The webserver responds with an HTTP Status of 200 to an invisible 1x1 pixel request.

Please contact your Account Manager before setting up this Tag to send data to your own web servers.

Sending Data to Your Server(s)

To specify your own server:

  1. Edit this Tag as described under Configuring the Tag.
  2. In the Server field replace the default pathname with the pathname to your web server.
  3. Save/Publish the profile.

Back to top