Keep users in the loop

Digest emails that summarise what actually matters to each user

Weekly activity summaries, unread notification roundups, project digests — fired by your backend on schedule, personalised per user from the event payload.

Why digest emails are hard to get right

Digest content is per-user, not per-list

A weekly digest for user A contains different activity than for user B. Marketing tools designed for uniform broadcasts struggle with this.

Generating digest content requires your backend

Only your backend knows what each user did (or did not do) this week. Marketing automation has no access to that data without complex syncing.

Unsubscribe handling must not break transactional sends

Digest emails are notification emails, not newsletters. Mixing them with marketing unsubscribe flows creates compliance risk.

Per-user frequency preferences are complex to encode

Some users want daily digests, others weekly, others none. Encoding that in a marketing tool requires fragile contact field setups.

Your backend generates the content. else.events sends it.

Fire a digest event from a scheduled job

A cron job collects activity for each user and fires a digest.weekly or digest.daily event with the summary in the payload.

Per-user content in the payload

The event payload carries the personalised content: unread count, recent activity items, project updates. The template renders it.

Respect user frequency preferences

Your backend decides whether to fire a digest event for a given user based on their preference. else.events handles the email for every event it receives.

Separate from marketing sends

Digest emails are routed through else.events, not through your marketing list. No unsubscribe mixing, no contact sync delay.

Frequently asked questions

Does else.events handle the scheduling for digest emails?
No. Scheduling is your backend responsibility — typically a cron job that runs once a day or week and fires a digest event per user. else.events handles the email from each event it receives.
How do I include a list of activity items in the digest email?
Include the list as an array in the event payload data. Your template iterates over it to render each item.
Can some users get daily digests and others weekly?
Yes — your backend controls which events to fire per user. Users who prefer daily digests receive a digest.daily event; weekly users receive a digest.weekly event. Different templates or different event types handle the frequency variation.
How do I handle users who opt out of digest emails?
Your backend should not fire digest events for opted-out users. else.events sends for every event it receives — opt-out logic lives in your application.

Digest emails that users actually want to open

Per-user content from your backend, rendered by else.events and delivered through your provider.

  • Free during public beta
  • Per-user personalisation via payload
  • No marketing list mixing