Consent & visitor tracking — found from sitemap — Crobox

Cited by

Facts read from this source

• First party cookie Report an error

  “The cookie _crbx is a first party cookie, and will not be used outside of our client’s domain.”

• No cookies before consent Report an error

  “If your cookie policy requires explicit consent (the setting “Opt-in needed to persist visitor data” is turned on), Crobox sets no cookies at all before that consent is given.”

• Cookie default expiry Report an error

  “the _crbx cookie is set as a “persistent” cookie, which will expire after the set time by our client (default 180 days)”

• Cookie not marketing Report an error

  “It is then used for aggregated analytics & AB testing and to remember a given consent. It is in no way used for tracking or marketing purposes.”

• Cookie removal on revocation Report an error

  “If a visitor revokes consent, the _crbx cookie is removed.”

• Optout marker Report an error

  “Where explicit consent is not required, the cookie is instead reduced to a marker that records the opt-out itself, so that the choice survives into the visitor’s next visit; it no longer holds a profile identifier.”

• Temporary local storage Report an error

  “it is treated as temporary: it is reset and removed after 30 minutes of inactivity (configurable by our client)”

• Storage scope Report an error

  “It is scoped to a single domain, so this state is not shared between subdomains.”

• Prestorage contents Report an error

  “Before consent is given, this storage holds functional state only — such as the answers a visitor gave in a product finder, and messages or campaigns the visitor dismissed”

• Optin event Report an error

  “const crobox = window.crobox || []; crobox.push(crobox => crobox.optIn());”

• Optout event Report an error

  “const crobox = window.crobox || []; crobox.push(crobox => crobox.optOut());”

• Post consent persistence Report an error

  “Only events sent after the consent has been given are persisted (anonymously) for analytics purposes”

• Preconsent events not queued Report an error

  “Before consent is given these events still drive the functionality on the page, but they are not sent to Crobox, they are not queued, and they cannot be counted retroactively.”

• Profile id length Report an error

  “After the visitor accepts, it should appear immediately — no page refresh needed — holding a 22-character profile id.”

• Optout marker suffix Report an error

  “A value ending in |dnp means the visitor is recorded as opted out, and carries no profile id.”

Scores citing this record

• The CRO Consultant Consent & visitor tracking
• The Data Protection Officer Consent & visitor tracking
• The E-Commerce Manager Consent & visitor tracking
• The E-Commerce Manager Snippet performance & flicker
• The Growth Lead Consent & visitor tracking
• The Growth Lead Snippet performance & flicker
• The Product Engineer Consent & visitor tracking
• The Product Engineer Snippet performance & flicker
• The Skeptic Consent & visitor tracking
• The Skeptic Snippet performance & flicker