Synerise cookies

Synerise SDK uses several different cookies that store customer data.

_snrs_p

This cookie stores general information about the customer.

Field Description
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

_snrs_sa

This cookie stores information about the current session. Each session lasts 30 minutes.

Field Description
ssuid A customer session ID
appear The start time of the current session
sessionVisits The number of page visits during this session

_snrs_sb

This cookie stores information about the time when the customer left the page.

Field Description
ssuid A customer session ID
leaves The end time of the session

_snrs_uuid

This cookie stores the customer’s UUID (may differ between devices).

_snrs_puuid

This cookie stores the customer’s permanent UUID.

_snrs_sdk_d

The presence of this cookie turns on the SDK debug mode.

_snrs_dc_sd_

This cookie stores information about the time when a dynamic content campaign should stop displaying.

_snrs_dc_views_sd_

This cookie stores information about the number of views after which a dynamic content campaign will no longer be displayed.

_snrs_dc_delay_

This cookie stores information about the delay before showing a dynamic content campaign.

_snrs_notify_delay_

This cookie stores information about the delay before showing a notification.

_snrs_notify_capping_

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.

_snrs_dc_frq_

This key stores information about the frequency of checking if a dynamic content campaign has expired.

synerise-traffic-storage

This key stores page visit events that were not saved in Synerise (for example, due to temporary network failure).

synerise-form-catch

This key stores information from submitted forms that has not been saved in Synerise (for example, due to temporary network failure).

snr-wp-state

This key stores the current status of the web push module.

Field Description
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
😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.