Here is a list of cookies we use to remember visitors' context. All of these cookies are first party
Expiration: 2 years
This is where we store various persistent data to make the experience of our visitors in line with our targeting.
Example: The campaigns the visitor has seen and converted, their A/B testing group, etc.
Expiration: 2 years
Persistent cookie where the last 10 visits dates are stored.
This is to resolve conditions such as "Display to the visitors who came 5 times in the last month".
Expiration: 2 years
This persistent cookie stores the custom properties across sessions.
This is also a cookie for targeting resolution. For example: "Last purchase date is before 1 month ago".
Data is stored during the session and a maximum of 2 hours for targeting resolution.
Example: The initial referrer, the UTM parameters of the first page of the visit, etc.
|Technical session cookie used for exit-intent detection.|
|Analytics identifier that allows us to provide reports of your campaign's performances|
|1||First Party||Exitbee_vid||The unique visitor id. This cookie should be set only the first time someone visits a website.||180 days.|
The current visit id and visit created timestamp.
Each time this cookie expires, a request is sent to the api so that a new visit is created for the current visitor and its id is returned and set as the cookie value along with the visit created timestamp.
|Dynamic expiration. Depends on session definition. Currently set to 30mins|
|3||First Party||Exitbee_dailyCampaigns||The campaign ids the visitor has viewed today (the same id can appear as many times as the user viewed the corresponding campaign).||At midnight each day.|
|4||First Party||Exitbee_sessionCampaigns||The campaign ids the visitor has viewed during the current visit (the same id can appear as many times as the user viewed the corresponding campaign).||180 days. Is reset on every new visit|
|5||First Party||Exitbee_lifetimeCampaigns||The campaign ids the visitor has viewed so far since the beginning of time (the same id can appear as many times as the user viewed the corresponding campaign).||180 days.|
|6||First Party||Exitbee_viewedCampaigns||The campaign ids the visitor has viewed since the beginning of time (each id is unique)||180 days.|
|7||First Party||Exitbee_viewedOnCampaigns||The campaign ids the visitor has viewed since the beginning of time (each id is unique) along with the corresponding timestamp it was last seen||180 days.|
|8||First Party||Exitbee_closedCampaigns||The campaign ids the visitor has rejected since the beginning of time (each id is unique)||180 days.|
|9||First Party||Exitbee_convertedCampaigns||The campaign ids the visitor has converted since the beginning of time (each id is unique)||180 days.|
|Τhe campaigns that are allowed to load for this visitor, based on his history and campaign_on_pagesvisited setting|
180 days. Same as Exitbee_
visit_id (it's updated on new
|11||First Party||Exitbee_nrPagesVisited||The number of pages a user has viewed during the current visit. The pages are not unique, meaning it's value would eg increase on a refresh||180 days. Is reset on every new visit|
|12||First Party||Exitbee_source||The referrer of the current visit.||180 days. Is reset on every new visit|
Drupal does not need cookies in order to function (with the exception of back where logged in users exist).
3rd party (google analytics/tag manager , which we know of):
_ga ( Performance cookie from Google Analytics and it is used for the maintenance of statistical data of visitors. Duration: 2 years)
_gid (Necessary cookie that is used for the division of users in logged in and non-logged in. Duration: 24 hours)
_gat_UA-30321587-1 (Performance cookie that is used for the neutralization of request percentage, limiting the data collection in locations of high traffic. Duration: 1 minute)