Skip to main content
Outpost Events lets you create events that members register for directly on your Ghost site, or with one click from a campaign email. Events are managed in the Outpost dashboard and published to Ghost as posts with an embedded registration widget. Your theme can also offer an event type whose registration happens on another site, such as Eventbrite. See Events registered on another site.
Screenshot of Events Beta in Labs
This flow handles webinars, in-person events, virtual meetups, and any other registration-driven event your publication runs.
Screenshot of Events Beta entry

​
How to

  1. Create an event in the Outpost dashboard by clicking the blue Create Event button. Fill in a name, date, time, and access settings (including link and image if applicable). Save, then the Create Draft Post in Ghost button will appear. This will open a draft post with an embedded registration code.
    Event Creator Draft Post Button
    You should see confirmation in the top right corner after saving:
    Confirmation of saved event
    After saving, the “Create Draft Post” button will change into one that opens the draft page in a new tab:
    Button to open draft post in Ghost
  2. Publish to Ghost: Fill in any additional information you would like to share with your readers in the draft post that’s created, then publish to Ghost.
    Events Draft Post
    Note: the draft post may not look like it has your event in it. The details you entered in Outpost are stored in the post’s Code Injection section, and the event widget displays them once the post is published, provided your theme is set up to show events.
    Events Code Injection
  3. Members register either through the on-page widget, which handles login, access checks, and RSVP, or with one click from a campaign email.
  4. Calendar links appear after registration so attendees can save the event.
  5. Attendee tracking records registrations and cancellations.
  6. Event countdown displays a live countdown to the event start time.

​
Creating an event

Go to Events (beta) under the Labs group in the left navigation (pictured below) and click Create Event.
Events Beta in the Outpost Labs Menu
Create event button
If your theme defines event types (e.g., “In-Person”, “Webinar”, “Virtual”), you’ll select the type first; this determines which fields and settings are available.

​
Event details

​
Registration settings

A Recommended size line sits under the Featured Image field, and the same line appears inside the crop dialog. Outpost takes that size from the first of these that is set: the featured image constraint in your theme manifest, then Event Settings → Default Featured Image Size, then a built-in 1200 x 630px. The recommendation always shows, even when neither of the first two is configured.

​
Events registered on another site

Some events take their sign-ups somewhere else, such as Eventbrite. If your theme defines an event type for these, an event of that type shows a button that opens the outside registration page in place of Outpost’s Register box. Everyone who sees the event sees the button, whether or not they are signed in. When you choose that type in the event editor:
  • Registration page URL is required before you can publish, and it must start with http:// or https://.
  • Button text is optional, up to 60 characters. Leave it blank to use the site default from Event Settings. See Default messaging.
  • Who Can Register, Extra Labels for Members Who Register (Optional), Max Attendees and Event Platform URL are hidden, because they only apply when Outpost takes the registrations. The Attendees section, the Reminder Settings for the event, and the Button and card for other posts panel are hidden too.
If the event type includes a registration deadline, readers see your Registration Closed message in place of the button once the deadline passes. Outpost records no registrations for these events, so it doesn’t know who signed up. That means it sends no confirmation emails, no reminders to registrants, and no pre-event reminder to you, because each of those depends on the list of registrants. It also adds no RSVP labels. To remind the people who signed up, use the reminder emails on the site that takes the registrations, if it offers them. You can also export the registrants from that site and import them into Ghost as a CSV file with a descriptive label, such as the event’s name. Members who already exist in Ghost keep all their details and gain the label. New members are added with the label and subscribed to your newsletters. You can still invite your members to the event with Send Campaign. In a campaign email for one of these events, the Register for Event button goes straight to the outside registration page. If the event has no outside registration URL, the button opens the event’s page on your site once its Ghost post is published, and your site’s homepage before that. Because Outpost records no registrations for these events, Skip members registered for this event has no effect on them. Outpost won’t save a change of event type between Outpost registration and registration on another site while members are registered for the event. Theme developers set this up with the registration key on an event type. See registration in the manifest reference.

​
Editing an event

