Cookie mode vs cookieless
Lightweight Analytics lets you the site owner decide:
| Mode | How it works | Accuracy | Visitor privacy |
|---|---|---|---|
| Cookie | First page-view generates a random UUID and stores it in localStorage and a first-party cookie la_uid.Each subsequent hit includes visitorId → this lets our backend more accurately count unique visitors. |
Best – returning visitors recognised even months later; more reliable bounce & time-on-page. | Cookie is scoped to your domain, contains no PII, never shared, does no cross-site tracking. Purely for returning-visitor stats & fully GDPR/ePrivacy compliant when disclosed as "This site uses cookies". |
| Cookieless | Script skips identifier; backend deduplicates hits from same IP + UA for 30-minute session window. | Good but returning visitors on different days count as new, less accurate data. | Zero client-side storage – passes strict “no cookies” disclosure policies needed by you. |
Switch under Site → Settings → High Accuracy mode or add data-c_mode="false"
to the script tag. Takes effect immediately for new hits. Existing la_uid
cookie persists until it expires (1 year) or user clears it.
High Accuracy toggle
GDPR / ePrivacy
A legitimate-interest analytics cookie is legal in many EU countries but requirements differ. If in any doubt, or if accurate returning user counts is not important to you, use Cookieless mode.