Triggerbee Cookies
Triggerbee uses a variety of cookies which are first-party cookies by default. Here's a complete list of all our cookies and their purpose:
- mtruid is the identifier cookie, creating a session between pageviews and connecting sessions over time. This article describes what type of data is stored in this cookie. Length: Up to 1 year.
- fpv{siteID} is a short cookie that keeps track of whether this is the first pageview of a visit—only stored during the session. Length: Session
- mtr-consent{siteID} are cookies related to viewing the "Privacy & Cookie notification" and to given consents. This is only applicable to accounts that have Triggerbee Consent activated. Length: Up to 2 years.
- mtr_goal are cookies related to achieving click-goals such as purchase, logging in, or reading a page and are only stored during the session. Length: Session
- triggerbee_widgets_state_{siteId} is a cookie that stores campaign targeting, eg. the number of page views for the current session and all checked audiences. Length: Session
- triggerbee_widgets_closed_{siteId} is a cookie that keeps track of all the campaigns that the visitor has closed, so he/she will not see them again. Length: Up to 1 year
- TiPMix Registers which server cluster is serving the visitor. This is used in connection with load balancing to optimize the user experience. Length: Session
- X-ms-routing-name Registers which server cluster is serving the visitor. This is used in connection with load balancing to optimize the user experience. Length: Session
- ARRAffinity is Used to distribute traffic to the website on several servers to optimize response times. Length: Session
- ARRAffinitySameSite is Used to distribute traffic to the website on several servers to optimize response times. Length: Session
Local- and sessionStorage
Apart from cookies, Triggerbee also stores some data in localStorage and sessionStorage.
- 1
-
mtr_p ("person") is localStorage and stores the identifier of the visitor (email) if such exists, together with goals and tags that can be used for campaign targeting. mtr_p is never removed.
- 1
-
mtr_v ("visit") is sessionStorage and stores tags, goals, landing page, and the number of page views of the visit. The mtr_v is also used to target Onsite Campaigns, but is deleted at the end of the current session.
Description of Triggerbee in Cookie Management Platform
If your Cookie Management Platform requires a description of the Triggerbee Cookies, you can add this:
Collects data about the visitor's source, navigation and interactions on the website to personalize the experience