Every event has its own page. Click Edit on any row of the Events list to open it. A breadcrumb trail above the form shows where you are: Events, then New event while you’re creating one, or the event’s name once it has been saved. Click Events in the trail to return to the list. Saving a new event takes you to that event’s own page, and the browser address, breadcrumb, and page title update to match. The editor also does the following:
  • Cmd+S saves the event. Ctrl+S does the same on Windows.
  • Unsaved edits are protected. Leaving the page with changes you haven’t saved raises a Leave without saving? confirmation, offering Keep editing or Discard changes. Closing the browser tab raises your browser’s own leave-this-page warning instead.
  • Errors appear next to the field that caused them. If a required value is missing, the message appears under that field and the page scrolls to it. When publishing to Ghost fails, the reasons are attached to the fields they belong to, and anything that doesn’t belong to a field appears as a notification instead.

​
Post address

A Post address line on the event page shows the link to the event’s Ghost post, with a copy button. Once the post is published, the link is live. Before that, and for an email-only post, the link is plain text marked Not live yet. For a draft or scheduled post, it’s your site’s URL followed by the post’s slug, so you can copy it ahead of time. If your site uses custom routes, the published link can be different, so check it once the post is live. For an email-only post, it’s the link to Ghost’s web copy of the email. The line doesn’t appear when there’s no link to show, such as for an email-only post with no web copy.

​
Send Campaign

Once an event is saved, a Send Campaign button appears in the row of buttons at the bottom of the event page, and it stays there until the event has passed. It opens a new email campaign named after the event, with one action that already has this event linked and an announcement email ready to edit. The email includes the event name linked to the event page, the description, date, time, and location, and a Register button. Until the event’s Ghost post is published, the event name links to your site’s homepage. See The announcement email. Send Campaign also ticks Skip members registered for this event under the Link an event field, so members who have already registered don’t get the invitation. Outpost checks registrations again before each email sends, so a member who registers after the first email doesn’t get the later ones. Untick the box to include registered members. You can still leave out other members with Exclude Members Labeled. Make sure the campaign has a Slug, then choose the audience and the send time as you would for any campaign. See One-click registration from a campaign email.

​
Deleting an event

Open the event and click Delete in the row of buttons at the bottom of the event page. A Delete Event dialog asks “Are you sure you want to delete this event?” Click Yes, Delete to go ahead, or No to keep the event. Turn off any campaign for the event before you delete it, so members aren’t sent an invitation to an event that no longer exists. If members have registered, a Cancel Event dialog follows. It shows how many members are registered and a cancellation email you can edit, with the subject “{event name} has been cancelled”. It offers three choices:
  • Send & Cancel Event emails every registrant and deletes the event.
  • Cancel Without Email deletes the event without emailing anyone.
  • Keep Event closes the dialog and leaves the event as it is.
If Notify registered members when an event is cancelled (the Event Cancelled email) is off, or the Basic Autoresponder is switched off for your site, the dialog tells you that registered members won’t get a cancellation email, why, and where to turn it on. The email and the Send & Cancel Event button don’t appear, so the only buttons are Keep Event and Cancel Without Email. If the email or the Basic Autoresponder is switched off while the dialog is open, the event is still cancelled, and a notice tells you that no email was sent. If cancelling the event fails, the Cancel Event dialog stays open with your edits to the email and an error appears, so you can try again. Trying again after a failed Send & Cancel Event emails every registrant again, so some members may get the email twice. If deleting an event with no registered members fails, the dialog closes, the event stays as it is, and an error appears.

​
The event’s Ghost post

When the event has a Ghost post, both dialogs show an Also delete the post in Ghost checkbox, unticked to start with. A note under it says what deleting the post means for readers, based on where the post stands in Ghost. For a published post it reads “This post is live on your site. Deleting it takes the page down for readers.” Outpost deletes the post only when you tick the box. If Ghost can’t delete the post, the event is still deleted and the post stays in Ghost, so check for it there. If you leave the box unticked, the post stays in Ghost as it is, but it shows no registration box, because its event is gone. Unpublish or edit the post in Ghost if readers shouldn’t see it.

​
Events list

The Events page lists every event you have created, with columns for Event Date, Name, Event State, Ghost Post, and Actions. The Ghost Post column tracks where the event’s post stands in Ghost: Draft rows link to the Ghost editor rather than to the post’s public page, since the post isn’t live yet. The state always matches the post in Ghost. If you switch a published post back to a draft in Ghost, the row shows Draft again, and the event’s links go back to your site’s homepage. See Links to the event page. In the Event State column, an event whose registration happens on another site has an Outside registration tag next to its state. The Actions column always includes Edit, which opens the event in Outpost. Next to it sits Create Draft Post in Ghost while the event has no post, and Edit in Ghost once a post exists.

