Product: Product Page
Hypothesis
If we test a similar change on our product pages as rejected, we should be cautious
Test Results
Key Learning
Problem: Users on the product need validation from others before committing — without visible proof of success, they hesitate.
What was tried: rejected this UI change (Aug 21, 2024). Rejection suggests the change underperformed the control
Why it failed: Social proof isn't universally positive — the wrong type, amount, or placement can feel manipulative or irrelevant.
How to Apply This to Your Site
This test showed that product: product page hurt conversions. The change was tested on a product page page in the e-commerce industry. Avoid replicating this exact approach — instead, consider testing the opposite direction or a more subtle variation.
Before you test: Consider that social proof tests typically require adequate traffic to reach statistical significance. Run your test for at least 2 full business cycles to account for weekly traffic patterns.
What Was Tested
Fails To Replicate 's Customer Reviews Banner. This leak shows what tested on their product pages.
Methodology
Build On These Learnings
Save your own experiments, spot winning patterns across your test history, and stop repeating what's already been tried.
Related Experiments
Product: Social Counts
Problem: The registration experience on the product asks too much too soon, causing potential users to drop off.
Checkout: Customer Star Ratings
Context: Users on the checkout need validation from others before committing — without visible proof of success, they hesitate.
Checkout: Testimonials
Context: Users on the checkout need validation from others before committing — without visible proof of success, they hesitate.
Product: Benefit Testimonials
Context: Users on the product need validation from others before committing — without visible proof of success, they hesitate.