Before AIUNIFY Analytics can collect and display Website activity, you must first create a Website inside your Analytics account.
A Website tells AIUNIFY Analytics:
The actual Add website form requires a Website Name and Website address, then provides the Tracking Type and available tracking controls.
The basic creation process is:
Websites → Add website → Enter Website Details → Choose Tracking Type → Configure Tracking → Review Optional Settings → Create → Install Tracking Code
Before beginning, make sure you know:
https:// or http://Most importantly, determine your Tracking Type before creating the Website.
As explained in Chapter 3, the interface warns that the Tracking Type cannot be changed later.
Website creation is available to the primary account user when the account has capacity to add another Website.
Two conditions can prevent Website creation.
If you are currently operating through shared Team access, the system does not allow you to create a Website from that Team context. It returns you to Websites with a no-access notification.
Your account may have a limit on the number of Websites that can be created.
If you have reached that limit:
The Website creation controller checks the account's Website limit before allowing creation.
Availability: The number of Websites you can create depends on the limits assigned to your AIUNIFY Analytics account.
To create a Website:
The Websites page describes itself as the place to view and manage all added Websites and provides the Add website action when your account can create another property.
The creation screen follows the breadcrumb:
Websites → Add website
The first field is:
Name
Enter a recognizable internal name for the Website.
Examples:
The Name is how the Website will be identified inside AIUNIFY Analytics.
It does not need to be identical to the domain name.
Both Name and Website are required fields.
Use a name that makes the property easy to recognize if you eventually track several Websites.
For example, instead of:
Website 1
use:
AIUNIFY Corporate Site
or:
Insurance Campaign Landing Page
The next field is:
Website
The Website field consists of:
Available protocols are:
https://http://For most modern secure Websites, select:
https://
Then enter the Website address.
For example:
example.com
Do not unnecessarily repeat the protocol inside the Website field because the protocol is selected separately.
The Website configuration can be associated with a specific:
The interface states that tracking only works on the domain, subdomain, or path specified for that Website.
Examples include:
example.com
shop.example.com
example.com/store
This is important when your business operates multiple Website properties.
If you create Analytics for:
example.com/store
do not assume that the same Website configuration automatically represents unrelated domains or paths outside the configured property.
If Custom Domains are available to your account, an additional field appears:
Custom domain
This field determines the domain used for the Analytics Tracking Code URL.
The Website form only displays this selector when compatible Custom Domains are available.
The interface describes this option as useful for using a Custom Domain for the tracking-code URL.
If you do not see Custom domain, continue with the standard Analytics domain provided by the system.
Custom Domains will be covered in detail later in this manual.
The next field is:
Tracking type
You must choose:
or
The form uses these exact options and dynamically adjusts other settings depending on which mode you select.
Choose Lightweight when you want a simpler privacy-focused configuration without persistent visitor identifiers.
Choose Advanced when you need capabilities such as:
Important: The Tracking Type cannot be changed later through the normal Website configuration. Make this decision before clicking Create.
When you change Tracking type, AIUNIFY Analytics automatically changes the form to show or hide settings associated with the selected mode.
When Lightweight tracking is selected, Advanced-only controls are hidden.
When Advanced tracking is selected, the Advanced-compatible controls are displayed.
You do not need to reload the page.
This behavior helps prevent you from configuring functionality that is incompatible with the selected Tracking Type.
The next switch is:
Tracking
This setting enables or disables tracking for the Website.
The interface describes the setting as:
Enable or disable tracking of the website completely.
AIUNIFY Analytics can collect supported activity after the Tracking Code has been installed.
The Website remains in your Analytics account, but Website tracking is disabled.
For most new installations, leave Tracking enabled unless you intentionally want to create the Website configuration before beginning collection.
The next available control is:
Track outbound clicks
This setting records supported clicks on links that take visitors outside the Website.
Examples include clicks to:
The interface describes this control as enabling or disabling tracking for user clicks on links that go outside the Website.
Outbound Click tracking is not limited to the Advanced Tracking form section, although account feature limits may determine whether the switch is available.
Enable it if outbound Website behavior is important to your Analytics strategy.
If Advanced tracking is selected, an additional control can appear:
Track visitors events
This records supported visitor interactions such as:
Visitor Events provide considerably more behavioral detail than Pageviews alone.
A Pageview may tell you:
A visitor loaded your pricing page.
Visitor Events can provide additional information about interactions occurring while that visitor is using the page.
This capability becomes important when analyzing detailed visitor behavior and Session activity.
Availability: Visitor Event tracking may depend on the usage/features available to your account.
When Advanced tracking is selected and Session Replay functionality is available, the form can display:
Session replays
Enable this setting if you want AIUNIFY Analytics to collect the supported activity required for visual Session Replays.
The form checks both:
before making the control available.
Session Replays will be covered in dedicated chapters later in this manual.
When Email Reports are enabled for the system and available to your account, the Website form provides an Email Report switch.
The interface describes Email Reports as providing simple Website Analytics through email.
Enable this option if you want Analytics summaries for the Website delivered through email.
If the feature is unavailable for your account, the option may be:
The creation screen checks account availability before allowing Email Reports to be enabled.
The Add Website screen contains a collapsible section labeled:
Public statistics
Open this section if you want to make overall Website statistics accessible through a shareable Analytics link.
The system describes Public Statistics as allowing you to share overall statistics through a link.
To enable it:
The creation form contains both the enable switch and the optional password field.
When using Public Statistics, you can enter a password for the public statistics page.
The system allows a password of up to 64 characters in the creation form.
The interface guidance states that leaving the password field empty disables password protection.
Therefore:
Public Statistics ON + Password entered
→ statistics page can be password protected.
Public Statistics ON + Password left blank
→ no Public Statistics password is configured.
Security recommendation: If Website Analytics should only be shared with selected people, configure appropriate protection rather than exposing the statistics publicly without restriction.
The Website creation form contains another collapsible section labeled:
Advanced
Expand this section to access additional tracking controls.
The available Advanced settings include:
These settings are optional and should be configured according to how you want the Website's Analytics data collected.
The first Advanced option is:
Bot exclusion
When enabled, AIUNIFY Analytics attempts to exclude widely known bots from tracking.
The application gives examples such as:
Automated bots can generate Website activity that is not equivalent to real human visitor behavior.
Excluding known bots can help keep Analytics reports focused more closely on actual visitor activity.
Enable this option when that matches your reporting requirements.
The next Advanced control is:
Track query parameters
URL query parameters are the values that can appear after a ? in a Website URL.
For example:
example.com/page?source=email
When Track query parameters is enabled, Analytics can retain query parameters instead of ignoring them.
If IP Tracking has been enabled for AIUNIFY Analytics, an additional switch may appear:
IP tracking
This control is associated with Advanced Tracking in the Website creation form.
The interface specifically recommends only enabling IP Tracking if you have obtained the appropriate consent from your users to store IP information.
If the setting does not appear, IP Tracking is not currently available for that configuration.
The Advanced section contains:
Excluded IPs
Use this field to specify IP addresses you do not want Analytics to track.
Enter multiple IP addresses as comma-separated values.
This can be useful for excluding traffic generated by:
when you know their applicable IP addresses.
192.0.2.10,192.0.2.25
Use this field carefully. An incorrectly excluded IP may remove legitimate Website activity from your Analytics data.
The Advanced section also provides:
Session replays - Hide text selector
This field allows you to enter CSS selectors identifying Website text that should be hidden in Session Replays.
The interface provides an example format similar to:
.custom-class,.another-custom-class
and states that the CSS selectors determine which text should be hidden.
You may enter multiple selectors separated by commas.
This setting is particularly important when certain Website content should not appear in Replay data.
Depending on your Website structure, you could use selectors to hide areas containing:
Your selector must correspond to actual CSS selectors used on your Website.
Before clicking Create, review the complete configuration.
Confirm:
If using Advanced Tracking:
This review is especially important because Tracking Type cannot be changed later through the normal Website settings.
After reviewing the configuration:
The form's final action is explicitly labeled Create.
AIUNIFY Analytics then validates the Website information.
The source confirms that Name and Website are required, and it also checks whether the entered Website/domain is allowed.
After successful Website creation, AIUNIFY Analytics:
The application generates a unique tracking/pixel key when the Website is created and redirects back to Websites with the tracking-code modal requested.
This is the transition from:
Website Configuration
to:
Tracking Code Installation
Each created Website receives its own unique Tracking Code identifier.
This identifier is associated with that specific Website configuration.
Do not assume that a Tracking Code copied from one Analytics Website should be installed on another unrelated Website.
When managing multiple properties, always obtain the Tracking Code from the correct Website record.
If creation does not complete, review the form for errors.
Potential source-supported causes include:
The Name field is required.
The Website field is required.
Your account has reached its available Website limit.
Website creation is not permitted while operating under the Team context shown in the source.
The application can reject a Website if its domain appears on the system's blacklisted-domain configuration.
Correct the indicated issue and submit the form again.
You may notice that certain controls are visible but disabled.
For example, the Add Website form checks account-level availability for:
A disabled switch does not necessarily indicate a malfunction.
It generally means that the associated functionality is not currently available under your Analytics account configuration.
Throughout this manual, these features will be marked as conditional where appropriate.
For a straightforward Lightweight Analytics setup, a typical starting configuration might focus on:
Name
Your recognizable Website name
Website
Correct domain or path
Tracking Type
Lightweight tracking
Tracking
Enabled
Track Outbound Clicks
Enabled if external-link activity is important
Email Reports
According to preference and availability
Bot Exclusion
According to reporting preference
Track Query Parameters
According to Website structure
Excluded IPs
Add internal IPs when appropriate
This provides a clean starting point without Advanced Visitor tracking.
For a Website where deeper behavioral Analytics is required, the starting configuration may include:
Name
Your recognizable Website name
Website
Correct domain or path
Tracking Type
Advanced tracking
Tracking
Enabled
Track Outbound Clicks
Enabled where useful
Track Visitors Events
Enabled when detailed interactions are needed
Session Replays
Enabled when available and appropriate
Email Reports
According to preference
Bot Exclusion
According to reporting needs
Track Query Parameters
According to Website structure
IP Tracking
Only when appropriate and available
Excluded IPs
Configured for traffic that should not be measured
Session Replays – Hide Text Selector
Configured when Website content should be hidden from recordings
These are recommendations for how to think through the form—not requirements. Your configuration should match your organization's actual Analytics, privacy, and operational needs.
Creating the Website prepares the property inside AIUNIFY Analytics, but creating the Website does not by itself begin collecting Website traffic.
The correct Tracking Code must still be installed on the Website.
Once the Website has been successfully created, the system surfaces the Tracking Code installation workflow.
That installation step is important enough to have its own chapter.
Before moving forward, verify:
Once these items are complete, you are ready to connect the Website to AIUNIFY Analytics.