​
Event lifecycle

Events transition automatically through three states based on dates and times:
1

Registration Open

The event date is in the future and the registration deadline (if set) hasn’t passed. Members can RSVP.
2

Registration Closed

The registration deadline has passed but the event hasn’t happened yet. New RSVPs are blocked.
3

Event Passed

The event date has passed and the end time (or start time, if no end time was set) has come and gone. The widget shows a past-event message.
Only members who have registered for the event can see the Event Platform URL. On the event page it appears as a Join Event button inside the registration widget. Event emails include it when you add the %EVENT_JOIN_LINK% merge tag to a template, and those emails go only to registrants. The default confirmation and reminder templates include it. Outpost has added the join link to older copies of these templates too, unless the event details list had been removed from the template. If your confirmation or reminder email still doesn’t show a join link, add the %EVENT_JOIN_LINK% tag yourself. See Customizing event email templates. In a campaign email, %EVENT_JOIN_LINK% is filled only for readers who have already registered. The update email Outpost drafts after you change an event lists the join link too. See Tracked fields for the update email. Outpost leaves the link out of the event data it publishes to your Ghost post, so a theme reading that data never sees it. The link arrives with the registration widget instead, and only for a member who has registered. A reader who hasn’t registered has no way to get it from the page. A member who registered before the deadline still sees the Join Event button after registration closes, right through to the start of the event.

​
Attendee management

Once an event has registrations, the event detail page shows an Attendees section with:
  • Member name and email
  • Registration timestamp (Registered At)
  • Export CSV button to download the attendee list (Name, Email, Registered At)
Each registration also has an internal status (registered, cancelled, attended). Today the page shows registered attendees and removes the row when a member cancels. There is no per-attendee status badge or attendance-marking control on the page yet.
After registering, members see calendar buttons to add the event to their preferred platform:
  • ICS File Download (Apple Calendar, Outlook desktop)
  • Google Calendar
  • Outlook Web
  • Yahoo Calendar
Choose which platforms to display in Event Settings → Default Messaging → Registered → Show calendar links.

​
What gets added to the calendar

Every platform receives the same core information, derived from the event you published:

​
ICS file specifics

The ICS download produces a standards-compliant file (RFC 5545) that Apple Calendar, Outlook desktop, Thunderbird, and other clients can import directly. Each entry includes:
The Event page: line in the description and the URL: line appear only once the event’s Ghost post is published. Carriage returns and other special characters in the site name, event name, location, and description are escaped per the RFC so the file always opens cleanly, even if a publisher pastes content with stray line breaks.

​
Google, Outlook, and Yahoo handoffs

These three buttons don’t generate a file; they open the platform’s “create event” form pre-filled via URL parameters. Every form receives:
  • The site-prefixed title ({Site Name}: {Event Name}).
  • The event start and end times in UTC.
  • The location.
  • The description: the From {Site Name} attribution, the event page line, and the event description.
The exact URL parameters are: These platforms don’t expose a separate STATUS or URL field via their compose URLs, so members get the title, time, location, and description. Once the event’s Ghost post is published, the link to the event page is already in the description, so you don’t need to add it to your event description yourself.

​
Ghost integration

​
Publishing

When you publish an event from Outpost, a Ghost post is created (or updated) with:
  • The event name as the post title.
  • A placeholder paragraph that starts “Write your event description here”, followed by an HTML card. Replace the paragraph with your own copy in Ghost. Keep the HTML card: on your site it shows the registration widget, and in a newsletter it shows a Register button. You can move the card anywhere in the post. See Sending the event post as a newsletter.
  • A JSON payload of event details in the post’s codeinjection_foot for themes to read (date, time, access level, registration state).
  • A custom post template if you’ve configured one in Event Settings or your theme manifest.
  • The featured image uploaded to Ghost (uploaded once, on first sync).

​
Links to the event page

