Installation of Triggerbee is done by adding the Triggerbee tracking code to your website. The tracking code is a JavaScript snippet that collects data from your website and is needed for Triggerbee to be able to display campaigns on the website. The tracking code only needs to be installed once.
Where can I find my Tracking Code?
You will find your tracking code in the Account Settings of your Triggerbee account. Click on the script to copy it.
How many codes do I need?
Each account in Triggerbee has its unique tracking code. So if you have multiple accounts in Triggerbee (eg. several domains) - you will need to implement one tracking code for each website.
How do I implement the code?
There are a couple of ways to implement the tracking code, provided that your eCommerce platform approves third-party scripts. Select what option fits you best below:
If you are not using any of the above tools - or just feel like installing manually - simply paste the tracking code before the closing </head> tag on your website.
Note: It's important to ensure that Triggerbee loads right after the cookie consent is granted, not after an extra page load. This will help ensure that Triggerbee starts tracking as soon as we have the necessary permissions.
What if I have a Single Page Application webpage?
Don't worry - we got you covered. To use Triggerbee on a SPA website, we recommend you implement Triggerbee with Google Tag Manager and follow the instructions in the article above. Other than that, you will need to activate the Single Page App feature in your Triggerbee account, which you will find in your Account Settings.
I have installed the code, but I don't see any data - why?
Once you have installed Triggerbee on your website, it might take a couple of minutes for the app to warm up and collect your data. Grab a coffee and check back in a while; we bet your data will be there when you return!
Triggerbee's impact on site performance and Core Web Vitals
Triggerbee uses two scripts on your site:
Tracking script injector (~5 KB)
Main client script (~50 KB)
Both are loaded asynchronously and make non–main-thread blocking requests, so they don’t affect rendering or page usability. In practice, the impact on load times is minimal (if any at all).
Once loaded, the scripts are cached in the browser and across multiple layers of cache, so returning visitors don’t need to re-download them.
Below you can see a Google PageSpeed test on a website running 5–10 campaigns at once. The test show that the combined setup results in ~84 KB of transfer size and about 30 ms of main-thread work. This is well below what would meaningfully impact performance.
Triggerbee also optimizes for efficiency by including only the features you actually use. If you don’t run a specific campaign type (for example, “Spin the Wheel”), that functionality isn’t loaded at all.
The only scenario where Triggerbee may influence your Core Web Vitals is with embedded campaigns placed in a container without a fixed height.
In those cases, the content may shift as the widget loads, affecting the CLS metric. To prevent this, set a fixed height equal to (or slightly larger than) the widget. This may leave a blank space for a split second, but it’s usually unnoticeable for visitors.
For perspective, here’s how Triggerbee compares to other tools in the market:
Optimonk: 170 KB
Wisepops: 69 KB
Sleeknote: 78 KB
Klaviyo: 69 KB
Triggerbee: ~55 KB (with 1–2 widgets live)