Tealium Collect Tag Setup Guide

Tealium Collect Tag Setup Guide

by akshata_yerdoor on ‎02-25-2016 09:40 AM - edited on ‎09-06-2018 05:54 AM by (7,898 Views)

This article describes how to add and configure the Tealium Collect tag in your Tealium iQ profile. The Tealium Collect tag is Tealium's primary data collection tag.

In this article:

Table of Contents Placeholder

You can leverage the Collect tag for the following features:

  • AudienceStream and DataAccess
    The Collect tag provides AudienceStream with the data it needs to identify and take action on your audiences. The event data coming from the Collect tag can also be made available to DataAccess, where it can be analyzed using Business Intelligence (BI) tools of your choice.
    Read more about Live Events and how to capture this data.
  • Enrich your Data Layer
    Data Layer Enrichment uses the Collect tag to gather attributes from your AudienceStream profile and make them available in your data layer.
  • Reduce pixel requests
    With the Collect tag, you can use Tealium's Webhook connector to offload pixels from your website.

Contact your account manager to enable this functionality for your account.

Adding and Configuring the Collect Tag

Use the following steps to add the Collect tag to your TiQ and configure the settings for the tag:

  1. Add the Collect tag to your TiQ profile from the Tag Marketplace.
    To locate the tag, use the search toolbar or look in the Big Data category.
    See Tags tab to learn how to add a tag.
  2. Configure the tag settings, as follows:
    1. Title  The default is 'Tealium Collect'. You may leave it as is or replace with a unique name.
    2. Server (legacy Leave this field blank.
      If the Tag was added prior to 03-03-2016, the server URL is prepopulated. We recommend leaving this field as-is.
    3. Data Enrichment (required Choose the frequency for enriching your Data Layer with AudienceStream data.
      • None (default enrichment will not occur.
      • Infrequent  enrichment occurs once per visit/session.
      • Frequent  enrichment occurs on every page load.


    4. Tealium Profile (optional By default, this field is blank.
      You may use it to override the existing data collection endpoint i,e. the AudienceStream profile that receives data from your site(s).
    5. Data Source Key (optional– The unique identifier of the Data Source you are tracking through Universal Data Hub. You may leave this field blank for now.
    6. Data Collection Region (required This is the geographic location of the data collection servers. The default option is "Global" (recommended).
      If you are not sure what to choose, contact your Account Manager.
    7. Sampling Percent (optional For existing customers, the recommended value is 100% (default).
      For Free Trial or Demo users, this option allows large volume sites to run Tealium Collect data collection for a subset of visitors only.
  3. Leave the Advanced Settings intact.
    Contact your Account Manager before changing any settings.
  4. Enter descriptive notes for the tag.
    This field is optional.
  5. Go to the Load Rules tab and apply the default 'All Pages' rule.
  6. Save/Publish your profile.

Best Practices

  • Move the Collect tag to the bottom of the list of your tags so that it will run last. This allows it to gather all the other tag and extension information and send it to the server.
  • DO NOT add more than one instance of this tag in your profile.
  • Apply the default "All Pages" load rule to load this tag on all pages.
  • Make certain to use the latest utag.js template (see utag.js release notes).

Data Collected

The Collect tag captures a mix of predefined data and dynamic data from the page. Read the EventStore Data Guide for more information.

Implementing with Mobile

For deployments using Tealium's Android and iOS integration libraries, note the following:

  • The default Mobile Publish Settings enable the direct Collect dispatch service by default.
  • If using the Collect tag with Tag Management enabled for mobile, the Collect option should be toggled 'OFF', to prevent duplicate events.