Magento 2 A/B Testing for CMS Blocks without Third-Party Tracking
SKU: CMSBLOCKABTEST1
- serve variants of a CMS block at random
- count goals such as click, cart and order in your own database
- assignment in the browser, full page cache stays active
- adopt the winning variant with one click
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 A/B testing for CMS blocks: compare variants instead of guessing
With Magento 2 A/B testing from Mironsoft you pit two or more variants of a CMS block against each other, for example a hero banner, a promotional text or a notice in the cart. The module splits visitors randomly between the variants, counts views and goals in your own database and shows in the admin which version performs better. It needs no third-party tracking and runs with Alpine.js in the Hyvä theme. Magento 2 A/B testing is configured in a few minutes and can be started and stopped per store view.
Variants per block
A CMS block gets variant B, C or more, each one a separate piece of content with its own name.
Random assignment
Visitors are assigned by your split and see the same variant on later visits.
Measure goals
Goals can be a click on an element, add to cart, an order or a page view.
No third-party tracking
Views and goals go into your database, no data is sent to third parties.
Cache friendly
Assignment happens in the browser, so the full page cache stays effective.
Results in the admin
Views, conversions, rate and a significance hint per variant in one overview.
Why merchants test content in a Magento 2 shop instead of assuming
Whether the red or the blue button works better, whether a delivery promise in the header brings more orders or whether a short text convinces is rarely something you can tell by gut feeling. Many merchants therefore search for Magento 2 A/B testing, a way to test CMS content, or a solution without external services. External testing tools load extra scripts, charge ongoing fees and raise data protection questions.
With Magento 2 A/B testing everything stays in your own shop. You create variants, start the test, read the numbers after a few days and adopt the better version. Decisions then rest on real visitors rather than on opinions in the team.
Set up Magento 2 A/B testing: create variants per CMS block
For Magento 2 A/B testing you choose an existing CMS block in the admin as the original and add one or more variants. Each variant is a normal CMS block that you design in the usual editor or in the Page Builder. Delivery runs through the existing widget or layout call of the original, so you do not have to change any templates. A running test can be paused without losing data.
- Original plus any number of variants
- Design in the usual editor or Page Builder
- Pause and resume without losing data
Random assignment without cache problems
In Magento 2 A/B testing, a small Alpine script on the first visit picks a variant and remembers it in a cookie, so the visitor sees the same one on the next page. Because the server delivers the same page to everyone, the full page cache stays active. You set the share per variant and can leave part of the traffic out of the test entirely. Bots are not counted.
- Split freely adjustable, for example 70 to 30
- Visitors consistently see the same variant
- Bots and admin users do not enter the numbers
Define conversion goals and measure them yourself
For each test you set one or more goals: a click on a CSS selector, a product added to the cart, a completed order or a visit to a certain URL. The module counts impressions and conversions per variant and stores them in aggregated form. No IP addresses and no profiles are created. Whether the assignment cookie requires consent is for the merchant to check legally.
- Click, cart, order or page view as a goal
- Aggregated counting without personal profiles
- Legal review stays with the merchant
Read the results and adopt the winning variant
The Magento 2 A/B testing overview shows views, conversions, conversion rate and the difference to the original for every variant. A hint tells you whether the amount of data is enough for a reliable statement. With one click you adopt the winner as the new original and end the test. The numbers stay available as an archive.
- Views, rate and difference per variant
- Hint about how meaningful the data is
- Make the winner the original with one click
Where Magento 2 A/B testing helps in daily shop work
Typical cases where Magento 2 A/B testing helps merchants.
Home page hero banner
Two image messages or headlines run against each other. The variant with more clicks to the category stays.
Notice in the cart
A shipping cost notice in two wordings shows which version leads more customers to checkout.
Category introduction
Short text against long text: which leads to more product clicks?
Promotion block
Discount in percent against discount in euro. The test shows which presentation works better.
Magento 2 A/B testing: with and without the module
What Magento 2 A/B testing changes compared with gut decisions and external testing services.
| Topic | Without module | With Mironsoft CMS Block A/B Test |
|---|---|---|
| Decision | Opinion in the team | Numbers from real visitors |
| Data storage | External service or no measurement | Own database, no third-party tracking |
| Performance | Extra third-party scripts | Small Alpine script, full page cache stays active |
| Effort | Change templates and code | Variants as CMS blocks in the admin |
| Adoption | Rebuild by hand | Winner as the original with one click |
How we set up Magento 2 A/B testing for you
The process after you place the order.
Alignment
You name the blocks you want to test and the goals that matter for your shop.
Installation
We install the module, set up Magento 2 A/B testing for your store views and connect delivery to the existing block calls. After that Magento 2 A/B testing runs without changes to your templates.
First test
Together we create a first test with variants, split and goals.
Check
We verify assignment, cookie, goal counting and cache behaviour in the storefront.
Handover
Your team gets an introduction to results, pausing and adopting the winner.
Differentiation from scheduler, customer group blocks and reports
The CMS block scheduler switches content at fixed dates, and the CMS block customer group module shows blocks depending on the group. Both decide by time or group. Magento 2 A/B testing decides at random in order to compare two versions, and it measures the result. The advanced reports from Mironsoft analyse revenue, not variants.
All modules can be combined. Delivery uses Alpine.js from the Hyvä theme and loads no extra library.
No download, but personal setup
CMS Block A/B Test is not listed here as a ready-made download file to install yourself. The purchase is a commission: we contact you after the purchase, install the module in your shop and agree on goals, split and first tests together with you.
Frequently asked questions
Everything important about variants, measurement, data protection and how the purchase works.
How can I run an A/B test for a CMS block in Magento 2?
How is a visitor assigned to a variant?
Does it bypass the full page cache?
Which goals can I measure?
Is data sent to third parties?
When is a result meaningful?
Can I test more than two variants?
Does Magento 2 A/B testing work with Hyvä?
How does it differ from the scheduler and customer group blocks?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 A/B Testing – Mironsoft CMS Block A/B Test