Triggerbee uses a variety of cookies, which are first-party cookies by default. Below is a detailed list of cookies and storage technologies used by Triggerbee, along with their purpose and duration.
Note: Your visitors must approve all Essential Triggerbee cookies for Triggerbee to function correctly. The separation of the types of cookies here is only for easier understanding.
Essential Cookies
These cookies are always added and help us understand how visitors use the site and allow us to personalize content based on user behavior. Some of these cookies are necessary for basic website functionality, such as load balancing and remembering session state, and some are related to Triggerbee functions, such as remembering campaign interactions and visitor history.
Some of these are Local- and SessionStorage, which are not actually "cookies", but another type of technology that is used by Triggerbee to store non-essential but helpful information for personalization and campaign targeting.
Cookie Name | Purpose | Duration | Storage |
| Identifies the server cluster for load balancing | Session | Cookie |
| Ensures session stickiness across servers | Session | Cookie |
| Distributes traffic across multiple servers | Session | Cookie |
| Distributes traffic with SameSite policy | Session | Cookie |
| Unique visitor ID to link sessions and behavior over time | Up to 1 year | Cookie |
| Identifies the first pageview of a session | Session | Cookie |
| Tracks user goal completions (e.g., purchases, logins) with their name, eg. | Session | Cookie |
| Tracks campaign targeting data and page views | Session | Cookie |
| Remembers dismissed campaigns | Up to 1 year | Cookie |
| Stores user identifier (email), goals, and tags for personalization | Persistent | localStorage |
| Stores visit-specific data like tags, goals, landing page, and page views | Session | sessionStorage |
Contingent Cookies
These cookies are only used if their corresponding features are toggled on.
Cookie Name | Purpose | Duration | Storage |
| Stores information about exit intent behaviour, only present if Exit Intent trigger is used. | Session | localStorage |
| Stores consent status and cookie banner visibility. Only present when Triggerbee Cookie banner is used | Up to 2 years | Cookie |
| Stores user interest, only present when Content Dimensions is used. | Session | sessionStorage |
| Unique visitor ID to link sessions and behavior over time. Only present if Server Side Tracking is used. | Up to 1 year | Cookie |
Note: Depending on your usage in Triggerbee, other cookies might be created for custom targeting or tracking. One example of this is the mtr_slidingCookie* that is used for the Buying Intent Script. Talk to your Customer Success Manager or Triggerbee Support to find out if you have customized cookies.
Debug Cookie
The triggerbee_widgets_debug cookie can be used for troubleshooting. However, this cookie is mainly used by employees at Triggerbee and yourself, and not by your customers, and it is manually added whenever needed - so it does not require listing in your cookie policy.
Description of Triggerbee in the Cookie Management Platform
If your Cookie Management Platform requires a description of the Triggerbee Cookies, you can add this:
Long version
We use cookies from Triggerbee to understand how visitors interact with our website. These cookies help us personalize your experience, track important actions (such as purchases or logins), and remember your preferences across visits. Some cookies are essential for showing personalized campaigns and remembering if you’ve closed them. No personally identifiable information is stored unless you have actively shared it with us (e.g., via forms).
Short version
We use cookies from Triggerbee to personalize your experience and track how you interact with our site. Accepting these helps us show relevant campaigns and offers.