Which cookies does CleverPush set?

The CleverPush script does not set cookies but works with LocalStorage and SessionStorage.

LocalStorage entries do not have a fixed term and remain in place until the user deletes their browser data.

The following entries can be set. Most of these are only set for registered subscribers and some only when using special features (e.g. tagging subscribers).

 

All technically necessary Local & Session Storage entries can also be set if the user does not accept or ignores the CleverPush Opt-In Consent. They are necessary for the functionality of the CleverPush script and prevent, for example, that the opt-in is played out several times per user.

 

Technology: SessionStorage
Description: Contains data about the current session
Runtime: Automatically empties after closing the browser tab

NameDescriptionCategoryExample value
cleverpush-alert-shown
Indicates whether the opt-in message has already been displayed to the user (to avoid multiple displays per session)Technically necessarytrue
cleverpush-confirm-alert-reported
Timestamp indicating when the opt-in message was last displayed (to avoid multiple displays per period)Technically necessary1633090547179

 

Technology: LocalStorage:
Description: Contains data that is also required beyond the current session
Term: Without a fixed term

NameDescriptionCategoryExample value
cleverpush-subscription-statusSubscription status, values: denied, allowed, unsubscribed, important for functionality so that the user is not asked again later after declining the opt-in.Technically necessarytrue
cleverpush-deny-time
Timestamp of opt-in rejection. Is used to offer the opt-in again after a definable time (frequency capping, e.g. 90 days).Technically necessary1633090547179
cleverpush-visitsNumber of page impressions (PIs) of a user, is used to display the opt-in only after a PI number has been reached. Is only set if the opt-in message has been configured with PI control.Technisch notwendig1
cleverpush-referrer
The user’s reference domain is only set if this is used in an opt-in filter (e.g. to not display the opt-in on certain reference domains).Technically necessaryhttps://google.com
cleverpush-subscription-idCleverPush subscription ID (only for registered subscribers)Technically necessary for subscribersXXXXXXXXXXXXX123
cleverpush-domain
CleverPush Domain through which the customer’s subdomain runs. This subdomain is used for the CleverPush iFrame. The iFrame is used to prevent double opt-ins if the customer uses multiple domains. Internal variable, important for functionality (only for registered subscribers)Technically necessary for subscribersmycleverpush.com
cleverpush-last-worker-versionVersion number of the currently installed ServiceWorker. Internal variable, important for functionality (only for registered subscribers)Technically necessary for subscribers1.0.0
cleverpush-last-sessionInformation on the current session: duration, visits (only for registered subscribers). Technically necessary for sending messages at the “optimal time”.Technically necessary for subscribers1633090547179
cleverpush-topicsIDs of the subscribed subject areas (checkboxes for opt-in) (only for registered subscribers if the “subject areas” function is used)Technically necessary for subscribers[“TOPIC_1″,”TOPIC_2”]
cleverpush-topics-versionVersion number of the subscribed subject areas, is used to synchronize the subjects with the backend (checkboxes for opt-in) (only for registered subscribers if the “subject areas” function is used)Technically necessary for subscribers1
cleverpush-tagsIDs of the subscribed tags (only for registered subscribers if “topic areas” function is used)Technically necessary for subscribers[“TAG_1″,”TAG_2”]
cleverpush-tag-datesLast assignment time of subscribed tags, can be used to create segments based on tag assignment time (only for registered subscribers if “topic areas” function is used)Technically necessary for subscribers{“TAG_1″:”2022-01-01T17:10:00.000Z”}
cleverpush-last-syncTime of the last synchronization of the subscription data with the CleverPush API. Internal variable, important for functionality (only for registered subscribers)Technically necessary for subscribers1633090547179
cleverpush-last-worker-updateTime of the last ServiceWorker update. Internal variable, important for functionality (only for registered subscribers)Technically necessary for subscribers1633090547179

 

Technology: IndexedDB:
Description: Contains data required in the ServiceWorker used for registered subscriptions. The ServiceWorker has no access to the LocalStorage, so separate storage is necessary here.
Term: Without a fixed term

NameDescriptionCategoryExample value
__dbnames.dbnamesIndexedDB Database names (contains only the word “cleverpush”). Is generated by the IndexedDB library “Dexie” used.Technically necessary for subscriberscleverpush
cleverpush.subscriptionCached subscription ID in the ServiceWorker, since it has no access to LocalStorage (only for registered subscribers)Technically necessary for subscribersXXXXXXXXXXXXX123

 

Start your free trial now

Non-binding test phase, ends automatically after 30 days