Read the dashboard

The dashboard is your site’s daily view: how the site is doing, what routing gains on each page, and how each variant does. This guide reads it screen by screen; What the numbers mean explains the kinds of number behind it.

Find your way

Each view has an address you can share: app.routingcat.com/lumen is Lumen’s Home, /lumen/home its page home, and /lumen/home/hero:oneclick a variant, with @v2 after it for one of its versions. An id the command printed, pasted after the site’s key, opens its view.

The sidebar holds the site switcher, the site’s Home and settings, and its routed pages, with a dot on a page that needs you. At its foot, on a site you own, the plan’s meter counts this month’s visitors across your sites against your plan, with its most serious state in a few words; on Hobby, a line counts your live variants against the 10, and those held, and another your sites against the 3. A click on the meter opens Billing.
The account menu, at the sidebar’s foot, opens your Settings and Billing, and signs you out. Your Settings are yours, not a site’s: the sidebar stays on the site you were on.
Every figure is production’s, from the prepared results the command reads.
Visits and visitors are people’s. Automated traffic is left out of every count, and how much was left out is said once, beside it.
The theme follows your system by default. The switch at the sidebar’s foot picks System, Light or Dark in one click, and this browser keeps your choice.

Start from the onboarding screen

Before you have a site, the dashboard opens on an onboarding screen. It starts from a card per stack: pick “Astro on Vercel or Cloudflare”, and it teaches setup in five steps:

Open your site’s repository on your machine.
Start your coding agent there: Claude Code with its most capable model, or Codex or Cursor.
Paste it the request the screen gives, which runs npx routingcat init and finishes setup, or run the command yourself.
Sign in when the browser opens: your site appears.
Deploy the usual way: the setup checklist takes the screen’s place.

If you chose a plan on routingcat.com before signing up, the screen says when it applies: Pro’s trial, or Hobby, at the card’s step. Set up RoutingCat walks through the same steps.

Follow setup until a page is routed

Until a page is routed, Home shows setup’s checks in doctor’s order, each with when it passed or what to fix, under the next step to take.

On Hobby without a card on file, a step asks for one: “Add a card to start routing”, with nothing charged, or “Start your 14-day Pro trial”, the plan you chose at sign-up first. Routing starts within about 2 minutes of either: see Add a card to start routing.

Once a page is routed, a one-line banner heads Home, each page and each variant whenever your plan needs attention. On a site you own, it speaks for all your sites: it says what happens to routing, draws a bar of what it counts, and gives you the way out: “Upgrade to Pro”, “Add a card” or “Raise the cap”. A member sees it only while the site’s routing is held off or one of its variants is held, without the owner’s figures, and is told to ask the owner.

Amber, on Hobby, from 80% of the 10,000 visitors across your sites in a month, or from your 9th live variant. You can hide it for a week, in this browser.
Red, once your sites are past 10,000 visitors on Hobby or a variant is held, while routing waits for a card, or when the plan turned routing off, Pro’s cap included. It stays until its cause ends.

The sidebar’s meter takes the same colors. Plans, billing and emails says what each state does to routing.

Check how your site is doing

Home’s head reads “Live” when a visit came in the last 15 minutes, and “Not recording” when RoutingCat’s middleware, or on Cloudflare its Worker, has recorded nothing for hours.

Under it, a strip lists what needs your attention, most serious first: errors, a page whose measured gain lies wholly below zero, routing turned off, a failed payment, warnings, then notices. Each row says what to do, and Messages explains every warning.

The site’s figures

The site’s counted figures lead, over the date range, each with its change against the same number of days before and a trend line. Click one to draw it by day.

Figure	What it counts
Visits to your site	Each arrival of a person from outside, on any page, routed or not; coming back from a payment or sign-in page is the same visit
Conversions	Your main conversion’s events, on the day they happened. A menu picks another outcome you track.
Conversion rate	Conversions per visit to your site. Its change is in points.
Revenue	The value your tracked events carried, other currencies apart. It shows once an outcome carries a value.

