Documentation

Scheduled reports

Configure recurring email, CSV, and PDF analytics delivery for stakeholders.

1 min read/10 sections

Scheduled reports keep analytics reviews consistent without asking every stakeholder to open the dashboard.

Choose a report scope

Pick overview, page views, referrers, SEO insights, or a white-label client report depending on who receives the report.

Operators usually need page-level reports with tables and deltas. Executives usually need summary metrics, top pages, trend changes, and the most important AI insight. Client-facing recipients should receive branded white-label summaries with only the relevant workspace data.

Select the cadence

Daily reports are useful during launches. Weekly reports suit operating reviews. Monthly reports work for leadership summaries.

Choose recipients carefully and keep the subject line specific. A report called "Weekly docs engagement" will be easier to act on than a generic analytics digest.

Review failures

Delivery failures are logged and visible in notifications so owners can fix recipients or provider configuration.

If a report fails, check Resend configuration, recipient syntax, workspace permissions, export generation, and R2 upload status. The dashboard should show the last error so the owner can correct the next run without digging through logs.

Was this helpful?

Feedback is stored anonymously so documentation can improve with real reader signals.

API keys and webhook signatures

Create scoped API keys, call workspace endpoints, and verify signed webhook deliveries.

Widget installation

Install the Notion Analytics tracking widget and verify events.

Operational guidance

Use this resource alongside the dashboard, widget studio, API settings, and onboarding flow to keep the analytics setup accurate as your Notion workspace changes.