NeuTargetNeuTarget
Feature

Understand collection before choosing how to deploy

Website analytics can process personal data even when the tag does not use an analytics cookie. NeuTarget uses per-tab sessions, approximate network groups and optional declared customer digests. Customers decide collection conditions and notices for their audience and enabled integrations.

Why this matters for your business

Review pseudonymous identifiers, browser storage, event fields, retention and integration processing. The product supports collection decisions; compliance depends on the deployment and applicable requirements.

Visible browser storage

The current tag uses sessionStorage for per-tab session and campaign context. Cookieless does not mean storage-free.

Approximate network groups

IP and User-Agent information support approximate weekly groups. Raw IP is absent from the event-table schema, while operational access logs may retain it.

Processing responsibilities

Review the Privacy Policy and DPA for customer-instructed analytics and NeuTarget account administration. Pseudonymous visitor data can remain personal data.

Deployment-specific records

Request the current hosting, subprocessor, processing-region and transfer record before relying on a residency requirement.

Collection conditions

Control tag and integration loading through the applicable collection or consent flow. The product does not determine a universal lawful basis.

Evidence with its limits

Separate configured product controls from verified operational assurance, external audits or legal compliance. Review the evidence applicable to your deployment.

How it works

1

Choose the purposes and minimum event fields needed for your website.

2

Review the session, network-group and declared-customer identity definitions.

3

Keep direct identifiers, secrets and sensitive information out of event paths, campaign values and errors.

4

Load the tag and enabled integrations under your applicable collection conditions.

5

Use lifecycle and erasure status to understand retention, deletion and provider cancellation progress.

Frequently asked questions

Does installing NeuTarget make a site DPDP or GDPR compliant?

No. Review the applicable requirements against your actual purposes and collection conditions. Configure appropriate notices and retention, and assess the processing performed by each enabled provider. Product controls alone do not establish compliance.

Can visitor hashes be personal data?

Yes. Session, network-group and declared customer digests are pseudonymous identifiers; a hash alone does not make related activity anonymous.

Where is my deployment processed?

Ask for the current infrastructure and subprocessor record. This page does not promise a cloud, single-country processing or a completed transfer agreement for every provider.

Where should I start?

Review /legal/privacy, /legal/cookies, /legal/dpa and the developer collection instructions, then configure the website and integrations for your actual audience.

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.