Outpost links readers to an event’s page only once its Ghost post is published. The link is the post’s own link in Ghost, so it stays correct if your site uses custom routes. Until the post is published:
  • %EVENT_URL% in emails, and the event name in the announcement email, link to your site’s homepage.
  • The confirmation page a reader sees after registering from an email shows a Go to {site name} button that opens your homepage, in place of View event page.
  • Calendar entries leave out the event page line and the event link.
  • For an event with no meeting link yet, the sentence that %EVENT_JOIN_LINK% inserts is plain text rather than a link.
  • In a button or card you copied into another post, a registered reader sees no View event page link, and the card shows the event name without a link.
If you send the event post to members as an email only, it isn’t listed on your site, but readers can still register. They can click Register in the email, or use a “view on the web” link in your email template to open a private copy of the post, which shows the same registration box as a post on your site. Event links in your Outpost emails go to that private copy, or to your site’s homepage if Ghost doesn’t have one.

​
Sending the event post as a newsletter

When you send an event post to your members as a Ghost newsletter, the email shows a card with the event name, date, time, and location, and a Register button. The button registers each reader with one click, the same way as a button or card you copy into another post. On your site, readers see the live registration widget in its place. While the post is a draft, Outpost replaces the card with a fresh copy each time you save the event, so a new date, time, or location shows up in the newsletter. Any change you make to the card’s HTML yourself is replaced at the same time. Once the post is published, the card stays as it was.

​
Automatic ordering

Ghost normally displays posts by publish date, not event date. Outpost bridges that gap by quietly adjusting event posts’ publish dates so that publish-date order always matches event-date order. The reorder runs every time an event is published or its date changes, so an events listing in your theme needs no special sorting: Ghost’s default publish-date ordering shows events in event-date order, with past events sinking below upcoming ones.
Because Outpost manages these publish dates, the dates themselves aren’t meaningful: an event post can show a “published” date that has nothing to do with when you actually published it. Event post templates and event cards should hide the publication date and show the event date from the code injection payload instead.

​
Theme support

Compatible Ghost themes (like Gazet) read event details from the codeinjection_foot payload to display event information, registration status, and sign-up buttons natively. The registration widget uses your Auto Display CTA design settings (accent colors, button styles, fonts).
The widget needs the theme to render codeinjection_foot and to keep the placeholder <div> in the post body. If the theme strips foot code injection, or if the placeholder div is deleted in the Ghost editor, the widget won’t appear.

​
RSVP labels

When a member registers, Outpost adds two labels to their member record so you can segment and filter event attendees in both Outpost and Ghost. The first is an RSVP label built from the event name and the month the event was created: an event named “Spring Webinar” created in March 2026 produces ZZZ_RSVP_spring_webinar_2026_03. Outpost writes this label into the event’s Extra Labels for Members Who Register (Optional) field when you first save, so you can see it there and remove it if you would rather not use it. The second matches the event’s Slug field exactly, so an event with the slug spring-webinar gives every registrant the label spring-webinar. The RSVP label is set once when the event is created. Renaming the event later does not update the label: existing registrants keep their original label, and new registrants receive the same label as everyone else on the event. Every label the event adds, including any you added yourself, is removed automatically when a member cancels their registration.

​
Event countdown

When an event has a date and start time configured, Outpost generates a live countdown displayed on the event page. The countdown adapts based on how far away the event is:
  • More than a day away: shows days and hours (e.g., “3d 5h”).
  • Less than a day: shows hours and minutes (e.g., “2h 30m”).
  • Less than an hour: shows minutes only (e.g., “45m”).
The countdown disappears once the event start time has passed. It respects the event’s configured time zone.

​
Event settings

Open global event defaults by clicking the Settings button on the Events list page. Values under Event Defaults fill in automatically when you create a new event, and you can override any of them on an individual event. Event email settings live in the same drawer, under Event Emails: see Event emails.

​
Default Post Template

The dropdown lists the custom templates Outpost read from the theme you uploaded through the Theme Connect Wizard. Outpost re-reads your theme each time you open Event Settings, so a template from a theme you uploaded a moment ago appears as soon as you close and reopen the drawer. If a template you expect is missing, upload your theme again through the wizard so Outpost reads the current files, then reopen Event Settings. If your theme has no custom templates, the dropdown reads “No templates found in your theme. Refresh your theme or type a template name.” The field also accepts a template name you type yourself. Only do that if you know what you are doing: it is there for the rare case where you are certain the template is in your theme and you know why Outpost isn’t listing it. A name that doesn’t match a real template means your event posts won’t render the way you expect. Enter the file name without the .hbs extension, so custom-event-post.hbs is entered as custom-event-post.

