Skip to main content
How Can We Help?

Elementor

Posted
Updated
ByEmily Gomez
Bluvia A/B Testing works with Elementor for test types that support full page or content editing.
When you create a Variant of an Elementor-built page using a supported Test Type, Bluvia A/B Testing opens the Variant in Elementor so you can make changes using the same visual editor as the original page.
Not every Test Type uses Elementor. Headline, CTA / Button, and Menu tests are configured directly within Bluvia A/B Testing and do not open the Elementor editor.

How Elementor Works With Bluvia A/B Testing

When you create an experiment that supports full content editing, start by selecting the page you want to test.
Bluvia A/B Testing uses the original page as the starting point for your Variant.
If the original page was built with Elementor, selecting Edit for the Variant opens the Elementor editor.
You can then make your changes using the same Elementor widgets, layout controls, and editing tools you normally use to manage the page.
You don’t need to recreate the page in a separate Bluvia A/B Testing editor.

Which Tests Open in Elementor?

Elementor opens when the Test Type allows you to edit the full content of an Elementor-built page.
Other Test Types provide their own editing experience directly within Bluvia A/B Testing.
The following tests do not open Elementor:
  • Headline: Configure the Headline Variant directly within Bluvia A/B Testing.
  • CTA / Button: Configure the CTA or Button Variant directly within Bluvia A/B Testing.
  • Menu: Configure the Menu Variant directly within Bluvia A/B Testing.
The editing experience depends on both the Test Type and how the original content was built.

Saving Your Changes and Returning to Your Experiment

When you’re finished editing your Variant, save your changes in Elementor before returning to Bluvia A/B Testing.
To save and return:
  1. Use Elementor’s Save Draft action to save your changes.
  2. Confirm that your changes have been saved.
  3. Select the dedicated Back button to return to your Bluvia A/B Testing experiment.
The Back button returns you to the experiment workflow but does not replace Elementor’s save action.
Always save your changes before selecting Back. Otherwise, changes made in Elementor may not be included in your Variant.
Once you return to Bluvia A/B Testing, you can continue reviewing your Variants, configure the remaining experiment settings, and prepare the test for launch.
We recommend using the dedicated Back button rather than your browser’s Back button when returning from Elementor.

What Can You Change?

When a Variant opens in Elementor, you can use Elementor’s editing tools to make the types of changes normally available for that page.
Depending on your page and Elementor setup, this may include:
  • Headlines and copy
  • Images
  • Buttons
  • Colors and styling
  • Spacing and layout
  • Hero sections
  • Calls to action
  • Sections and containers
  • Other Elementor widgets and content
The changes are made to the Variant being tested while the original page remains the Control during the experiment.

Editing an Elementor Variant

For a test that supports full content editing:
  1. Create a new experiment in Bluvia A/B Testing.
  2. Select the appropriate Test Type.
  3. Select the Elementor page you want to test.
  4. Create your Variant.
  5. Open the Variant for editing.
  6. Make your changes using Elementor.
  7. Save or update the Variant in Elementor.
  8. Confirm that your changes have been saved.
  9. Use the dedicated Back button to return to your Bluvia A/B Testing experiment.
  10. Review your Variants and configure the remaining experiment settings.
  11. Preview the Control and Variant before launching.
  12. Launch the experiment when you’re ready.
Visitors participating in the experiment will receive the Control or a Variant according to your configured Traffic Allocation.

Preview Before Launching

Always preview your Elementor Variant before starting the experiment.
Check that:
  • Content displays correctly.
  • Images and media load.
  • Buttons and links work.
  • Sections and containers appear as expected.
  • Interactive elements function correctly.
  • Responsive layouts look correct across the devices important to your audience.
Previewing is particularly important after making larger layout or structural changes.

Elementor Widgets and Other Plugins

Elementor and other WordPress plugins can provide widgets with their own scripts, styles, and functionality.
If your page uses third-party Elementor widgets, confirm that they work correctly in the Variant before launching your experiment.
If a widget doesn’t behave as expected:
  1. Confirm that it works correctly on the original page.
  2. Preview the Variant and reproduce the issue.
  3. Check whether the problem only occurs in the Variant.
  4. Review potential JavaScript, caching, or optimization conflicts.
If necessary, review JavaScript Conflicts, Cache Issues, or contact Bluvia A/B Testing Support.

Troubleshooting Elementor Experiments

If your Elementor Variant doesn’t display or behave as expected:
  1. Confirm that the original Elementor page works correctly.
  2. Preview the Variant.
  3. Check the affected widgets or functionality.
  4. Review whether caching is serving outdated content.
  5. Check for JavaScript conflicts.
  6. Review any performance or optimization tools that modify scripts or page content.
If you need to check the original page without the experiment running, pause the experiment first.
See the Troubleshooting section for additional guidance.

Related Articles

Continue with:

Tags: