Interactive Email for Weekly Team KPI Recaps

An internal team recap doesn't need to be built from a blank canvas every week. Starting a new project as "Dashboard" drops in the Dashboard grid preset — three KPI scorecards over a bar chart, already laid out — with plausible example numbers standing in until you point each block at your own data source.

Subject

This week's team recap

Starting a new project as "Dashboard" drops in the Dashboard grid preset — three KPI scorecards over a bar chart, already laid out — the one-click starting point for a team's own weekly numbers recap.

A weekly internal recap shouldn't need to be rebuilt from a blank canvas every Monday.

One click, a full layout

Choosing Dashboard in the project purpose picker seeds a heading, three KPI scorecards, and a bar chart in one step, followed by a footer — a real starting layout, not a blank project.

It ships with example numbers, not live data

The seeded scorecards and chart hold plausible literal numbers as authored rows — they aren't bound to anything automatically. Restyle the labels to match what your team actually tracks, then connect a real source once you know it.

Rebind once, reuse every week

Each KPI/bar chart's Inspector has a Bind to data section — connect it to a real data source or a past campaign's response results, and the same block keeps pulling current numbers on every send from then on. See Binding charts to real data for the full picker.

Put it on a weekly cadence

A weekly recurring schedule re-renders the whole recap against current data on every run, so the team gets a fresh version without anyone rebuilding it by hand — see Automated performance digest emails for the same mechanism applied to a fuller, more customer-facing report.

Getting started

Start a new project as Dashboard, restyle the three KPI labels and chart title to match your team's numbers, then bind each block to your real data source once you know it.

A typical build-and-send sequence

1
Start a new project as "Dashboard"
The purpose picker's Dashboard topic seeds the KPI-row-plus-bar-chart layout — the Dashboard grid preset — in one click, followed by a footer.
2
Restyle it to match your team's numbers
It's a starting point, not a finished report — swap the three KPI labels and the chart's title for whatever your team actually tracks.
3
Rebind each block once you know your source
Each KPI/bar chart's Inspector "Bind to data" section connects it to a real data source or a past campaign's response results, replacing the seeded example numbers.
4
Put it on a weekly recurring send
A weekly recurring schedule re-renders the whole recap against current data on every run, so the team gets a fresh version without anyone rebuilding it.

Blocks built for this

Frequently asked questions

Is the Dashboard grid preset bound to real data automatically?

No — it ships with plausible literal example numbers as authored rows. You connect and bind each block yourself once you know which data source or past campaign the recap should track.

Can I use the preset without starting a whole new project?

The Dashboard grid preset itself is what "Start as Dashboard" seeds automatically; the same KPI-row-plus-chart shape can also be composed manually in any existing project by adding a KPI scorecard and bar chart yourself.

How is this different from a general automated performance digest?

Same underlying blocks and binding mechanism — the difference is just the starting point: Dashboard grid is the one-click preset for a team's own internal recap, where a fuller automated digest (see the related guide) is built around wiring live data bindings from scratch for a more customer- or leadership-facing report.

Can only some team members see certain numbers?

There's no per-recipient field-level masking within a single KPI or chart block — whatever it's bound to renders the same for every recipient of that send, unless you scope with a chart filter referencing merge tags or send a different audience segment separately.

Does sending this weekly cost more on our plan?

It counts as an ordinary send against your plan's monthly volume — there's no separate metering for analytics blocks or recurring schedules beyond the normal send cap and the account-wide schedule count limit.

Related docs

Build this in the studio

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

Start building free See all use cases