Skip to main content
How Can We Help?

Avada

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

 

How Avada Works With Bluvia A/B Testing

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

 

Which Tests Open in Avada?

Avada opens when the Test Type allows you to edit the full content of an Avada-built page or post.
Other Test Types provide their own editing experience directly within Bluvia A/B Testing.
The following tests do not open Avada:
  • 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 Avada before returning to Bluvia A/B Testing.
To save and return:
  1. Save the changes you’ve made to the Variant in Avada.
  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 Avada’s save action.
Always save your changes before selecting Back. Otherwise, changes made in Avada 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 Avada.

 

What Can You Change?

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

 

Editing an Avada 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 Avada-built page or post you want to test.
  4. Create your Variant.
  5. Open the Variant for editing.
  6. Make your changes using Avada.
  7. Save your changes in Avada.
  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 Avada Variant before starting the experiment.
Check that:
  • Content displays correctly.
  • Images and media load.
  • Buttons and links work.
  • Containers and layouts 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.

 

Avada Elements and Other Plugins

Avada and other WordPress plugins can provide elements with their own scripts, styles, and functionality.
If your page uses these elements, confirm that they work correctly in the Variant before launching your experiment.
If an element 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 Avada Experiments

If your Avada Variant doesn’t display or behave as expected:
  1. Confirm that the original Avada page works correctly.
  2. Preview the Variant.
  3. Check the affected elements 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: