--- title: "Dependencies" slug: "webtrends-tag-manager-dependencies" updated: 2024-06-13T20:53:29Z published: 2024-06-13T20:53:29Z --- > ## Documentation Index > Fetch the complete documentation index at: https://onpremises.webtrends.help/llms.txt > Use this file to discover all available pages before exploring further. # Dependencies ## Dependencies ### Tag Installer/App Extension Prior to installing the tag manager, any existing Webtrends tags must be **removed** from a tagged site. Having Tag Manager installed in parallel with the Tag Administrator or App Extension may cause code collisions which ultimately disables tracking. Refer to the link below for instructions on removing the existing **Webtrends Tag Installer** and **App Extension**. [https://onpremises.webtrends.help/docs/webtrends-sharepoint-tag-installer-removal](https://onpremises.webtrends.help/docs/webtrends-sharepoint-tag-installer-removal) ### Modern Site Collection The **Tag Manager** requires a dedicated **modern** site collection to host the *web part* and *configuration lists*. When creating the site, use the URL "webtrends-tag-manager". This may be installed at the root, e.g., https://yourdomain.sharepoint.com/**webtrends-tag-manager** Or this may be installed at a site collection level, e.g., https://yourdomain.sharepoint.com/sites/**webtrends-tag-manager** Note: This is **case-sensitive**. Creating a Modern Site: For more information about creating a modern site, please see the following: [Create a communication site in SharePoint Online](https://support.microsoft.com/en-us/office/create-a-communication-site-in-sharepoint-online-7fb44b20-a72f-4d2c-9173-fc8f59ba50eb) *When asked to choose a **site design**, select *Blank*. ### Deploy Permissions Users must have permission to upload a package to the tenant app catalog. If using the Tenant-Wide Tag Manager, the user will also need permissions to allow tenant-wide deployment and management of the tenant-wide-extensions list of the app catalog site. ### Installation Permissions Tag managers must have at least *Site Owner* on the **webtrends-tag-manager** site to install and edit the web part and configuration lists used for tracking. ### Site Inventory Permissions SharePoint Search must allow the display of Sites within the search results in order for them to appear in site inventory. Tag managers must have at least *Site Visitor* permissions on each site that requires tracking in order for the site to appear within the inventory results. ### Management Permissions Tag managers must have *Full Control* permissions on each site that requires tracking in order to install *User Custom Actions* required for tracking of classic pages. When using the tenant-wide deployment, modern pages do not require additional permissions . The Extension is deployed to all site automatically using SharePoint's tenant-wide-extensions list with permission granted from the app-catalog administrator. When using single-site deployment (optional in v3 and above), tag manager's must have *Full Control* permissions on each desired site (and subsite) in order to install the WT Tag Manager app. ### Tracking Permissions The **webtrends-tag-manager** site must be included within the search results of a tracked site. The *extension* and *user custom action* use a search query to locate the **webtrends-tag-manager** site to begin the rest of the tracking process. If the **webtrends-tag-manager** site is excluded from search results, the site will not be found and tracking will not continue. As of v3 and above, all users in the tenancy must have at least *Read* permissions to the **webtrends-tag-manager** site, the **WT Tag Manager - Site Tags** list, and the **WT Tag Manager - Tag Configuration** list for tracking to take place when visiting a tagged site. The **WT Tag Manager - Site Collections** list can be locked down to just managers of the **webtrends-tag-manager** site to hide potentially sensitive site details. Prior to v3, all users in the tenancy must have at least *Read* permissions to the **webtrends-tag-manager** site, the **WT Tag Manager - Site Collections** list, and the **WT Tag Manager - Tag Configuration** list for tracking to take place when visiting a tagged site. ### Classic Pages Tagging of Classic pages requires that *Allow Custom Scripting* be enabled to install the *User Custom Action* for **classic experience** pages. *Allow Custom Scripting* is now typically disabled by Microsoft in the tenancy by default. It should be possible to temporarily allow custom scripting to install the *User Custom Action* for tracking of classic pages and then disable the feature after installation is complete. Microsoft documentation states that [If you allowed custom script in the past, items that were already created will still work](https://docs.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script). **This is not officially tested.** --- #### Tagging Matrix | SharePoint Online | Classic Page | Modern Page | | --- | --- | --- | | **Classic Site** | Custom Scripting, Tag Manager | Tag Manager | | **Modern Site** | Custom Scripting, Tag Manager | Tag Manager | Note: To enable Custom Script, see [How to enable custom script in sharepoint online](https://www.sharepointdiary.com/2017/12/how-to-enable-custom-script-in-sharepoint-online.html) --- [Continue](https://onpremises.webtrends.help/docs/webtrends-tag-manager-deployment-and-installation)