Published on August 15, 2026

Chapter 5 — Installing the AIUNIFY Analytics Tracking Code

5.1 Overview

After creating a Website in AIUNIFY Analytics, the next step is to install that Website's unique Tracking Code on the Website you want to monitor.

The Tracking Code connects your Website to its corresponding record inside AIUNIFY Analytics.

The installation workflow is:

Create Website → Open Install Pixel → Copy Pixel → Add Code to Website <head> → Publish Changes → Generate Website Activity → Verify Analytics Data

AIUNIFY Analytics calls the installation window:

Install pixel

and instructs users to copy and paste the supplied JavaScript snippet before the end of the Website's <head> tag.

5.2 What the Tracking Code Does

The Tracking Code is a small JavaScript snippet associated with the Website you created in AIUNIFY Analytics.

It allows that Website to communicate supported visitor activity to the Analytics platform.

Depending on your Website's Tracking Type and enabled options, the installed code can support Analytics functions such as:

  1. Pageviews
  2. Sessions
  3. Visitors
  4. Realtime activity
  5. Goals
  6. Outbound Clicks
  7. Visitor Events
  8. Heatmaps
  9. Session Replays
  10. Custom Parameters
  11. Other supported Website Analytics

The capabilities available after installation depend on whether the Website uses Lightweight Tracking or Advanced Tracking and which optional tracking settings are enabled.

5.3 Each Website Has Its Own Tracking Code

When a Website is created, AIUNIFY Analytics generates a unique Tracking Code key for that Website.

The source creates a unique 16-character pixel key and stores it with the Website record.

This means that if you manage several Websites, each Website record has its own Analytics Tracking Code.

For example:

Website A

→ Tracking Code A

Website B

→ Tracking Code B

Do not copy a Tracking Code from one Website and install it on a different Website unless that is specifically the Website configuration you intend to use.

5.4 Opening the Tracking Code After Creating a Website

When you successfully create a new Website, AIUNIFY Analytics automatically returns you to Websites and opens the Tracking Code installation workflow for the newly created Website.

The window is titled:

Install pixel

Inside it, you will see:

  1. Installation instructions
  2. The generated JavaScript code
  3. A Copy pixel button


This allows you to proceed directly from Website creation to installation.

5.5 Opening the Tracking Code Again Later

You can return to a Website's Tracking Code after the initial setup.

To retrieve it:

  1. Sign in to AIUNIFY Analytics.
  2. Open Websites.
  3. Locate the Website you want to configure.
  4. Find the Tracking code control represented by the code icon.
  5. Select the code icon.
  6. The Install pixel window opens.
  7. Copy the displayed Tracking Code.

The Websites interface associates the code button with the Website's unique pixel key and labels that control Tracking code.

5.6 Understanding the Install Pixel Window

The Install Pixel window contains the instruction:

Copy and paste the following JS code snippet before the end of the head tag of your website.

Below that instruction, Analytics generates the code for the selected Website.

Its general structure is:


<!-- Pixel Code - ANALYTICS_URL -->
<script defer src="ANALYTICS_URL/pixel/WEBSITE_KEY"></script>
<!-- END Pixel Code -->

The actual values are generated automatically by AIUNIFY Analytics for the Website you selected.

Important: Do not manually create or guess your Website's Tracking Code. Use the code displayed inside your own Install pixel window.

5.7 Step 1 — Click Copy Pixel

Inside the Install pixel window:

  1. Review the displayed code.
  2. Click Copy pixel.

When the code is copied successfully, the button temporarily changes to:

Copied!

The application then returns the button to its normal state.

You now have the complete Tracking Code ready to place on your Website.

5.8 Step 2 — Access Your Website's Code or Header Area

Next, access the location where your Website's HTML <head> section is managed.

The exact method depends on how your Website was built.

Examples can include:

  1. A Website theme or template
  2. A global header file
  3. A Website builder's custom-code area
  4. A content management system's header-code setting
  5. A tag/code injection area
  6. A developer-managed HTML template

