Skip to main content
How Can We Help?
Test Not Running
If an experiment in Bluvia A/B Testing isn’t running as expected, start by checking the experiment’s status and configuration.
Several factors can prevent a test from running, including its current status, scheduling, targeting, or website configuration.
Use the steps below to identify the issue.
Check the Test Status
Navigate to Bluvia A/B Testing ā Test Library and locate the experiment.
Check the Status column to confirm the test is Active.
If the experiment is:
- Draft ā The experiment hasn’t been launched yet.
- Scheduled ā The experiment is waiting for its scheduled start date and time.
- Paused ā The experiment must be resumed before it can continue running.
- Completed ā The experiment has been stopped and cannot be resumed.
- Archived ā The experiment is no longer part of your active testing workflow.
If the experiment should currently be running, make sure its status is Active.
Check Your Schedule
If you’re using scheduling, confirm that the experiment’s start and end times are configured correctly.
Check that:
- The scheduled start time has passed.
- The experiment hasn’t reached its scheduled end time.
- The selected dates and times are correct.
If the experiment is still waiting for its scheduled start time, it will remain under the Scheduled filter in your Test Library.
Review Your Targeting Rules
Targeting Rules determine which visitors are eligible to participate in your experiment.
If you’re checking the website yourself and don’t see the experiment, you may not meet the targeting conditions you’ve configured.
Review your experiment’s Targeting Rules and confirm that the visitor you’re using to test the experience is eligible.
See Targeting Rules for more information about configuring your audience.
Review Your Exclusion Rules
Exclusion Rules can prevent certain visitors from participating in an experiment.
For example, your current visit may be excluded because you’re:
- Logged into WordPress.
- A WordPress administrator.
- Using an excluded IP address or range.
- Otherwise covered by one of the experiment’s configured exclusion rules.
If the experiment is Active but you aren’t seeing it yourself, check your Exclusion Rules before assuming the test isn’t running.
Check the Content Being Tested
Confirm that the experiment is associated with the correct page, post, menu, or other WordPress content.
Open the content you selected when creating the experiment and make sure you’re checking the correct location on your website.
For URL-based experiments, confirm that you’re visiting the correct URL.
Check the Variant
If the experiment appears to be running but you’re only seeing the Control, the issue may be related to the Variant rather than the experiment itself.
Remember that participating in an A/B test doesn’t mean you’ll always see a Variant. Depending on your Traffic Allocation, you may be assigned to the Control.
If you believe the Variant itself isn’t being displayed correctly, continue with Variant Not Showing.
Check for Caching
Caching can sometimes cause an older version of a page to continue appearing after an experiment has been launched or updated.
If the experiment configuration appears correct but the expected experience isn’t appearing, your WordPress caching configuration may be involved.
See Cache Issues for additional troubleshooting steps.
Check for JavaScript or CDN Issues
Some website configurations, plugins, themes, scripts, or content delivery services can interfere with how an experiment runs.
If you’ve confirmed the experiment itself is configured correctly, continue troubleshooting with:
These guides cover website-level issues that may affect Bluvia A/B Testing.
Still Having Trouble?
If you’ve reviewed the experiment status, scheduling, targeting, exclusions, and website configuration but the test still isn’t running, contact Bluvia A/B Testing Support.
When contacting Support, include:
- The name of the experiment.
- The URL where the experiment should be running.
- The test type.
- The experiment’s current status.
- A description of what you expected to happen.
- A description of what you’re seeing instead.
Providing this information can help the Support team investigate the issue more quickly.
Related Articles
Continue with:
