Email Communications & Blasts

Overview

The Communications module provides email templates, audience blasts, open/click tracking, unsubscribe handling, SES webhooks, and analytics—gated by email_blasts_enabled on events and Essentials+ subscription.

Purpose

Send targeted, trackable email campaigns to RSVPs, registrants, and module participants without external ESP juggling for basic workflows.

Who should use it

  • Marketing and comms teams
  • Event hosts sending reminders and updates
  • Compliance reviewing unsubscribe rates

Benefits

  • Blast editor with preview and autosave
  • Tracking pixels and link wrapping
  • Preference center
  • Analytics dashboard

Note: sms_reminders_enabled exists on events but email is the primary channel. SMS requires provider configuration and is supplementary (see vendor/talent SMS logging).

Action Path
Communications hub /communications/
Blast list /communications/blasts/
Create blast /communications/blasts/new/
Blast detail /communications/blasts/<pk>/
Preview /communications/blasts/<pk>/preview/
Analytics /communications/analytics/
Email preferences /communications/preferences/
Unsubscribe /communications/unsubscribe/<token>/

Prerequisites

  • Subscription: Essentials+ (communications tool key)
  • Event: email_blasts_enabled=True
  • Email provider configured (Resend/SES in environment)
  • Audience data from RSVPs/registrations/modules

Step-by-step — Send a blast

  1. Open /communications/blasts/new/.
  2. Select event and audience segment.
  3. Compose subject and body (HTML).
  4. Preview → verify merge fields.
  5. Schedule or send immediately.
  6. Monitor opens/clicks in analytics.

[SCREENSHOT: Blast editor]

Field descriptions

Field Description
Blast subject Email subject line
Body HTML Rich content
Audience RSVP, registrants, module cohorts
Tracking tokens UUID per recipient for open/click
email_blasts_enabled Event-level master toggle
sms_reminders_enabled SMS flag (secondary channel)

Business rules

Rule Detail
Unsubscribe Honored via token URL; stored preferences
Open tracking /communications/t/o/<token>/
Click tracking /communications/t/c/<token>/
SES webhook Bounce/complaint at /communications/webhooks/ses/
SMS Not sent from Communications hub — event flag enables module SMS helpers

Validation rules

  • Subject and body required
  • Valid audience selection

User permissions

Role Create blast View analytics
Host ✅ ✅
Staff ✅ ✅
Recipient ❌ Own prefs only

Workflow

flowchart LR Compose[Compose blast] --> Preview --> Send --> Track[Open/click tracking] Track --> Analytics[Analytics dashboard]

Examples

Reminder email: 48h before event to all attending RSVPs.

Sponsor update: Module-specific announcement (see sponsor/vendor announcement URLs).

Best practices

  • Send test blast to internal list first
  • Include unsubscribe link (auto-injected)
  • Avoid blast during check-in peak hours

Tips

  • Autosave: /blasts/<pk>/autosave/
  • Module announcements also in speakers/vendors/sponsors apps

Common mistakes

Mistake Result Fix
Toggle off Can't send Enable email_blasts on event
Expect SMS from hub Not supported here Configure SMS at event/module level

FAQs

Is SMS supported?
Flag exists (sms_reminders_enabled); email is primary. SMS logged/stubbed without provider.

Troubleshooting

Symptom Cause Fix
No sends ESP misconfig Check Resend/SES env vars
Zero opens Tracking blocked Normal for privacy-focused clients

Screenshot placeholders

  • [SCREENSHOT: Communications hub]
  • [SCREENSHOT: Blast analytics charts]
  • [SCREENSHOT: Unsubscribe page]

Administrator notes

  • Configure EMAIL_BACKEND and SES webhook signing
  • Monitor bounce rates in analytics

Developer/API notes

Route Purpose
track_open Pixel beacon
track_click Redirect wrapper
ses_webhook Delivery events

No public REST API for blast creation.

See also: Social Sharing & Hashtag Generator · Security & Privacy

Help home Back to Nigall