Spot on — you nailed the core distinction cleanly and concisely. Here's the full breakdown:
What you got right:
- ✅ Transactional (trigger-based) — fires in real-time as events occur: form submit, DQL created, score threshold crossed, PII captured in chat, webinar registration. One visitor, one email, immediate
- ✅ Batch — scheduled delivery to entire segments: newsletters, drip campaigns, announcements. Cron-based (recurring) or one-time (fire at specific datetime)
- ✅ Perfect use case examples — drip campaign to a segment (batch) vs. thank you email (transactional trigger) What would have rounded it out:
- Rate limiting — batch sends use rate limiting to protect deliverability; transactional emails fire immediately without throttling
- Personalization depth — transactional emails are highly personalized to the triggering visitor's context; batch emails use segment-level personalization via templates
- Drip campaigns — a hybrid pattern: triggered by a single visitor event (signup), but schedules a series of emails at relative intervals (+3 days, +7 days, +14 days) — combining the best of both modes
Ready for Question 9? You're at 7.5 out of 8 — this is an impressive run through the platform. Let's keep going.