After a Website has been created in AIUNIFY Analytics, you can continue adjusting how that Website collects and reports Analytics data from the Edit website screen.
Navigate to:
Websites → Select Website → Edit
The Website configuration allows you to control:
The available controls depend partly on the Website's Tracking Type and partly on the features available to your Analytics account.
The key principle is:
Tracking Type determines which capabilities the Website can use.
Website settings determine which available capabilities are turned on.
To configure an existing Website:
The Website actions menu provides Edit, Reset, and Delete.
The Edit Website screen contains the Website configuration and an Update button for saving changes.
The first setting is:
Name
This is the internal name used to identify the Website inside AIUNIFY Analytics.
You can change this name without changing the Website's Analytics Tracking Type.
Examples:
Use names that allow your team to quickly recognize the correct property.
The Edit Website form allows the Website Name to be updated directly.
The next setting is:
Website
This contains:
Available protocols are:
https://http://The Website address can represent a:
https://example.com
or
https://example.com/sales
Remember that the system states tracking operates for the domain, subdomain, or path defined in the Website configuration.
If the Website's domain or path changes, you can update it from Edit website.
Examples include:
Old
example.com
New
newexample.com
or:
Old
example.com/offer1
New
example.com/offer2
After changing the address:
Changing a Website address should always be followed by a tracking verification.
When Custom Domain functionality is available, the Website can be associated with a:
Custom domain
The Custom Domain determines the Analytics domain used for the Website's Tracking Code URL.
The Edit screen displays available Custom Domains when that feature is enabled.
The system describes Custom Domains as useful for using your own domain with Analytics tracking-code URLs.
A separate chapter later in this manual will explain Custom Domain management.
The Website's Tracking type is visible from the Edit screen.
It will display either:
However, the field is disabled.
You cannot change it from the Edit Website screen.
This confirms the rule established earlier:
Tracking Type is selected when the Website is created and cannot be changed later through normal Website settings.
The main Website collection switch is:
Tracking
This controls whether Analytics tracking is enabled or disabled for the entire Website.
The interface describes it as:
Enable or disable tracking of the website completely.
When Tracking is enabled:
For an operational Website where you want ongoing Analytics collection, this setting should normally remain enabled.
When Tracking is disabled:
This is useful when you want to pause collection without deleting the Website.
Examples include:
Do not confuse these three controls.
| ActionWebsite Kept?Existing Analytics Kept?New Collection | |||
| Disable Tracking | Yes | Yes | Stops |
| Reset | Yes | No / cleared | Can continue |
| Delete | No | No | Stops permanently |
If your goal is only to temporarily stop tracking, use Tracking rather than Reset or Delete.
The setting:
Track outbound clicks
controls whether Analytics records visitor clicks on links that lead outside the Website.
The application describes this as:
Enable or disable tracking for user clicks on links that go outside of the website.
Enable Track outbound clicks when you want to understand how visitors leave your Website through external links.
Examples include:
This data appears in the Outbound Clicks area of Analytics.
Suppose a Website contains:
Visit Partner Website
and that button sends users to:
partnercompany.com
With Outbound Click tracking enabled, Analytics can record that visitor interaction as an outbound event.
This helps answer questions such as:
For Advanced Tracking Websites, the Edit screen can include:
Track visitors events
This setting controls collection of supported detailed Website interactions.
The system identifies examples such as:
This control is only shown for Advanced Tracking Websites.
A Pageview answers:
Which page did the visitor open?
Visitor Events can help answer:
What did the visitor do after opening it?
For example:
Pageview
Visitor opens:
/pricing
Visitor Events
Visitor:
This provides a more detailed view of Website engagement.
Consider enabling Visitor Events when you need:
Availability: Visitor Events may depend on the limits or features available to your AIUNIFY Analytics account.
The Edit form checks account availability before enabling this control.
Advanced Tracking Websites may also contain:
Session replays
This controls visual Session Replay tracking.
The setting is only available when:
Session Replays can help when you want to visually investigate how visitors interact with the Website.
Use cases include:
Session Replay operation will be explained in dedicated chapters later in the manual.
Choosing Advanced Tracking does not automatically mean Session Replays are active.
Three conditions must align:
Advanced Tracking + Replay Feature Availability + Session Replays Enabled
If Replays are missing but other Analytics functions work, review these conditions before troubleshooting the Tracking Code itself.
When available, Website configuration includes:
Email Reports
The system describes this as receiving simple Analytics for the Website through email.
The Edit screen lets you enable or disable Email Reports after the Website has already been created.
Email Reports are useful when Website performance should be reviewed regularly without requiring the user to sign in for every summary.
Examples include:
Email Report availability depends on your Analytics account configuration.
The Website configuration includes a collapsible section:
Public statistics
When enabled, this allows overall Website statistics to be shared through a dedicated link.
The system describes the setting as:
Enabling this will allow you to share your overall statistics via a link.
To enable Public Statistics:
The Websites table only enables the Public Statistics button when this setting is active.
The configuration includes:
Public statistics password
This allows the shareable statistics page to be password protected.
The interface indicates that leaving the password empty disables password protection.
Below Public Statistics is:
Advanced
Expand this section to access additional Website collection controls.
These include:
The first Advanced control is:
Bot exclusion
The interface describes this as excluding widely known bots from tracking.
Examples named by the application include:
Website traffic can come from both:
Human visitors
and
Automated systems
Search crawlers and other automated agents can generate page requests that do not represent normal customer behavior.
Bot Exclusion helps keep reports more focused on visitor activity rather than recognized automated traffic.
Consider enabling it when you primarily care about:
Because bot-detection systems are not necessarily perfect, interpret Analytics as measured Website activity rather than an absolute census of every request.
The next setting is:
Track query parameters
When enabled, AIUNIFY Analytics includes URL query parameters in tracking instead of ignoring them.
A query parameter appears after a question mark in a URL.
Example:
example.com/page?campaign=summer
Consider these URLs:
example.com/pricing
example.com/pricing?source=email
example.com/pricing?source=facebook
When Query Parameter Tracking is enabled, those parameterized URLs can provide additional reporting detail.
This can be useful when query values identify:
Do not automatically enable this option for every Website.
Some Websites generate many unnecessary parameters.
For example:
example.com/product?id=10&session=abc123
If large numbers of constantly changing parameters are recorded, Pageview reporting can become fragmented.
Consider leaving query-parameter tracking disabled when parameters:
When available, Advanced Tracking Websites may contain:
IP tracking
The system recommends enabling IP storage only if appropriate user consent has been obtained.
The Edit form displays IP Tracking only when the Analytics system has that functionality enabled.
IP Tracking should only be enabled when your organization's privacy requirements and Website practices support doing so.
Potential operational uses can include:
Because IP information can have privacy implications, do not enable this simply because the option exists.
The next Advanced setting is:
Excluded IPs
This allows you to exclude specified IP addresses from being tracked.
The interface requires multiple IPs to be entered as comma-separated values.
Excluded IPs can be useful for preventing internal activity from influencing Website reports.
Examples include:
If employees repeatedly visit the Website while editing content, those Pageviews could inflate Analytics.
Excluding the organization's known applicable IP can help prevent those visits from appearing in collected Analytics.
Do not exclude an IP unless you are confident that its traffic should not be measured.
An IP address may sometimes represent:
Incorrect exclusions can remove legitimate visitor activity.
Review this list periodically.
Another Advanced Website setting is:
Session replays - Hide text selector
This lets you specify CSS selectors for text that should be hidden from Session Replays.
The system provides an example format similar to:
and describes the field as defining which text should be hidden.
Session Replays are designed to help you analyze Website behavior, but certain Website areas may contain information you do not want visible in recordings.
Examples could include:
The Hide Text Selector gives your implementation team a way to identify those elements using CSS selectors.
Suppose your Website contains:
A compatible selector could be:
If multiple elements need protection:
The exact selectors depend on your Website's own HTML and CSS structure.
If you are unsure which selectors to use, consult the person who manages your Website code.
A useful way to understand Website configuration is:
| SettingLightweightAdvanced | ||
| Tracking | Yes | Yes |
| Track Outbound Clicks | Yes, when available | Yes, when available |
| Visitor Events | No | Yes |
| Session Replays | No | Yes |
| Email Reports | Yes, when available | Yes, when available |
| Public Statistics | Yes | Yes |
| Bot Exclusion | Yes | Yes |
| Query Parameters | Yes | Yes |
| IP Tracking | Not presented in Lightweight configuration | Yes, when available |
| Excluded IPs | Available in Advanced settings | Available |
| Replay Hide Text Selector | Not useful without Replays | Yes |
The actual Edit Website interface conditionally displays Visitor Events and Replays only for Advanced Tracking Websites.
Even if a Website uses Advanced Tracking, some switches may be disabled because your account does not currently have access to the associated feature or usage capacity.
Examples include:
The Website edit form actively checks account limits before allowing those controls to be used.
Therefore, when a control appears disabled:
Do not immediately assume there is an error.
First review:
Most Website configuration changes do not require you to create a new Website or copy a new Tracking Code.
For example, you can change:
while keeping the Website record.
However, after major Website or tracking changes, it is still good practice to verify that Analytics is operating correctly.
After making your changes:
The actual Website configuration form ends with the Update action.
After updating, verify the Website from the Websites screen.
After modifying tracking behavior, perform a simple verification.
Check:
Realtime → Pageviews → Dashboard
Visit the Website, click a supported external link, then review:
Outbound Clicks
Interact with an Advanced Tracking Website and review the applicable Visitor/Session activity.
Generate a new Advanced Tracking Session and later review:
Replays
Return to:
Websites → Public Statistics
and confirm the shareable link behaves as intended.
A typical Lightweight Website might use:
Tracking
Enabled
Track Outbound Clicks
Enabled where useful
Email Reports
As needed
Public Statistics
According to sharing requirements
Bot Exclusion
Enabled when human traffic is the priority
Track Query Parameters
Only when useful
Excluded IPs
Configured for known internal traffic where appropriate
This creates a straightforward traffic-reporting configuration.
A typical Advanced Website focused on deeper behavioral Analytics might use:
Tracking
Enabled
Track Outbound Clicks
Enabled
Track Visitors Events
Enabled
Session Replays
Enabled where appropriate
Email Reports
As needed
Public Statistics
According to sharing requirements
Bot Exclusion
Enabled when appropriate
Track Query Parameters
Based on Website structure
IP Tracking
Only when appropriate
Excluded IPs
Configured carefully
Session Replays – Hide Text Selector
Configured wherever sensitive content should not appear
The actual settings should always reflect your Website's operational and privacy requirements.
When reviewing Website settings, verify:
These Website settings directly influence what you will see in later Analytics sections.
For example:
Tracking disabled
→ New Analytics collection stops.
Outbound Clicks disabled
→ New outbound-link activity is not collected through that feature.
Visitor Events disabled
→ Detailed supported visitor interactions are not collected through that setting.
Session Replays disabled
→ New Replay collection is not performed through that feature.
Query Parameters disabled
→ Parameters are ignored rather than tracked as configured.
Excluded IP added
→ Activity from that IP is excluded.
This is why Website configuration should be reviewed before interpreting an empty or incomplete report.
At this point, you have completed the core Website setup sequence:
Create Website → Choose Tracking Type → Connect Website → Manage Website → Configure Tracking Settings
You are now ready to begin working with the actual Analytics reporting interface.