Schedule and deliver reports

A Report setup can be generated manually or automatically on a schedule. You can also configure Integration settings when another system should receive or process generated report data.

Content of this page

Manual generation vs scheduled generation

Use manual generation when you want an immediate report instance, for example while testing a new setup or checking an ad-hoc question.

Use scheduled generation when the same report should be created repeatedly, for example every day, week, or month.

  • Manual generation is useful for testing and one-time analysis.
  • Scheduled generation is useful for recurring reporting workflows.

Configure the schedule

Open the Report setup editor and find the Schedule section. Choose the schedule that matches how often the report should be generated.

Depending on the available options for your setup, schedules can include intervals such as hourly, daily, weekly, or monthly.

[screenshot: Schedule section in the Report setup editor]

Choosing a schedule

  • Use an hourly schedule only when the report needs frequent updates.
  • Use a daily schedule for operational checks and short feedback loops.
  • Use a weekly schedule for recurring team reviews.
  • Use a monthly schedule for broader performance summaries.

The best schedule depends on how often the underlying data changes and how often someone will act on the result.

Check the report before relying on the schedule

Before you rely on a scheduled report, generate or inspect a report instance manually. Check that each report block answers the intended question.

  1. Confirm the setup title and query titles are understandable.
  2. Confirm the measured events are in the right order.
  3. Confirm Include only filters are not too narrow.
  4. Confirm breakdowns create useful rows.
  5. Confirm row limits and sorting make the result readable.

Integration and webhook delivery

The Integration section is setup-level configuration. Use it when generated report data should be delivered to another system or processed by an integration workflow.

The Integration section can include:

  • A webhook URL.
  • An authorization header or similar secret needed by the receiving system.

Webhook URL

The webhook URL identifies where Keytiles should send or make report data available for the integration. Use the endpoint provided by the system that will receive the report.

Authorization header

If the receiving system requires authentication, enter the required authorization header. Treat this value as a secret.

When editing an existing setup, the secret may be masked. If you do not want to change it, leave it unchanged according to the editor behavior.

Integration via Reporting API

Check our Reporting API contract. Using this you have full control over managing / executing / querying reports.

Scheduling and Integration work together

Scheduling controls when report instances are generated. Integration controls how generated report data can be delivered or consumed by another system.

For example:

  • A weekly campaign report can be generated every Monday and delivered to an internal data workflow.
  • A daily content performance report can be generated every morning and consumed by a dashboard process.
  • A monthly summary can be generated automatically and archived by another system.

Troubleshooting scheduled reports

If a scheduled report does not produce the expected result, check the setup in this order:

  1. Is the Report setup disabled?
  2. Is the schedule enabled and set to the intended interval?
  3. Do the queries produce useful results when generated manually?
  4. Are Include only filters too narrow for the scheduled period?
  5. If using Integration, is the webhook URL still correct?
  6. If using Integration authentication, is the authorization value still valid?

When debugging, simplify first: confirm the report generates correctly without relying on the delivery workflow, then check Integration.