The email half of running an event
Campaigns, templates, forms and tracked links live in the same console as the event itself. That matters for one practical reason: the list you are emailing is the attendee list, not a copy of it that went stale the moment somebody was added.
What this looks like in the product
One console section, one list, and no export-import loop with a separate mail tool.
- Email campaigns
- Themed, branded sends to your attendee list, with a signature footer on every message.
- Reusable templates
- Templates you build once and send from, rather than rewriting an email per event.
- Forms
- Build and publish a form; responses land in the console rather than in an inbox.
- Tracked links
- Branded click tracking on the links you send, so you know what was opened.
- Per-recipient delivery
- Delivery, opens and clicks recorded per recipient, so a bounce is visible rather than assumed.
Communications
- Campaigns, sent and scheduled
- Email templates
- Forms and their responses
- Tracked links
- Delivery, opens and clicks per recipient
The argument is the list, not the editor
Every organizer already has an email tool, and it is almost certainly a better editor than this one. So the reason to send from here is not the editor.
It is that a separate mail tool needs a copy of your attendee list, and a copy is wrong the moment anybody is added, removed or corrected. The practical consequence is familiar: the person who registered on Tuesday does not get the Wednesday email, and the person who cancelled gets the joining instructions.
Sending from the console removes the copy. The audience is the event's attendee list as it stands when the send goes out. Delivery, opens and clicks are recorded per recipient, so a bounced address is a visible fact rather than an assumption you make on the day when somebody says they never received anything.
Campaigns and templates
A campaign is a send to your attendees. A template is the thing you build once so that the next event does not start with a blank page.
Email from event67 is themed. It carries your branding and a signature footer on every message, so the invite, the reminder and the thank-you all look like they came from the same organisation rather than from three different tools at three different times.
The practical shape most events settle on is four sends: the invite with the claim link, a reminder about a week out, a morning-of message with the practical detail, and a thank-you with the feedback form. Everything past that is a decision to be interesting, and it should be made deliberately rather than by habit.
- Invites
- Bulk import from CSV and send, with the claim link that turns a row into an attendee. Invites are unlimited and never the thing you are billed for.
- Campaigns
- Any other send to the list, branded and tracked.
- Templates
- Reusable message shells, so a recurring event is a copy rather than a rewrite.
- Tracked links
- Branded click tracking, so you know which link in a send did the work.
Forms, and the one thing they do not do
Forms are built in the console and published for attendees, with responses landing back in the console rather than in somebody's inbox. They cover the ordinary needs of an event: dietary requirements, workshop preferences, a post-event survey longer than a session rating, a nomination or a submission with a deadline.
The limitation is worth stating in bold rather than in a footnote. Forms collect responses. They do not collect money. There is no payment field, no checkout, no invoice and no ticket. If your form needs to take a payment, it needs to be built somewhere else, and that is not a configuration you have not found.
- No payments, no checkout and no paid submissions.
- No conditional branching between questions.
- No approval workflow with reviewers and rounds. Responses land; a human reads them.
- No file-upload review pipeline for abstracts or papers, which is what a call for papers actually needs.
What this is not
This is event communication, not marketing automation, and the difference is roughly the difference between four sends and a nurture sequence.
- No behavioural automation. Nothing sends itself because somebody did or did not click something.
- No lead scoring, no CRM sync and no integration with a marketing platform.
- No A/B testing of subject lines.
- No SMS.
- No sending to a list that is not your event's attendees. This is not a general-purpose mailing tool, and treating it as one is how a sending reputation gets damaged.
Who this replaces a tool for
Small teams with no marketing platform, for whom the alternative is a personal mail client and a spreadsheet with a mail-merge. Association staff running a members' meeting where the list changes daily right up to the door. Internal communications teams who cannot get a marketing tool provisioned for a two-day event and should not have to.
If you already run a serious marketing platform and your event list genuinely lives there, keep it there. The gain here is a single list, and if you do not have two lists, there is nothing to gain.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Can forms take payments?
No. Forms collect responses only. There is no payment field, no checkout and no invoicing anywhere in event67, because the product does not do registration or ticketing at all. A form that needs money attached to it has to be built elsewhere.
Do we email from our own domain?
Email is themed and branded with your identity and carries a signature footer on every send. Anything beyond that about sending domains and authentication is a setup conversation rather than a self-serve switch, and it is worth raising early if your organisation has strict email policy.
Can we see who opened an email?
Yes. Delivery, opens and clicks are recorded per recipient, and links carry branded click tracking. That is also how a bounced address becomes visible before the morning of the event rather than during it.
Can we send to a segment of the list?
Campaigns target your attendee list, which is the meaningful advantage over a separate tool holding a stale copy. If you need push to reach a subset, it cannot — push goes to the whole event — so email is the targeted channel of the two.
Does sending email cost extra?
No. There is no per-email or per-campaign charge and invites are unlimited. Only activated attendees meter: 50 free, $5 each after that, capped at $4,750 per event. Emailing someone who never opens the app costs nothing.
Keep reading
Features this connects
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.