CRO · Behavioral research · VWO · GA4 · BigQuery

VWO A/B Test: Turning Product-Page Doubt into Purchases

Paid traffic was growing, but purchase conversion was not. Behavioral data showed that shoppers wanted delivery and return answers before adding a product to cart. I turned that evidence into a VWO experiment, validated the measurement end to end, and proved that reducing uncertainty could lift both conversion and revenue.

Company
Home & lifestyle retailer · anonymized
Test
Product-page reassurance
My role
CRO Strategist & Analyst
Platform
VWO Web Testing
VWO · Campaign reportTest completed
Primary metricPurchase conversion per exposed visitor
Variation wins
Probability to beat control98.7%
ExperienceVisitorsConv. rateImprovement
Control82,1643.42%Baseline
Variation B82,3083.91%+14.3%
Cumulative conversion rateControlVariation
Anonymized UI reconstruction · normalized data28 days · 164,472 users
Purchase conversion+14.3%

3.42% control vs 3.91% variation.

Probability to beat control98.7%

Primary business metric in VWO.

Revenue per visitor+11.6%

Validated against backend order value.

GuardrailsProtected

No material harm to AOV, refunds or speed.

The business problem

More shoppers reached product pages, but too few felt confident enough to buy.

Paid product-page sessions increased 24% quarter over quarter, while purchases rose only 2%. The team first suspected weak traffic quality. GA4 funnel data, Hotjar behavior and support questions showed a different issue: delivery timing, return terms and payment reassurance appeared too late in the journey.

That created a costly decision gap. Users were interested in the product, but they had to add it to cart or search the footer before they could answer the practical questions required to commit.

My Role

I owned the experiment from diagnosis to rollout: triangulating evidence, writing the hypothesis, defining metrics, building the VWO test, validating tracking and translating the result into a commercial decision.

  • Analyze GA4 funnels, Hotjar recordings and customer questions
  • Write the hypothesis and prioritization case
  • Define primary, secondary and guardrail metrics
  • Configure targeting, traffic split and variation in VWO
  • Run cross-device QA with GTM, GA4 and backend order checks
  • Read the result, recommend rollout and monitor realized impact

Experiment Workflow

01

Diagnose

Find the decision-stage friction in quantitative and behavioral data.

02

Hypothesize

Connect one observed problem to one expected behavior change.

03

Design

Define audience, experiences, metrics, guardrails and stop rules.

04

Build & QA

Configure VWO and verify exposure, events and orders end to end.

05

Run

Hold the 50/50 allocation for 28 days and two full business cycles.

06

Decide

Interpret primary impact, guardrails and implementation risk.

VWOVariation, targeting, allocation and experiment report
Google Analytics 4Funnel diagnosis and secondary behavioral metrics
BigQuery + SQLExposure-to-order validation and revenue reconciliation
HotjarRecordings, heatmaps and interaction evidence
Google Tag ManagerExperiment events and QA instrumentation
Backend ordersPurchase and revenue source of truth
Looker StudioDaily health and post-rollout monitoring
i

Portfolio-safe case. The retailer, products, volumes and monetary values are fictionalized. Percentages are normalized representative data. The research logic, experiment design, QA process and decision framework reflect the work performed. Interface screens are custom reconstructions, not production screenshots.

Evidence, not opinion

Three data sources pointed to the same hesitation.

The traffic was not simply “bad.” Users demonstrated product interest, then paused exactly where practical purchase information was missing.

GA4 journeyUsersStep rateChange
Product view
100%+24%
Shipping info open
61%+31%
Add to cart
14%+3%
Checkout start
7.9%+1%
Purchase
3.4%+2%
Hotjar recordings43%

Repeated information-seeking

In a coded sample of high-intent sessions, users opened shipping, returned to the CTA, then searched reviews or the footer before exiting.

Scroll heatmap18%

Critical policy content was rarely seen

Only 18% of mobile PDP visitors reached the delivery and returns content positioned below recommendations and reviews.

Support themes37%

Questions were about confidence, not features

“When will it arrive?”, “Can I return it?” and “Is payment secure?” dominated pre-purchase questions.

The key insight

The product page answered “Why this product?” but not “Can I safely buy it now?”

The fix did not need more persuasion. It needed to move delivery, returns and payment certainty into the moment of decision.

61%of high-intent users actively looked for shipping information before adding to cart.
Hypothesis & variant

Bring practical confidence into the purchase moment.

The test deliberately changed one decision mechanism. Product imagery, price, reviews, promotion and CTA copy stayed the same, so the result could be attributed to reassurance rather than a full redesign.

If we

show the delivery date, free-return window and payment reassurance beside Add to Cart

