Interactive Email for Automated Performance Digests

Most "weekly numbers" emails are a screenshot of a dashboard, stale the moment it's pasted in. Binding a KPI scorecard or chart directly to a connected data source means the block's own value comes from your real rows, and a recurring send re-renders it fresh on every run — so a Monday digest actually reflects Monday's numbers.

Subject

This week's performance digest

Bind a KPI scorecard or a bar/line chart to a real data source, and a recurring send re-renders the whole digest against your current numbers on every run — a "weekly numbers" email that's actually current, not a screenshot pasted in once and forgotten.

The usual performance digest is a dashboard screenshot dropped into an email — stale the second it's exported, and someone's manual job every single week.

Start from the Dashboard preset

Starting a new project as Dashboard seeds a heading, three KPI scorecards and a bar chart in one click. It's a starting point with plausible example numbers, not a finished report — you restyle and rebind from there.

Bind blocks instead of typing numbers

Four of the thirteen analytics blocks — KPI scorecard, bar chart, line chart, and pie chart — can pull from a connected data source or a past campaign's response results, instead of rows typed by hand. Each has its own Bind to data section in the Inspector: pick a binding, a group-by field, and up to three series fields with an aggregate each. See Binding charts to real data for the full picker.

Scope it per recipient, if you need to

A bound chart's optional filter can reference the recipient's own merge tags — {{team}}, {{region}} — so the same block shows each recipient their own slice of the same underlying source rather than the whole account's numbers.

It's a snapshot, refreshed on your schedule

The mailed HTML is static at render time, exactly like every other block — a bound chart doesn't keep updating after it's sent. What makes the digest feel live is the cadence: a recurring send re-renders the whole email against your data source's current rows on every run, so each week's copy is genuinely current even though any one copy is fixed.

Getting started

Start a project as Dashboard, connect your data source from the Data panel, bind each KPI scorecard and bar chart to it, then put the project on a weekly recurring schedule.

A typical build-and-send sequence

  1. 1

    Start from the Dashboard purpose

    Starting a new project as "Dashboard" seeds a heading, three KPI scorecards and a bar chart in one click — a starting point to restyle and rebind, not a finished report.

  2. 2

    Connect a data source

    Add a collection-role binding to your metrics data source from the studio's Data panel — the same binding a repeat block draws from.

  3. 3

    Bind each block instead of typing numbers

    Each KPI/bar/line/pie chart's Inspector has a "Bind to data" section — pick the binding, a group-by field, and up to 3 series fields with an aggregate (sum, average, count, or latest row) each.

  4. 4

    Send it on a recurring cadence

    A recurring schedule re-renders the whole email against your data source's current rows on every run, so each digest carries real, current numbers without anyone rebuilding it by hand.

Frequently asked questions

Which chart types can bind to a live data source?

Four of the thirteen: KPI scorecard, bar chart, line chart, and pie chart. The other nine (scatter, histogram, heatmap, funnel, waterfall, gauge, radar, treemap, sankey) are authored-rows only today — you'd update those by hand.

Does a bound chart keep updating after the email is sent?

No — mailed HTML is a static snapshot at render time, the same as every other block. A recurring send re-renders with fresh data on each run, so each individual digest is current when it goes out, but a copy already sent won't change afterward.

Can different recipients see a different slice of the same data?

Yes — a chart's optional filter can reference the recipient's own merge tags (like {{team}} or {{region}}), so the same block shows each recipient their own team's numbers rather than the whole account's.

Can I show results from a past campaign instead of a data source?

Yes, as a separate binding mode — pick a campaign and one of its polls, ratings, or scored questions instead of connecting a data source. That mode is the one exception where the number keeps updating live on the hosted live-view page as more responses come in, unlike a data-source binding.

Do I need a developer to set this up?

No coding — connecting a data source and binding a chart's fields are both done from the studio's Inspector panels. An API-connected data source (fetched server-side from your own endpoint) is the option that needs an existing API on your end; a manually maintained hosted data source needs none.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.