Learn how to leverage the Mapping toolkit and understand the role of E-Commerce Extension and Data Tags in the mapping process.

Contents:

Before You Begin

Before you begin mapping the Data Layer variables to Coremetrics' destination variables, be sure to add the E-Commerce Extension. Certain E-commerce variables like Product View, ShopAction5, and ShopAction9 values are automatically populated by the Extension. The Mapping toolkit should be used to map variables if,

  • The E-commerce Extension does not automatically perform mapping
  • You want to override the E-Commerce variables in the Extension

Coremetrics Data Tags and Mappings

Coremetrics' Data Tags are functions that tell the Coremetrics tool how to organize the data it receives. Custom metrics called "Attributes" are available for each function call. Attributes are stored in numbered variables (generally between 1-100) for most functions and will have a nomenclature of something like pv_a1…pv_a100 (Coremetrics Page View Attributes 1-100) in the tag call to Coremetrics. All attributes for each Coremetrics Data Tag should be defined in the Tealium Data Layer.

 

Best Practice: We recommend including a variable in your Tealium Data Layer that you can use to define which Coremetrics Data Tag should fire in any given situation. For example, on Cart Pages include a variable in the Tealium Data Layer (utag_data) called "event_type" and give it the value of something like "shopping" (event_type = "shopping"). Or, when you are using the link tracking Data Tag assign "event_type" the value of "element" (event_type = "element"). This will greatly facilitate managing the Coremetrics tag through Tealium iQ.

 

Mapping Toolbox

The tabs in the Tealium's Mapping toolbox are categorized according to Coremetrics' Data Tags, making it easy to select the destination to which you want to send data. Below is a rundown on each tab and the Data Tag function it corresponds to.

 

Events Tab

Start out by configuring the Events tab because it controls when to fire the various Coremetrics Data Tag functions. Do you remember the event_type variable we asked you to add to your Data Layer? You will use the value contained in this variable to determine which Data Tag function to fire.

 

  1. In the Value field, enter the value of the event_type variable that identifies the type of event.
  2. From the Trigger drop-down, select the appropriate Data Tag function. You can map additional event triggers by clicking the plus button.

event_mapping.png

 

Page View Tab

 

Data Tag: Page View
Tagging Function: cmCreatePageViewTag()
Description: This Data Tag captures page information as the visitor navigates the site. The function should be called on every page where you want to measure a page view.
Mappings: Use the Mapping toolkit to map the below destination variables:

  • Page ID (pi) - alphanumeric identifier of the page
  • Page Category (cg) - category to which the page belongs
  • Search String(si) - search keyword used to generate the search results page
  • Search Results (sr) - Number of results returned by the keyword search
  • Attribute variables pv_a1 through pv_a10
  • Extra Field variables pv1 through pv10

Product View Tab

Data Tag: Product View
Tagging Function: cmCreateProductViewTag()
Description: This Data Tag captures information about the views received by the product. To track views of multiple related product details, more than 1 ‘Product View’ function call may be sent from a single page.
Mappings: Use the Mapping toolkit to map the Product Virtual Category (cm_vc) and all Attribute variables ('pr_a1' through 'pr_a10').

The E-Commerce Extension, if configured, automatically maps:

  • _cprod to Product ID (pr), unique identifier of the product
  • _cprodname to Product Name (pm), name of the product being viewed
  • _ccat to Product Category (cg), category to which the product belongs

Cart View (ShopAction5) Tab

Data Tag: ShopAction5 (Cart View)
Tagging Function: cmCreateShopAction5Tag()
Description: This Data Tag captures data about the selected products and which products are present in the shopping cart. The function should be called for each product in the cart (3 items in the cart = 3 Shop Action 5 function calls).
Mappings: Use the Mapping toolkit to map all Attribute (s_a1 through s_a10) and Extra Field (sx1 through sx10) variables.

The E-Commerce Extension, if configured, automatically maps:

  • _cprod to Product ID (pr) - unique identifier of the product
  • _cprodname to Product Name (pm) - name of the product viewed in the cart
  • _cquan to Product Quantity (qt) - quantity of the product viewed in the cart
  • _cprice to Product Price (bp) - unit price of the product
  • _ccat to Product Category (cg) - category to which the product belongs

Order (ShopAction9) Tab

Data Tag: Shop Action 9 (Products Ordered)
Tagging Function: cmCreateShopAction9Tag()
Description: This Data Tag captures information about the product purchased by the visitor. The function call should be made on the Receipt or the Confirmation page for each line item in the order. Anytime the Tealium E-Commerce Extension Order ID variable (_corder) is populated, this function will automatically run.
Mappings: Use the Mapping toolkit to map all Attribute (o_a1 through o_a10) and Extra Field (or1 through sx10) variables.

The E-Commerce Extension, if configured, automatically maps these ShopAction 9 variables:

  • _ccustid to ShopAction9 Registration ID (cd), unique registration code. If you do not map anything to this destination either through the E-Commerce Extension or manually through the Mapping Toolbox, then Tealium maps the session ID from the utag_main cookie to this destination automatically.
  • _corder to ShopAction9 Order Number (on)
  • _csubtotal to ShopAction9 Order Subtotal (tr)
  • _cprod to ShopAction9 Product ID (pr)
  • _cprodname to ShopAction9 Product Name (pm)
  • _cquan to ShopAction9 Quantity (qt)
  • _cprice to ShopAction9 Product Price (bp)
  • _ccat to ShopAction9 Product Category (cg)

