Cookies and cookieless tracking
Attriboo's standard website tracker uses a first-party cookie and local storage to remember a browser. For daily pageview totals without browser storage or visitor identifiers, choose Cookieless in Settings → Privacy & data and publish the c.js code from Setup. Blocking cookies alone does not make this tracker cookieless, because local storage can retain the identifier.
Instructions reviewed
Browser records on a tracked website
Cookie expiry and local-storage lifetime are different. Deleting only the cookie can leave the ID in local storage, and the tracker can use that copy to create the cookie again. Browser exclusions are a reporting control; the tracker may create identifier storage before applying the exclusion, so they are not a replacement for consent controls.
| Record | Purpose | Lifetime |
|---|---|---|
| _atb_vid cookie | Recognizes a browser. Normally shared across the website's root domain and its subdomains. | Up to 365 days, refreshed on page load when the tracker runs; browsers may remove it sooner. |
| _atb_vid local storage | Keeps a copy of the browser ID on the current origin. | No built-in expiry. Remains until removed by the site, visitor or browser. |
| _atb_root test cookie | Finds the root domain that accepts a shared cookie when no domain override is supplied. | Set briefly and removed during detection; has a 10-second maximum age. |
| _atb_ignore cookie and local storage | Remembers a browser exclusion when the exclusion link is used. | Cookie: up to 365 days. Local storage: until removed. |
| _atb_cart session storage on Shopify | Avoids repeatedly tagging the cart with the same visitor ID in a tab. | The tab's session. |
First-party does not mean consent-free
First-party describes where a cookie is set. It does not establish a legal exemption. Cookie and similar-technology rules can cover local storage, link decoration and other device access too. Assess the actual purpose and applicable rules, including any narrow exemptions, before deciding whether consent is required.
The UK has a statistical-purposes exception with conditions. Do not assume visitor identification and payment-linked revenue attribution qualify just because they produce statistics. EU member-state rules and other countries' requirements also differ.
What cookieless would change
Cookieless is a description of a particular implementation, not a guarantee of anonymity or compliance. A tool that avoids persistent identifiers generally has less information for connecting a first visit to a sale weeks later. Other identifiers or device access still need their own privacy assessment.
Standard tracking uses t.js and a persistent browser ID. Cookieless tracking uses c.js and stores only a daily pageview total for the website, with no page paths, sources, unique visitors or identity links. Open the Cookieless report from Privacy & data to read those totals. Payment-provider connections can still send customer records separately. Switching modes does not erase earlier data: review existing storage and records, replace the old script, and keep one installation. In WordPress, choose the same measurement mode in the plugin settings. Disabling email capture or third-party cookies alone does not switch modes.
Attriboo's website has its own cookie choices
Cookie settings in Attriboo's footer controls optional analytics on Attriboo's own website. It does not configure consent on your separate website. Attriboo's own site also uses storage for requested functions such as sign-in, appearance and remembering cookie choices. Those records are listed in its Cookie Policy.
Still need a hand?
Send a question without needing to sign in.