Skip to main content
How Can We Help?

JavaScript Conflicts

Posted
Updated
ByEmily Gomez
WordPress themes, plugins, and custom code can add JavaScript to your website. In some cases, a JavaScript error or conflict may interfere with how an experiment or Conversion Goal works in Bluvia A/B Testing.
If your experiment is configured correctly but a Variant, interaction, or conversion isn’t working as expected, a JavaScript conflict may be worth investigating.

Signs of a JavaScript Conflict

A JavaScript issue may be involved if:
  • An experiment is Active but part of the Variant doesn’t work correctly.
  • Buttons or interactive elements stop responding.
  • A Variant displays incorrectly.
  • A Conversion Goal isn’t tracking as expected.
  • A custom JavaScript event isn’t being recorded.
  • The experiment works when certain plugins or scripts are disabled.
Before investigating JavaScript, confirm that your experiment and Conversion Goal are configured correctly.

Pause the Test and Check the Original Page

First, determine whether the issue occurs when the experiment isn’t running.
If the experiment is currently Active, pause the test temporarily before troubleshooting the original page.
Then:
  1. Pause the experiment from the Test Library or test progress page.
  2. Visit the original page being tested.
  3. Check whether the affected element or functionality works correctly.
  4. Preview the Variant and compare its behavior with the original page.
For example, if a button isn’t responding in your Variant, confirm that the same button or functionality works correctly on the original page while the experiment is paused.
If the issue also occurs when the experiment is paused, the problem is more likely related to your website, theme, plugin, or custom code rather than the experiment itself.
If the original page works correctly but the problem appears in the Variant, continue troubleshooting the Variant and its changes.
Once you’ve finished troubleshooting, review the experiment before resuming it.
For more information about temporarily stopping an experiment, see Pausing or Stopping a Test.

Check the Variant

If the issue only occurs on a Variant, review the changes made to that Variant.
Pay particular attention to changes involving:
  • Custom JavaScript.
  • Interactive elements.
  • Buttons or links.
  • Forms.
  • Dynamically loaded content.
  • Third-party scripts.
Preview the Variant and confirm that the affected functionality works before continuing the experiment.

Check for JavaScript Errors

Your browser’s developer tools can help identify JavaScript errors occurring on the page.
Open the page where you’re experiencing the issue and use your browser’s Developer Tools ā†’ Console.
Look for errors that appear when:
  • The page loads.
  • The Variant appears.
  • You click the affected element.
  • You submit a form.
  • You perform the action that should trigger a conversion.
An error doesn’t necessarily mean Bluvia A/B Testing caused the problem. The Console may contain errors generated by your theme, another plugin, custom code, or a third-party service.

Check Other WordPress Plugins

Another WordPress plugin may load JavaScript that conflicts with your experiment.
Common areas to investigate include plugins that modify:
  • Page content
  • Forms
  • Navigation
  • JavaScript loading
  • Performance and optimization
  • Caching
  • Minification or script combining
If you’re comfortable troubleshooting WordPress plugins, temporarily disabling a suspected plugin can help determine whether it’s involved.
Avoid making troubleshooting changes on a production website if doing so could affect your visitors. Use a staging environment when appropriate.

Check Your Theme or Page Builder

Your WordPress theme or page builder may also control JavaScript used by the content you’re testing.
If an experiment involves content created with a page builder or theme-specific feature, confirm that the original content works correctly before testing it.
This can be especially important for interactive elements that rely on JavaScript to initialize after the page loads.

Trigger Custom JS Event

If you’re using Trigger Custom JS Event as your Conversion Goal, confirm that your website is actually firing the event Bluvia A/B Testing is configured to track.
The Event Name entered in your Conversion Goal must match the custom event generated by your website.
If the event name doesn’t match or your website never triggers the event, the conversion won’t be recorded.
Because this is a Developer Goal, you may need assistance from the developer responsible for your website’s custom JavaScript implementation.

Check Optimization and Caching Tools

Some performance tools modify how JavaScript loads by:
  • Delaying scripts
  • Deferring JavaScript
  • Combining scripts
  • Minifying JavaScript
  • Changing script execution order
These changes can occasionally affect functionality that depends on scripts running at a particular time.
If you suspect a performance or caching configuration is involved, continue with Cache Issues.

After Making Changes

After resolving a suspected JavaScript issue:
  1. Clear any relevant website caches.
  2. Preview the Variant again.
  3. Confirm that the affected functionality works.
  4. Verify that the Conversion Goal behaves as expected, if applicable.
  5. Resume or launch the experiment when you’re satisfied with the results.
Remember that editing an Active experiment will pause it.

Still Having Trouble?

If you’ve confirmed the original page works correctly and believe a JavaScript conflict is interfering with Bluvia A/B Testing, contact Support.
When contacting Bluvia A/B Testing Support, include:
  • The experiment name.
  • The URL where the issue occurs.
  • The affected Variant.
  • A description of what isn’t working.
  • Whether the problem occurs on the Control, Variant, or both.
  • Any relevant JavaScript errors from the browser Console.
  • The theme or page builder you’re using.
  • Any plugins you believe may be involved.
If you’re troubleshooting a Trigger Custom JS Event goal, also include the event name you’re attempting to track.

Related Articles

Continue with: