Tealium Collect Tag Setup Guide

Tealium Collect Tag Setup Guide

by ‎02-25-2016 09:40 AM - edited ‎06-29-2017 10:22 PM (4,887 Views)

The Tealium Collect Tag is Tealium's primary data collection tag. You can leverage this 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 the 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.

Please contact your account manager to enable this functionality for your account.

This article describes how to add and configure the Tealium Collect Tag in your Tealium iQ profile.

Table of Contents Placeholder

Tag Configuration

Step 1: Add the Tag to your Tealium iQ profile

This Tag is available in the Tag Marketplace. Use the search toolbar or look in the Big Data Category and add this Tag. See Tags Tab to learn how to add a Tag.

Step 2: Configure the Tag Settings

  1. Title: The default is 'Tealium Collect'. You may leave it as is or replace with a unique name.
  2. Server (legacy ): You may leave this field blank.

    If the Tag was added prior to 03-03-2016, the server url is pre-populated. We recommend you leave it as is.

  3. Data Enrichment (required): Choose the frequency for enriching your Data Layer with AudienceStream data.
    • None (default): Keep this setting if you do NOT want the Attributes to be imported from your AudienceStream profile.
    • Infrequent: This will sporadically import the Attributes into the corresponding Data Layer, keeping the operating costs low.
    • Frequent: This will import the Attributes more frequently. NOTE: Frequent enrichment adds to the overall operating cost of the feature.


  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, please 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.
  8. Leave the Advanced Settings intact. Contact your Account Manager before you change any settings.
  9. Enter suitable notes for the Tag. This field is optional.
  10. Go to Load Rules Tab and apply the default 'All Pages' Rule.

Step 3: 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 Tag captures a mix of pre-defined data and dynamic data from the page. Read the EventStore Data Guide for more information.

Implementing with Mobile

For deployments using Tealium's Android & iOS integration libraries, note that the default Mobile Publish Settings already enable the direct Collect dispatch service.

If using the Collect Tag with Tag Management enabled for mobile, the Collect option should be toggled 'OFF', to prevent duplicate events.