AIUNIFY Analytics provides several user-facing controls that affect how Website activity is collected, stored, excluded, or protected.
These include:
Privacy configuration should be treated as part of Website setup—not as an afterthought.
The core principle is:
Choose the Tracking Type → Configure only the data you need → Exclude traffic that should not be tracked → Protect sensitive Replay areas → Provide appropriate visitor controls → Review applicable privacy requirements
AIUNIFY provides technical controls for managing Analytics collection.
These controls do not determine whether a particular tracking configuration is legally appropriate for every Website, organization, visitor, or jurisdiction.
Your organization remains responsible for determining applicable:
This chapter explains what the software does, not what the law requires in every situation.
When a Website is created, AIUNIFY requires you to choose between:
This choice has major implications for Visitor identification and behavioral data.
The system also explicitly warns:
“The tracking type cannot be changed later on.”
Therefore, privacy requirements should be considered before creating the Website record.
AIUNIFY describes Advanced tracking as using:
This enables capabilities such as:
Advanced Tracking therefore provides the greatest behavioral detail.
The key difference is that Advanced Tracking can recognize the same Analytics Visitor across Website activity.
Conceptually:
First Visit
↓
Analytics Visitor Identifier
↓
Later Visit
↓
Same Visitor Record
↓
Sessions + Pageviews + Events + Goals + Replays
This is what makes individual Visitor Journeys possible.
AIUNIFY's own Advanced Tracking Help states that permission should be considered for this tracking mode.
This is particularly relevant when enabling additional features such as:
Your implementation should reflect the privacy rules applicable to your Website.
AIUNIFY describes Lightweight tracking as not using:
as part of its normal tracking model.
As a result, Lightweight Tracking cannot provide the same persistent Visitor relationship as Advanced Tracking.
Because Lightweight Tracking does not create the same persistent Visitor identity, you should not expect features such as:
Instead, Lightweight Tracking concentrates on less identity-oriented Website statistics such as:
The AIUNIFY interface itself describes Lightweight Tracking as designed around a privacy-focused model and makes specific regulatory claims in its internal Help text.
For this operations manual, the safer interpretation is:
Lightweight Tracking minimizes persistent Visitor identification, but each Website operator must still evaluate its own legal and privacy obligations.
Do not assume that selecting a particular Analytics mode automatically satisfies every privacy requirement applicable to your organization.
A simple comparison is:
| CapabilityAdvanced TrackingLightweight Tracking | ||
| Persistent Visitor identifier | Yes | No |
| Repeat Visitor association | Yes | No |
| Visitor history | Yes | No |
| Custom Parameters | Yes | No persistent Visitor model |
| Session Replays | Available | No |
| Heatmaps | Available | No |
| Visitor Events | Available | Reduced model |
| Pageviews | Yes | Yes |
| Goals | Yes | Yes |
| Outbound Clicks | Yes | Yes |
The actual availability of Advanced features also depends on account configuration.
Each Website has a setting labeled:
Tracking
AIUNIFY describes it as:
“Enable or disable tracking of the website completely.”
To access it:
Websites → Edit website → Tracking
This is the broadest Website-level tracking control.
When Tracking is disabled, AIUNIFY stops the Website's Analytics pixel from operating normally.
The tracking endpoint explicitly rejects disabled Websites.
Use this when you intentionally want to stop Analytics collection for the entire Website.
Disabling Tracking:
Deleting a Website is a separate and much more destructive action.
For Advanced Tracking, AIUNIFY can provide a Website setting labeled:
IP tracking
The Help text states:
“We recommend only enabling this if you got consent from your users to store their IPs.”
This option appears only when IP-storage functionality itself has been enabled for the Analytics platform.
The IP Tracking switch is specifically associated with the Advanced Tracking configuration in the Website form.
Lightweight Tracking does not expose the same persistent Visitor IP-storage option.
When Advanced Tracking initializes a Visitor, AIUNIFY checks whether:
Only when the applicable conditions are met does the Advanced Visitor record retain the actual IP value.
Otherwise, the stored IP representation is masked.
When actual IP storage is not allowed by the current configuration, the Advanced Visitor-processing logic replaces numeric portions of the IP with masking characters before storing it.
The interface can therefore show a masked representation such as:
**.***.***.*
instead of a full stored IP.
The source shows that the incoming IP can be used during Visitor initialization to determine geographic information such as:
while the value stored on the Visitor record depends on the Website's IP-storage configuration.
Therefore:
Using an IP during request processing
and:
storing the actual IP in the Visitor record
are not necessarily the same thing.
If your Analytics objectives can be achieved without storing actual Visitor IP addresses, leaving IP Tracking disabled reduces the amount of Visitor-identifying information retained in the Advanced Visitor record.
This is a practical data-minimization choice.
Your organization's specific requirements may differ.
Each Website provides:
Excluded IPs
The interface explains:
“Exclude IPs from being tracked. Comma separated values.”
This setting is located under:
Websites → Edit website → Advanced
Common uses include excluding traffic generated by:
This can help prevent internal activity from contaminating Website Analytics.
Enter multiple IP addresses as:
comma-separated values
For example:
The interface accepts the values in the Excluded IPs field and saves them as part of the Website configuration.
Before serving the Tracking Code, AIUNIFY compares the current request IP against the Website's Excluded IP list.
When there is a match, tracking is stopped.
The tracking-data endpoint performs the same type of exclusion check before accepting tracked activity.
This makes Excluded IPs different from a report filter.
A filter says:
Collect the data, but hide it from this report.
Excluded IP says:
Do not track this IP.
That distinction is important.
Unlike IP Storage, the Excluded IPs field is not limited to the Advanced Tracking portion of the Website form.
The Pixel itself checks the Website's Excluded IP list before selecting and executing the appropriate Tracking Type.
Therefore, Excluded IPs can protect Analytics quality for both:
After adding your current IP to Excluded IPs:
Remember that your public IP may change depending on your network or Internet provider.
AIUNIFY provides a built-in visitor:
Opt-Out
mechanism.
The Help documentation states:
“If you use our tracking services, we recommend providing users with the option to opt-out.”
This provides a Website-controlled way to let a browser stop participating in AIUNIFY tracking.
To trigger Opt-Out, add:
?pixel_optout=true
to a page on the Website that uses the AIUNIFY Tracking Code.
For example:
When a user activates the Opt-Out URL, AIUNIFY states that it:
sets a local storage variable to stop tracking.
That browser is then prevented from normal tracking while that Opt-Out state remains available.
There is an important distinction here.
Lightweight Tracking normally does not use local storage to create a persistent Visitor identifier.
However, the explicit Opt-Out mechanism itself uses local storage to remember that the browser requested tracking to stop.
So:
Lightweight visitor tracking does not depend on persistent local-storage identity
but:
Opt-Out uses local storage to remember the user's tracking preference.
The Opt-Out Help explicitly states that tracking can resume if the user:
Therefore, Opt-Out is not a permanent server-side identity blacklist.
It is remembered by the applicable browser storage.
A Website could provide a privacy link such as:
Disable Analytics Tracking
which directs to:
The browser receives the Opt-Out state and AIUNIFY tracking is stopped for that stored browser context.
How you present this option to Website users is your organization's decision.
These controls solve different problems.
Primarily visitor/browser controlled.
Stored in browser local storage.
Configured by the Website operator.
Stops tracking based on matching IP addresses.
Use the appropriate control for the intended purpose.
There is also a major difference between:
Stops tracking for the applicable browser context.
When disabled, stops Analytics tracking for the entire Website.
Do not disable Website Tracking merely because one visitor wants to opt out.
Session Replays provide significantly more detailed behavioral context than basic Pageview reporting.
AIUNIFY describes Session Recording as providing:
“Automatically hidden private details.”
In addition, Website operators are given a specific configuration field for hiding additional text.
Under Website Advanced settings, AIUNIFY provides:
Session replays - Hide text selector
The Help text explains:
“The CSS selector(s) that dictates which text should be hidden.”
This lets the Website operator identify elements whose text should not be readable in Replay collection.
The field expects CSS selectors.
The interface placeholder is:
Multiple selectors can therefore be entered using normal comma-separated CSS selector syntax.
Suppose an account page contains:
You could configure:
as a Hide Text Selector.
The intent is to keep the text associated with that selected element hidden from Session Replay presentation.
Suppose the page contains:
.account-number.private-message.billing-informationThe selector could conceptually be entered as:
Always test your selectors against the actual Website implementation.
Although the configuration field is stored with the Website, the Pixel only passes the Hide Text Selector into the Advanced Tracking Replay configuration when Session Replay functionality is enabled.
Therefore, the field is meaningful primarily when:
Before enabling Session Replays:
A selector that worked before a redesign may no longer match the new Website markup.
As covered in Chapter 21, Custom Parameters can attach Website-provided information such as:
to an Advanced Visitor record.
This can make Analytics far more operationally useful, but also increases the sensitivity of the Visitor record.
Do not send information merely because your Website has access to it.
Prefer the minimum data necessary for your Analytics use case.
For example, you may decide that:
provides enough context without also sending:
This is a recommended data-minimization practice.
Do not send:
through Custom Parameters.
Custom Parameters are Analytics context, not secure credential storage.
Advanced Tracking can also collect detailed Visitor Events when:
Track visitors events
is enabled.
The Website setting describes these as:
Consider whether your privacy disclosures appropriately reflect this level of behavioral measurement.
If you need Advanced Visitor history but do not need detailed interaction events:
This lets you reduce behavioral collection without necessarily disabling the entire Website's Analytics Tracking.
Likewise, you can use Advanced Tracking without enabling Session Replays.
To stop collecting new Replays:
Websites → Edit → Session replays → Off → Update
This preserves the rest of the Website's applicable Analytics functionality.
Instead of thinking only in terms of:
Tracking On
or:
Tracking Off
Advanced Tracking lets you make more specific decisions.
For example:
Advanced Tracking: On
Visitor Events: Off
Session Replays: Off
IP Tracking: Off
This provides persistent Visitor Analytics without enabling every available behavioral feature.
Under Website Advanced settings, AIUNIFY provides a control for:
Track query parameters
The system explains:
“Enabling this will allow query parameters to be tracked instead of ignored.”
URLs can sometimes contain information after ?.
For example:
or:
Those may be useful for Analytics.
However, some Websites may place sensitive or identifying information in query parameters.
Therefore, before enabling Query Parameter Tracking, understand what your Website places in its URLs.
As a general Website practice, avoid placing sensitive information in URLs or query parameters.
If your Website does so, enabling Query Parameter Tracking could increase the amount of that URL information represented in Analytics.
Review the Website implementation before enabling this setting.
The Advanced Website settings also contain:
Bot exclusion
described as:
“Exclude widely known bots from being tracked (e.g. Google Bot, Yahoo Bot , etc).”
This is primarily a data-quality control rather than a visitor-privacy feature.
However, it reduces unnecessary automated traffic in the Analytics dataset.
Website settings can optionally enable:
Public statistics
AIUNIFY describes this as:
“Enabling this will allow you to share your overall statistics via a link.”
Because this changes who may be able to see Analytics information, it should also be reviewed as part of your data-sharing posture.
AIUNIFY also provides a:
Public Statistics Password
for the Public Statistics page.
Use password protection when public access should be restricted to people who have the password.
Remember:
Visitor tracking privacy
and:
Analytics-report access
are separate security considerations.
AIUNIFY includes Help documentation for the browser:
Do Not Track
setting.
Historically, the system states that it honored the DNT browser setting.
However, that is no longer the current system behavior.
The current AIUNIFY source explicitly states that DNT functionality was removed in 2026 because the DNT standard is deprecated and not recommended.
The system now:
ignores the DNT header
and it:
does not affect tracking decisions.
This is an important current-behavior detail.
Because AIUNIFY currently ignores the DNT header, do not rely on a visitor's browser DNT setting as the AIUNIFY Opt-Out mechanism.
Instead, the explicit AIUNIFY Opt-Out mechanism is:
These should not be confused.
Currently ignored by AIUNIFY tracking.
Explicitly sets a local-storage state instructing the tracking system to stop tracking that browser context.
The second is the active user-facing mechanism documented by the current source.
Advanced Tracking normally uses local storage and unique identifiers to recognize returning Visitors.
The Opt-Out mechanism also uses local storage—but for the opposite purpose:
to remember that tracking should stop.
Understanding this distinction is important when describing AIUNIFY privacy behavior to Website visitors.
Because the Opt-Out preference is stored locally, clearing browser local storage can remove it.
AIUNIFY specifically warns that:
can re-enable tracking.
If your organization offers an Opt-Out link, this limitation should be understood when explaining how it works.
| ControlPurpose | |
| Lightweight Tracking | Reduce persistent Visitor identification |
| Advanced Tracking | Enable persistent Visitor analytics |
| Tracking | Enable/disable Website tracking entirely |
| IP Tracking | Control storage of actual Visitor IPs |
| Excluded IPs | Prevent selected IPs from being tracked |
| Track Visitor Events | Enable/disable detailed interaction events |
| Session Replays | Enable/disable visual Session recording |
| Hide Text Selector | Hide selected text from Replays |
| Query Parameter Tracking | Control whether URL query parameters are tracked |
| Custom Parameters | Attach Website-provided context to Visitors |
| Opt-Out | Let a browser stop AIUNIFY tracking |
| Public Statistics | Control public sharing of overall statistics |
| DNT | Currently ignored by AIUNIFY |
If you need Advanced Visitor Journeys but want to minimize collection, consider starting conservatively:
Advanced Tracking: Required for Visitor history
IP Tracking: Off unless needed
Visitor Events: Enable only if useful
Session Replays: Enable only if useful
Custom Parameters: Minimum necessary values
Query Parameters: Enable only after URL review
Excluded IPs: Add internal/testing traffic
Hide Text Selectors: Configure for sensitive Replay areas
Opt-Out: Make available according to your privacy approach
Then add additional collection only when there is a clear business need.
When persistent individual Visitor analysis is not needed:
Remember that Tracking Type cannot later be changed for the existing Website record.
To prevent your own organization from affecting Analytics:
AIUNIFY checks the Excluded IP list both when loading the Pixel and when receiving tracking requests.
Before enabling Session Replays:
Before deploying Custom Parameters:
If you added an Excluded IP but still see activity:
Excluded-IP matching is based on the IP seen by the AIUNIFY tracking request.
If you intended to disable actual IP storage:
Remember that existing historical records may have been collected under earlier settings.
Changing the current setting does not necessarily rewrite historical Visitor records.
If a visitor previously opted out but begins appearing again, determine whether they:
AIUNIFY explicitly states these conditions can re-enable tracking because the Opt-Out state is stored locally.
This is expected under the current system.
AIUNIFY states that DNT support was removed in 2026 and the DNT header is now ignored.
Use the explicit AIUNIFY Opt-Out mechanism instead when appropriate.
If text you intended to hide appears:
The setting controls text hiding through CSS selector(s).
Session Replays are an Advanced Tracking feature.
The Pixel only passes Replay configuration, including the Hide Text Selector, through its Advanced Tracking setup.
Therefore, Replay privacy selectors are not relevant to ordinary Lightweight Tracking.
Revisit Analytics privacy configuration after:
Privacy configuration should evolve with the Website.
A practical recurring review could include:
Before considering a Website's Analytics configuration complete, confirm:
AIUNIFY Analytics privacy controls can be understood as several layers:
Layer 1 — Tracking Model
Advanced
or
Lightweight
↓
Layer 2 — Website Tracking
Tracking On / Off
↓
Layer 3 — Data Collection Choices
IP Tracking
Visitor Events
Session Replays
Query Parameters
Custom Parameters
↓
Layer 4 — Exclusions
Excluded IPs
Visitor Opt-Out
↓
Layer 5 — Sensitive Data Protection
Replay Hide Text Selectors
Custom Parameter Minimization
↓
Layer 6 — Analytics Access
Team Access
Public Statistics / Password Protection
↓
Ongoing Privacy Review
You should now understand that AIUNIFY Analytics provides several separate privacy and tracking controls rather than one universal privacy switch.
Advanced Tracking uses local storage and persistent Visitor identifiers, while Lightweight Tracking avoids the same persistent identification model.
IP Tracking controls whether an Advanced Visitor's actual IP is retained, while Excluded IPs prevent specified IP addresses from being tracked at all.
The visitor Opt-Out mechanism uses:
?pixel_optout=true
and stores the preference in browser local storage; clearing that storage, changing browsers, or using Incognito can re-enable tracking.
For Session Replays, AIUNIFY provides both automatic privacy handling and a configurable:
Session replays - Hide text selector
for specified Website elements.
Finally, browser Do Not Track should not be treated as an active AIUNIFY privacy control: the current source states that DNT functionality was removed in 2026, and the DNT header is now ignored.
Most importantly:
Privacy should be configured according to the data you actually need—not simply according to every feature the system makes available.