How Can I Remove Nelio Scripts From Pages That Are Not Under Test?

By default, Nelio A/B Testing may load its tracking scripts on pages that aren’t directly under test. This allows the plugin to prepare navigation to tested pages and track conversion actions that may occur elsewhere on your site.

If you want to limit Nelio scripts to test-related pages, you need to:

1. Disable the automatic insertion of testing query parameters.
2. Limit goal tracking to specific pages.

1. Disable the Automatic Insertion of Testing Query Parameters

To prevent Nelio from adding the nab parameter to all internal links:

1. Go to Nelio A/B Testing → Settings → Behavior.
2. Disable the option “Add testing query args nab to all URLs to speed up page loading times when browsing your site”.

What this option does:

• When enabled, Nelio A/B Testing can add the appropriate nab query argument to internal links so that, when visitors navigate to a tested page, the correct alternative content can be loaded directly.
• Disabling this option prevents Nelio from proactively adding these testing query arguments throughout your site.

2. Limit Goal Tracking

By default, conversion actions may need to be tracked outside the page directly under test. For example, a visitor might see a tested pricing page but complete the conversion on another page.

If you don’t need site-wide goal tracking, you can restrict where conversion actions are tracked.

In the Goal Tracking settings, choose:

• Custom Pages to specify the pages where conversion actions should be tracked for that test.
• Tested Pages to track conversion actions only on the pages being tested.

Result

By disabling the automatic insertion of nab query arguments and limiting goal tracking to tested or selected pages, Nelio A/B Testing can avoid loading its tracking scripts on pages where they aren’t needed.