Skip to main content

Benefits of Consentless Tracking

The practical case for consentless tracking is that we measure all the traffic you lose today to the cookie banner. Cookie-based analytics typically lose the visitors who reject or ignore the cookie banner — the range depends on sector, brand strength and traffic mix — because a tool that only fires after consent records nothing from visitors who decline. Sealmetrics does not depend on consent to record a visit, so there is no consent-shaped hole in the numbers.

Four benefits follow from having no cookies and no persistent identifiers.

No consent gap. Hits are measured regardless of whether a banner was accepted, what the browser's privacy settings are, or whether the visitor is in a private window. That removes the two most common distortions in EU reporting: missing traffic and the "dark traffic" that gets filed as Direct.

Much less for privacy tooling to block. Ad blockers and browser protections such as Safari's ITP target identifiers, third-party cookies and known tracking domains. Sealmetrics stores nothing on the device, keeps no persistent identifier and serves from its own domain, so measurement stays far more consistent across browsers and browser versions. A custom filter rule can still block it.

Cleaner attribution. UTM values are read when the visitor arrives, not after they interact with a banner, so a mid-journey consent acceptance cannot overwrite the original source. Attribution is last-click at channel level — the model that works without linking touchpoints to a person. Multi-touch attribution is not available for exactly that reason.

No consent machinery to run. No CMP, no Consent Mode v2 configuration, no cookie categorisation, no region-conditional GTM triggers, and no re-testing analytics every time the banner changes. The tracker is 1.1 KB gzipped, loads asynchronously and does not block rendering.

What is the trade-off?​

The trade-off is real and worth stating plainly: consentless measurement gives up user-level metrics. There are no unique visitors, no session duration, no cross-session journeys and no cohorts, because each of those requires a persistent identifier. See what the model can and cannot measure.

In short
  • Cookie-based analytics lose the visitors who reject or ignore the cookie banner depending on sector, brand strength and traffic mix; Sealmetrics does not depend on consent to record a visit.
  • No cookies and no persistent identifiers leave far less for ad blockers or Safari ITP to strip, no CMP or Consent Mode v2 to maintain, and UTMs read on arrival.
  • The trade-off: no unique visitors, session duration, cross-session journeys or cohorts — attribution is last-click at channel level.
Written and maintained by the Sealmetrics Team