Skip to Content
Email Campaign Builder

Email Campaign Builder

Use Hub -> Admin -> Email to manage hub email settings and send custom campaign updates.

Who Can Use It

  • OWNER and ADMIN can create, send, schedule, and export campaigns.
  • MANAGER access depends on your current role policy and permissions in the hub.

For full role boundaries, see Roles and Permissions.

Email Studio

Use this when you want to build and send a real hub email.

It is best for:

  • Event reminders,
  • Logistics updates,
  • Community announcements,
  • Targeted follow-ups to members, ticket holders, or waitlists.

Workflow

Step 1: Audience and Context

  1. Select an event when the audience or footer links need event context.
  2. Choose one or more audience segments and filters.
  3. Use Preview Audience to verify count, skipped recipients, suppressions, and sample recipients.
  4. Check the Readiness health card for sender identity, policy, tracking, and suppression signals.

Step 2: Message Content

  1. Set subject and optional preheader.
  2. Add hero image and choose placement.
  3. Build content using Visual Builder blocks (for example heading, paragraph, list, divider, image, button, event card).
  4. Use Campaign templates to save a whole campaign layout or apply a saved one.
  5. Use style controls for spacing, fonts, alignment, and button appearance.

Configure optional campaign actions:

  • Primary CTA button,
  • Secondary links (My Tickets, View Event, Open Hub, custom URL),
  • Alignment and display order.

Step 4: Review and Deliver

  1. Save draft.
  2. Use Refresh Exact Preview and Send Campaign Test.
  3. Send immediately with Send Now or set a date/time to schedule.
  4. Open Campaign History for the Scheduled send command center, delivery actions, HTML viewer, and CSV exports.

Autosave and recovery

Email Studio keeps a local recovery copy of unsaved composer edits in your browser. This is not a server save and does not change Campaign History until you click Save.

If you reload or navigate away with unsaved edits, the composer can show a recovery banner when you return. Use Restore to bring back the local copy, or Discard to keep the server-saved campaign state.

Campaign templates

Campaign templates save the reusable parts of a campaign:

  • Subject and preheader,
  • Message blocks,
  • Hero image,
  • Style choices,
  • Footer actions.

Templates do not save the audience. Apply a template from the Message step, then choose the audience for the specific send.

Email Defaults

Use this section to set the shared defaults that apply across hub emails and campaigns.

Set or review:

  • From display name and reply-to for outbound hub emails,
  • Header image/logo defaults,
  • Brand colours and button text colour,
  • Default footer/sign-off,
  • Whether optional hub and campaign email sends are paused.

Good practice:

  • Set these once before your first campaign,
  • Review them before a major send,
  • Keep reply-to monitored by a real operator.

Template QA

Use this before high-importance sends when you want to verify the exact template output.

This is where you:

  • Preview standard templates with sample variables,
  • Confirm fallback text and branding,
  • Send one-off test emails to yourself or a teammate before using the live campaign flow.

Live Preview Tips

  • The right panel starts as a stable Live draft mirror.
  • Keep editing while the preview stays visible in the right panel without reloading on each typed letter.
  • Use desktop/mobile preview toggles to check layout differences.
  • Use Refresh Exact Preview before final send to verify final server-rendered output.

Scheduled send command center

Campaign History includes a Scheduled send command center for upcoming scheduled campaigns. Use it to jump to the scheduled filter, open upcoming sends, reschedule, unschedule, or cancel before the campaign is claimed for sending.

Readiness health

The composer side panel includes Readiness health so organisers can see:

  • Sender identity setup,
  • Optional email policy state,
  • Engagement tracking mode,
  • Suppression, invalid-email, and preference-disabled counts after audience preview.

Policy and Compliance Notes

  • Mandatory system emails are always sent when required by workflow.
  • Non-essential update emails respect user preferences and unsubscribe behaviour.
  • Campaign exports and sends are permission-gated and audited.

Engagement Insights

Email Studio can show aggregate delivery, click, and optional estimated open metrics for each campaign, opt-in per hub.

Where to find the setting

Engagement tracking is a hub-wide policy, not a per-campaign toggle, so it lives in Hub Admin Settings rather than the campaign composer:

  1. From Email Studio, click Email Settings in the action row, or open Hub -> Admin -> Settings.
  2. Expand the Email card.
  3. Under Email engagement insights, choose Off, Clicks only, or Clicks and opens.
  4. Save the page.

The setting takes effect on the next campaign sent after the save.

What the modes mean

  • Off (default for every hub) - delivery, bounce, and complaint handling still run, but no per-message open or click tracking is enabled.
  • Clicks only - aggregate link clicks are recorded for Email Studio campaigns. Recommended.
  • Clicks and opens - aggregate link clicks plus estimated opens. Opens can be affected by privacy tools and image blocking.

Where the metrics appear

Once tracking is enabled, every Email Studio campaign detail page shows an Engagement insights section with aggregate Delivered, Unique clickers, Total clicks, optional Estimated unique opens and Total opens, and Last engagement.

Privacy posture

  • Only optional Email Studio campaign emails are eligible. Mandatory and system emails (ticket confirmations, security notices, account emails) are never tracked.
  • Metrics are aggregate-only. Hubbaly does not show per-person read receipts and does not add per-recipient open or click columns to CSV exports.
  • Opens are estimates. Some email clients prefetch images and others block them, so open numbers are best read as a directional signal.
  • Delivery, bounce, and complaint diagnostics still run regardless of engagement tracking choice.
Last updated on