Setting Up A/B Testing
A/B testing in ConversionWax lets you compare two versions of a banner to determine which one performs better. Traffic is automatically split between the two versions, and detailed metrics help you make data-driven decisions.
Requirements
A/B testing is available on the Growth plan and above. Starter plan users will need to upgrade to access this feature.
Enabling A/B Testing on a Banner
Open the banner you want to test in the banner editor.
Toggle the Version A/B switch to enable A/B testing.
This creates two complete banner sets - Version A and Version B.
Configure each version with its own image assets, click URLs, and alt text for all breakpoints (desktop, tablet, mobile).
How Traffic Splitting Works
Once A/B testing is enabled and the banner is published, ConversionWax automatically splits traffic between Version A and Version B. Each visitor is randomly assigned a version, ensuring a fair comparison between the two variants.
Tracking Performance
The analytics dashboard provides detailed metrics for each version:
Clicks - Total click events per variant.
Page Loads - How many times the page containing the banner was loaded.
Renders - How many times each banner version was actually displayed to visitors.
Per-Device Breakdown
Metrics are broken down by device type, so you can see how each version performs on desktop, tablet, and mobile separately. This helps identify cases where one version might win on mobile but underperform on desktop.
Analyzing Results
Navigate to the Analytics tab for your banner.
Use the date range picker and time granularity controls (5-minute, hourly, or daily) to focus on the period you want to analyze.
Compare Version A and Version B side by side in the summary cards and trend charts.
Look for statistically meaningful differences in click-through rates before declaring a winner.
Tips for Effective A/B Tests
Test one variable at a time - change the image, headline, or CTA, but not all at once.
Let tests run long enough to collect sufficient data before drawing conclusions.
Use the device breakdown to catch performance differences across screen sizes.
