Skip to main content

Events

Event Management is a Mailtarget capability for running registration-based events: webinars, workshops, conferences, and any flow where attendees sign up, optionally pay, and receive a ticket.

Event records and registrant data live alongside the rest of Mailtarget CDP. Registrant emails feed back into the Contact Book.

What an event includes​

An event in Mailtarget bundles the following surfaces:

  • Event details. Name, schedule, description. The container for everything else.
  • Registrant list. People who have signed up. Imported from CSV, added manually, or captured through an integrated form.
  • Products. Ticket types or add-on products tied to the event landing page.
  • Coupons. Discount codes that adjust ticket price at registration.
  • Email configuration. Sender name, sender email, and the templates for ticket and payment emails. Sending these emails requires the Mailtarget Transactional Email feature on the account.
  • Payment settings. Integration with Midtrans or other supported payment gateways. Skip if all tickets are free.
  • Bank settings. Account holder name, bank name, account number for payouts.
  • Landing page. A page on Mailtarget that serves the event registration flow.
  • Form integration. Two form types: Registration (data flows to Contact Book) and Check-in (data flows to attended-list).

How events feed Mailtarget CDP​

Three integration points:

  1. Registration form to Contact Book. When a registrant submits the form, their data is added to the Contact Book. Subsequent sends can target them through segments.
  2. Email automation trigger. A registration form can also be the trigger for an email automation. This is the alternate path for accounts without Transactional Email enabled. See the Event Email Automation guide.
  3. Check-in record. When the attendee arrives, the check-in form flips them from registered to attended. The attended state is queryable as a segment dimension.

Where events sit in the data model​

Events are first-class records, parallel to contacts. A registrant record references both the event and the underlying Contact Book entry. The same person registering for two events appears in two registrant lists but stays as one contact in the Contact Book.

Email types fired from events​

EmailWhenRequires
Ticket emailAfter successful registration.Transactional Email feature, or substitute via Email Automation triggered by the form.
Payment emailAfter successful payment confirmation.Transactional Email feature.
Check-in confirmationAfter attendee marked checked in (if configured).Transactional Email feature.

The exact templates and subject lines are configured per event. Consult the dashboard for the current template surface.

What event records contain in the API​

The dashboard exposes event configuration; the API exposes runtime operations on registrants. Tag the API surface as review_needed: true and confirm the available endpoints with the engineering team before relying on them in code.

The OpenAPI reference is the source of truth. See API Reference.

When to use Event Management vs a custom flow​

Use Event Management when:

  • The flow involves ticket-based registration with payment.
  • You want a hosted landing page tied to email automation without writing the integration glue.
  • You need check-in recording on the day.

Use a custom flow when:

  • Registration requires logic Event Management does not express (multi-step approval, complex pricing tiers, conditional product availability).
  • Your application already owns the registrant list and only needs Mailtarget for transactional sends.

A custom flow can still feed contacts back into the Contact Book through the API and trigger Event-style emails through the Transmission API. The Event Management feature is convenience, not a hard dependency.

Next​