Skip to main content
Use a recurring report when the same audience needs the same decision-ready view on a predictable schedule. Start with the decision the report should support, then choose the smallest set of metrics that answers it.

Define the report

  • Audience: who reads it and what they decide.
  • Scope: accounts, channels, campaigns, products, or markets.
  • Period: reporting window and comparison.
  • Metrics: primary outcome and supporting diagnostics.
  • Cadence: when the report should run.
  • Delivery: where the configured workflow should send or store the result.

Starting request

Verify the first run

  • Confirm the connected accounts and filters.
  • Check the reporting window, timezone, currency, and comparison.
  • Verify that every metric has a clear source.
  • Confirm the destination and who can access it.
  • Read one completed run before depending on the schedule.
A scheduled report is only as current as its connected sources. A delayed sync can change what is available when a run starts.
Manage cadence, delivery, and run history in Workflows. If you deliver through Slack, review Slack.
Last modified on August 7, 2026