Issue Tree: Why Did Our Website Conversion Rate Drop?

A ready-made issue tree. Open it in Razn and fill it with your numbers.

Open this tree in Razn

Free during beta · no card needed

A conversion drop triggers redesigns, new copy and A/B tests, often before anyone checks whether the traffic changed or the tracking broke. This tree splits the drop into four branches: who arrives, what they see, what we offer and whether we measure it correctly. Check each branch by channel and device. Most drops trace back to one change, such as a new traffic source, a slower page or a broken form.

Why did our website conversion rate drop?

  1. Did the traffic change?

    • Did the mix shift toward lower-intent channels or campaigns?
    • Did mobile share grow on pages built for desktop?
  2. Did the experience get worse?

    • Did page speed, forms or checkout break or slow down?
    • Did a recent site change move or hide the main call to action?
  3. Did the offer get weaker?

    • Did price, shipping or trial terms change?
    • Did a competitor offer something better?
  4. Is the measurement wrong?

    • Did tracking tags, consent banners or attribution change?
    • Are bots inflating the session count?

How to use this tree

  1. Confirm the root question and who makes the call. If they would phrase it differently, rewrite it first.
  2. Put a number on each branch with data you already have. A rough figure beats a long debate.
  3. Cut the branches that explain little, so the effort goes where the gap is.
  4. Write the answer first: one sentence with the main driver and what you will do about it.

Going further

Your problem is a bit different? Describe it and Razn builds the tree for you.

Structured with Razn → try free