What is the preferred Optimizely implementation?

Silver Contributor
Silver Contributor

It was suggested that we implement Optimizely using the utag.sync.js. After reading two Tealium community articles. It appears utag.sync.js works best with Adobe Test & Target. One article mentions the Optimizely tag to include the Optimizely JavaScript file. I see there are 2 Optimizely tags, one Sync and one Async.

Which method would provide the best Optimizely flicker free implementation, utag.sync.js, Optimizely (Sync), or Optimizely (Async)?

Second, we will be using Optimizely customTag and Optimizely addToSegment.

Traditionally they would be added using the following JavaScript.

window['optimizely'].push(["customTag", "article type", "sports"]);
optimizely.push(['addToSegment', 'segmentApiIdentifier', 'optionalSegmentValue']);
optimizely.push(['removeFromSegment', 'segmentApiIdentifier']);

What would be the best way to accomplish this using Tealium?


What is the preferred Optimizely implementation?

Employee Emeritus

If you are doing content replacement and flicker free is a critical factor for you, you'd want to maintain your current method rather than deploying the tag as you would other tags. This allows you to maintain utag.js' asynchronous loading which has a great benefit in allowing your other tags to remain async, and prioritizing your site's performance for the best possible user experience.

As for the second part, since the contents are dynamic, I'd probably run it via a preloader (assuming these are to run after the Optimizely's library has loaded). But I would need to take a closer look at your implementation, as well as the code snippet/implementation guide Optimizely provided you. If you need more assistance or want to talk discuss testing best practices in general, please don't hesitate to reach out to your Account Manager.

What is the preferred Optimizely implementation?

Tealium Employee