Configuring Plugin Behavior

The Plugin Behavior settings control how Nelio A/B Testing delivers variants, loads its tracking script, interacts with cache systems, and provides debugging information.

Most websites work correctly with the default configuration. These settings are intended for advanced use cases, compatibility with specific hosting environments, or troubleshooting.

Variant Settings

These options affect how visitors access test variants.

Use Control ID in Test Variants

By default, each variant has its own WordPress post or page ID.

Some themes and plugins rely on the original page ID when rendering menus, templates, shortcodes, or other dynamic content. Enabling this option allows variants to reuse the control page’s ID, improving compatibility with those systems.

However, some page builders generate CSS based on the post ID. If variant styles appear incorrect, disable this option so each variant uses its own ID.

💡 Recommendation: Leave this option disabled unless you’re experiencing compatibility issues with your theme or plugins.

Make nab the First Query Parameter

When variants are loaded using query parameters, Nelio adds the nab parameter to the page URL.

Some caching systems and CDNs only consider the first query parameter when generating cache keys. Enabling this option ensures that nab appears first, improving compatibility with those systems.

💡 Recommendation: Leave this setting disabled unless your cache provider specifically recommends it.

Hide nab After Loading the Variant

When enabled, Nelio removes the nab parameter from the browser’s address bar after the correct variant has loaded. This creates cleaner URLs while preserving the visitor’s assigned variant. The URL is updated using the browser’s History API, without reloading the page.

💡 Recommendation: Enable this option if you prefer visitors not to see testing parameters in the address bar.

Add nab to Internal Links

When a visitor navigates to another page, Nelio can automatically append the current nab parameter to internal links. This allows the next page to immediately load the correct variant, reducing the need for additional redirects.

💡 Recommendation: Enable this option if your tests rely on query-parameter variant loading.

Tracking Script

Insert Tracking Script as an Inline Script

By default, Nelio loads its public tracking script as an external JavaScript file. Enabling this option embeds the script directly into the page instead.

This may improve compatibility with strict Content Security Policies (CSP), optimization plugins, or environments that restrict external JavaScript files.

💡 Recommendation: Leave this option disabled unless your hosting environment or security policy requires it.

Debug Tools

Show the Debug Panel

When your site is running in Staging Mode (or when using the nabstaging query parameter), Nelio can display a debugging panel directly on the page. This makes it much easier to validate tests without inspecting the browser console.

💡 Recommendation: Enable this option when testing tests on staging or during troubleshooting. Disable it for normal day-to-day browsing.

🔍 Learn more in Using the Debug Tools

Include Test Names in the Debug Panel

Displays the names of active tests alongside their identifiers in the debugging panel. This can make debugging easier when several tests are running simultaneously.

Cloud Proxy

Some ad blockers prevent requests to Nelio Cloud because they recognize analytics domains. Cloud Proxy lets your own website relay tracking requests instead.

Disabled

Tracking requests are sent directly to Nelio Cloud. This is the default configuration and works for most websites.

REST API Mode

Tracking requests are routed through a WordPress REST API endpoint. This improves compatibility with some ad blockers but increases the load on your WordPress server. If you use page caching or a CDN, make sure the REST endpoint is excluded from caching.

Domain Forwarding Mode

Tracking requests use a subdomain of your own website that forwards traffic to Nelio Cloud. This approach usually offers the best compatibility with ad blockers while avoiding additional load on your WordPress server.

💡 Recommendation: Use Disabled unless ad blockers are preventing tracking. If necessary, prefer Domain Forwarding over REST API whenever possible.

Variant Loading

Enable Cookie-Based Testing with Dynamic Caching

By default, Nelio identifies variants using the nab query parameter. When this option is enabled, variants are selected using the nabAlternative cookie instead. This allows compatible caching systems to serve the correct variant directly, avoiding redirects and improving page load times.

However, your cache or CDN must support cookie-based cache variation. Improper configuration may result in visitors seeing the wrong variant.

💡 Recommendation: Enable this option only after configuring your caching solution for cookie-based testing.

🔎 Learn more: How Nelio A/B Testing Works With Cache Plugins and CDNs.

Recommended Configuration

For most websites, we recommend: