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.

Included Campaign Sends

Every hub includes 5,000 campaign sends per UTC calendar month. Every attempted campaign recipient counts once sending starts, whether or not delivery later succeeds.

Owners and admins can check the current count in Hub -> Admin -> Settings -> Included usage.
At the effective campaign-send allowance, Hubbaly blocks new live or scheduled campaign sends. Existing drafts, templates, Campaign History, exports, and email settings stay available.
The allowance resets at the start of the next UTC calendar month.
If the hub needs more sends, or the count looks wrong, use Contact Hubbaly for capacity help from the Included usage card.

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

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

Step 2: Message Content

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

Event cards

An event card puts an event in your email as a tidy box: a picture, a title, the date and place, a few words of your own and a button.

Pick one of your events. Choose it in the card’s Event list. The name, date, place, picture and link come from the event, so there is nothing to type or paste. If the event changes before the email goes out, the card changes with it. Add more cards to mention several events in one email.
Or write the card yourself. Choose No event: write your own for something that has no event page yet, such as a save the date. The card shows only what you type. Leave the button link empty and the card has no button.
Large or Small. A large card puts the picture on top. A small card puts a small picture beside the words, which suits a list of events.

Only events your members can open are offered. Drafts and cancelled, archived or invite-only events are left out. If an event stops being available after you schedule an email, the email still goes out at its time, without that card.

Step 3: Footer Actions

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

Save draft.
Use Refresh Exact Preview and Send Campaign Test.
Send immediately with Send Now or set a date/time to schedule.
Open Campaign History for the Scheduled send command centre, 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.
Treat Refresh Exact Preview and Send Campaign Test as the final email-client check. They use the safer rendered email layout, including constrained hero media, email-safe video fallback buttons, and dark-style cleanup.

Scheduled send command centre

Campaign History includes a Scheduled send command centre 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,
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 shows recorded delivery counts and optional estimated opens for each campaign. Every email link goes straight to its destination. Clicks are never recorded by email tracking.

Where to find the setting

From Email Studio, open Email Settings, or go to Hub -> Admin -> Settings.
Expand the Email card.
Under Email engagement insights, choose Off or Estimated opens.
Save the page.

The choice is saved when a campaign starts sending. Queued messages and retries keep that choice; later settings changes do not add figures to past campaigns.

What each choice does

Off (the default) adds no tracking image and records no campaign opens.
Estimated opens adds an invisible image to optional Email Studio campaigns. Loading that image records an open. Automatic image loading can increase the count, while blocked images can hide opens.

Both choices keep links direct. Delivery, bounce and complaint checks always run. Mandatory emails and test sends are never tracked.

Where the counts appear

Open a campaign in Campaign History to see Engagement insights. Delivered counts messages accepted by the receiving mail server; it does not confirm that someone read them.

When open estimates were enabled for that send, the page also shows Estimated unique opens, Recorded opens and Last recorded open. Unique opens count distinct messages whose tracking image loaded. Recorded opens count all recorded loads, including repeat loads. These are estimates, so a zero does not prove nobody read the email.

Open events are kept for 180 days. Older open events are removed, so open counts are not lifetime totals. Hubbaly shows aggregate campaign counts, without per-person read receipts or open columns in recipient exports.