Skip to main content
A scheduled report is the client report on a clock. Once a week or once a month, every address you name receives a short email with the period’s headline numbers and a link that opens the full report without an account. Nobody has to remember to send it. Schedules live on the Reports page, under the share links, in the Scheduled reports section. Owners and admins create and manage them; members and viewers can see them. Because a schedule mails the workspace’s numbers to people outside UTMKit, it needs the same plan feature as the client report, which is included in some plans — see the plans page.

​
Creating one

1

Choose the cadence

Press Schedule a report. Pick Week (Monday to Sunday) or Month (a calendar month). A monthly report needs a plan that keeps at least a month of history.
2

Pick the reader's time zone

The zone decides on which day a week or a month has ended for the people reading it. The numbers themselves are counted in UTC days, like the report page, and the mail says so.
3

Name the recipients

One email address per line. Recipients need no account; a client’s people are the usual case, and members of the workspace are welcome too. There is a cap on addresses per schedule and on schedules per workspace, and the page names it if you reach it.
The first mail goes out after the next full period ends: a weekly schedule created on a Wednesday sends its first report the following Monday. Each recipient gets their own mail and never sees the other addresses.

​
What the mail says

It is plain text, sent from UTMKit’s address with your organization’s name as the sender. The subject names the workspace, the cadence and the period. The body says:
  • who sends it and for which workspace;
  • the period, its total clicks and unique visitors, and the change in clicks against the previous week or month when there is one;
  • the period’s conversions, and their value when they share one currency;
  • when automated visits were left out, the same sentence the client report uses;
  • a link to the full report, opened on that period;
  • a link to stop receiving it.
A period with no clicks still sends, and says so plainly. If the numbers could not be read at the moment of sending, the mail says that too, and the link still works.

​
Pausing, editing, removing

Each schedule row shows its cadence, its next send date, when the last one was queued and whether it was delivered, and the recipients. Four buttons sit beside it.
  • Pause stops the sends; the row says paused. Resume starts again with the next full period — the periods it slept through are not sent.
  • Edit changes the cadence, the time zone or the recipients. The list at the moment of sending is the one used.
  • Delete removes the schedule. The report links in the mails it already sent stop opening, so this is also how to make old mails inert.
A schedule can also stop on its own, and the row says why: the plan lost the feature, the subscription ended, the custom domain it mailed links on was removed, or every recipient opted out. It resumes by itself when the reason clears, with the next period that ends.

​
Recipients can stop it themselves

Every mail carries a stop link. It opens a page naming your organization and the workspace, with one button; pressing it removes that address at once and confirms it. Only opening the link changes nothing, so a mail scanner cannot opt a client out by accident. An address that opted out is struck through on the schedule and cannot be added to this workspace’s schedules again. Addresses the mail provider bounced, or that complained, are marked the same way. Creating, editing, pausing, resuming and deleting a schedule, and every opt-out, are recorded in the activity log.