Synerise storage

Synerise SDK uses several different cookies that store customer data.

Cookies

Expiration time

By default, the _snrs_p, _snrs_uuid, and _snrs_puuid cookies expire after 30 years. You can change this by using the cookieExpiration parameter. The value is the number of days after which the cookies expire.

Note: The expiration time of the _snrs_sa and _snrs_sb cookies is 30 minutes and cannot be changed.

The following example sets cookie expiration time to 60 days:

SR.init({ 
    'trackerKey': 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
    'cookieExpiration': 60
});

_snrs_p

This cookie stores general information about the customer.

Field	Description
host	The owner’s domain address
~~permUuid~~	This field is deprecated. Do not use it.
uuid	A randomly generated customer UUID. This value cannot be used to identify a customer until they provide more information.
identityHash	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 customer.
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 is deprecated. 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.

_snrs_reset_uuid

This is a special purpose cookie that allows you to assign customer UUIDs.

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

snr-token

Stores the JSON Web Token used for customer authentication.