Tag Versions

Version 5.5.0 – due May 2021

This version featured the following improvements:

  • Lightweight – As part of our continual effort to trim down our tag and improve performance (both with download times and impact during execution), we’ve rewritten some parts of our tag and trimmed down others, reducing the footprint we have on the page.
  • New conversion function – WT.track – this uses the Beacon Tracking API where available for more reliable communication.
  • Groundwork for new integrations – we’ve done the tag-side changes for a new batch of integrations. Integration manager UI changes to follow.

 

Version 5.4.0 – March 2021

This version featured one key bugfix:

  • Accounts created with newer-format domains were not being picked up by the tag, and this was intefering with our ability to set cookies. We simplified the process in tag 5.4, looking at whichever domain we pick up using window.location.hostname, and stripping out the “www.” where found. This can be overwritten for people who’d prefer custom rules such as those who operate across multiple subdomains and want to share cookies throughout the journey.

 

Version 5.3.0 – August 2020

This version featured one key bugfix:

  • When looking up tests using WT.optimize.lookup, if multiple tests were on the page, there were times where the wrong test’s code would show up. While this didn’t affect test rendering, it did affect our ability to re-render changes. This fixed that problem.

 

Version 5.2.0 – June 2020

This version featured a few key upgrades.

  • The Optimize Build Framework was included as an option in the Tag Configurations UI, and is enabled for all customers. For advanced-editor tests, this allows users to navigate the preferred option of using the Optimize Build Framework to better manage all of their tests.
  • The tag contained an empty Data Layer by default. Data could more easily be pushed into here as a result.
  • The tag introduced a small handful of utility Helpers by default for all customers.

 

Version 5.1 – March 2019

As a layer of protection, Optimize relied on HTTP Referer headers to detect what page a user was on – something which is much more difficult to spoof for users on other domains trying to hijack your ideas. However, releases by browsers with Referrer-Policy headers where you can limit what information is transmitted in a HTTP header restricted our ability to accurately detect what page the user was on.

Version 5.1 saw us being able to use the more traditional location.href to collect this information instead, as collected automatically in our tag.

 

Version 5.0 – October 2018

This version was a port of the Webtrends Optimize 4.3 tag, with the removal of all Webtrends Infinity Analytics-related components as part of the split from Webtrends Inc.

Whilst the 4.x tags leveraged Akamai as the CDN provider, the 5.x tags have notably used Azure CDN as part of a user usage of Azure CDN for the entire product range.

This version of the tag was made available under https://c.webtrends-optimize.com/, where the former versions were available under https://c.webtrends.com/.

Beyond these differences and points, there was no change in functionality, namespaces, etc.

 

Versions earlier than 5.x

Webtrends Optimize was previously a product under the suite of Webtrends Inc. During this time, many tags were released, including versions 3.x and 4.x. The particulars of these tags will not be described in this help site.