AIUNIFY Analytics itself does not prescribe a CMS-specific installation workflow in the supplied source. Its instruction is specifically to place the generated JavaScript before the end of the <head> tag.

Therefore, follow the appropriate method for your Website platform while preserving that placement requirement.

5.9 Step 3 — Locate the Closing Head Tag

In a standard HTML document, the Website structure contains a <head> section similar to:


<head>

<!-- Website metadata and other scripts -->

</head>

AIUNIFY Analytics instructs you to place its code before the end of this section.

For example:


<head>

<!-- Existing Website content -->

<!-- AIUNIFY Analytics Tracking Code -->
<!-- Paste the exact code copied from Install pixel here -->

</head>

Do not copy the example placeholder shown in this manual.

Use the actual Tracking Code provided by your AIUNIFY Analytics account.

5.10 Step 4 — Paste the Complete Tracking Code

Paste the entire code copied from Copy pixel.

Do not remove:

  1. The <script> element
  2. The generated Analytics URL
  3. The /pixel/ path
  4. The unique Website key
  5. The defer attribute

The generated script source is constructed using the Website's assigned Analytics base URL plus:

pixel/WEBSITE_KEY


Using the complete generated snippet ensures the Website sends activity to the correct Analytics Website record.

5.11 Step 5 — Save or Publish the Website Changes

After pasting the Tracking Code:

  1. Save your Website code or settings.
  2. Publish/deploy the changes if your Website platform requires it.
  3. Open the live Website.

The Tracking Code must exist on the live Website pages you want AIUNIFY Analytics to monitor.

Saving a code change only in a draft, development environment, or unpublished Website configuration will not cause activity on the public Website to be tracked.

5.12 Where Should the Tracking Code Be Installed?

The system's explicit placement instruction is:

Before the end of the <head> tag.

For a Website where multiple pages share one common header/template, installing the code in that common Website header can allow the tracking script to load on the pages that use it.

The precise implementation depends on the Website's architecture.

The important requirement from AIUNIFY Analytics is that the generated script be loaded on the Website pages that should be measured.

5.13 Tracking a Specific Website Path

When creating the Website, AIUNIFY Analytics allows tracking to be associated with a domain, subdomain, or specified Website path.

The application states that tracking works on the:

  1. domain.com
  2. sub.domain.com
  3. domain.com/path

that you specify.

Therefore, verify that the Website record you created corresponds to the Website location where you are installing the code.

For example, if the Analytics Website was configured for:

example.com/store

make sure the Tracking Code is being used for that intended Website property.

5.14 Custom Domain Tracking Codes

If your Website was configured with an AIUNIFY Analytics Custom Domain, the generated Tracking Code automatically uses the appropriate Custom Domain as its Analytics base URL.

If no Custom Domain is assigned, the system uses the standard Analytics URL.

You do not need to manually rewrite the generated code.

Always copy the latest snippet from:

Websites → Tracking code → Install pixel

This ensures the correct base URL is used.

5.15 Do Not Copy Another Website's Code

If your Analytics account manages multiple Websites, confirm the Website before copying the Tracking Code.

The Websites list generates the installation button using:

  1. That Website's Tracking Type
  2. That Website's pixel key
  3. That Website's URL
  4. That Website's Analytics base URL


For this reason, obtain the Tracking Code directly from the row belonging to the Website you intend to track.

5.16 Step 6 — Visit Your Website

After publishing the Tracking Code:

  1. Open the live Website in your browser.
  2. Navigate through one or more pages.
  3. Allow the pages to finish loading.
  4. Perform normal Website activity.

For example:

  1. Open the home page
  2. Open another page
  3. Navigate through several sections
  4. Click an outbound link if Outbound Click tracking is enabled
  5. Perform additional interactions if Advanced Visitor Events are enabled

This creates activity that Analytics can attempt to record.

