Real traffic against the test set, cluster by cluster. Sample data: eight request clusters, full refunds 31% of traffic and 38% of the set, partial + coupon 14% and 0%.
Installation
- 1
Set up the registry once
Your token in .env and @chartory in components.json. Skip this when another chart is already installed.
Installation guide - 2
Add the chart
One command adds the Traffic vs set component to your project.
npx shadcn add @chartory/traffic-vs-set - 3
Use it
Pass your rows. The props are the Figma properties.
usage.tsximport { TrafficVsSet } from "@/components/chartory/traffic-vs-set"<TrafficVsSet data={clusterShares} size="m" legend/>
Props
<TrafficVsSet>
Every prop but data is a Figma property with the same name and values.
TrafficVsSetData
The data prop: one object for the whole chart.
TrafficVsSetRow
One object per entry in rows.
The data as a JSON Schema: schemas/traffic-vs-set.json
Traffic vs set chart: a React and Figma chart in four sizes
What does a traffic vs set chart show?
A traffic vs set chart puts each cluster's share of production traffic next to its share of the test set. The cluster flagged as a gap is shaded, and a set share below traffic turns warning. Use it to keep a golden set in line with real use.
Chartory ships it as a Figma component and a React component with the same name. The code installs from the shadcn registry with one command and lands in your project as a file you own.
What is the Traffic vs set component?
It is one <TrafficVsSet> component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is two shares per cluster, an optional gap or under flag.
Sizes XS, S, M and L re-lay the chart out from the data instead of scaling it, so labels stay readable at every size.
When should I use it?
- Are two shares compared per cluster? Yes means the traffic vs set fits.
- Is the share the point? Yes means the traffic vs set fits.
- Is it a list of clusters? Yes means the traffic vs set fits.
When does another type fit better?
- One share per cluster. Use Horizontal bars instead.
- Case counts on a map of traffic. Use Coverage map instead.
- Two values per item, any kind. Use Dumbbell instead.
Traffic vs set questions
Installing, data, Figma and plans.
Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.
Add your token and the @chartory registry once, then run npx shadcn add @chartory/traffic-vs-set. The Installation guide has the steps.
Yes. Connect the Chartory MCP server and ask for the traffic vs set chart; the agent runs the same command and you review the diff.
Two shares per cluster, an optional gap or under flag. The sample data comes with the component, and the props table lists every field.
XS, S, M and L, in Figma and in code. Each size is laid out again from the data, so text and lines keep their size.
Yes. chart/119-traffic-vs-set has the same properties as the component.
Yes. Every paint is a token, so the chart follows light and dark mode and the collection you pick.
Code and Complete. Figma has the Figma file only.