IMPORTANT: This Tag is now deprecated. Please use the utag.sync.js for implementing Optimizely Synchronous. We will continue to support existing instances of the Tag.


Tealium's Tag Marketplace offers two versions of the Optimizely Tag, one that loads on your page asynchronously, and one that loads synchronously. So which one to use?

 

  • Async: Loading a Tag asynchronously removes the risk of a Tag load failure breaking your site.
  • Sync: This version is best suited if avoiding content flicker is your primary concern. Keep in mind that any time you load something synchronously, you introduce the risk of breaking your site if the browser is unable to retrieve the element for some reason. Talk to your Account Manager for a custom solution if necessary. 

Prerequisites

  • Optimizely Account
  • Project ID

Adding the Tag

Tealium iQ's Tag marketplace offers a wide variety of Tags. Click here to learn how to add a Tag to your profile.

 

Configuring the Tag

Sync Tag config.png

  1. Title (Required): Enter a descriptive title to identify the Tag instance.
  2. Project ID (Required): Enter the numeric Project identifier provided to you by Optimizely.

Applying Load Rules

Load Rules determine when and where to load an instance of this Tag. The 'Load on All Pages' rule is the default Load Rule. To load this Tag on a specific page, create a new load rule with the relevant conditions.

Best Practice: We recommend loading this Tag on all your pages, so leave the 'Load on All Pages' load rule selected. Also, place the Optimizely Tag at the top of your Tag list on the Tags tab.

 

Setting up Mappings

Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag.

 

NOTE: If you plan to track E-Commerce data with the Optimizely Tag, we recommend that you use the E-Commerce Extension to automatically map that data.

 

For instructions on how to map to a Tag destination, please refer Mapping Data Source.  

Sync Tag mapping.png

 

  • Event Name for trackEvent (EVENT_NAME)

    Map the data source that identifies the event.

  • Event Value for trackEvent (EVENT_VALUE)

    Map the data source that identifies the value of the event.


 

Vendor Documentation

Version history
Revision #:
5 of 5
Last update:
‎07-08-2016 02:23 PM
Updated by: