Tag Manager

Webeyez Script Implementation Guide

Overview

This guide explains how to implement the Webeyez script on your website using Google Tag Manager (GTM). It also covers the required Content Security Policy (CSP) updates when CSP is enabled.

Purpose

Implementing the Webeyez script allows your site to load the Webeyez tracking script across your pages through GTM, without requiring a direct hardcoded deployment in the site’s source code.

Prerequisites

Before starting, make sure the following are in place:

Access to your Google Tag Manager account and the correct container
The GTM container is already installed on the website
Permission to create and publish tags in GTM
Access to update your site’s Content Security Policy, if CSP is enforced

Implementation Summary

The implementation consists of two main steps:

Add the Webeyez script as a Custom HTML tag in Google Tag Manager
Whitelist the required Webeyez domains in your Content Security Policy, if applicable

Step 1: Add the Webeyez Script in Google Tag Manager

GTM Setup Instructions

Open the correct GTM container - In Google Tag Manager, open the container that is installed on your website. The guide notes that this should be the container added to the site’s <body>.
Create a new tag - From the Tags section, click New to create a new tag.
Select tag type - Choose Custom HTML as the tag type.
Paste the Webeyez snippet - Paste the Webeyez tag snippet into the Custom HTML field.
Set the trigger - Configure the trigger to fire on All Pages.
Save and publish - Save the new Webeyez tag and publish the GTM container. The guide specifically instructs saving the tag and publishing the container once the trigger is configured.

Step 2: Update Content Security Policy (CSP)

If your website uses a Content Security Policy, the required Webeyez domains must be whitelisted for the service to work correctly.

Required Allowlist Entries

Add the following domains to your CSP configuration:

*.webeyez.com
webeyez.blob.core.windows.net

In addition, the guide specifies the following frame-ancestors directive requirement:

Content-Security-Policy: frame-ancestors https://app.webeyez.com

Example CSP Reference

Your exact CSP structure will depend on your current policy, but the Webeyez-related entries should be included wherever relevant in your existing directives.

Example reference structure:

*.webeyez.com
webeyez.blob.core.windows.net
frame-ancestors https://app.webeyez.com

Validation Checklist

After publishing the tag, verify the implementation using the checklist below:

The Webeyez Custom HTML tag exists in GTM
The tag is triggered on all pages
The GTM container has been published
The Webeyez script loads successfully in the browser
No CSP errors related to Webeyez appear in the browser console
Webeyez data begins flowing as expected in the platform

Troubleshooting

Tag is not firing

Check that:

The correct GTM container was updated
The trigger is set to All Pages
The container was published, not just saved

Script is blocked