and these Order variables,

  • _cship to Order Shipping Amount (sg)
  • _ccity to Order City (ct)
  • _cstate to Order State (sa)
  • _czip to Order Zip/Postcode (zp)

Registration Tab

Data Tag: Registration
Tagging Function: cmCreateRegistrationTag()
Description: This Data Tag tracks registration events on the site and collects the visitor's demographic information (zipcode, city, state, etc.) and email address provided as part of the registration. If you don't use the E-Commerce Extension, Tealium uses either the value mapped to ShopAction9 Registration ID or the session ID from the utag_main cookie.
Mappings: Use the Mapping toolkit to map the Registration Email (em) and all Extra Field (rg1 through rg10) variables.

The E-Commerce Extension, if configured, automatically maps:

  • _ccustid to Registration ID (cd). If you don't use the E-Commerce Extension, then Tealium uses either the value mapped to ShopAction9 Registration ID or the session ID from the utag_main cookie.
  • _ccity to Registration City (ct)
  • _cstate to Registration State (sa)
  • _czip to Registartion Zip/Postcode (zp)
  • _ccountry to Registration Country (cy)

Conversion Event Tab

Data Tag: Conversion Event
Tagging Function: cmCreateConversionEventTag ()
Description: This Data Tag collects the non-monetary details of a conversion event. It is important to note that adding Conversion Event tags on load of high volume pages could inflate Server Call charges.
Mappings: Use the Mapping toolkit to map these variables:

  • Conversion Event ID (cid) - unique identifier for the type of conversion
  • Conversion Event Action Type (cat) - conversion event's initiation or successful completed
  • Conversion Event category ID (ccid) - category of Event IDs
  • Conversion Event Points (cpt) - points assigned to the conversion to measure its value
  • Attribute variables c_a1 through c_a10
  • Extra Field variables cx1 through cx5

Element Tab

Data Tag: Element
Tagging Function: cmCreateElementTag
Description: This Data Tag tracks visitors' interaction with dynamic elements on your site. Examples of dynamic element include videos, hover-overs, error messages, feature selectors, etc.
Mappings: Use the Mapping toolkit to map these variables:

  • Element ID (eid) - unique identifier of the element being tracked
  • Element Category (ecat) - category to which the element belongs

Make certain that you map a different data source to Conversion Event ID (cid) than you do to Element ID (eid).

Manual Tab

This Tab houses three different Data Tag functions: Manual Link Click, Manual Page View, and Manual Impression.

Data Tag: Manual Link Click
Tagging Function: cmCreateManualLinkClickTag()
Description: This Data Tag captures links clicks which are not automatically tracked. Examples include,

  • Links without HREF="" attributes or which otherwise use JavaScript to create navigation at time of click.
  • Flash, Silverlight or other interactive application elements without HTML anchors.

Mappings: Use the Mapping toolkit to map the Manual Link Click/Page View/Impression destination variables:

  • Manual Link HREF (hr) - href value of the link clicked
  • Manual Link Name (nm) - name of the link clicked
  • Manual Link Page ID (pi) - unique alphanumeric value identifying the page

Data Tag: Manual Page View
Tagging Function: cmCreateManualPageviewTag()
Description: This Data Tag captures page view events that don't have a page load event (e.g. modal pop-ups, etc.).

  • Manual Page View Destination URL (ul) - the destination URL
  • Manual Page View Referring URL (rf) - the referring URL

Data Tag: Manual Impression
Tagging Function: cmCreateManualImpressionTag ()
Description: This Data Tag captures ad impressions from a certain feature like a display ad tag.

  • Manual Impression Page ID (pi) - the impression's Page ID matching the Link Page ID(pi)
  • Manual Impression Track Real Estate (cm_re) - Real Estate Impression with a valid cm_re= value: “version-_-area-_-link”
  • Manual Impression Track Site Promotion (cm_sp) - Site Promotion Impression with a valid cm_sp= value: “group-_-promotion-_-link”

Config Tab

This tab does not correspond to any Data Tag function. Instead, you can use it to dynamically set the Coremetrics Tag configuration settings connected to a Test site/environment.

  • Client ID (ClientID) - Coremetrics-assigned ID
  • Test Client ID (TestClientID) - test site's Client ID
  • Test Data Collection Method (TestDataCollectionMethod) - test site's Data Collection Method
  • Test Data Collection Domain (TestDataCollectionDomain) - test site's data collection domain

Order Data Tag

No mapping tab is available for this Data Tag. However, you must configure the E-commerce Extension in order to fire this function on a page. The Extension, if configured, automatically maps the _corder variable.

Data Tag: Order
Tagging Function: cmCreateOrderTag()
Description: This Data Tag captures the final order information such as Registration ID, order ID, order subtotal as well as shipping and handling. The function call should be sent on the Receipt/Thank-You page confirming the order completion. Only one Order function should be called per order. Anytime the Tealium E-Commerce extension order id variable (_corder) is populated, this function will run automatically.

 

Version history
Revision #:
4 of 4
Last update:
‎07-27-2016 06:24 PM
Updated by: