> ## Documentation Index
> Fetch the complete documentation index at: https://docs.instantcampaign.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduled reports

> Email a branded weekly or monthly performance report, with a PDF and a link your client can open without logging in.

**Scheduled reports** (**Analytics → Scheduled reports**, or **Schedule a report** on the analytics page) send a summary of how your email, website and ads performed to up to ten people — usually a client, your manager or your own team. Each report arrives as an email with the PDF attached and a link to an online copy that opens without an InstantCampaign login, so it can be forwarded.

Every number in a report is the number the analytics dashboard shows for the same dates. Nothing is calculated a second way.

## Create a report

<Steps>
  <Step title="Name it">
    For example "Acme — weekly email results". The name is the report's title and the email subject.
  </Step>

  <Step title="Pick how often">
    **Weekly** (choose the day), **Monthly** (choose a day from 1 to 28) or **Manual only**, and the hour it goes out. The hour is in your workspace time zone (Settings → General).
  </Step>

  <Step title="Add recipients">
    Up to 10 addresses, one per line. Recipients do not need an account. A report with no recipients can still be created and opened from its history.
  </Step>

  <Step title="Choose the sections">
    Email performance with a daily chart, campaigns, automations, website traffic and channels, conversions and attribution, advertising, deliverability health and audience growth. The preview on the right updates as you tick them.
  </Step>

  <Step title="Narrow it (optional)">
    Limit the email sections to one source, campaign or automation. **Schedule a report** on the analytics page carries over the filters you had applied there. Website traffic and conversions always cover the whole workspace.
  </Step>

  <Step title="Brand it">
    The logo and accent colour come from your [brand kit](/guides/sending-and-workspace/brand-kit). Agencies can add a **Prepared by** line. Pick the report language, or leave it on the workspace default.
  </Step>
</Steps>

## Which period a report covers

| Frequency | Period | Compared with |
| - | - | - |
| Weekly | The previous full week, Monday to Sunday | The week before it |
| Monthly | The previous calendar month | The equally long span just before it |
| Manual only | The last 30 full days, ending yesterday | The 30 days before them |

The days are the analytics days (UTC), exactly as the dashboard counts **From**–**To**, so opening `/analytics` with the same dates shows the same totals and the same changes.

## Send now

**Send now** renders the report for its period and emails it straight away, whether or not it is scheduled. The run appears in **History** within a few seconds and shows when it has been handed to the mail provider. Up to 10 manual sends per workspace per hour.

## History, links and PDFs

Every run keeps the PDF and the online copy exactly as they were sent, so last month's report still reads the same next quarter. From the history you can open the online copy, copy its link or download the PDF.

The online link does not expire. Deleting the report deletes its history and turns every link it has sent off. If your workspace uses a [custom endpoint domain](/guides/sending-and-workspace/workspace-settings), links use that domain.

<Note>
  The PDF uses the standard PDF fonts, which print Latin-alphabet text. A report written in Japanese is emailed and shown online in Japanese, and its PDF is printed in English. Names containing characters outside the Latin alphabet print a "?" for those characters in the PDF only.
</Note>

## Who can do what

* Anyone who can see analytics can see reports, their preview and their history, and download the PDFs.
* Creating, editing, deleting and sending reports needs workspace administrator rights — the same people who can export analytics.

## Ask Spark

Spark and the MCP server can list your reports (`list_reports`) and read a run's headline numbers and link (`get_report_run`). They never send a report; that stays on this page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.