​
Default messaging

Event Settings includes customizable messaging templates for each audience state: Each state has configurable text and toggles. Per-event overrides take priority over site-level defaults. On the event page, both Login Required states always include an “Already have an account? Sign in” link, so a member who arrives signed out can sign in instead of joining again. The sign-in, sign-up, and upgrade links on the event page follow Use Ghost Portal for membership features on Publication Details. When it is on, they open Ghost Portal. When it is off, they use the links you saved under Edit Membership Links. They don’t use the Site-wide sign-in URL from your CTA design settings. Link Pending Message sits in the Registered / Confirmed panel. A registered member sees it where the Join Event button would go, on an event that expects a join link and has no Event Platform URL yet. It reads “The event link will be provided on this page before the event starts.” until you write your own, and it takes up to 500 characters. The button takes its place as soon as you fill in the Event Platform URL. The message is only shown to members who have registered, and it stops showing once the event has passed. An event that expects no join link, such as an in-person event at a venue, shows nothing in its place. Outpost uses the Location to decide whether an event expects a link. A location of “Online”, or one that mentions “virtual”, means the event expects a link, and a venue name means it does not. If your theme defines event types, the event’s type decides instead: an event whose type includes the Event Platform URL field expects a link, and one whose type leaves that field out does not. Event emails don’t use this wording. On an event that expects a link and has no Event Platform URL yet, they use a fixed line, in your site’s language, telling the reader the link will be posted on the event page.

​
Event emails

Outpost can send emails to registrants at key moments in the event lifecycle. Event emails are managed through the Basic Autoresponder and use the same template system as other autoresponder actions.

​
Enabling event emails

Event emails are controlled at two levels:
  1. Site-level switch: Enable event emails in Event Settings turns event emails on or off for your whole publication. Switching it on turns on all six event emails in the Basic Autoresponder, even ones you had switched off there, and switching it off turns them all off. Saving any other event setting leaves your Autoresponder choices alone.
  2. Per-event override: Individual events can disable emails even when the site-level switch is on. Useful for informal events where you don’t want automated notifications.
Both levels govern the emails Outpost sends your registrants automatically: the confirmation and the two reminders. The Event Updated and Event Cancelled notices are ones you send yourself from the event page, so they still go out on an event where you switched emails off. The two notices that come to you, the pre-event reminder and the post-event recap, go out whatever these settings say. Neither goes out for an event whose registration happens on another site, and the recap only goes out for an event with at least one registration. If Enable event emails is off in Event Settings and a member registers anyway, Outpost emails you to point that out, along with a note on what turning event emails on would do. However many registrations arrive, that email is sent at most once every three days.

​
Email types

Confirmation emails send regardless of a member’s email opt-out preference: they’re transactional. Reminder emails respect the member’s email preferences and will not send to members who have opted out.

​
Pre-event reminder

About two days before a published event starts, Outpost emails you a short checklist for it. The email gives the event name, the start date and time, and how many members have registered so far. It asks you to add the meeting link in the Event Platform URL field if the event uses one and you haven’t set it yet, points you to the attendee export, and gives you the label to target if you want to email everyone who registered. It goes out once per event, to the site owner and every other user on your Outpost account, whether or not anyone has registered. An event whose Ghost post hasn’t been published yet doesn’t get one, and neither does an event whose registration happens on another site, because Outpost has no list of who registered for it, so there is no attendee list to export and no one to send a meeting link to. If you publish an event less than two days before it starts, the reminder goes out on the next hourly check.

​
Reminder configuration

Reminders are set at the site level in Event Settings and can be overridden per event: Reminders are checked every hour and send within a three-hour window, so the exact timing varies: a reminder set for “24 hours before” can go out any time between 25 and 22 hours before the event starts.

​
Tracked fields for the update email

Outpost watches six fields and prompts you to send the Event Updated email if any of them change after registrations exist:
  • Event Date
  • Start Time
  • End Time
  • Time Zone
  • Location
  • Event Platform URL
