Triggerbee can be installed via Google Tag Manager in two ways - with our GTM template or with an HTML tag.
Did you know that you can also log events and identification to Triggerbee with our GTM Event Template? Please check out this guide after installing Triggerbee.
Key features of the Triggerbee Tracking Template:
Easy script installation: Capture detailed visitor behavior, helping you monitor key actions and conversions.
Automatic duplicate script handling: The tracking template checks if the script is already loaded, and will not inject the script if it already finds another Triggerbee script on the website.
Easier multi-account setup: You can use custom GTM variables and lookup tables to assign dynamic site ID’s .
Data layer integration: You have the option to send a Triggerbee event to your data layer named “triggerbeeActive”. When the data layer event is sent, you can use it to fire other tags or perform other actions only when Triggerbee is active.
Detailed debugging: If you use GTM’s preview mode, our tracking template logs console messages for every step it performs to make it easier to debug any issues.
Install Triggerbee with the GTM Template (recommended)
Before proceeding with the installation guide, grab your Site ID from your Triggerbee Account under Account Settings.
In Google Tag Manager (GTM), go to Tags in the left menu. Create a new Tag by pressing New and give it a name, for instance, "Triggerbee Tracking".
Open Tag Configuration and go to the Template Gallery:
Search for Triggerbee and add the "Triggerbee Tracking" Template to your workspace
Add your Triggerbee Site ID (which you can fin in your Account Settings) to the template:
If you want to send an event to the data layer when the tracking script is fully injected, tick the checkbox that says "Send DataLayer event on successful script injection". The data layer event can be useful for both debugging or triggering other things that might rely on Triggerbee being active.
Then, open the "Triggering" box beneath the tag area and select the trigger "All Pages".
Note: If your webpage is built on SPA (single page application), please use the "Window Loaded" tag instead. You will also need to activate the SPA feature in your Account Settings for Triggerbee to load correctly.
Save your tag and make sure to publish your changes, then you're done!
Video tutorial
Install Triggerbee with a HTML tag
Before proceeding with the installation guide, grab your tracking code from your Triggerbee Account under Account Settings.
In Google Tag Manager (GTM), go to Tags in the left menu. Create a new Tag by pressing New and give it a name, for instance, "Triggerbee Tracking".
Open Tag Configuration and select Custom HTML as the tag type. Paste your tracking code in the HTML field.
Then, open the "Triggering" box beneath the tag area and select the trigger "All Pages".
Note 1: If your webpage is built on SPA (single page application), please use the "Window Loaded" tag instead. You will also need to activate the SPA feature in your Account Settings for Triggerbee to load correctly.
Save your tag and make sure to publish your changes, then you're done!
Troubleshooting GTM Setup
How to check if the GTM Tracking Template has been installed correctly
If you use GTM’s preview mode, our tracking template logs console messages for every step it performs to make it easier to debug any issues, here are some examples:
Example GTM console output for successful script injection:
Example GTM console output log of when the tag failed to fire:
"I can't see my visits in Triggerbee"
If you have finished the installation of Triggerbee in GTM, but can't see your visitors in Triggerbee, these are some possible reasons to double-check:
Make sure that you have published the tag from GTM to the website.
If you have multiple Triggerbee accounts, make sure you have added the correct tracking code. Each account in Triggerbee have their own unique ID (siteID)
Make sure you have selected the correct trigger for the tag. For instance, SPA websites should use the "Window loaded" trigger instead of "All Pages". If you have used custom triggers or added custom consent before loading the Triggerbee tag, double-check that the visitors can fulfill your requirements.
Lastly, if all the above looks correct, it might just be a cache issue. Go and grab a coffee and check back in a few minutes.