Browse Help Center guides
Alerts and communication
Reports, branding, and scheduled delivery
Use web summaries, monthly or custom PDF reports, CSV exports, branding, and scheduled delivery safely.
What reports include#
Web report summaries and uptime metrics include enabled Uptime and Keyword monitors in the selected project and period. TLS, Domain, Heartbeat, and Sitemap monitors remain visible operationally but are not folded into web uptime percentages.
Open a report summary#
- Open Monitors for the intended project.
- Find Monthly web summary or Web report summary.
- Select Month or Range.
- Review the selected period and Data as of timestamp.
- Verify that the included monitor set matches the customer context.
Download a PDF#
Use Download PDF for an eligible plan and valid report period. The PDF is a customer-facing artifact, so review project name, branding, period, incidents, and explanatory context before sending it.
CSV exports#
Use CSV exports for detailed authenticated data. Summary and incident exports are the preferred long-term reporting artifacts. Raw monitor checks are retention-limited and may be unavailable or incomplete for older periods.
Report data windows#
Watchfox separates fast detection from long-term storage:
- Free raw web checks: 14 days.
- Paid raw web checks: 30 days.
- Medium history: 15-minute rollups where applicable.
- Long history: daily uptime summaries and incidents.
Do not interpret missing old raw rows as missing long-term report evidence when rollups, daily summaries, and incidents are available.
Branding#
Eligible plans can configure report branding. Use customer-safe names, logos, colors, and footer context. Preview European diacritics and long text before scheduled delivery.
Scheduled delivery#
Eligible plans can configure project-scoped monthly report recipients. Recipient limits and shared automation-email budgets are plan-aware. A quota-suppressed scheduled email is not a successful delivery and is not a Postmark failure.
Generated at and data as of#
Generated at describes when an artifact was produced. Data as of describes the latest data included in the summary. Use both when reviewing cache or timing questions.