Recipient filters

Overview

You can find this area when you open a mailing template and scroll to the dispatch settings. Here you configure when emails are sent, which recipients are targeted and you can send test emails.

Features

Edit dispatch settings

  1. Open a mailing template.
  2. Scroll to the dispatch settings.
  3. Change the settings you want to update.
  4. Click "Save" (bottom right in blue).

Fields

Dispatch types

You can choose between three dispatch types (explained in more detail on the separate page):

  1. Manual: Emails are sent manually when you click "Send mail to single contact".
  2. Single timestamps: Emails are sent automatically at specific points in time. You can configure multiple timestamps.
  3. Recurring dispatch: Emails are sent based on a pattern. You can define start/end time and a pattern (e.g. daily, weekly).

Recipient filters

Recipient filters let you define exactly who receives an automated email.
All filters are combined with AND: only contacts that match all filter conditions at the same time receive the email (or appear in the preview).

In the UI you can add multiple filter cards (e.g. "Voucher", "Ticket status", "Category"). Below all filter types and their options are explained in detail.

Voucher status ("Voucher")

General explanation
Many events use personal voucher codes (e.g. discount, free ticket or priority vouchers). The "Voucher" filter narrows the selection based on whether a contact already has a voucher assigned or not.
This is especially useful when you:

  • only want to remind contacts who have not yet used their existing voucher, or
  • want to send new vouchers only to people without an existing voucher.

Options

  • Has voucher
    The contact already has a personal voucher assigned in contact_lead_event_access_vouchers.
    Typical use cases:
    • Follow-up emails to people who already received a voucher (e.g. "Use your discount until …").
    • Reminder emails shortly before a voucher expires.
    • Communication that directly refers to an individual voucher code. Effect:
    • Only contacts with a voucher are selected.
    • Contacts without a voucher are excluded even if they match all other conditions.
  • Has no voucher
    The contact does not have a personal voucher assigned.
    Typical use cases:
    • Backfilling: you only want to contact those who have not yet received a voucher (e.g. because they were added later). Effect:
    • Only contacts without a voucher are selected.
    • Contacts with a voucher are excluded, even if they match all other conditions.

Mailing ("Has received / not received mailing X")

General explanation
This filter lets you filter contacts based on their behavior with regard to other mailings for this event. It covers typical scenarios such as "only send to those who have not yet received an invitation" or "reminder only for those who received the first mailing".

The filter consists of several sub‑settings

  • Which mailing?
    • This mailing
      Refers to the currently open template.
      Example: you build a reminder mailing and only want to select contacts that already received this exact mailing once (e.g. for a follow-up).
    • Mailings of this event
      Refers to all mailings of the current event.
      Example: you want to email everyone who has already received any invitation for this event, regardless of the specific template.
    • Specific mailing
      Select a specific other mailing from a list (e.g. "SAVE-THE-DATE", "Early-bird invitation").
      • You open a dialog and search by internal name.
      • Useful when you want to target recipients of one concrete mailing only.
  • Minimum time since mailing ("more than … ago")
    • Optionally specify how much time must have passed at least since the selected mailing was sent to a contact (e.g. "more than 2 days ago").
    • Only contacts whose last send of that mailing is older than this duration are considered. Typical usage:
    • Ensure reminders are not sent too frequently.
    • Stagger communication flows (e.g. 3 days after first invitation, then 7 days before event start, etc.).
  • Received status ("already received / not yet received")
    • already received
      Selects contacts that have received the selected mailing (this, any or a specific one) at least once.
      Typical usage:
      • Reminders to everyone who already received an invitation.
      • Follow-up campaigns ("Thank you for your interest…").
    • not yet received
      Selects contacts that have not received the selected mailing so far.
      Typical usage:
      • Backfilling for newly added contacts.
      • Cleaning target groups to avoid duplicate or overly frequent mailings.

Ticket status ("Ticket status")

General explanation
This filter refers to the contact’s ticket status for the current event. It lets you distinguish precisely between registered, cancelled and checked-in participants.

