Live data token

What it is#

A live data token is a placeholder in a brief template that gets replaced with a real, current value when the brief renders. Think of it as a typed template variable that knows where to fetch its value from a connected data source.

In SendBriefs syntax, tokens look like {{revenue.mom}} or {{traffic.organic_sessions}} — the bit before the dot is the data source, the bit after is the specific metric.

Why it matters#

Without live data tokens, an agency operator writes a sentence like:

"Revenue grew 18% month-over-month, driven by improvements in the paid funnel."

…and has to manually update the "18%" every month when the data changes. Copy-paste from a dashboard. Risk of typo. Risk of using stale data. Time-consuming.

With live data tokens, the sentence is written once as:

"Revenue grew {{revenue.mom}} month-over-month, driven by improvements in the paid funnel."

…and every render replaces {{revenue.mom}} with the current value. No copy-paste, no stale data, no typos.

What can be a token#

In SendBriefs, tokens can be:

• Metrics — single numbers ({{ga4.sessions}}, {{stripe.mrr}})
• Deltas — period-over-period changes ({{revenue.mom}}, {{retention.qoq}})
• Charts — auto-rendered visualizations
• Tables — rows from a query
• Strings — client-context info ({{client.name}}, {{period.label}})

Where tokens come from#

Tokens resolve against any connected data source — HubSpot, Stripe, GA4, GSC, Linear, Meta Ads, Google Ads, or a generic webhook for anything else. See Integrations for the full list.

In SendBriefs specifically#

Tokens are core to the block-based editor. You type {{ anywhere in a narrative block, and an autocomplete picker shows you the available tokens for the connected sources on the current client's workspace.