A page’s figures count its own visits instead: each visitor once per visit, from their first view of that page.

Routed pages

Each routed page has a card; past six, the rest are rows of a table.

Measured gain, since the page went live: the extra conversions its routed visits produced over the control, with its 95% range, drawn green above zero and red below, on a scale all cards share. “98% matured” is the share of its visits whose window has closed. It is the only figure that counts as a gain, and pages’ gains don’t add up: see the measured gain.
vs control: the same gain, measured too, in percent of the conversions the routed visits would have made at the control’s rate. Its range can be uneven, and stays wide while the control has few conversions.
Conversion rate over the date range, routed against control, each point over the 7 days up to it, or since the range’s first day while the control is small. The space between the lines is green where routed visits convert better, red where worse, and grey until the measured gain has a range. Dashed days hold visits that can still convert, and a marker shows where a default changed.
Routed and control visits and conversions behind the measured gain, since the page went live, counted.
What routes now in each slot: the variant routing favors and the share of routed visits it intends for it, or “even split” for a slot whose fixed share is 1.

The rest of Home

Visitors this month: on a site you own, people on the routed pages of all your sites this UTC month: what your plan counts, with this site’s part marked in the bar and said in words, a projection at the month’s pace, and on Hobby your live variants against the 10 and your sites against the 3. A member sees this site’s own visitors, and the plan it is on. See Plans, billing and emails.
Where conversions come from: conversions by channel over the date range, as accounting: where they came from, not what caused them (sources).
Latest activity: the last visit, conversion and deploy, and when the estimates were last prepared.

Read a page

A page’s screen opens with its routes, its goal and the day it went live. Its first card sets routing against the control, since that day: the measured gain, with vs control, and the routed and the control conversion rates, each over visits whose window has closed, with the visits and conversions behind them. Below, three charts over the date range: the conversion rate, the measured gain as it stood each day, and visits by day. A range of one day gives its figures rather than a line.

Compare a slot’s variants

Below, a card per slot names its default and counts its variants live, held by the plan, paused and retired. “Code default” means your code still declares another default than the live one, as after a promote: make your code agree. The table sets the variants side by side, in two groups of columns: counted over the date range, then predicted for all visitors. Click a column to sort every slot by it. Under the table, “Share of visits over time” draws each variant’s share of the slot’s routed visits, the random slice included.

Column	What it shows	Kind
Share	Its share of the slot’s routed visits, with a tick at the share routing intends now	Counted
Visits, Conversions	Its routed visits and their conversions	Counted
Rate	Conversions over its visits whose window has closed: no fair comparison between variants, which routing shows to different visitors	Counted
Rate	Its predicted rate for all visitors, with its 95% range	Predicted
vs default	Its difference from the default, relative, with its range as a bar on the slot’s scale	Predicted
Signal	How much evidence backs the prediction: no bar for New, one for Early, two or three for Building, four for Strong	Predicted

A click on a row opens its variant, and the button at the row’s end copies the variant’s address, such as home/hero:oneclick.

A label beside the key says what routing is doing with the variant now, never a verdict (labels):

Favored: routing intends to show it most. It need not have the slot’s highest predicted rate, which is for all visitors: routing shows each variant to the visitors it predicts it converts best.
Starting estimate: no evidence of its own yet. “Same start” under vs default means it still starts where the default does.
At its cap, At its floor: a bound, yours or routing’s own, holds its share there.
Held by the plan: on Hobby, past the 10 live variants across the owner’s sites, it is registered and not served, so it gets no visits. It goes live once there is room: see held variants.

Look closer at a variant

A variant’s screen gives its row’s figures, then, over the date range from the day it was first served: its predicted difference from the default by day, with its range; its counted rate; its visits; and its share beside the slot’s others. Below are its declared content beside the default’s, and its versions, each with its commit message, what changed and when it was served.

Choose the date range

Choose the last 7, 28 or 90 days, all time, or days in the calendar, at the head of each screen; 28 days is the default, and your choice stays in this browser. All time starts at your site’s first record. In the calendar, pick the first day, then the last; the last is today unless you pick another, and a range ending today moves forward with the days. The first day comes before today, which is still counting. Apply sets it. Where a screen’s figures start later than the range, as for a page that went live since, it says from when.

