Configure value routes
Mark the routes that represent activation, revenue, onboarding completion, or other product outcomes.
Value routes tell TrueClara which outcomes matter. They are used to prioritize observations and to calculate value-reach regression signals.
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.
/checkout/success
/signup/success
/onboarding/completeUse 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 observations
| Signal | Effect |
|---|---|
| Route regression | Measures how often sessions that visit a route later reach any value route. |
| Edge regression | Prioritizes transition drops that make value-route reach less likely. |
| Severity | Raises priority when a regression blocks activation, checkout, or other marked outcomes. |
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 traffic health, but route and edge regression priority will be generic.