Integration & Setup

  1. Home
  2. Integration & Setup
  3. Settings & Accounts
  4. etracker Cookies
  5. Cookies used

Cookies used

Functional or required cookies

NamePurposeStorage durationTypeExample value
et_oi_v2Opt-In Cookie stores the visitor's decision when the tracking opt-in is played on the customer's page. Also used for an eventual opt-out."no" - 50 years
"yes" - 480 days
First-party, local storageyes, no|3138274773810
et_allow_cookiesWhen using data-block-cookies, this cookie is set to "1" by the API call _etracker.enableCookies() to indicate that etracker is allowed to set cookies. The cookie will be deleted when _etracker.disableCookies() is called."1" - 480 daysFirst-party, local storage1, 1|1612600938445
et_oipWhen using Signalize: Opt-in cookie for "Signalize". If the customer chooses "no", the cookie is set with the value "no" and a validity of 30 days. If the customer chooses "x" or presses the ESC key (no decision), the cookie is set with the value "no" for the validity of 1 day.
If the customer rejects the native browser dialog, the value "denied" is set for 30 days. If the customer agrees, the cookie is set with the value "yes" for 30 days. The values are updated based on the browser settings when the customer revisits the page.
If the customer agrees to the wallet opt-in, then the cookie is set with "yes" for 480 days.
If the customer does not make a decision, the cookie is set with the value "undefined" and a duration of 0 days.
"no" - 30 days

"no" (Session) 1 day

"yes" 480 days

"yes" 30 days

"denied" 30 days

"undefined" 0 days
First-party, local storageno, no|3123100800000
cntcookieExclusion from the count (list of account IDs).4 yearsThird-party1234%7C4567
et_scroll_depthData for the scroll depth measurementBrowser sessionSession storage{"foo":{"buckets":{"0":{"stayTime":954594,"to":9,"from":0},"10":{"stayTime":954594,"from":10,"to":24},"25":{"stayTime":0,"from":25,"to":49},"50":{"stayTime":0,"from":50,"to":74},"75":{"stayTime":0,"from":75,"to":100},"101":{"stayTime":0,"from":101,"to":1000000}},"tm":1561467961409,"lastBuckets":["0","10"]}}

Cookies set when cookies are activated

NamePurposeStorage durationTypeExample value
_et_coid Cookie recognition2 years or configurableFirst-party, local storage108bf9a85547edb1108bf9a85547edb1
isSdEnabledDetection of whether the scroll depth is measured for the visitor.24 hours First-partytrue
BT_sdcContains Base64-encoded data of the current visitor session (referrer, number of pages, number of seconds since the start of the session, smart messages displayed in the session), which is used for personalization purposes.Duration of the sessionFirst-party
eyJldF9jb2lkIjoiTkEiLCJy...DMzNTYzNzM

3LCJwaSI6NH0=
BT_pdcContains Base64 encoded visitor history data (is customer, newsletter recipient, visitor ID, smart messages displayed) for personalization.1 yearFirst-partyeyJldGNjX2N1c3QiOjAsImVj...GNjX25l

d3NsZXR0ZXIiOjB9
BT_eclContains a list of project IDs for which the visitor is excluded. This cookie is set by the web service if the client has configured that not all visitors are assigned to a test, but only to a certain fraction.30 days First-partyBT-6037799f213de9e9961facc224b69
signalizeIsSubscriber When using Signalize: Notes whether a visitor is also a Signalize subscriber. The entry is only set if this is the case. If the subscriber unsubscribes, the entry is deleted during the next PI.Until unsubscription*Local storagetrue
signalizeSubscriptionChecked When using Signalize: Prevents rechecking a subscription on every PI → reduces server requests. Set only if the visitor is a subscriber.Browser sessionSession storagetrue

*By means of a virtual expiration date (timestamp), no more data is read out after this point in time has been exceeded and the corresponding entry is removed.