Schedules and Reports
Each aggregator has one schedule. When it comes round, Eventkiwi builds a report from the events collected since the last one and sends it to every channel connected to the aggregator.
Schedule types
You pick the schedule when you create or edit an aggregator.
| Schedule | You choose | Example |
|---|---|---|
| Hourly | The minute past the hour | Every hour at :15 |
| Daily | Time and timezone | Every day at 08:00, Europe/Berlin |
| Weekly | Day of the week, time and timezone | Mondays at 09:00, America/New_York |
| Monthly | Day of the month, time and timezone | The 1st at 07:30, UTC |
Times are worked out in the schedule's own timezone, so a report set for 08:00 in Berlin arrives at 08:00 Berlin time on both sides of a daylight saving change.
What a report covers
A report covers the events received since the previous report was delivered. Once it has gone out, the counts start again from zero for the next period.
Each report contains:
- A written summary at the top: a sentence or two on whether the period was good, bad or normal, and which events moved. It looks at the last few reports to judge what's normal, and takes the calendar into account, so a quiet Sunday or a public holiday in your timezone's region is called that rather than reported as a drop.
- Event counts, each with the change against the previous report.
- A trend line per event: a sparkline in email, a grid of trend charts in Telegram.
- Tag breakdowns under each event. See Event Tags.
Email and Telegram show the report slightly differently; see Delivery Channels.
Report options
Two options sit under the schedule in the aggregator form:
| Option | Default | What it does |
|---|---|---|
| Send empty reports | Off | Send a report even when no events arrived in the period. When off, an empty period is skipped silently. |
| Humanize event names in reports | Off | Show user_signup as "User Signup" in reports. Events are stored under the name you sent either way. |
Delivery guarantees
- Each report goes out once. A due schedule is claimed before anything is sent, so two overlapping runs cannot send you the same report twice.
- Nothing is lost if delivery fails. If no channel accepts the report, the period's counts are kept and included in the next report. If at least one channel receives it, the period is closed.
- Unreachable Telegram chats are stopped, not retried. See Delivery Channels.
Past reports
Every delivered report, including its written summary, is listed on the Reports page in the app.
Next Steps
- Delivery Channels - Get reports by email or in Telegram
- Sending Events - Start sending events to your aggregator