The range covers whole UTC days up to yesterday. Today shows apart, as “Today so far”, and is never drawn, since a day half counted would read as a drop; a range ending before today leaves today out. Each figure compares with as many days just before; all time has nothing before it. Past 90 days, the charts of counts draw a point a week; a shorter first week stands apart.

The range sets every count. Predictions, labels and signal are always the latest, and the measured gain always runs from the day the page went live.

Check how fresh the figures are

“Up to date”, beside the date range, means the counts include everything production has recorded. “Updates in 26 min” means newer visits came in, and says when the next refresh adds them; the screen takes in each refresh without a reload. Counts refresh every hour, every 15 minutes on Pro; predictions follow each fit of the model, daily on Hobby and up to hourly on Pro; the measured gain once a day: see what updates when.

Read a grey or a missing figure

Grey means early evidence. A difference from the default whose signal is New or Early stays drawn in grey: read its range rather than its point. The space between the routed and control rates stays grey too, until the measured gain has a range.
A dash with a few words says why a figure is missing, such as “First figure Oct 15” or “No control visits yet”; hover for the full reason. None means zero: see when a value is missing.

Hand a request to your agent

“Copy for your agent” copies a short request for an analysis, naming the address, such as “In RoutingCat, analyze the hero slot of the home page (home/hero) over the last 7 and 28 days: each variant against the default, the newest first, and for whom each works. Then tell me what you’d do next.” Each page and slot has one: paste it to your coding agent, which reads the same figures through the command and says what it would keep, retire or try (Work with your coding agent). Acting stays your next message. When a page’s measured gain lies wholly below zero, its request asks your agent which variants do worse than the default and for whom, to propose better ideas, and to retire the worse ones once you agree.

Upgrade to Pro

“Upgrade to Pro” opens one dialog, for every site you own:

yearly, preselected at $80 a month beside the struck $100, or monthly at $100;
today’s charge, for the days to the next 1st, or the trial, which charges nothing for 14 days; then the price from the 1st; and the card on file;
one button: “Upgrade and pay … today”, “Start the 14-day trial” or, without a card, “Continue to Stripe”. If the quote changed while the dialog was open, nothing is charged and the dialog shows the new one.

Upgrade to Pro gives the terms.

Change your settings

The account menu opens your Settings, at app.routingcat.com/settings: they are yours whichever site you’re on, and open before your first site. Three tabs:

Account, your profile and sign-in, kept by Clerk;
Emails, the emails you choose, for each site you own or belong to, and product news once;
Billing, your plan for every site you own: the plan and its limits, the card on file, this month’s visitors, and on Pro the monthly cap. You upgrade, add the card and manage billing there. Billing counts only the sites you own: those you belong to are their owners’ to bill.

Plans, billing and emails covers Emails and Billing.

See the month by site

Billing draws this month’s new visitors by day as columns stacked by site, each site in its own color, the same on every screen. The list under the chart is its legend: each site’s visitors this month, its share of them, and on Hobby its live variants. Untick a site to take it out of the chart: the scale and the figures on hover follow, while the month’s count above stays your sites’ total. Every site shows again the next time you open Billing. With one site, the chart has one color and no list.

Read a site’s settings

Settings in the sidebar, under Home, opens the site’s own, at app.routingcat.com/lumen/settings:

The site: its key, production origin, Vercel or Cloudflare project and creation date, your role, and the plan it is billed on, with the way to Billing on a site you own;
Its routing settings, read only: the switch, the control’s share, the random slice and the visit’s length;
Each slot’s fixed share, floor, cap and personalization;
The domains its browser events are checked against, each with where it came from.

They change in your code and with npx routingcat set: see Routing settings.

Last, People lists who has access to the site: its owner, then its members, “Pending” marking a member until their first sign-in with the address you added. On a site you own, add a member by email, or remove one, each after a confirmation: see Access and keys.