Olark cookiesAll need consent
Olark sets 3 cookies we know of. Every one may only be set after the visitor opts in.
Reviewed · Provider: Olark
List of Olark cookies
hblidFunctionalConsent required2 yearsUnique visitor identifier set by Olark live chat. Used to recognise and connect returning visitors to their previous chat history.
olfskFunctionalConsent required2 yearsStores the Olark visitor fingerprint to help identify visitors across page loads.
wcsidFunctionalConsent requiredSessionSession identifier for the active Olark chat session.
How to handle Olark cookies
- 1Load it only after consent
Hold the Olark script until the visitor accepts functional cookies. Blocking the script is what stops the cookies; hiding them in a banner does not.
- 2Make Reject work
After a visitor rejects, none of the 3 consent-requiring cookies below may be set or kept.
- 3Name every cookie in your policy
List each cookie by name with its purpose, provider (Olark) and lifetime.
- 4Check the result, not the settings
Open your site in a private window, reject cookies, and look at what was stored. Or run a scan and compare the three stages.
Tools that help: tracking script blocker · Consent Mode v2 generator
Other vendorsAnd the cookies they set
Does Olark wait for consent on your site?Scan it in 2 minutes
Free scan · every cookie before consent, after Reject and after Accept