Cookies
Exponea stores the following cookies in the browser:
Name | Description | Type | Expires |
|---|---|---|---|
| Customer's Exponea generated client-side cookie | first-party, client-side | 7 days - 3 years (depends on browser) |
| Customer's Exponea generated server-side cookie | first-party (for CTD) or third-party, server-side | 3 years |
| Timestamp offset between browser and server time | first-party, client side | 60 minutes |
| Variant name returned for an A/B test | first-party, client side | 7 days - 3 years (depends on browser) |
xnpe_{project-token} cookie is a server-side version of the __exponea_etc__ cookie. They will both hold the same value and in combination with custom tracking domain (CTD) and they help to keep the user's identity for browsers that have shorter expiration for client-side cookies such as Safari.
Local storage
Exponea stores the following data in Local storage:
Name | Description |
|---|---|
| Customer's last session ping |
| Customer's last session start |
| Timestamp of last showing of specific banner to the customer |
| Timestamp of last customer's interaction with specific banner |
Session storage
Exponea stores the following data in Session storage:
Name | Description |
|---|---|
| Customer's specific tracking definitions set up in Data Manager -> Automatic Web Tracking |
Exponea stores information about when the last session for the customer occurred to decide whether to track the page visit within the last session, or whether to track it as a new session.
The storage for ‘Experiment’ settings, to ensure that experiments are displayed within their defined policy setting, is also stored. This data has no expiration.
Under session storage the SDK settings for tracking are cached. This setting expires when the tab/browser is closed. IndexedDB, a JavaScript-based object-oriented database, can be a data storage for actions from browser push notifications. This data has no expiration. There is potentially PII in push notification messages.
Updated 5 months ago