Back

The Tealium Collect tag is Tealium's primary data collection tag.

This article describes how to add and configure the Tealium Collect tag in your iQ Tag Management (TiQ) profile.

In this article:

Table of Contents Placeholder

Prerequisites

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

How it Works

The Collect tag captures a mix of predefined data and dynamic data from the page. For detailed information, see the EventStore Data Guide.

You can leverage the Collect tag for the following features:

  • AudienceStream, DataAccess, and EventStream
    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 EventStream connectors or Tealium's Webhook connector to offload pixels from your website.

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.
    To learn how to add a tag, see Tags.
  2. Configure the tag settings, as follows:
    • Title
      • The default is 'Tealium Collect'.
      • Leave as-is or replace with a unique name.
    • Server (legacy)
      • Leave this field blank.
      • If the Tag was added prior to 03-03-2016, the server URL is prepopulated.
      • Tealium recommends leaving this field as-is.
    • 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.

          data_enrichment_settings.png

    • Tealium Profile (optional)
      • By default, this field is blank.
      • Use to override the existing data collection endpoint, such as the AudienceStream profile that receives data from your site.
    • Data Source Key (optional)
      • The unique identifier of the data source you are tracking through Universal Data Hub.
      • Leave this field blank for now.
    • Data Collection Region (required)
      • 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.
    • 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 as-is.

    Contact your Account Manager before changing any of these settings.

  4. (Optional) Enter descriptive notes for the tag.
  5. Go to the Load Rules tab and apply the default 'All Pages' rule.
  6. Save/Publish your profile.

Best Practices

Apply the following best practices in your implementation:

  • Move the Collect tag to the bottom of the list of your tags so that it will run last. This allows the tag to gather all other tag and extension information and send it to the server.
  • Do not add more than one (1) instance of this tag in your profile.
  • Use the latest utag.js template. For more information, see Release Notes - utag.js.

Best Practices for Load Rules

A common best practice is to use the default "All Pages" load rule to load this tag on all pages. Applying this rule will reduce the number of events, which are limited only to link events in most implementations. In this scenario, applying the "All Pages" load rule stops the ability to end a trace because, in doing so, the kill_visitor_session event is triggered.

If you are using an event-based load rule, it must to contain the following OR clause:

Where ut.event equals (ignore case) kill_visitor_session, as shown the following example:

Kill Trace Event.png

Best Practices for 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 to 'OFF' to prevent duplicate events.
Tags (2)