Reports & Diagnostics
Review protection evidence, export CSV, and create a merchant-safe support packet.
Protection reports
Open Reports to review the last 7, 30, or 90 days of monitoring evidence. The report summarizes checks, availability, incidents, downtime, and estimated revenue at risk when revenue inputs are configured.
Per-monitor rows help you identify the paths that fail most often or carry the weakest evidence. A monitor with no current result is shown as pending or stale instead of being counted as healthy.
Download CSV
Select a reporting window and choose Download CSV. The export uses the same shop-scoped evidence as the report and is useful for incident review, operational reporting, or analysis in a spreadsheet.
Check the selected window
The on-screen report and downloaded CSV should use the same 7-, 30-, or 90-day range. If you change the range, regenerate the export before sharing it.
Diagnostics
Open Diagnostics when you need to verify whether the installed app, monitors, alert routes, and Fire Drill are ready. The page separates application health from protection coverage so a healthy service is not mistaken for a fully configured account.
The activation checklist includes:
- current monitor evidence;
- a connected email route;
- a successfully accepted email Fire Drill;
- deployed application and worker health;
- the build identifier used for support correlation.
Copy a support packet
Choose Copy diagnostic summary and paste the result into a support request. The packet is designed to omit target URLs, credentials, request headers, and customer data.
Before sending it, include:
- what you expected to happen;
- the approximate time and your timezone;
- the affected monitor or route name;
- a response request ID, when one is available.
Never include API tokens, Shopify credentials, webhook secrets, or OAuth authorization codes.
Was this page helpful?

