Monthly Reports

Customer monitoring reports are generated for a selected client. Open Clients, choose the client, and use Generate report now, Report history, and Report subscribers on that client's detail page.

What a client report contains

The report covers the previous calendar month. Its assets are selected by both workspace and client ID; its alert summary includes alerts associated with those assets during the period. It includes SSL and DNS observations, check and alert counts, and upcoming certificate expiries. Available crawl-health data may also appear.

Health observations reflect the data available when the report is generated. Do not describe them as a complete historical snapshot of the last day of the month. Assets monitored during the period can still appear after monitoring is paused.

Workspace-wide vendor alerts without an asset association are not included in this client report. Vendor stack tags do not establish client impact. If you add vendor context to your own delivery email, confirm its relevance to that client's services first.

Generate and inspect a PDF

1. Open Clients and select the intended client.
2. Under Generate report now, click Generate previous-month report.
3. Open Open PDF, or select View PDF in Report history when rendering is complete.
4. Check the client name, period, domains, included assets, and branding before sharing.

Generating a report manually refreshes the previous-month report; it does not email subscribers. There is no customer Reports → Monthly period picker or Reports → Schedule screen for choosing arbitrary months or delivery dates.

The PDF link is a public sharing link: anyone holding it can open the report while the link is valid. The generated link has a 180-day lifetime. Removing a subscriber stops future scheduled delivery to that address; it does not revoke a PDF link already sent or a downloaded copy.

Monthly email delivery

Under the selected client's Report subscribers, an owner or admin can add recipient addresses or remove subscribers. Start with an internal agency reviewer and inspect a generated report before adding client recipients.

The monthly run generates the previous month's report and sends active subscribers an email with a View the report link and an unsubscribe link. It does not send a PDF attachment. The subject identifies the client and reporting period. A client with no active subscribers receives no report email.

Check Report history for the PDF and email status. Generation, rendering, and delivery can fail independently; a generated entry is not proof that an email reached every recipient. This workflow does not offer a first-business-day guarantee or a customer-configurable delivery schedule.

Branding and sharing

On-demand reports use your workspace name and remove Merlonix report branding when the white-label add-on is enabled, or when an eligible report credit is used. The scheduled monthly renderer currently uses the standard Merlonix branding. Preview the actual PDF rather than assuming that scheduled and on-demand output have identical branding. See white-label pricing.

Only share a report after checking that its contents belong to the intended client. Do not forward workspace-wide exports or combined agency summaries as though they were a single-client report.

Monthly and quarterly business reports

The separate monthly business report and quarterly review are operator-only business reporting, not customer monitoring reports. They are not a tenant-wide PDF delivery option for agency clients. The customer workflow described above is the per-client monthly report; there is no equivalent customer quarterly-report scheduler.

API access

Authenticated members can list a client's reports with GET /v1/clients/:id/reports. Owners and admins can generate the previous month's report with POST /v1/clients/:id/reports/generate and manage recipients under /v1/clients/:id/report-subscribers.

The client must belong to the signed-in workspace. The previously documented /v1/reports/monthly routes are not customer report endpoints. See API Integration Reference for authentication.

Next: read Client Status Pages for public status links, or Alert Channels for workspace-wide notifications.