5.17 Step 7 — Check Realtime Analytics

One of the most practical first places to check after installation is Realtime.

Return to AIUNIFY Analytics and:

  1. Make sure the correct Website is selected.
  2. Open Realtime.
  3. Keep the live Website open in another browser tab or window.
  4. Navigate through the Website.
  5. Look for recent activity inside Realtime.

Realtime is designed to show approximately the last 60 seconds of Website activity and refresh automatically.

This makes it useful for checking whether new Website activity is reaching Analytics.

5.18 Step 8 — Check Pageviews

Next, open:

Pageviews

Look for activity from the pages you visited after installing the Tracking Code.

The Pageviews section represents the Website events Analytics has tracked for page access.

Remember that AIUNIFY Analytics automatically uses the correct Pageviews implementation for the Website's Tracking Type.

5.19 Step 9 — Check the Dashboard

You can also return to:

Dashboard

The primary Dashboard metrics include:

  1. Pageviews
  2. Sessions
  3. Visitors where applicable

If no activity has been recorded, the Dashboard displays:

No data available

and specifically advises:

Make sure you have properly installed your tracking code.

This is the system's primary built-in indication that installation should be checked.

5.20 Tracking May Not Appear as a Visitor Immediately in Every Mode

Remember that Lightweight Tracking and Advanced Tracking process visitor information differently.

Lightweight Tracking

Does not create persistent visitor associations in the same manner.

You should primarily use:

  1. Dashboard
  2. Pageviews
  3. Realtime
  4. Supported Goal and outbound data

to evaluate tracking.

Advanced Tracking

Can support:

  1. Visitors
  2. Visitor histories
  3. Session Events
  4. Heatmaps
  5. Session Replays

when those functions are enabled.

Therefore, do not use the absence of an Advanced-only Visitor record as the sole verification method for a Lightweight Website.

5.21 The Tracking Code Uses Deferred Loading

The generated Tracking Code contains the HTML defer attribute.

The application's built-in FAQ also states that the Analytics JavaScript executes asynchronously relative to normal Website loading and begins its tracking process after the page is ready.

This design is intended to allow Analytics tracking without requiring the Website's primary page content to wait on the tracking script before proceeding.

5.22 If Analytics Shows No Data

If Realtime, Pageviews, and Dashboard remain empty after installation, work through the following checks.

Check 1 — Correct Website Selected

Look at the Website Selector in AIUNIFY Analytics.

Confirm that you are viewing the same Website whose Tracking Code you installed.

This is particularly important when the account contains several Websites.

Check 2 — Tracking Is Enabled

Open:

Websites → Edit Website

Confirm that:

Tracking

is enabled.

The Website setting allows tracking to be completely enabled or disabled.

A correctly installed code will not produce the expected collection if Website Tracking has intentionally been disabled.

Check 3 — Correct Tracking Code Was Installed

Return to:

Websites → Tracking code

and reopen Install pixel.

Compare that generated snippet with the code on the Website.

Make sure the Website uses the correct unique Analytics code.

Check 4 — Code Is Inside the Website Head

Confirm that the code is located before the closing:


</head>

This is the location specified by AIUNIFY Analytics.

Check 5 — Website Changes Were Published

Make sure the Tracking Code is present on the live Website rather than only in an unpublished editor or development copy.

Check 6 — Correct Domain or Path

Confirm that the Website address configured in Analytics matches the property where the code was installed.

Analytics states that tracking is associated with the domain, subdomain, or path specified in the Website configuration.

5.23 Browser Conditions That Can Prevent Tracking

The application's built-in FAQ identifies several situations where Website activity may be excluded from tracking.

These include when a visitor:

  1. Has JavaScript disabled
  2. Has localStorage disabled or unavailable where applicable
  3. Uses a browser or browser extension that blocks tracking
  4. Has opted out of Website tracking


These factors mean that no browser-based Analytics system should be expected to record every possible Website request.