When you save a change to any of these fields and members are registered, an Event Details Changed prompt opens. It reads “Event details have changed. N members are registered. Would you like to send an update email to notify them?” Skip closes the prompt without emailing anyone, and your changes stay saved. Send Update Email opens a draft. The draft has the subject “{event name} has been updated”. Its body lists the event’s current Date, Time (the start and end times with the time zone), Location, and Join link. A line is left out when the event doesn’t have that detail, and the time shows only the start when the event has no end time. Edit the subject and body as you like, then click Send to N members. If sending fails, the draft stays open with your edits and an error appears, so you can try again. Trying again sends the email to everyone again, so some members may get it twice. If Notify registered members when event details change (the Event Updated email) is off, or the Basic Autoresponder is switched off for your site, the prompt tells you that members won’t get an email about the change, why, and where to turn it on. Its only button is OK, and your changes stay saved. If the email or the Basic Autoresponder is switched off while the draft is open, a notice tells you that no update email was sent.

​
Customizing event email templates

Each event email has its own template in the Basic Autoresponder. Templates support event-specific merge tags:
Event templates also support the standard member, site, and subscription merge fields, plus fallback syntax for empty values like %SUBSCRIBER_FIRST_NAME%,fallback="there". See Email templates for the full reference.
Edit templates in Autoresponder > Basic: event email actions appear alongside other autoresponder actions. Each reminder shows its site-level timing there as the number of hours before the event, or as Off when Number of reminders is set low enough that the reminder never sends. Per-event overrides are not reflected in that row. The timing itself is changed in Event Settings, not in the Autoresponder.

​
One-click registration from a campaign email

You can announce an event in an email campaign with a Register for Event button that registers each reader in one click, without signing in.

​
Setting it up

It starts a campaign with the event linked and an announcement email ready to edit: see Send Campaign. Edit the email, choose the audience and the send time, and save. You can also start a new campaign from Campaigns, or use an email of your own:
  1. Click Add Action and choose or create the email. In the email editor, add a registration button: click the + button, choose CTA Button, open the button’s settings, and choose Register for Event.
  2. Save the email. A Link an event field appears under it in the campaign. Choose the event the email is about.
  3. Save the campaign. Outpost won’t save it until every email that uses an event detail, such as the event name or date, or has a registration button has an event chosen. Emails that have already sent don’t need one.
Once an action has an event linked and no email yet, a Use the event announcement email button appears under it. Click it to start from the announcement email instead of choosing one. Either way, the registration button’s URL is %EVENT_REGISTER_LINK%, which Outpost replaces with each reader’s own registration link when the campaign sends. You can change the button’s Title, but leave its URL as it is.

​
The announcement email

Both Send Campaign and Use the event announcement email open a copy of your site’s Event Announcement - Default email named “Announcement: {event name}”, with the subject “You’re invited: %EVENT_NAME%”. Each time you use it you get a new copy, and nothing is added to the campaign until you save that copy. Edit it as you would any email. The Event Announcement - Default email is added to your site’s email templates the first time you use Send Campaign or Use the event announcement email. Editing it there changes the starting point for future announcements; copies you have already made stay as they are. The Link an event list shows your upcoming events, most recently created first, with each event’s date beside its name, and you can search it. An event whose registration deadline has passed is still listed, and readers who click its button are told registration has closed. If the event’s Who Can Register setting is Paid Subscribers Only and the campaign’s Apply to includes Free, a warning appears under the field. Free members who click the button are told the event is for paid members only.

​
Event merge tags in a campaign email

A campaign email with an event linked can use these merge tags: The four calendar tags, %EVENT_CALENDAR_GOOGLE%, %EVENT_CALENDAR_ICS%, %EVENT_CALENDAR_OUTLOOK%, and %EVENT_CALENDAR_YAHOO%, work in campaign emails for every reader. %EVENT_JOIN_LINK% and %EVENT_CANCEL_LINK% are filled only for readers who have already registered for the event. Everyone else gets nothing in their place, or the tag’s fallback text if you set one. A test email follows the same rule: it fills these two tags only if you are registered for the event yourself.
A test email’s Register for Event button is real: if your login email belongs to a member of your site, clicking it registers you.

​
What readers see