Options

  • Has ticket
    The contact owns at least one ticket for the event (regardless of whether cancelled or checked in).
    • Ideal to steer ongoing communication for participants (e.g. travel info, program tips).
  • No ticket
    The contact does not yet have a ticket.
    • Use this for invitations, registration reminders or last-minute campaigns.
  • Has non‑cancelled ticket
    The contact has a ticket that is not cancelled (i.e. active).
    • Typical for event information relevant only to active participants (e.g. check‑in instructions).
  • Has cancelled ticket
    The contact had a ticket that has been cancelled.
    • Use this for re‑engagement or feedback mailings (e.g. "We’re sorry you cancelled…").
  • Has checked‑in ticket
    The contact has a ticket and has been checked in at the event.
    • Use this for post‑event follow-ups (e.g. "Thanks for joining", surveys, materials).
  • Has non‑checked‑in ticket
    The contact has a ticket but has not been checked in.
    • Ideal for "no‑show" communication or information that should only go to people who did not attend.

Participant category ("Participant category")

General explanation
For an event, contacts can belong to one or more participant categories (e.g. "Speaker", "Sponsor", "VIP", "Attendee"). This filter targets mailings based on those categories.

Options

  • Has any category
    The contact is in at least one category.
    • Useful if you want to separate people with categories from "raw" contacts or test contacts without categories.
  • Is in one of the following categories
    You select one or more categories. A contact must be in at least one of them.
    • Typical for role‑based communication (e.g. only "Speakers" and "Sponsors").
  • Is not in any of the following categories
    You select categories and exclude any contacts that are in any of them.
    • Useful to explicitly exclude certain groups (e.g. everyone except "VIP").

Unsubscribed from event ("Person is not unsubscribed from this event")

General explanation
This filter refers to whether a person has unsubscribed from the event. Independent of ticket status, it helps you exclude people who opted out from further invitations or reminders.

Options

  • Not unsubscribed
    The contact has not explicitly unsubscribed from the event.
    • Standard case for invitations and all event‑related updates.
  • Unsubscribed
    The contact has actively unsubscribed from the event.
    • This filter is used e.g. to send them a confirmation or separate information, while at the same time excluding them from further marketing mailings for this event.

Email bounce ("Previous deliverability")

General explanation
Filter by contacts that had email bounces in the past (delivery issues like "mailbox full", "address does not exist", etc.).

Options:

  • No bounces so far
    No delivery issues are recorded for this contact.
    • Recommended when you want to maximize campaign efficiency and avoid problematic addresses.
  • Has bounces
    There has been at least one bounce for this contact.
    • Can be used to reach out via alternative channels or to run a data‑cleaning campaign ("Please confirm your current email address").

Email address in list ("Email address in list")

General explanation:
With this filter you can provide a concrete list of email addresses. Only contacts whose email is included in this list are considered.

Typical use cases

  • You’ve built a target group externally (e.g. Excel list) and only want to reach those addresses.
  • You want to test a mailing with a small subgroup without creating dedicated categories.

Details

  • You can add email addresses to the list step by step in the UI.
  • The system checks for duplicates and prevents them.
  • Only contacts whose primary address exactly matches an entry are included.

Manual invitation flag ("Person is marked as invite manually")

General explanation
Some contacts can be explicitly marked as "invite manually". This indicates whether they should be invited via automated mailings or not.

Options

  • Marked as "invite manually"
    The contact has the "invite manually" flag.
    • Use this when you have a group that you want to invite personally, and therefore do not want to include in automated invitations (e.g. close personal contacts).
  • Not marked as "invite manually"
    The contact does not have this flag.
    • Useful when a campaign should only go to the regular audience and exclude special cases handled manually.

Limit count ("Limit number of simultaneous invitations")

General explanation
This filter limits how many recipients are considered for dispatch in a single run.

How it works

  • You enter a maximum number (e.g. "first 50 people").
  • After applying all other filters (voucher, ticket status, etc.), only the first X contacts in the result are selected.
  • The order is based on internal sorting (e.g. creation date or ID) and cannot be manually controlled.

Typical use cases

  • You want to test a new dispatch logic with only a small part of the target group.
  • You want to send in batches (e.g. waves of 100 contacts) to distribute load or monitor manually.

Notes

  • Avoid using very high values to keep your spam risk low.
  • By default, 100 contacts are configured.

Usage

With the dispatch settings and recipient filters you can precisely control when and to whom emails are sent. You can define automatic send times, define the target audience via filters and send test emails to ensure everything works correctly.