• ANALYTICS AND A/B TESTING • SETUP GUIDE

How to Configure Design Variants for A/B Testing

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Compare Shopify registration form design variants using the form’s A/B testing JSON settings.

Before you begin

Select the form and reporting period you want to inspect. Use a known storefront visit and application as a test, and keep visit, submission, approval, and sales counts separate when interpreting results.

Design variants use the Advanced JSON setting

A/B testing splits visitors between design/theme variants using the configured percentage. Each visitor keeps the assigned variant. The setup is a JSON settings box, not a visual editor.

Only use keys shown by the current in-app schema/example. Keep application questions and approval policy stable when evaluating a design change; this feature is not documented as a way to run different approval rules or arbitrary JavaScript.

Set up this workflow

  1. Open the form Settings and select Advanced.

  2. Find A/B testing and review the current Variants JSON example and schema guidance.

  3. Define design-only variants using the supported keys shown by the app.

  4. Set the intended percentage split and check that the JSON is valid.

  5. Save and visit the form in separate test sessions to check the rendered variants.

  6. Review variant views and submissions in Analytics after real traffic accumulates.

Example

Create two button-color variants using only keys shown in the current in-app JSON example and a 50/50 split. Keep questions unchanged.

Expected result

Different test sessions can receive the configured design variants, while the same visitor keeps a consistent variant.

Limits and important behavior

  • A/B testing uses a JSON settings box rather than a visual editor.
  • It covers design/theme changes, not different approval policies or arbitrary JavaScript.
  • Visitors keep seeing their assigned variant.
  • Use documented JSON keys rather than copying an unverified configuration.

Troubleshooting and verification

If no valid variants appear, inspect the JSON syntax and supported design keys in the current app settings. The experiment changes design, not approval policies or questions. Test the saved allocation and variant appearance before comparing performance.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “How to Configure Design Variants for A/B Testing” after completing the setup. Show the controls used to open the form Settings and select Advanced. Add a second screenshot showing the result of this check: Review variant views and submissions in Analytics after real traffic accumulates. Use dummy applicant details and mask any secrets.

Related guides