Clicking the button opens a short confirmation page in your site’s language. It looks like the event pages on your site: it shows the event’s date, time and location, and its main button uses your site’s accent color. If the reader can register, they’re registered at that moment, with no sign-in and nothing more to click. The page tells them one of these things:
  • They’re registered. The page also tells them a confirmation email is on its way, so keep event emails on for the event.
  • They were already registered, on the event page or from an earlier email.
  • Registration has closed, because the registration deadline has passed.
  • The event is full, because every place under Max Attendees has been taken.
  • The event has already taken place.
  • The event is for paid members only. Free members see this on an event set to Paid Subscribers Only.
  • The event can’t be found, because it has been deleted or cancelled.
  • The link wasn’t recognized, because Outpost can’t match it to a member of your site. The page suggests signing in to register.
Registration page on a phone showing the event date, title, time and location, a You're registered message, and Back to your email and View event page buttons

The page a reader sees after registering from an email.

The page has a Back to your email button that closes the tab and returns the reader to their inbox. Some browsers don’t let the page close the tab, such as the ones built into the Gmail and Outlook phone apps. There, the page asks the reader to close the tab themselves. Once the event’s Ghost post is published, the page also has a View event page button. Before that, the same button reads Go to {site name} and opens your site’s homepage. The page also links to your site’s sign-in page. When the link wasn’t recognized, the page shows a Sign in button, and when the event can’t be found, it shows a button that goes to your site.

​
Things to know

  • Use the Register for Event button only in campaign emails. In any other email, such as an autoresponder email, the button doesn’t work: readers get the tag instead of a link.
  • Publish the event’s Ghost post before the campaign sends. The event page links in the email and on the confirmation page lead to that post, and to your site’s homepage until it is published. While the linked event isn’t published, a warning appears under the Link an event field.
  • Skip members registered for this event is ticked whenever you choose an event, whether you start from Send Campaign or from Campaigns. Outpost checks registrations again before each email sends, so a member who registers after the first email doesn’t get the later ones. Untick the box to include registered members.
  • A campaign saved before this option existed keeps the exclusion label it already has. Open the campaign and tick the box to use the new option.
  • The campaign’s Members Count is for the whole campaign and doesn’t reflect the members who are skipped.
  • A registration from an email counts the same as one made on the event page: the member appears in the event’s Attendees list, gets the event’s RSVP labels, and receives the confirmation email when event emails are on.
  • Registering from an email doesn’t sign the reader in to your site. The event page shows their registration, the calendar links, and the Join Event button once they sign in. For an online event, check that your confirmation and reminder emails include %EVENT_JOIN_LINK%, so registrants have the link in their inbox.
  • Each button is tied to the reader it was sent to, so clicking it in a forwarded email registers the original reader, not the person who clicked. That person can sign in from the confirmation page and register on the event page.
  • The confirmation page has no cancel option. A reader who can’t come cancels on the event page, or with the cancel link in their confirmation email.
  • Turn off any campaign for the event before you cancel or delete the event.
You can put a registration button, or a card with the event details and a button, into any Ghost post or newsletter. On your site it shows live registration for each reader. In a Ghost newsletter, the button registers the reader with one click.

​
Copying the button or card

The Button and card for other posts panel is on the event’s page in Outpost. It appears once the event has a Ghost post, whether that post is a draft or published.
  1. Choose Card or Button. Card is selected to start with.
  2. Check the preview, labeled How it looks in the newsletter.
  3. Click Copy HTML. Outpost confirms with “HTML copied. Paste it into an HTML card in the Ghost editor.”
  4. In the Ghost editor, add an HTML card to your post and paste the HTML into it.
The card shows the event name, date, and time, then the location, and a register button. A virtual event shows “Virtual event” as its location, and a virtual event in a US time zone also shows the times in Eastern or Pacific time. The button on its own is just the register button. The button text is the button text you set for Can Register in Event Settings, and its color is your site’s accent color.

​
What readers see

On your website, Outpost replaces the pasted block with a live version for each reader:
  • A signed-in member who can register gets a Register button that registers them in one click.
  • A signed-out reader, or a free member on an event for paid members, sees the same message and button as on the event page.
  • A reader who has already registered sees that they’re registered, with a View event page link once the event’s Ghost post is published. From then on, a card’s event name links to the event page too.
  • Once registration has closed, or the event is full, readers who haven’t registered see that message instead.
  • Once the event has passed, the button is removed. A card still shows the event details.
In a Ghost newsletter, the button is a personal one-click registration link for each recipient. Clicking it opens the same confirmation page as the Register for Event button in a campaign email. See What readers see.