5.24 Browser or Tracking Blockers

Some visitors may use:

  1. Browser privacy controls
  2. Tracking-blocking extensions
  3. Content blockers
  4. Other browser tools

that prevent the Analytics script from operating.

If you can see the Tracking Code correctly installed but a particular browser does not generate Analytics activity, test the Website in another browser or browser configuration before assuming the Website installation itself is incorrect.

The source specifically recognizes browser or plugin tracking blocking as a reason a visitor may be excluded.

5.25 Website Visitor Opt-Out

AIUNIFY Analytics includes an Opt-Out mechanism.

The built-in help indicates that a Website can allow users to stop Analytics tracking through an opt-out URL parameter.

The documented parameter is:

?pixel_optout=true

When triggered, the system stores the opt-out state in browser local storage so tracking stops for that browser context.

Privacy and opt-out implementation will be addressed more fully in the dedicated privacy chapter.

5.26 Verify the Correct Tracking Type

Installation of the Tracking Code does not change the Website's Tracking Type.

The Website remains either:

Lightweight Tracking

or

Advanced Tracking

according to the choice made when the Website was created.

If basic Analytics data works but you do not see:

  1. Visitors
  2. Heatmaps
  3. Replays

check whether the Website was created using Lightweight Tracking.

Those features are not available under Lightweight Tracking in the same way they are under Advanced Tracking.

5.27 Verify Individual Feature Settings

A functioning Tracking Code does not automatically mean every optional Analytics feature is enabled.

For example:

Outbound Clicks

Requires Track outbound clicks to be enabled.

Visitor Events

Requires Advanced Tracking and Track visitors events.

Session Replays

Requires Advanced Tracking, account availability, and Session replays to be enabled.

IP Tracking

Requires feature availability and the corresponding setting.

Therefore, when a specific report is empty but Pageviews are working, verify the configuration for that specific feature before reinstalling the entire Tracking Code.

5.28 Do Not Duplicate the Tracking Code Unnecessarily

Use the code supplied for the Website and install it according to the Website's architecture.

Avoid intentionally placing identical Analytics snippets multiple times on the same rendered page unless your Website implementation specifically requires and accounts for that behavior.

Your goal is to ensure the assigned Tracking Code loads correctly for each page you want measured.

5.29 Updating the Website Later

After installation, you can return to the Website configuration to adjust supported settings such as:

  1. Tracking on/off
  2. Outbound Clicks
  3. Visitor Events
  4. Session Replays
  5. Email Reports
  6. Public Statistics
  7. Bot Exclusion
  8. Query Parameter Tracking
  9. IP Tracking
  10. Excluded IPs
  11. Session Replay hidden-text selectors

You do not need to create a new Website record simply because you want to change one of these configurable settings.

The important exception is the Website's Tracking Type, which the creation interface identifies as non-changeable after creation.

5.30 Tracking Code Installation Checklist

Before considering installation complete, verify:

  1. Correct Analytics Website selected
  2. Correct Tracking Code opened
  3. Copy pixel used to copy the complete code
  4. Entire code pasted on the Website
  5. Code positioned before the closing </head> tag
  6. Website changes saved
  7. Website changes published
  8. Tracking enabled for the Website
  9. Correct domain/subdomain/path configured
  10. Website opened after installation
  11. Test activity generated
  12. Realtime checked
  13. Pageviews checked
  14. Dashboard checked
  15. Optional feature settings checked if specific data is missing

5.31 Successful Installation

You can consider the basic Analytics installation operational when the Website generates activity and AIUNIFY Analytics begins displaying that activity in an appropriate reporting area such as:

Realtime → Pageviews → Dashboard

After that, the focus shifts from installing the tracking technology to managing how the Website is configured.

The source confirms that the installation modal generates the unique deferred JavaScript snippet, provides Copy pixel, and instructs placement before the end of the Website <head>.

Write Your Comment