Marketing tools cannot access per-user activity
Only your backend knows what each user did this week. Marketing tools designed for uniform campaigns cannot generate per-user digest content without complex sync.
SaaS email template
Fire digest.weekly from a cron job with per-user activity data. else.events renders a personalised digest and sends it to each user — no marketing list required.
Only your backend knows what each user did this week. Marketing tools designed for uniform campaigns cannot generate per-user digest content without complex sync.
User A has 3 unread comments and 2 completed tasks. User B has different activity. Sending the same digest to everyone is noise.
Digest emails require a cron job to aggregate content and a separate email service to send. Keeping these in sync adds coordination overhead.
Syncing to a marketing tool before sending the weekly digest adds latency and a failure point.
Your cron job runs weekly, aggregates per-user activity and fires a digest.weekly event per user with their activity data in the payload.
Unread count, activity items, project summaries — included per user in the event payload. The template renders each user's unique digest.
Your backend fires events only for users who have weekly digests enabled. else.events sends for every event it receives.
Recipient data comes from the event payload. No sync, no import, no delay.
{{ user.name }}Recipient name for the greeting{{ data.week_start }}Start date of the digest period{{ data.week_end }}End date of the digest period{{ data.unread_count }}Number of unread notifications{{ data.activity_items }}Array of activity items — each with title, description and link{{ data.app_url }}Link to the app for the primary CTAPer-user content from your cron job, rendered by else.events and delivered without a marketing list.