Synerise SDK uses several different cookies that store customer data.
This cookie stores general information about the customer.
|host||The owner’s domain address|
|permUuid||A permanent UUID for the customer|
|uuid||A randomly generated customer UUID. This value cannot be used to identify a customer until they provide more information.|
|emailHash||If the customer provided an email address, the value is hashed and the hash is then used to compare email addresses provided during subsequent visits. If the email address changes, a new UUID is generated for the user.|
|user_hash||If the _ush cookie is set, the value is stored here. In the _ush key, you can keep the id of the customer logged in to the owner’s website. Thanks to this parameter, Synerise is able to link these two identifiers.|
|init||The time of the first page visit (time from the customer’s browser)|
|last||The time of the most recent page visit|
|current||The current time|
|uniqueVisits||The number of unique page visits|
|allVisits||The total number of all page visits|
This cookie stores information about the current session. Each session lasts 30 minutes.
|ssuid||A customer session ID|
|appear||The start time of the current session|
|sessionVisits||The number of page visits during this session|
This cookie stores information about the time when the customer left the page.
|ssuid||A customer session ID|
|leaves||The end time of the session|
This cookie stores the customer’s UUID (may differ between devices).
This cookie stores the customer’s permanent UUID.
The presence of this cookie turns on the SDK debug mode.
This cookie stores information about the time when a dynamic content campaign should stop displaying.
This cookie stores information about the number of views after which a dynamic content campaign will no longer be displayed.
This cookie stores information about the delay before showing a dynamic content campaign.
This cookie stores information about the delay before showing a notification.
This cookie stores information about the maximum number of times a notification is to be displayed.
Synerise local storage
Additionally, Synerise SDK uses several different local storage keys that store customer data.
This key stores information about the frequency of checking if a dynamic content campaign has expired.
This key stores page visit events that were not saved in Synerise (for example, due to temporary network failure).
This key stores information from submitted forms that has not been saved in Synerise (for example, due to temporary network failure).
This key stores the current status of the web push module.
|permission||Informs about the the browser’s notification permission setting|
|permissionSaved||Informs if the permission has been saved|
|subscription||Informs about the customer’s consent in Synerise to receive web-push notifications|
|subscriptionSaved||Informs if the subscription has been saved|
|tokenHash||The token for the current web-push status|
|tokenTime||Timeout for the token of the permissionSaved status. Permission saved will be set to false after the timeout.|
|uuid||The customer’s UUID|