Configure value routes

Mark the routes that are experiment targets — activation, revenue, onboarding completion, or other product outcomes a canary measures.

Value routes are experiment targets: they tell TrueClara which outcome metric a randomized canary should measure, and they let the reward verdict price its lift in ±$/day.

Choose routes

Good value routes are routes that prove a user reached a meaningful outcome:

/checkout/success
/signup/success
/onboarding/complete
/app/[workspaceSlug]
/upgrade/confirmation
/bookings/confirmed

Avoid broad routes such as /, /pricing, or /dashboard unless reaching that route is itself the outcome.

Configure them

Open project settings and add route patterns separated by commas or new lines.

Text

/checkout/success
/signup/success
/onboarding/complete

Use the route pattern from Map or the Routes table, not a single raw URL with an id embedded in it. For example, use /projects/[id], not /projects/123.

How they affect experiments

Signal	Effect
`target_metric`	A value route can be registered directly as an experiment's target metric (see the Reward API).
`value_at_risk`	When `value_per_conversion` is set on a value route, the verdict prices lift as `±$/day`.
Guardrail severity	Raises priority when a broken URL sits on a route that leads to a marked outcome.

Validation checklist

The value route appears in the parsed graph.
The route receives real production traffic.
The route is specific enough to represent completion.
Production and staging have separate project settings.

If no value routes are configured, TrueClara can still report broken URLs and run experiments against generic traffic metrics, but verdicts cannot price value_at_risk and guardrail priority stays generic.