When including the Xponent Web Tag use the SHA-384 integrity value from the above table when including the tag into your web site. This adds additional security to ensure that you are including the valid Xponent web tag and thwarts person-in-the-middle attacks.

<script src="https://cdn.kitewheel.com/kwTagV<VERSIONNUMBER>.js"
        integrity="sha384-<SHA-384-VALUE>"
        crossorigin="anonymous"></script>

You may also wish to consider using the “async” or “defer” attributes on the script tag to avoid blocking behavior.

webTagv6.1.js

• Added functionality to ignore unexpected events.

kwTagLatest.js

This is always the latest build of the Xponent Web Tag. Not recommended for production use - will migrate into an official version after final QA.

• Replaced jQuery with jQuery Slim to reduce size of JavaScript

• Replacement of jQuery Ajax call with JavaScript fetch() function

• Replacement of the UUID generating function with a more modern library

kwTagv6.js

• Removed fingerprint tracking

kwTagV5.1.js

• Added support for pages that only have WebComponents

kwTagV5.js

• Initial support for WebComponents

• Replaced jQuery with jQuery Slim to reduce size of JavaScript

• Replacement of jQuery Ajax call with JavaScript fetch() function

• Replacement of the UUID generating function with a more modern library

• Replace whitelist with allowList in _kw.options

kwTagV4.js

• The optional _kw.extras value can now be set to an object or a function - this supports the collection of dynamic data at the point an event occurs. One simple use case is to capture local or session storage from the browser.

• For example the following code can be added in the tag deployment to pass the values from local storage as part of the event that is posted to the Xponent Graph API in the “extras” value.
  _kw.extras = function() { return window.localStorage }

kwTagV3.js

• Removed the use of legacy Xponent function String.prototype.startsWith() as this is now supported by all modern browsers.

kwTagV2.js

• Includes a fix for cookie values that are large integers. Integer values that were larger than the JavaScript MAX_SAFE_INTEGER were being encoded in exponential format rather than as a full integer value. This was causing a problem with some tracking cookies.

kwTagV1.js

• The script name has been changed with this release from webTrack.v1.1.js to kwTagV<X>.js. Some browser security plugins have low quality matching mechanisms and we have seen the "webTrack" part of the script name cause it to be blocked from downloading. A new version of the script has been published as "kwTagV1.js" to avoid these name matching issues. 

• An event propagation issue - some modern websites can have problems with form submission and other JavaScript events. The "stopBodyPropagation" option is now included with the default as enabled set to "true" as this was the previous behaviour. If you are having issues you should set this to "false" and should also consider using the "noConflict" options as well for "trackForms" and "trackClicks". 

• Cookies created by Xponent are now set with the SameSite = Strict value to reinforce that this is a first party cookie and to avoid issues with ad-blockers and browser privacy settings.