Skip to content
EventDrakeEventDrakeEventDrake Docs

    Ticket rules

    A ticket rule matches one ticket, and through it the attendee, their order, and what they bought. For how conditions and groups work, see Rules.

    Where ticket rules are used

    Section titled “Where ticket rules are used”
    • Queue assignment. A rule decides which check-in queue a ticket is sent to. See Queue assignment rules.
    • Badge numbers. A rule decides which badge number a ticket is given. See Badge numbers.
    • Badge templates. A rule decides which badge design a ticket gets. See Badge templates.
    • NFC templates. A rule decides which NFC template a ticket gets. See NFC templates.

    Because the rule is about a ticket, every one of these places offers the same fields.

    What you can match on

    Section titled “What you can match on”

    The fields are grouped by what they describe:

    • Attendee. The person on the ticket: badge name, legal name, date of birth, age, email, and their public contact handles.
    • Ticket. The ticket itself: its booking type (for example a day pass or a weekend pass), its status, and any tags.
    • Payment. How the ticket was paid for.

    You can also reach related records:

    • A field on a single related record, such as the attendee’s email or the booking type’s title.
    • Matching across the ticket’s add-ons, using any, all, none, or a count. For example, “any add-on is Gala Dinner”, or “has at least one add-on”. Cancelled and refunded add-ons are not counted.