Skip to main content

Why can't I enable A/B testing on my bundle?

A/B testing requires the bundle to target all products and to have been saved. Both conditions must be met before variants can be created.

Written by Eddie Lavandera

A/B testing needs one thing: the bundle must have been saved at least once. Until then the A/B test tab shows a banner instead of the controls. Save the bundle and the tab becomes available.

In this article:

Save the bundle first

  1. Open the bundle.

  2. Select Publish Bundle, or Save as draft if you are not ready to go live.

  3. Wait for Bundle saved successfully!

  4. Reopen the A/B test tab and select Enable A/B testing.

A variant is a copy of the bundle, so there has to be a stored bundle to copy. That is the whole requirement.

The banner on an unsaved bundle

A/B testing is disabled, Select all products and save the bundle to create A/B testing variants

ℹ️ A bundle targeting specific products or specific collections can be tested exactly like one targeting all products. Only the save matters.

If it is still disabled after saving

  1. Reload the page. The tab reads the bundle's saved state, which can be stale after an edit.

  2. Confirm the save succeeded. If you saw Error saving bundle or Bundle validation error. Please check all fields., the bundle was not saved. Fix the field and save again.

  3. Check you are on the main bundle, not a variant. Variants do not have their own test tab.

  4. Confirm your subscription is active. A/B testing needs an active Atlas subscription, and active subscription is required will block related actions.

Still disabled? Start a chat from the bubble in the bottom right of Atlas, or email support@helloatlas.io. Include your store URL and the bundle name.

Next steps

Related Articles
Did this answer your question?