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 400 days. You can change this by using the cookieExpiration parameter. The value is the number of days after which the cookies expire.

Important:
  • If a browser’s cookie expiration limit is lower than your setting, your setting is ignored.
  • 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_params

This cookie stores all _snrs_ parameters attached to URLs (such parameters can be added to a link when a visitor to a website clicks a recommendation or dynamic content) for 3 days. If the visitor makes a transaction within this period, the _snrs_ parameters will be added to transaction events sent through JS SDK thanks to DataLayer integration.

_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_sdk_d

Special-purpose cookie for Synerise. It’s not created automatically. Expiry time is set when the cookie is created.

_snrs_uuid

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

_snrs_puuid

Deprecated.

This cookie stores the customer’s permanent UUID.

_snrs_cid

This cookie stores the ID of a DC campaign. Expires after a year.

_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_notify_delay

Deprecated.

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

_snrs_notify_capping

Deprecated.

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 local storage keys that store customer data.

_snrs_dc_delay

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

_snrs_dc_frq

This key stores information about the frequency of checking if a dynamic content campaign has expired. Cleared when browser data is cleared.

_snrs_dc_tests

This key stores an array of dynamic content variants if A/B testing was applied in dynamic content campaigns.

_snrs_profile_config

This is an object stored in browser’s localStorage. This object contains settings of the workspace from which the tracking code is implemented into the website. The objects store the following information:

Field Description
recognizeBy This key stores the name of the attribute based on which the visitor to the website is recognized when form tracking is enabled based on the JS SDK methods. Possible values: email and custom_identify. You can indicate this attribute in the Synerise platform.
profile This key is deprecated. Do not use it.
This key stored the subdomain (a random string of characters) generated automatically for the workspace when the workspace was created. This subdomain was used by JS SDK for integrating web push notifications.
dataMarker This key is deprecated for the new workspaces. Do not use it.
This key stores the configuration for form integration on the website. This key is available for old workspaces.
providers This object is required for notification integration (such as web push). Data in this object is necessary for communication between Synerise and Firebase.
signedIdentifiedActions This key contains an array of events which require JWT authentication as a result of JS SDK implementation.
notifications This key is deprecated.
This key contained an array of dynamic content campaigns that had been displayed to the visitors to the website.
cookieMatchers This key is deprecated.
This key contained the configuration that enabled cookie matching.
snrsProfileConfigExpire This key contains the time when the _snrs_profile_config object will be retrieved again.

synerise-traffic-storage

This is a JSON object that contains all requests sent from the website to a tracker. The data is stored in case of a network failure so the SDK can retry sending later. Cleared when browser data is cleared.

How does it work?

  1. JS SDK sends an event, for example page.visit.
  2. An entry is created with a randomly generated UUID (synerise-traffic-storage-UUID). This entry contains the request to API.
  3. If the request is successful (response 200), the entry with the request is removed. If the request cannot be executed (for example, due to temporary network failure), the request is kept in the entry and executed at the nearest opportunity.

synerise-traffic-storage-UUID

This key stores UUIDs under which requests from the website to a tracker are saved.

synerise-form-catch

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

snr-wp-state

This key stores the current status of the web push module. Cleared when browser data is cleared.

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. Cleared when browser data is cleared.

😕

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.

Close modal icon Placeholder alt for modal to satisfy link checker