Webtrends Tag Manager Enabling Tracking
  • 03 Dec 2021
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Webtrends Tag Manager Enabling Tracking

  • Dark
    Light
  • PDF

Enabling Tracking

Default vs. Custom Tag Configuration

Default

To automatically add tracking to all existing and new Modern pages in the tenancy, simply activate the Default tag.

See Creating Configurations > Creating the Default Tag

Note:

The Default Tag is only available when using the Tenant-Wide version of the Webtrends Tag Manager.

Note:

Classic experience pages cannot be tagged automatically with a default tag due to the requirement of installing a User Custom Action on the site collection.

Custom Tag

To apply a Custom Tag to individual site collections, and/or to enable tracking of Classic pages, apply a Custom Tag:

  1. Click the Site Collections tab.

  2. Select one or more sites in the list.
    image.png

  3. Click Tag Sites at the top.

  4. A Tag Selection form appears.
    image.png

  5. Choose the desired Custom Tag from the List

Note:

You may alternatively click Create New Tag to create a brand new Tag Configuration and automatically apply it to the selected sites.

  1. Click Apply Configuration to apply the selected tag to the selected site collections.
    image.png
Note:

In the Single-Site version of Webtrends Tag Manager, the application of a Custom Tag will install the Webtrends Tag Manager package onto the site collection and sub-sites directly, where it is visible in the Site Contents page of each site collection and sub-site.

It is recommended to only add/remove this using the Webtrends Tag Manager interface to avoid the Tag Manager and the site from becoming out of sync.

Note:

In the Single-Site version of Webtrends Tag Manager, the application of a Custom Tag will display a warning bar on the left side of the affected row(s).

Affected rows will be unselectable within the UI for 5 minutes, and display a warning to "Please wait 5 minutes before modifying highlighted site(s)." when hovered over.

Further interaction with the site within the 5 minutes can result in errors if the SharePoint Timer Job is still pending. This delay helps prevent unnecessary errors.

image.png

Note:

Classic experience tracking requires the installation of User Custom Actions on the site collection. Allow Custom Scripting must be enabled on the site collection to allow the installation of a UCA for classic pages.

Please see: Allow or prevent custom script

Continue


Was this article helpful?