Avanoo docs
Deployment

Identified and Pseudonymous modes

Choose the identity mode that best balances analytics and employee privacy.

Avanoo attributes browser activity to a real identity, or to a pseudonymous identifier that your organization controls. Both modes give accurate per-user analytics, groups, and reconciliation across browsers and devices. The difference is whether Avanoo receives the real identity.

The identity mode does not change what the extension collects. Organization settings control monitoring separately.

At a glance

IdentifiedPseudonymous
Identity sent to AvanooThe user’s real email addressThe Windows SID at the organization domain
Per-user analyticsAvailable under the real identityAvailable under the SID address
Groups and segmentsAvailableAvailable
Cross-device reconciliationAvailableAvailable
Employee privacyReal identities are visible in AvanooAvanoo stores the SID address and cannot resolve it without your directory
Main responsibilityKeep directory and access controls accurateKeep the organization domain stable; changing it re-keys every identity

In Pseudonymous mode, policy writes each user as <Windows SID>@<primary domain>.

Choose Identified when

  • your directory can provide each user’s email address;
  • administrators need to investigate activity by person;
  • groups are already managed in a directory or identity provider; and
  • your privacy policy allows Avanoo to receive real identities.

Choose Pseudonymous when

You need per-user and group analytics, and the link between an employee and their identity must stay on your side. Your directory is the only mapping from a SID to a person. Avanoo receives the SID address and any configured tags, never the directory.

Privacy responsibilities

For Identified deployments

Confirm that your organization may send real user identities to Avanoo. Limit directory membership and administrator access to the people who need it.

For Pseudonymous deployments

Your organization is responsible for:

  • writing the Windows SID at the organization domain;
  • controlling read access to the directory that maps a SID to a person;
  • keeping the organization domain stable, since changing it re-keys every identity; and
  • keeping tag paths broad enough that no group narrows to one person.

Tags are the most common leak. A tag path that applies to a few people identifies them by elimination, without resolving any SID. Apply tags to large groups only. Treat any breakdown that isolates a small team as identifying.

Anyone with read access to your directory can resolve a SID to a person: with Get-ADUser for an AD SID, or with the Entra object ID for a cloud SID. That is expected: the mapping stays under your control. Avanoo, and Avanoo users without directory access, cannot resolve it.

For all deployments

Document the mode, the reason for it, and the administrators who can change the policies. Review the mode when your privacy requirements, directory model, or analytics needs change.

What about Anonymous mode?

Anonymous mode attributes activity to a device signature only. It gives no per-user analytics, groups, cross-device reconciliation, or nudging. It is a legacy mode: do not choose it for a new deployment without confirming the use case with Avanoo.

Next steps

Choose a mode and explain it to stakeholders before you deploy. How a deployment works gives the order of operations. With platform access, your implementation team follows the Deployment section page for its console, in the tab for your mode.

See also What Avanoo collects and Hosting, security, and compliance.

On this page