instead of hiding them in accordions and policy pages below the fold,

Then

more high-intent product-page visitors will add to cart and complete a purchase

because the immediate practical risks of buying will be resolved before commitment.

Measured by

purchase conversion per exposed visitor

with add-to-cart, checkout start and revenue per visitor as supporting evidence, plus AOV, refunds and performance as guardrails.

ControlExisting product page
50% traffic
Bestseller
★★★★★ 4.8 · 286 reviews

Textured ceramic table lamp

Warm light · Natural glaze · Linen shade

€96.00
0

Practical purchase information remains hidden until the user opens a lower-page accordion.

Variation BDecision-stage reassurance
50% traffic
Bestseller
★★★★★ 4.8 · 286 reviews

Textured ceramic table lamp

Warm light · Natural glaze · Linen shade

€96.00
Arrives Thu–FriOrder within 4h 18m
Free 30-day returnsSimple prepaid return label
Secure paymentCard, PayPal and Apple Pay
3

Three verified reassurance signals appear directly above the CTA without changing offer, price or product presentation.

01

Reduce information cost

No accordion, footer search or checkout step is needed to find basic purchase terms.

02

Resolve perceived risk

Delivery, returns and payment uncertainty are addressed at the precise decision point.

03

Preserve causal clarity

One focused module changes while product, price, promotion and CTA remain stable.

Experiment design & QA

A clean result required more than launching a variation.

The test plan defined who entered, what counted, which risks could invalidate the result and exactly when the team was allowed to make a decision.

PDP · Reassurance at purchase decisionCampaign setup · reconstructed
1Variations
2Audience
3Metrics
4Traffic
5QA status

Production experiment configuration

AudienceNew mobile visitors on eligible PDPs
URL targeting18 high-volume product templates
ExclusionsEmployees, QA, returning experiment users
Primary metricBackend-validated purchase
Control · 50%Variation B · 50%
Population164,472 unique users

Stable VWO assignment; one experience per user.

Duration28 full days

Two complete business cycles plus weekend coverage.

Allocation50% / 50%

Held constant after launch to protect comparability.

Decision rulePrimary win + safe guardrails

No shipping decision based on a secondary metric alone.

MetricDefinition / sourceRole
Purchase conversionUnique purchaser ÷ exposed visitors · backend order joined to VWO IDPrimary
Add to cartSuccessful add event after inventory validation · GA4Secondary
Checkout startFirst valid checkout view per exposed user · GA4Secondary
Revenue / visitorNet merchandise revenue ÷ exposed visitors · backendSecondary
AOV, refunds, LCPCommercial and experience health · backend + web vitalsGuardrail

Pre-launch QA

Launch was blocked until every critical check passed on staging and production.

Correct bucketingControl / B stable
No visual flickerMobile + desktop
One exposure eventGTM + DebugView
Purchase deduplicatedorder_id verified
Revenue reconciled±0.6% to backend
Sample ratio healthy49.96 / 50.04
01

No early winner calls

The report was monitored for health, not stopped when the uplift first appeared.

02

One primary decision metric

Secondary signals explained the mechanism but could not override purchase conversion.

03

Segments stayed exploratory

Mobile cohorts informed the next test; they were not used to manufacture a win.

Result & business decision

The variant won on purchases — and the economics held.

The experiment answered the original question. Reducing uncertainty at the CTA increased completed purchases, while revenue and operational guardrails showed no hidden trade-off.

Purchase conversion+14.3%

3.42% control → 3.91% variation.

Probability to beat control98.7%

Primary metric in the VWO report.

Revenue per visitor+11.6%

Backed by reconciled order revenue.

Incremental purchases+403

Observed within the normalized test sample.

How behavior changed

Supporting metrics moved in the expected sequence, strengthening the interpretation that reassurance reduced purchase friction.

Add to cart
Control
Add to cart
+9.8%
Checkout start
Control
Checkout start
+7.4%
Purchase
Control
Purchase
+14.3%
Decision

Ship Variation B

The primary metric won, the behavioral chain was coherent and no guardrail crossed its risk threshold.

Week 1Native build

Engineering rebuilt the module in the product-page component, removing dependence on the test layer.

Week 2Staged rollout

Traffic moved 10% → 50% → 100% with the same purchase and guardrail monitoring.

Weeks 3–8Realized impact

BigQuery and Looker Studio compared post-launch performance with the matched baseline.

Post-rollout validation

The shipped experience retained most of the experimental gain.

Across six weeks at full rollout, purchase conversion remained 9.4% above the matched pre-launch baseline after controlling for channel mix, device and promotion periods. Delivery-related support contacts also stayed lower, confirming that the change improved both conversion and clarity.