Anonymous Analytics

This guide explains what Attriax means by anonymous analytics, when those counters appear, and how they relate to GDPR-style consent flows.

What anonymous analytics means

Anonymous analytics is not a second user model. It is a privacy-preserving reporting path for analytics-capable activity when normal identified delivery is not allowed.

  • These metrics cover sessions where policies like GDPR blocked analytics permission from being granted for the normal identified path.
  • Attriax can still count certain analytics-capable activity in aggregate when the integration and consent outcome allow that anonymous path.
  • Anonymous analytics should be read as trend visibility and product volume, not as a recoverable user identity ledger.

When teams see these numbers

The overview page surfaces anonymous counts so privacy-restricted traffic does not disappear completely from analytics review.

Consent denied

If analytics consent is denied after a pending phase, aggregate event volume can still land in the anonymous path when the runtime allows it.

Consent still pending

During a waiting state, GDPR-gated work stays local first. Whether anything later contributes anonymously depends on the final decision and SDK behavior.

Consent not required

If GDPR is not required, the runtime resumes the standard identified path and the traffic should no longer be interpreted as anonymous analytics.

How to use the metrics well

Anonymous analytics is most useful as an operations and product-reading tool, not as a substitute for identified lifecycle reporting.

  • Compare identified and anonymous traffic to understand how much of your product usage is passing through privacy-restricted consent paths.
  • Use it to QA onboarding, consent, and privacy-sheet changes after a release so teams can spot accidental analytics drop-offs quickly.
  • Do not interpret anonymous counts as proof of attribution eligibility, stable device identity, or user-level retention behavior.

Related guides

Anonymous analytics sits between the broader analytics workspace and the consent model that controls it.