9 docs tagged with "cookieless"

What you gain by measuring without consent — no data lost to banner rejection, far less for ad blockers to strip, no CMP to maintain, and cleaner attribution.

Why, on our self-assessment, Sealmetrics needs no consent banner for its own analytics (Germany is an open question) — no cookies, nothing stored on the device, a session identifier that rotates daily, and what exactly is recorded on each hit.

How Sealmetrics attributes traffic and conversions without User-IDs, cookies or cross-session tracking — last-click attribution read from the URL on every hit.

The mechanics of consentless tracking — a small set of non-identifying fields, isolated hits, a daily re-keyed session identifier, and EU-only aggregate storage.

How Sealmetrics measures your traffic — one script tag, a small set of non-identifying fields per hit, aggregate reports, and no consent banner for its own analytics (self-assessed).

Step-by-step guides to implement Sealmetrics cookieless tracking: pageviews, e-commerce conversions, SPAs, and content grouping — no consent banner for its own analytics (self-assessed).

How Sealmetrics measures without identifying anyone — a small set of non-identifying fields, nothing stored on the device, EU-only storage in Dublin — with the index of every privacy and security page.

What consentless analytics is, the small set of non-identifying fields Sealmetrics records, and why storing nothing on the device and nothing that identifies anyone means, on our self-assessment, no consent banner is required (in Germany an open question).

Sealmetrics needs no consent banner because it stores nothing on the visitor's device and no data that identifies anyone, and fits the audience-measurement exemption — the short version, as our self-assessment.