Cohortum

What-If

Pick a goal event, nudge transition conversion rates, and watch the share of users reaching that goal move.

What-If turns your transition graph into a conversion simulator. Pick a goal event, then ask one question: if this transition converted better, how much would the overall share of users reaching my goal move?

It follows how users flow through the session transition graph toward your goal, then ranks every transition by how much leverage it has on getting them there. Spend your effort where it pays off instead of guessing.

When to use What-If

Reach for What-If when you know your goal event and need to decide where to invest. It answers the questions the Transitions graph can show you but can't put a number on:

  • Which single step, if you improved it, moves the goal the most?
  • Do you fix a high-volume transition that already converts well, or a small leak with huge leverage?
  • If you lift conversion on two steps at once, do the gains add up or cancel out?

Think of it as a planning tool, not a report. You're testing counterfactuals — "what would happen if" — not measuring what already did. Journey shows you the paths users already take; What-If lets you test paths that haven't happened yet.

Open What-If

What-If is its own analysis level, alongside Events Analysis and Sessions Analysis. It runs on session transitions.

Launch it from the sidebar
Click What-If in the left nav. Like the other analysis entry points, it opens in a new tab, so your current work stays put.
Pick a source and Build
You get the same left panel as Events and Sessions analyses. Pick a Source, dial in the Date range, Session range, or Filter to scope the simulation, and click Build. Cohortum computes the baseline chain and the per-transition leverage. The button reads Computing… while it works, and big sources take a moment.
Select your goal event
Click the Select target event pill at the top and search (the box reads Search events…). Once you choose one, the pill updates to Target: <event> — for example, Target: Checkout completed.

The left panel does more than it looks. Every filter reshapes the population the simulation runs on, so Baseline, Current, and the sensitivity coloring all shift the moment you scope to, say, mobile users or the last 30 days. See Filters and Session range for what each control does. Two controls from the standard panel are hidden here — the Path window and the Cluster filter kind — and the Events list is read-only: you can filter on events, but you can't rename or exclude them from inside What-If.

Until you pick a target, the canvas just shows a prompt: "Choose a goal event above to see which transitions move users toward it." Nothing computes without a goal.

What-If workspace showing the transition graph with edges shaded by sensitivity and the Impact on target panel on the right
Edges are shaded by Sensitivity; the right panel tracks Baseline, Current, and the delta as you edit.

Read the sensitivity coloring

Set a target and the canvas draws your transition graph with edges colored by Sensitivity — Cohortum's name for per-transition leverage. The ramp runs from faint gray (low leverage) to brand blue (high leverage), with a Sensitivity legend at the bottom of the canvas.

A brightly colored edge is a high-leverage transition: nudge it up a little and a lot more users reach your goal. Faint edges barely move the needle, however busy they look. This is the fastest way to spot where to focus before you touch a single number.

Prune the noise

The Min users: N% pill hides low-volume transitions from the graph. Raise it to declutter a dense graph and keep the view on the paths enough users actually take. It's a display filter — it changes what you see, not the underlying model.

Measure the impact

The right panel, Impact on target, is your scoreboard. It shows three numbers:

MetricWhat it means
BaselineShare of users reaching the goal in the unedited graph.
CurrentShare reaching the goal after your edits.
ΔThe change, in percentage points (e.g. +3.21 pp).

Baseline never moves — it's your reference point. Current and Δ update every time you adjust a transition, so you always see the net effect of your scenario.

A low Baseline isn't a bug

If the target event is rare — or never reached at all for the current source and filters — Baseline can read very low or 0.00%. That's expected, not a broken build. Pick a goal that users actually reach, or widen your filters, to see meaningful leverage.

Edit a transition's conversion

Here's where the simulation happens. Click any edge to open the Edit conversion editor in the right panel.

Select an edge
Click a transition on the canvas. The editor shows the source → target events as colored chips.
Drag the slider
Set a new conversion rate on the 0–100% slider. The exact percentage shows to its right, and the Impact panel recomputes.
Stack more edits
Edits stack. Click another edge, adjust it, and the model layers the changes together — so you can test a combined scenario, not just one lever.
Right panel showing the Edit conversion slider for a selected edge and a Changes log listing old to new conversion rates
Every edit lands in the Changes log as old% → new%.

The Changes log

Every adjustment is recorded under Changes as old% → new%, so you always know what your scenario assumes. Before you touch anything, it reads: "Click an edge and adjust its conversion to see the effect on reaching the target."

Why there's no per-edit impact number

Edits interact — raise one transition and its siblings renormalize — so a fixed "this edit added X pp" would mislead you. The one figure you can trust is the cumulative Δ at the top of the Impact panel.

Reset your edits

Click Reset to defaults at the bottom of the panel to clear every edit and snap all transitions back to their measured rate. The button is disabled when you have no edits.

Warnings to watch for

Two guardrails can pop up. Both are expected on tricky graphs, not errors:

  • Stranded state — "These edits leave a state with no path to the target or exit — result withheld." Your edits created a dead end: users can land in a state they can never leave to reach the goal or exit. The result is withheld because it's undefined. Ease off the change or pick a different edge.
  • Ill-conditioned graph — "Graph ill-conditioned — leverage coloring suppressed." The math behind the sensitivity ranking couldn't settle on a stable answer, so Cohortum drops the leverage coloring rather than show you misleading colors. You can still edit and read the Impact panel.
What-If explores, it doesn't predict

A What-If scenario assumes the rest of the graph keeps behaving the same when one transition changes. Real users don't always play along. Treat the Δ as a prioritization signal — "this lever is worth chasing" — not a revenue forecast.

Save, share, and export

A What-If scenario is a first-class analysis. From the top toolbar you can:

  • Save it, so the target and every edit come back exactly as you left them. Saved scenarios show up on the Saved page with Whatif in the Level column.
  • Share link — copies an in-app link to a shared snapshot your teammates with source access can open.
  • Export as PNG — captures the canvas exactly as edited, scenario changes and all, for a slide or doc. The Reset button and zoom controls are stripped from the image.