Not to be confused with: this is about emailing people already enrolled in one of your Adventures. It's a separate system from bluerabbit.io's own waitlist emails on the marketing site. Different audience, different tool, so don't mix the two up when someone asks "did the email go out?"
What a Campaign Is
A campaign is a one-time email to some or all of the people enrolled in an Adventure, written once and personalised for each recipient with merge tags. You write and send it from Admin Tools → Email Notifications. Email has to be set up for the platform first: until a platform admin connects an email service in Sys Config, the page says Email isn't configured yet.
Who Receives It
Either All enrolled players, meaning everyone enrolled in the Adventure who has an email address (GMs and NPCs included), or Selected players, picked by hand from a searchable grid of avatar cards. There's no audience based on activity, such as "hasn't logged in lately", and no guild audience from here — for those, see Automatic Emails & Audience Rules below, or hand-pick the people.
Email Notifications works from inside a cohort too, and lists that cohort's own players — its campaigns, send log and CSV exports are entirely its own. You don't need to go through the template to reach a cohort's roster.
Want BLUERABBIT to email the right players automatically, on a schedule, without you composing anything? See Automatic Emails & Audience Rules.
Merge Tags
Click the tag buttons above the compose box to insert one, or type it directly:
- Player —
{{name}},{{first_name}},{{last_name}},{{email}} - Progress —
{{level}},{{xp}},{{bloo}},{{ep}},{{completion}},{{rank}},{{latest_achievement}} - Guild —
{{guild_name}},{{members}} - Adventure —
{{adventure_title}},{{start_date}},{{end_date}},{{today}},{{site_name}}
Write {{tag | fallback text}} to show something else when a value is blank — handy for a player who hasn't earned an achievement yet. Misspell a tag and BLUERABBIT tells you before the campaign sends, rather than mailing it out broken. Preview and "View the email" always show a real player's numbers, so you see exactly what a recipient will get. These tags work in the message, not the subject line, and they're separate from the {{ player.nickname }}-style tokens used in step content — see Personalising Text with Player Tokens.
Delivery You Can Trust
Pressing Send opens a live console that prints every address as it goes out, a few at a time. What's still pending is worked out from what has actually been sent, so nothing is lost if the tab closes or the connection drops — you can close the tab and come back, and BLUERABBIT picks up exactly where it stopped, so nobody is ever emailed twice. The campaign also waits under Unfinished Campaigns with a Resume Sending button.
Dry Run walks through the whole send without actually emailing anyone, so you can check your recipient list and content first. On behalf of lets you choose who the campaign appears to come from (name and reply-to), picked from a fixed list rather than typed freely.
A message that fails on a temporary error is retried automatically. Anything that still fails can go again with Retry failed, which never re-sends to people who already got it. Every campaign is listed under Past Campaigns, and the Send Log shows Target / Sent / Failed / Missing counts, with tabs to see exactly who's in each group, a CSV export per tab, and "View the email" for any recipient.
Good Use Cases
- Nudging players who've gone quiet: pick them from the grid. The Last Login column on the Players page tells you who they are.
- Announcing a new Tabi or chapter that just opened.
- A deadline reminder a few days before a milestone closes.
- A wrap-up or congratulations message at the end of the Adventure.
Who Can Send
GMs and admins. An NPC sees the page view-only: the campaign history and send log, but no Compose.
Where to go next: How to Send an Email Campaign.