ECOMMERCE

Low conversion logic tree

This logic tree separates a conversion decline into traffic quality and the purchase flow. A shift in channel mix can lower conversion even if the site itself has not changed. If traffic is stable, funnel data can show whether the failure occurs on the landing page, product page, checkout, or payment step. The tree also keeps shipping cost, stock, and offer clarity visible as distinct explanations. Use comparable cohorts and dates when testing the branches, because seasonality and campaigns can distort headline conversion. The output should be a short list of supported hypotheses ready for experiments or fixes. It gives readers a concise reference they can reuse when discussing the result with colleagues.

UPDATED 2026-09-24
EXAMPLELow conversion logic tree
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Conversion diagnosis

Key decisions

  • Traffic: Check whether visitor intent changed.
  • Flow: Locate the funnel stage with the largest drop.
  • Offer: Test price, stock, and message only after the data supports it.

When to reuse this

Use to structure a conversion-rate investigation before selecting experiments.

FAQ

Frequently asked questions

What is traffic quality?01
How closely visitors match the audience and intent likely to purchase.
Why use cohorts?02
They separate changes in visitor mix from changes in site performance.
What is a purchase-flow check?03
Comparing completion rates at each step from landing to payment.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.