​
Things to know

  • The newsletter version doesn’t update after you paste it. If you change the event’s date, time, or location, copy the HTML again and replace the old block before the post is sent.
  • After the registration deadline, or once the event has passed, the panel warns you that a newly pasted button or card can only tell readers that registration has closed or that the event has passed.
  • Pasting the HTML into an Outpost campaign email won’t register anyone, because the personal link only works in a Ghost newsletter. In a campaign email, use the Register for Event button instead. See One-click registration from a campaign email.

​
Tracking registrations

Each button or card you copy appears in a table under the preview, with these columns:

Event Creator

Create reusable event HTML widgets to embed in Ghost posts. To put a registerable event into any post or newsletter, use the event’s Button and card for other posts panel instead.

Theme Connect Wizard

Connect your Ghost theme to enable event widgets and other Outpost features.

Labels

RSVP labels are auto-applied when members register for events.

Basic Autoresponder

Configure event email templates and reminder timing.

​
FAQ

Events (this page) creates full Ghost-integrated events with registration, attendee tracking, and lifecycle management. Event Creator is a simpler tool for creating reusable event HTML widgets that you paste into Ghost posts: no registration or attendee tracking. To put a registerable event into any post or newsletter, use the event’s Button and card for other posts panel instead. See Promote an event in other posts and newsletters.
Yes. Set Max Attendees on the event. Once that many members have registered, the event page, any event Button or Card, and the Register for Event button in campaign emails all tell new readers “This event is full.” Members who have already registered keep their place and their join link. A cancellation frees up a place.
Open the event detail page, scroll to the Attendees section, and click Export CSV. The export includes name, email, and registration timestamp.
The registration widget works on any theme as long as the theme renders codeinjection_foot and the placeholder <div class="outpost-ghost-event-container"></div> is left in the post body. Themes specifically built for Outpost (like Gazet) provide richer event rendering using the metadata Outpost injects.
Outpost updates the Ghost post and reorders all event posts so they display in chronological event-date order. If members have registered and Notify registered members when event details change (the Event Updated email) is on in the Basic Autoresponder, Outpost offers to send them an update email as soon as you save the change. If that email or the Basic Autoresponder is off, Outpost tells you that they won’t get one and where to turn it on.
That’s Outpost keeping your events in order. Ghost sorts posts by publish date, so Outpost automatically adjusts event posts’ publish dates to match the order of their event dates. The reorder runs whenever any event is published or has its date changed. It’s harmless, but it means the publish date on an event post isn’t meaningful; themes should hide the publication date on event posts and show the event date instead.
The dropdown lists the custom templates Outpost read from the theme you uploaded through the Theme Connect Wizard. Outpost re-reads your theme every time you open Event Settings, so closing the drawer and opening it again picks up a theme you uploaded a moment ago. If the template still doesn’t appear, upload your theme again through the wizard and reopen Event Settings. That is the ordinary fix. If your theme has no custom templates at all, the dropdown reads “No templates found in your theme. Refresh your theme or type a template name.”The field will also accept a template name you type yourself. Only do that if you know what you are doing: it is there for the rare case where you are certain the template is in your theme and you know why Outpost isn’t listing it. A name that doesn’t match a real template means your event posts won’t render the way you expect. If you do need it, enter the file name without the .hbs extension, so custom-event-post.hbs is entered as custom-event-post.
Go to Event Settings and turn on Enable event emails. That one switch turns on all six event emails in the Basic Autoresponder, including any you had switched off there. You can still disable emails for individual events without turning off the site-wide setting. The pre-event reminder and the post-event recap, which come to you rather than to your registrants, send whatever these settings say.
Yes. The default is two reminders: 24 hours and 2 hours before the event. You can change the timing and the count (0, 1, or 2) in Event Settings, and override these settings on individual events.
Because Outpost doesn’t know who registered. Readers sign up on the other site and Outpost never receives that list, so it has no one to remind. The pre-event reminder to you is skipped for the same reason: it asks you to add the meeting link for registrants and points you to the attendee export, and an event like this has neither. For reminders, use the other site’s own reminder emails, if it offers them. See Events registered on another site.
Yes. Confirmation emails are transactional and send regardless of email preferences. Reminder emails respect opt-out preferences and won’t go to members who have unsubscribed.