About this block

Sync Volume Chart proves connectors with throughput. Records per day run as shadcn bars across a week, weekend dip left in, beside the two freshness facts integration buyers actually check, median sync lag in seconds and the success rate. The copy frames the category honestly, a connector is a promise about freshness.

Built on ui/chart, the data wires to real pipeline metrics. The weekend dip plays the same authenticity role as every honest dip in this collection, traffic shaped like business is traffic that happened.

When to use

Reach for this block on integration pages beneath the directory blocks, integrations-grid-tiles says what connects, this says how well. Data products and reverse ETL adjacent tools especially, their buyers think in lag seconds.

A natural flow around it on a Marketing Pro page:

Before

• Integration directory blocks establishing breadth

After

• Status sections for the reliability layer beneath
• Developer CTAs for builders convinced by the lag number

What you can display

One strong use is sync throughput with freshness facts. Other charts:

• Webhook delivery. Events per day with delivery lag for an event driven product.
• Import volume. Migrations processed weekly for a switching heavy product.
• API traffic. Requests served with error rate as the companion fact.

Tip: lead with lag, not volume, integration buyers fear stale data more than small pipes.