What it is
A small record a site leaves in the browser: remember the language, keep you signed in, count visits. Analytics counters on our sites switch on only after the visitor agrees, hence the cookie notice.
How we use it
On the studio site a cookie stores the chosen language, the online store's admin panel has its own session cookie on a separate subdomain, and on the ยซะัั
ะฐะฝะธะต ะะพะฒะพะปะถััยป site analytics loads only after consent. The video downloader bot uses a cookies.txt file for restricted YouTube videos.
Where it helps a business
- A site should remember the chosen language instead of switching it again on every page.
- The owner signs into the admin panel and should not re-enter the password at every step.
- Analytics is needed, but the visitor should agree first.
How we use it
- Language. On the studio website the i18n module remembers the language choice in a cookie.
- Sign-in. The online store admin panel has its own session cookie on a separate subdomain that does not overlap with the storefront. In the finance assistant dashboard, signing in through a link from the bot gives the browser a cookie for 30 days; in the UNLOCK cabinet a session also lasts 30 days.
- Consent. On ยซะัั
ะฐะฝะธะต ะะพะฒะพะปะถััยป analytics loads only after cookie consent; on the studio site the notice and counter switch on only when a counter ID is set.
- A bot. The video downloader bot uses a cookies.txt file for age-restricted and private videos and YouTube's "Sign in to confirm" check; the file is uploaded through the admin panel, and the bot shows how fresh it is.
Common problems
- A counter before consent. Analytics that loads immediately is exactly what a cookie notice is meant to prevent.
- One cookie for everything. An admin session on the same address as the storefront mixes roles; a separate subdomain solves it.
When you do not need it
A static page with no analytics and no sign-in needs no cookies, and no cookie notice either.