Configuring Tracking Settings

The Tracking settings determine how Nelio A/B Testing measures your tests. They control which visitors participate in tests, when conversions are recorded, how visitor segments are evaluated, and whether tracking integrates with third-party services such as Google Analytics.

For most websites, the default configuration is appropriate and doesn’t need to be changed. This guide explains what each option does and when you might want to customize it.

Tested Visitors

The Tested Visitors setting determines what percentage of eligible visitors participate in your tests.

By default, 100% of eligible visitors are included.

Reducing this percentage can help conserve your monthly quota on high-traffic websites while still collecting statistically meaningful results.

For example:

• 100% – Every eligible visitor participates.
• 50% – Approximately half of eligible visitors participate.
• 10% – Only a small sample of visitors participates.

💡 Recommendation: Unless you’re trying to reduce quota consumption, leave this setting at 100%.

Goal Tracking

This setting controls where conversion actions may be triggered.

You can choose one of three modes:

All Pages (Default)

Conversion actions can be triggered anywhere on your website. Use this option when conversions may naturally occur on pages other than the one being tested, such as checkout or Thank You pages.

Tested Pages

Conversion actions are only evaluated on pages included in the test’s scope. This helps isolate tests that track similar actions on different pages.

Custom

Each conversion action can define its own tracking scope. Choose this option when different goals require different tracking behavior.

🔍 Learn more: Can I Limit Where Conversion Goals Are Tracked?

Segmentation

These settings determine when Nelio A/B Testing evaluates the segments defined in your tests to decide whether a visitor should participate.

Three evaluation modes are available.

Evaluate on Site Landing

Nelio evaluates the segments of all active tests as soon as a visitor first arrives on your website. This ensures that participation is decided at the beginning of the visitor’s session and remains consistent while they browse your site.

Evaluate on Tested Pages

Nelio only evaluates the segments of tests that affect the current page. This reduces unnecessary evaluations and is the recommended option for most websites.

Custom Evaluation

Each test defines when its own segments are evaluated. Use this option if different tests require different evaluation strategies.

Require Participation in All Tests Affecting the Current Page

When several active tests affect the same page, this setting controls whether a visitor must qualify for all of them.

• Enabled: The visitor participates only if they match at least one segment in every active test affecting the current page.
• Disabled: Each test is evaluated independently. The visitor participates only in the tests whose segments they match.

Exclude Bots from Participating in Split Tests

When enabled, Nelio attempts to detect automated traffic and prevent bots from participating in tests. Detection is based on user-agent information.

💡Recommendation: Keep this option enabled.

Excluded IPs

You can exclude one or more IP addresses from tracking. Visitors using these IP addresses continue to see test variants, but their page views and conversions aren’t recorded.

💡Recommendation: Add the IP addresses of anyone who regularly works on your website.

GDPR Consent Cookie

If your website requires visitor consent before collecting analytics data, you can configure Nelio A/B Testing to wait until that consent has been granted before tracking page views and conversions. To do this, specify the name of the cookie your consent solution creates and, optionally, the value it must contain to indicate that analytics cookies have been accepted.

When this setting is configured:

• Nelio A/B Testing still assigns visitors to a variant and displays the correct version of the page.
• The essential cookies required to provide a consistent experience (such as nabAlternative) continue to work.
• No analytics events are recorded until the required consent cookie is present with the expected value.

This approach ensures that visitors always see the same variant throughout the test while respecting their privacy preferences.

The analytics data collected by Nelio A/B Testing is used exclusively for statistical purposes, such as measuring page views, conversions, and test performance. It is processed in a way that does not identify individual visitors.

Leave this setting empty if your website doesn’t require visitor consent before analytics tracking.

💡 Recommendation: Configure this option if you use a cookie consent solution or must comply with privacy regulations such as GDPR or CCPA.

🔍 Learn more: Does Nelio A/B Testing Work With Cookie Plugins?

Google Analytics Integration

Nelio A/B Testing can send test events to Google Analytics 4 (GA4). When enabled, page views and conversions recorded by Nelio are also sent to your connected Google Analytics property, making it easier to compare test data with your broader website analytics.

This integration complements Nelio’s own reports—it doesn’t replace them.

🔍 Learn more: How to Integrate Google Analytics 4 with Nelio A/B Testing.

Recommended Configuration

For most websites, we recommend the following settings: