checkout_started
Shows whether offer packaging is clear.
Do not read without checkout_success and refund_rate.
price without trap
Pricing tests
How to test packaging, tiers, add-ons, gifts, and membership without pressing user fear.
Price should explain value and boundaries, not promise a miracle for more money.
average_order_value
Average order value without worsening expectation quality.
Higher order value with higher refunds is not a win.
refund_rate
The main pricing guardrail.
Every pricing test must manually inspect refund reasons.
Write the hypothesis
Formula: if we change X for audience Y, metric Z will move because a specific friction disappears.
- There is one main changed element.
- There is one primary metric and one guardrail metric.
- There is a pre-written decision after the test.
Launch quietly
Start with a small traffic share or one segment, especially when testing payment, email, trust, or beginners.
- The test can be turned off without deploy chaos.
- Events are logged without private questions or scroll text.
- Support knows what changed.
Read the result
Do not declare a winner from one day. Check device split, traffic source, complaints, refunds, and behavior quality after payment.
- The result is compared with baseline.
- The guardrail did not worsen.
- The outcome is written into the experiment log.
experiment cards
- Three tiers versus guided 'recommended for your question' card.
- Add-ons shown after answer versus before checkout.
- Gift reading sold as credit versus sold as named product.
rollback rules
- Stop if refunds rise or support sees guarantee expectations.
- Stop if the expensive tier sounds like a more powerful fate.
output
- Pricing decision with revenue, refund, support, and trust notes.
- Updated pricing page and FAQ if the test wins.
red flags
- Price is tied to fear of losing love, money, or the future.
- The cheap option is intentionally described as weak or incomplete.
related doors