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:

1: _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.
1: 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
2: mtr-consent{siteID} are cookies related to viewing the "Privacy & Cookie notification" and to given consents. Only applicable for accounts that has Triggerbee Consent activated.
Length: up to 2 years.
3: mtr_goal are cookies related to achieving click-goals such as purchase, logging in, or reading a page. Only stored during the session.
Length: session
3: triggerbee_widgets_state_{siteId} is a cookie that stores campaign targeting, eg. the number of pageviews for the current session and all checked audiences. Length: session
4: 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

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.

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