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.
Keep users in the loop
Weekly activity summaries, unread notification roundups, project digests — fired by your backend on schedule, personalised per user from the event payload.
A weekly digest for user A contains different activity than for user B. Marketing tools designed for uniform broadcasts struggle with this.
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.
Digest emails are notification emails, not newsletters. Mixing them with marketing unsubscribe flows creates compliance risk.
Some users want daily digests, others weekly, others none. Encoding that in a marketing tool requires fragile contact field setups.
A cron job collects activity for each user and fires a digest.weekly or digest.daily event with the summary in the payload.
The event payload carries the personalised content: unread count, recent activity items, project updates. The template renders it.
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.
Digest emails are routed through else.events, not through your marketing list. No unsubscribe mixing, no contact sync delay.
Per-user content from your backend, rendered by else.events and delivered through your provider.