Do price framing A/B tests work on product pages?

Worse here than elsewhere. Price framing tests win 8% of the time on product pages, against 13% across all page types. The category is not the problem; this page is.

It is not the best use of a test slot on this page either. Headline tests win 18% on product pages on 100+ tests.

Small sample. Few of these tests cleared the bar. The 95% interval on that win rate runs 3% to 21%, so read the figure as directional.

The numbers

	product pages	all page types
Tests analysed	38 tests	100+
Beat control	8%	13%
No measurable difference	79%	—
Lost to control	13%	—
Median lift when it won	not reported	—

Median traffic per variant was 3117 visitors.

What else is worth testing on product pages

change type	win rate on product pages	tests
Headline	18%	100+
Styling	14%	250+
Body copy	9%	100+
Split URL	9%	100+
Social proof	8%	50+
Price framing (this page)	8%	38 tests
Layout	6%	50+
CTA copy	6%	48 tests

Only change types with at least 30 tests on product pages appear here.

What counts as a price framing test

The number stays the same; the presentation changes. Per-day instead of per-month, annual instead of monthly, fee broken out instead of rolled in, anchor shown or hidden.

Control and variant wireframe for a price framing A/B test — Control on the left, variant on the right. For how this differs from adjacent categories, see the price framing benchmark.

Price framing tests that won on product pages

CTA/price copy offering a plan priced with a discount noted
Adds a Save X discount label next to the sale price and restyles the price box layout and sizes

Price framing tests that did not

In the cart drawer, hides the original price element and strips the original total label while showing the discounted total with strikethrough styling
In cart drawer, hides the original pre-discount price element, shows the compare-at price with the original total label removed and strikethrough styling applied
Adds VAT labels next to prices and relocates/renames the wishlist link to Save for later, plus adds USP text for a specific product

These are individual tests, not rules. Each ran on one site, with one audience, against one page we are not showing you. They are picked to be illustrative rather than sampled at random, and a change that won here can lose on your page for reasons none of this captures. Read them as prompts for what to test, not as findings to copy.

Who ran these tests

This is every Mida account that ran a readable test — in-house marketers, founders, product teams, and agencies working on client sites. Nothing here is filtered by who ran the experiment or how experienced they are.

Low win rates are normal in experimentation, including at the top end. Microsoft's experimentation team, reporting on its own platform, found that only about one third of ideas improve the metric they were designed to improve — and that roughly another third actively hurt it. That is a dedicated experimentation organisation with research, prioritisation and review behind every test.

A mixed population like this one runs below that. The gap is roughly what disciplined practice buys you: ideas grounded in research rather than opinion, one variable at a time, and tests built so the result can actually be read.

So treat these as a general base rate, not a target. If you would rather not close that gap the slow way, find a CRO agency in the United States, the United Kingdom, the Netherlands or Australia — or browse every region.

A win is a variant that beat its control on that test's primary goal with a statistically significant result. Tests that never got enough traffic to say anything either way are excluded. The methodology has the full detail, including what these numbers cannot tell you.