NeuTargetNeuTarget
Feature

Sessions and approximate visitor groups, with transparent browser storage

The current analytics SDK uses a random per-tab nonce and sessionStorage rather than an analytics cookie. The server also derives approximate weekly network/browser groups from IP and User-Agent information. Neither measure verifies a person, and privacy requirements depend on the actual processing.

Why this matters for your business

Measure website activity with a per-tab session and approximate weekly network groups. Optional site-scoped customer digests support declared identity; these data remain pseudonymous.

No analytics cookie in the current tag

Session and campaign context still use sessionStorage. Account sign-in and connected services have separate storage and cookie behavior.

Documented collection choices

Review notices and collection conditions for the tag and integrations. Cookie absence alone does not establish a consent exemption.

Optional declared identity

Use a permitted, site-scoped server-generated digest of an internal customer ID. Avoid globally hashing an email address or exposing the raw email to the browser.

Best-effort browser delivery

Network failures, blockers, consent settings and navigation can affect observed events. Critical financial confirmation uses a server receipt path.

Measurement definitions

Sessions, approximate network groups, declared customer IDs and paid orders are different measurements. Reports expose their evidence and limits.

Separate anonymous-network estimate

Weekly network/browser groups can combine different people on a shared network or split one person across environments. They are not exact visitor counts.

How it works

1

Load the tag only when your collection conditions are satisfied.

2

The current tag maintains per-tab session context with a thirty-minute inactivity window.

3

The server processes IP and User-Agent information for request handling, geographic enrichment and approximate weekly groups.

4

Raw IP is not a field in the analytics event table; operational logs can retain request metadata.

5

Supply an optional site-scoped customer digest only when your declared-identity use is permitted.

6

Interpret cohorts as declared customer-ID retention, not anonymous network groups or verified people.

Frequently asked questions

How are sessions different from visitors?

A current SDK session uses a per-tab nonce with thirty-minute inactivity expiry. Approximate weekly network/browser groups are separate. Storage restrictions and older tags can reduce continuity.

Can I link a signed-in customer across devices?

A consistent site-scoped customer digest can link declared activity where your collection conditions permit it. It is pseudonymous personal data, not independent proof of identity or consent.

Will every visitor be counted?

No. Consent settings, blockers, network failures, client restrictions and integration coverage can affect measurement. The product does not promise one-hundred-percent observation or identity accuracy.

What should my storage notice say?

Describe the current sessionStorage, identifiers, purposes and enabled providers. Review the Cookie and Browser Storage policy and your own requirements rather than copying a blanket no-consent claim.

Start with a 14-day analytics trial

Explore cookieless website analytics with limited NeuIntel usage. Paid revenue reporting and connected ad spend have separate plan requirements.