Sankey Diagram | Zyeon UI

status="ready" · 8 flows over 4 layers. “Visitors → Paid” skips two layers straight to the last column; “Activated → Refunded” is 12 of 10,000 (0.12%), about 0.26px at true scale — only minLinkWidth=2 keeps it visible.

Acquisition paths · last 30 days

10,000 sessions · 4 layers · 8 flows

Every flow in 10,000 sessions of traffic, from source to target, with its share of the total.
From	To	Value	Share	Note
Visitors (stage 1)	Signed up (stage 2)	4,200 sessions	42%	measured
Visitors (stage 1)	Bounced (stage 2)	5,500 sessions	55%	measured
Visitors (stage 1)	Paid (stage 4)	300 sessions	3%	skips 2 stages
Signed up (stage 2)	Activated (stage 3)	2,600 sessions	26%	measured
Signed up (stage 2)	Dormant (stage 3)	1,600 sessions	16%	measured
Activated (stage 3)	Paid (stage 4)	888 sessions	8.9%	measured
Activated (stage 3)	Free (stage 4)	1,700 sessions	17%	measured
Activated (stage 3)	Refunded (stage 4)	12 sessions	0.12%	measured

Stage, inflow and outflow for every node. Inflow equals outflow at every node that is neither a source nor an endpoint. Stage counts steps from a source; endpoints are all drawn in the last column whatever their stage, so the two can differ.
Node	Stage	Column	In	Out	Role
Visitors	1 of 4	1 of 4	0	10,000	source
Signed up	2 of 4	2 of 4	4,200	4,200	pass-through
Bounced	2 of 4	4 of 4	5,500	0	endpoint
Activated	3 of 4	3 of 4	2,600	2,600	pass-through
Dormant	3 of 4	4 of 4	1,600	0	endpoint
Paid	4 of 4	4 of 4	1,188	0	endpoint
Free	4 of 4	4 of 4	1,700	0	endpoint
Refunded	4 of 4	4 of 4	12	0	endpoint

status="empty" · a valid contract with no flows at all, told apart from loading and from a failed fetch.

Acquisition paths · last 30 days

No flows yet

Paths appear here once the first journeys are recorded.

status="loading" · a three-column skeleton, aria-hidden, no timers involved.

Acquisition paths · last 30 days

status="error" · the fetch failed; “Try again” shows up only when onRetry is passed, and clicking it flips to ready.

Acquisition paths · last 30 days

Couldn't load this diagram

The data source didn't respond.

imbalance="reconcile" (default) · Engineering takes 620 and spends only 560, Marketing takes 380 and spends 420. The gaps are drawn as two dashed flows: 620−560=60 into Unaccounted, 420−380=40 out of Unattributed. Without that step the underlying Sankey sizes each node by max(in, out) and draws a chart that looks perfectly fine.

Quarterly budget · reported figures

1,040 k · 3 layers · 8 flows

2 reconciled

Every flow in 1,040 k of traffic, from source to target, with its share of the total.
From	To	Value	Share	Note
Budget (stage 1)	Engineering (stage 2)	620 k	59.6%	measured
Budget (stage 1)	Marketing (stage 2)	380 k	36.5%	measured
Engineering (stage 2)	Salaries (stage 3)	500 k	48.1%	measured
Engineering (stage 2)	Tooling (stage 3)	60 k	5.8%	measured
Marketing (stage 2)	Ads (stage 3)	300 k	28.8%	measured
Marketing (stage 2)	Events (stage 3)	120 k	11.5%	measured
Engineering (stage 2)	Unaccounted (stage 3)	60 k	5.8%	reconciled, not measured
Unattributed (stage 1)	Marketing (stage 2)	40 k	3.8%	reconciled, not measured

Stage, inflow and outflow for every node. Inflow equals outflow at every node that is neither a source nor an endpoint. Stage counts steps from a source; endpoints are all drawn in the last column whatever their stage, so the two can differ.
Node	Stage	Column	In	Out	Role
Budget	1 of 3	1 of 3	0	1,000	source
Engineering	2 of 3	2 of 3	620	620	pass-through
Marketing	2 of 3	2 of 3	420	420	pass-through
Salaries	3 of 3	3 of 3	500	0	endpoint
Tooling	3 of 3	3 of 3	60	0	endpoint
Ads	3 of 3	3 of 3	300	0	endpoint
Events	3 of 3	3 of 3	120	0	endpoint
Unaccounted	3 of 3	3 of 3	60	0	reconciled
Unattributed	1 of 3	1 of 3	0	40	reconciled

imbalance="error" · the same non-conserving data, except it refuses to draw and names the shortfall.

Quarterly budget · reported figures

This flow can't be drawn

Flow is not conserved at 2 nodes: Engineering +60, Marketing −40.

cyclic input (Triage → Review → Rework → Triage) · a Sankey has to be acyclic, so the component detects the cycle and refuses; fed straight to the recharts Sankey it recurses forever and ends in “Maximum call stack size exceeded”.

Ticket workflow · with rework loop

This flow can't be drawn

Flow loops back on itself through Triage → Review → Rework. A Sankey needs a direction.

minLinkWidth=0 · with the floor off, width is strictly proportional to volume: the 0.12% “Activated → Refunded” above drops back to 0.26px and all but disappears — the number is still in the tooltip and in the sr-only flow table.

Acquisition paths · last 30 days

10,000 sessions · 4 layers · 8 flows

Every flow in 10,000 sessions of traffic, from source to target, with its share of the total.
From	To	Value	Share	Note
Visitors (stage 1)	Signed up (stage 2)	4,200 sessions	42%	measured
Visitors (stage 1)	Bounced (stage 2)	5,500 sessions	55%	measured
Visitors (stage 1)	Paid (stage 4)	300 sessions	3%	skips 2 stages
Signed up (stage 2)	Activated (stage 3)	2,600 sessions	26%	measured
Signed up (stage 2)	Dormant (stage 3)	1,600 sessions	16%	measured
Activated (stage 3)	Paid (stage 4)	888 sessions	8.9%	measured
Activated (stage 3)	Free (stage 4)	1,700 sessions	17%	measured
Activated (stage 3)	Refunded (stage 4)	12 sessions	0.12%	measured

Stage, inflow and outflow for every node. Inflow equals outflow at every node that is neither a source nor an endpoint. Stage counts steps from a source; endpoints are all drawn in the last column whatever their stage, so the two can differ.
Node	Stage	Column	In	Out	Role
Visitors	1 of 4	1 of 4	0	10,000	source
Signed up	2 of 4	2 of 4	4,200	4,200	pass-through
Bounced	2 of 4	4 of 4	5,500	0	endpoint
Activated	3 of 4	3 of 4	2,600	2,600	pass-through
Dormant	3 of 4	4 of 4	1,600	0	endpoint
Paid	4 of 4	4 of 4	1,188	0	endpoint
Free	4 of 4	4 of 4	1,700	0	endpoint
Refunded	4 of 4	4 of 4	12	0	endpoint