Why Are Visitors Not Being Tracked Properly?

If you see unexpected differences in visitor counts—or if tracking appears inconsistent—there are several possible reasons.

First, make sure the test is actually running and collecting data. If you don’t see any results at all, see Why Do I Still Have No Results in My Test?.

If results are being collected but the numbers look lower or different from what you expected, check the following..

1. Only a Percentage of Visitors Is Eligible to Participate in Tests

The global Tested Visitors setting determines what percentage of your site’s visitors are eligible to participate in running tests.

For example, if Tested Visitors is set to 50%, approximately half of your visitors will be eligible for testing. Visitors who aren’t selected:

• See the original content
• Don’t participate in tests
• Don’t consume testing quota
• Aren’t included in test results

Other analytics tools may still track those visitors, so their traffic numbers can be higher than those reported by Nelio A/B Testing.

In addition, segmentation rules may further determine whether an eligible visitor participates in a particular test.This naturally creates differences in total counts.

2. Your Analytics Tool May Track Page Views Differently

Nelio A/B Testing and analytics tools such as Google Analytics don’t necessarily record page views in the same way.

For example, when Nelio uses a redirection to load a variant, another analytics script may run before the redirection takes place and record the initial page load. It may then record the resulting variant page as another page view.

Nelio A/B Testing, on the other hand, records the Tested Page View associated with the test.

This is one reason why page view counts in different tools may not match exactly.

3. You May Be Comparing Different Metrics

Make sure you’re comparing equivalent metrics.

Page views, visitors, and sessions represent different things, and analytics platforms may also define and calculate them differently.

Nelio A/B Testing measures Tested Page Views for pages involved in running tests. This isn’t the same as measuring all traffic or sessions across your website.

4. Tracking May Be Prevented for Some Visitors

Some visitors may not be tracked because of their browser or privacy configuration.

For example:

• Required consent hasn’t been granted yet
• Cookies are disabled
• An ad blocker prevents the tracking request
• A security or privacy tool blocks the tracking script

These visitors may still appear in another analytics platform depending on how that platform is configured.

5. Your Available Quota Has Been Exhausted

When your available Tested Page View quota is exhausted, your tests can continue displaying variants, but Nelio A/B Testing stops recording new views and conversions.

Tracking resumes when quota becomes available again.

Why Nelio and Other Analytics Tools May Not Match Exactly

Different analytics systems use different:

• Counting rules
• Tracking scripts
• Loading times
• Cookie mechanisms
• Privacy and consent configurations
• Definitions of page views, visitors, and sessions

For this reason, you shouldn’t expect Nelio A/B Testing’s numbers to match another analytics platform exactly.

When evaluating an A/B test, use Nelio A/B Testing’s results to compare the performance of its control and variants consistently within the same test, rather than trying to match its totals exactly with another analytics tool.