<script> element to your pages that points to the
webtrends.load.js JS file as part of the src attribute.
This is typically done by editing the master page.Note:
Master page editing is not recommended, due to the potential for reset or modification that can result in the loss of tracking.
Note that some pages utilize different master pages, and each would need to be identified and edited.
Inheritance can be broken so that sub sites do not receive the same master page as the parent site, and editing of their respective master pages would be required.
Manual tagging can also be accomplished via a Script Editor web part that inserts a
This web part would need to be added to all pages.
An alterantive option is to add appropriate JS to insert a
<script>element within a file that is already in use on the site, such as a branding script, e.g.
var s = document.createElement("script"); s.async = true; s.src = window.wt_sp_globals.baseTagUrl + "webtrends.load.js"; var s2 = document.getElementsByTagName("script"); s2.parentNode.insertBefore(s, s2);
- The associated files are located in the root of the .zip file for your convenience.
- Both minified (
.min) and full files are available for use.
- Full files are intended to allow customization for your particular environment with the help of consulting and
.minfiles are recommended.
You must configure the
webtrends.load.js file directly with the appropriate settings prior to uploading to your server for deployment.
- Ensure that the
- Ensure that the src properties for each plugin within the plugin section reference the proper desired file name (full or
- See Manual Configuration.
Manual tagging cannot be combined with the App/Add-in model on the same site. Implementing more than one tag will result in unreliable behavior up to and including loss of tracking.
The Webtrends SharePoint 2019 Modern View Extension cannot use the manual method of tagging due to the dependency lists created by the App/Add-in model.