SaaS email template

Weekly digest email — per-user activity summary from your backend

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.

Why weekly digests are hard to personalise

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.

Digest content differs for every user

User A has 3 unread comments and 2 completed tasks. User B has different activity. Sending the same digest to everyone is noise.

Scheduling is separate from sending

Digest emails require a cron job to aggregate content and a separate email service to send. Keeping these in sync adds coordination overhead.

Contact list sync delays digest delivery

Syncing to a marketing tool before sending the weekly digest adds latency and a failure point.

Cron job generates content — else.events sends per user

Fire digest.weekly once per user from a cron job

Your cron job runs weekly, aggregates per-user activity and fires a digest.weekly event per user with their activity data in the payload.

Per-user content from the payload

Unread count, activity items, project summaries — included per user in the event payload. The template renders each user's unique digest.

Respects user preferences

Your backend fires events only for users who have weekly digests enabled. else.events sends for every event it receives.

No contact list or marketing tool

Recipient data comes from the event payload. No sync, no import, no delay.

Template variables for the weekly digest email

  • {{ 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 CTA

Frequently asked questions

How do I handle users who have no activity to report?
Your cron job should skip users with no activity or explicitly-opted-out users. Do not fire the event for them. else.events sends for every event it receives — the filtering is in your backend.
What subject lines work for weekly digest emails?
"Your [App] week in review — 3 updates waiting", "Weekly summary: what happened in [App] this week", "[App] weekly digest — [user first name]'s activity". Include activity count for open rate.
Can I send both weekly and daily digests?
Yes. Use two separate event types — digest.weekly and digest.daily. Create separate rules and templates for each in else.events.
How do I include a list of activity items in the digest?
Include an activity_items array in the event payload. Each item should have a title, description and link. Your MJML template iterates over the array to render each item.

Weekly digest emails that users actually open

Per-user content from your cron job, rendered by else.events and delivered without a marketing list.

  • Per-user content from the event payload
  • Fire from a cron job — no marketing list
  • Respects user notification preferences