This document outlines some of the requirements for an IBM Digital Analytics, or CoreMetrics (CM), Implementation. We'll start with an description of how CM records traffic. If you are familiar with how CM operates then you can skip this section and move to the Data Layer Section.
In this article:
CM uses "Data Tags" to determine how the traffic is getting bucketed on the CM end. The tags are actually various IBM functions that are called. Each of these functions are contained within the IBM CoreMetrics tag from the Tealium Marketplace.
The widely used CM tags available are:
Other CM tags include:
site_real_estate = "Version-_-page_area-_-estate_info"
The site_real_estate variable will then get mapped to ManualImpressionTag_cm_re in the Data Mapping dialog. CoreMetrics will break apart the variable based on the "-_-" and populate the reporting accordingly.
site_promotion = "promotion_type-_-promotion_name-_-promotion_info"The site_promotion variable will then get mapped to ManualImpressionTag_cm_sp in the Data Mapping dialog. CoreMetrics will break apart the variable based on the "-_-" and populate the reporting accordingly.
Now that we have an understanding about how CM collects data lets see how the Tealium data should be structured. CM breaks out custom metrics, called attributes, for each function call. Attributes are numbered between 1-100 for most functions and appear in the server call to CM like pv_a1, for Page View attribute 1. In order to set up CM, the client will need to provide an outline of which UDO variables correspond to each attribute.
Typically each attribute will need it’s own UDO variable.
As a best practice for Tealium, include a variable in the UDO that defines when each type of CM function should be called. For example, on Cart Pages include a variable called event_type = “shopping”, or when you are using link tracking and you want to call cmCreateElementTag() then event_type=”element”. This will aide in setting up the Tealium implementation.
There are several sections to fill out to make sure the CM tag is set up properly.
|Title||A Tealium Specific label that is used exclusively in the Tealium UI.|
|Tag Version||Leave the default to load the eluminate.js (CM main library) via Tealium, or select External to load it from the CM CDN.|
||This is the client ID given from CM i.e. 89999999|SiteID.|
|Test Client ID
||This is the Client ID that corresponds to your test site.|
||True indicates 1st Party Cookie, False indicates CM managed 1st party or 3rd party as applicable.|
||Usually should be left as default.|
||The domain of the client’s site i.e. Tealium.com.
||The domain of the client’s test site. When this is filled in the tag template will automatically recognize this domain and set the Collection Domain and Test Client ID accordingly.
This tag should load on All Pages like most analytics tags.
Once we have the outline of which variables should be assigned to each attribute we can begin mapping the variables. When we select a variable to map the Data Mapping dialog will appear like so:
You can see each Category corresponds to the previously outlined CM Data Tags. The Data Mapping dialog defaults to the Page View Category.
For each Category there will be standard variables that are defined above all attributes and extra fields. In the picture above the standard variables are
These variables are customary variables CM is expecting to be passed with each function.
One variable can be used for the same attribute in multiple functions. i.e. page_type can be used for Page View attribute 1 along with Product View attribute 1 etc.
The Events Category in the Data Mapping dialog is where you can define when each of the CM functions should fire depending on the value of a certain variable.
When a variable has been selected and you click on the Events tab you will see 2 fields: Value and Trigger. The Value field is where you insert the value of the variable you selected, and the Trigger drop box is where you select the event you want to fire. This is where you define a kind of if/then statement like, “if the variable selected equals what is contained in the Value field then run the selected event in the Trigger drop box”.
In the following example we are saying when the selected variable EQUALS “cart” Trigger the Cart/ShopAction5 function:
If a defining variable is not available, extensions can be used to determine when specific calls should be made. Define a Data Layer variable called _cevent in the Data Sources Tab. To trigger one of the following functions set _cevent as follows:
|Data Tag||_cevent value|
As an example, let's say you need to trigger the cmCreateProductviewTag() on product detail pages, and the product pages have a URL similar to this:
Using a Set Data Values Extension you could:
Then ensure that you have the mapping configured for _cevent for the Product View event.