Eventbrite ➔ Engagefully

Source System

Eventbrite

Destination System

Engagefully

Version

1.4.2026.8260

Description

Imports registrants from Eventbrite onto the Engagefully event roster with their name, email address, company and job title, and optionally their postal address, badge fields, and answers to registration questions. Registrants can also be placed into event roles and copied into a custom delegates list.

Event roles are populated in two separate ways, and the two are matched differently.

• From ticket classes. Ticket Class Mapping pairs an Eventbrite ticket class ID with an Engagefully role name, and roles are matched by name. Several ticket classes may point at the same role name. Each registrant is added to the role for the ticket they hold and removed from the other mapped roles. This mapping also supplies the Badge Type when Populate Badge Type is enabled, so the badge label is always the same text as the role name.
• From registration question answers. Populate Event Roles from Question Choices takes a list of question IDs. For every choice on those questions, the registrant is added to or removed from a role matched by external key, in the form {questionId}-{choiceId} - for example 12345678-87654321. With Auto-create event roles for registrants enabled, these roles are created for you the first time a registrant selects the choice, named after the choice text. You may rename them in Engagefully afterwards and the name will not be overwritten, because matching is on the external key. Without that setting, create each role by hand with its external key set exactly.

Ticket class IDs, question IDs and choice IDs are all specific to a single Eventbrite event, so each new event needs its own mapping entries and its own role external keys. All three can be read from the Eventbrite API harness: ticket class IDs from Get Ticket Classes, and question and choice IDs from Get Questions, where each question has an id and a choices array whose entries each carry their own id.

Only an answer that exists as a defined choice on the question can produce a role. A free-text answer, including anything typed into an "Other" box, has no choice ID and is ignored for role purposes - though it still appears in any custom field mapped to that question.

The Delegates Custom List is limited by Delegate List Roles, which matches on role name. Both kinds of role can be named there, but a role created from a question choice is named after the choice text, so the name must be entered exactly as the choice reads.

Other options: registrant postal address, Badge Type from the ticket class role, defaults for the Badge Custom fields, Company and the Directory and Lead custom fields from registration questions, and a communication opt-in derived from a question answer.

Mapping Information