Which cookies does Plumbr use?
In order to monitor user interactions and to offer to you the functionality of our product, Plumbr agents create cookies on the devices of the end users of the monitored web applications. Here’s a description of these cookies and how they work:
| Name | Purpose | When is it removed | Storage type and expiration |
|---|---|---|---|
| plumbr_session_tracker plumbr_session_tracker_XXXXX |
Tracks user sessions so that we would know how many user sessions the monitored application has. Cookie name can be unique per application. |
– | Persistent cookie, expiration period 30 minutes. |
| plumbr_user_tracker | Links together user interactions from the same user so that we would know how many unique users interact with the monitored application. | – | Persistent cookie, expiration period 10 years |
| plumbr-supported | Used for checking if the browser supports cookies. | Deleted right after cookie validation is finished. | Session cookie, localStorage |
| plumbr-tx-XXXXX | Temporarily stores Plumbr transaction identifier, while Plumbr javascript loads. | As soon as the Plumbr javascript code loads. | Session cookie |
| (deprecated)plmbr.usr.key | Old method of tracking users. | As soon as the Plumbr javascript code loads. | Persistent cookie, expiration period 10 years, localStorage |
| plmbr.latency | Used to estimate internet connection speed. | – | localStorage |
| plumbr_user_identity | Used by PLUMBR.setUserId API to check if user idendity has changed. | – | localStorage |
| plmbr.session.batch | Is used to store one number in order ensure that all Plumbr’s data is sent successfully. | – | Session cookie, sessionStorage |
| plumbr-redirect-backend | Used by backend agents to track redirects | – | Persistent cookie, expiration period 1 day |
Note that the default Browser agent configuration does not retain any personal data as defined by the EU General Data Protection Regulation (GDPR). For more information, see How do we collect and process personal data.
