Create and Install Tagging Pixel
TryTagging allows you to create a custom Tagging Pixel, a modified version of the Google Tag Manager script. This pixel replaces the standard Google Tag Manager script (if you currently use it) and offers enhanced functionality. By loading the script directly from your server or a custom subdomain (e.g., tagging.domainname.nl) instead of googletagmanager.com, the Tagging Pixel ensures accurate traffic measurement on your website, even in the presence of third-party cookie blockers or AdBlockers.
This documentation will guide you through the process of creating and installing the Tagging Pixel for seamless integration with your site.
Prerequisites
Create Tagging Pixel
Install Tagging Pixel
Let’s get started 🚀
Before creating and installing your Tagging Pixel, ensure the following prerequisites are met:
You must have an active TryTagging account and access to the container where you want to generate the Tagging Pixel.
Ensure the domain name for your tagging pixel is correctly configured. If the "Domain Name" section displays the status as 'Done,' you can proceed. Otherwise, you need to configure the required CNAME record in your DNS settings.
Have the Google Tag Manager Web Container ID. This is necessary to establish communication between the server container and Google Tag Manager.
Ensure you have access to your website’s HTML or CMS backend to embed the tagging pixel code as part of the installation process.
To begin using the tagging pixel, you first need to create it within your platform. This step involves generating a pixel specific to your domain that can be used for tracking and data collection.
Once you’ve created the tagging pixel, the next step is to install it on your website. This involves embedding the pixel’s code into the appropriate sections of your site. The process may differ based on your CMS platform. In this demonstration, we will show the process for 'Custom' Platform.
It’s important to ensure that only the required Google Tag Manager (GTM) is installed on your website to avoid conflicts or duplicate data tracking. If multiple GTM containers are present, it can lead to inaccurate tracking and data redundancy. In this demonstration we will guide you to identify and verify if other GTM scripts are installed on your website.
When implementing analytics tracking, it’s important to ensure that no extra or duplicate collect events are being sent to the same GA4 property. Extra events can lead to inaccurate reporting and skewed data analysis. This guide will help you verify and troubleshoot collect events to maintain the integrity of your analytics setup
This documentation will guide you through the process of creating and installing the Tagging Pixel for seamless integration with your site.
Prerequisites
Create Tagging Pixel
Install Tagging Pixel
Let’s get started 🚀
Prerequisites
Before creating and installing your Tagging Pixel, ensure the following prerequisites are met:
You must have an active TryTagging account and access to the container where you want to generate the Tagging Pixel.
Ensure the domain name for your tagging pixel is correctly configured. If the "Domain Name" section displays the status as 'Done,' you can proceed. Otherwise, you need to configure the required CNAME record in your DNS settings.
Have the Google Tag Manager Web Container ID. This is necessary to establish communication between the server container and Google Tag Manager.
Ensure you have access to your website’s HTML or CMS backend to embed the tagging pixel code as part of the installation process.
Create Tagging Pixel
To begin using the tagging pixel, you first need to create it within your platform. This step involves generating a pixel specific to your domain that can be used for tracking and data collection.
Install Tagging Pixel
Once you’ve created the tagging pixel, the next step is to install it on your website. This involves embedding the pixel’s code into the appropriate sections of your site. The process may differ based on your CMS platform. In this demonstration, we will show the process for 'Custom' Platform.
How to Check for Other Google Tag Manager Installations
It’s important to ensure that only the required Google Tag Manager (GTM) is installed on your website to avoid conflicts or duplicate data tracking. If multiple GTM containers are present, it can lead to inaccurate tracking and data redundancy. In this demonstration we will guide you to identify and verify if other GTM scripts are installed on your website.
How to Check for Extra Collect Events in the Same GA4 Property
When implementing analytics tracking, it’s important to ensure that no extra or duplicate collect events are being sent to the same GA4 property. Extra events can lead to inaccurate reporting and skewed data analysis. This guide will help you verify and troubleshoot collect events to maintain the integrity of your analytics setup
Updated on: 06/01/2025
Thank you!