Skip to main content

Eventbrite to iPaaS.com Attendee Mapping Documentation

How Eventbrite attendees and order buyers transfer TO iPaaS.com as customers, one per email address, with their addresses and a summary of the events they registered for and attended.

Summary

Eventbrite attendees and order buyers can be transferred TO iPaaS.com as Customer records through Eventbrite webhooks, an order's transfer, an initialization run or Manual Sync. Each person becomes one iPaaS.com customer identified by their email address, with a summary of their event attendance in customer custom fields, and the addresses on their Eventbrite profile are written through the child collection Add/Update Eventbrite Attendee Address TO iPaaS.com in the same transfer. Because the Eventbrite API reference describes one attendee for each ticket sold (Attendee object), the integration treats the email address as the person, links each registration to the iPaaS.com customer with the same email, and then sends the person's attendance record through Add/Update Eventbrite Attendance TO iPaaS.com (see Integration Flow).

ID Format

Manual Sync ID Format

  • An attendee: the Eventbrite event id and attendee id joined by a vertical bar, for example 2004666506485|22902212230.

  • An order's buyer: the Eventbrite order number, for example 16096958843.

Any other value fails with the message that it "is not an Eventbrite attendee or order id". When you do not have the attendee id, resend the person's order by its order number from the Transaction Manual Sync instead: an order transfer sends its people first.

External ID Format

iPaaS.com saves the Eventbrite registration the person arrived with as the external ID on a dedicated external ID record, one per subscription: {event id}|{attendee id} for an attendee (for example 2004666506485|22902212230) or {order number} for a buyer (for example 16096958843). Because the same person arrives with a new attendee id at every event, the link moves to the newest registration; the email stays the same, so the customer stays the same.

Each address of the child collection is linked by the person's lowercased email and the address type joined by a vertical bar: {email}|bill, {email}|home, {email}|ship or {email}|work (for example jane.doe@example.com|home). The same person's address of the same type is therefore updated at every later event instead of being added again.

A customer number is also mapped (EB- and the person's first registration, for example EB-2004666506485-22902212230) for reference; it is not what links the person.

Deleted Record Support

Delete is not supported. This collection only adds and updates customers, and delete mappings are not part of the default template. A cancelled or refunded Eventbrite registration keeps the iPaaS.com customer: the event leaves the person's registered and attended lists and Eventbrite Attendance Status becomes Cancelled or Refunded. For an attendee deleted in Eventbrite, or an id Eventbrite does not know, nothing is transferred. An address removed from an Eventbrite profile stays on the iPaaS.com customer.

Custom Field Support

The default template writes twelve iPaaS.com customer custom fields:

Custom field (Customer)

Value

Eventbrite Events Registered

Every event the person registered for, newest event date first, as yyyy-MM-dd Event name [event id] entries separated by ;

Eventbrite Events Attended

Every event the person checked in to, in the same form

Eventbrite Events Registered Count

The number of events in Eventbrite Events Registered

Eventbrite Events Attended Count

The number of events in Eventbrite Events Attended

Eventbrite Last Registered Event

The event with the latest date in Eventbrite Events Registered

Eventbrite Last Registered Date

That event's local start date (yyyy-MM-dd)

Eventbrite Last Attended Event

The event with the latest date in Eventbrite Events Attended

Eventbrite Last Attended Date

That event's local start date (yyyy-MM-dd)

Eventbrite Attendance Status

The person's state at the event of the latest transfer: Attended, Registered, Cancelled or Refunded

Eventbrite Company

The company on the person's Eventbrite profile

Eventbrite Job Title

The job title the person gave at registration, when the event asks for it

Eventbrite Email Opt In

true or false for the person's opt-in to your marketing emails; empty when Eventbrite does not say

Keep these custom fields and their exact names. The integration reads Eventbrite Events Registered, Eventbrite Events Attended, Eventbrite Attendance Status, Eventbrite Company, Eventbrite Job Title and Eventbrite Email Opt In back from the customer by name; a renamed or missing field restarts the attendance lists or loses the value kept when a transfer carries none.

More Attendee fields can be mapped with Field mappings, for example Prefix, Suffix, CellPhone, WorkPhone, EventName, EventDate (the event of this registration) and AttendanceId (the person's attendance record at this event; empty for a buyer who holds no ticket).

Answers to an event's custom registration questions can be mapped with a Dynamic Formula that calls the conversion function EventbriteAnswer, for example return EventbriteAnswer(Answers, "Dietary requirements");. It returns the person's answer to that question, matched by the question's text or its Eventbrite question id, or an empty value when the question was not asked. An attendee's transfer carries the answers that attendee gave; a buyer's transfer carries the buyer's answers to the questions asked once per order. See the Eventbrite Mapping Functions.

Eventbrite has no custom fields of its own for this collection to read.

Mapping Collection Status

  • Status: Enabled.

  • Trigger Events: the attendee scopes turned on under the subscription's Inbound Data Flows: attendee.updated, attendee.checked_in, attendee.checked_out and, only when the Order collection's order.placed scope is off, attendee/registered. Also every transfer of Add/Update Eventbrite Order TO iPaaS.com (its scopes order.placed, order.updated and order.refunded, and transaction/initialize; its people are sent first), the customer/initialize initialization, and Manual Sync. No automatic transfers occur until the scopes are turned on.

Scope

What starts it

What is transferred

attendee/registered

A new Eventbrite order (Eventbrite's order placed event)

Each attendee with a different email, then the order's buyer

attendee.updated

An attendee changed in Eventbrite (for example their name, email, answers or address)

That attendee

attendee.checked_in

An attendee checked in

That attendee, now attended

attendee.checked_out

A check-in was undone

That attendee, with their attendance worked out again

customer/initialize

Running the initialization from the subscription

Every attendee changed in the last Initialization Days days, once per person per event; one run reads at most about 10,000 attendee tickets

When a webhook scope is turned on, the integration creates the matching webhook in your Eventbrite organization; turning the scope off removes it. The Eventbrite API reference names the check-in webhook actions attendee.checked_in and attendee.checked_out (Webhooks); in the organization's webhook list observed when this documentation was written, Eventbrite showed them as barcode.checked_in and barcode.un_checked_in. The integration recognizes either name as the same webhook. customer/initialize creates no Eventbrite webhook, but it must also be turned on for the subscription before it can run.

This collection has no mapping filter. To send only people from some events, subscribers or their MiSP can add a filter on the event name (EventName). Subscribers should validate this behavior in a staging environment before relying on it in production.

Whether a transfer adds or updates a customer depends on whether the person is already linked by an external ID or by email, not on which scope fired.

Duplicate or Conflicting Mappings

  • One customer per email. Several Eventbrite registrations of the same person (several tickets, several events, buyer and attendee) all update the same iPaaS.com customer.

  • Add/Update Eventbrite Order TO iPaaS.com. Each order transfer sends its people through this collection first. Its order.placed scope and this collection's attendee/registered scope start from the same Eventbrite event: turn on only one of them, or each person is sent twice.

  • Customers from other systems. A customer created by another system connected to iPaaS.com with the same email is linked and updated. The template protects what that system owns: FirstName, LastName and CustomerNumber are filled only when the customer has none, and Company and Comment keep their existing values. A name corrected in Eventbrite therefore does not change an existing customer. Subscribers should validate this behavior in a staging environment before relying on it in production. Decide which system is the source of truth for each customer field before enabling this collection alongside other customer sources.

  • Address collections TO iPaaS.com of other subscriptions. They can write addresses on the same customer. Their addresses are separate records: the address child collection updates only the addresses it wrote, identified by email and address type. Important: Treat Eventbrite as the source of truth for the addresses the address child collection writes; addresses that other systems write on the same customer are not changed.

Record Matching and Duplicates

This collection has no Collision Handling Method setting. Matching an existing customer is automatic: before each transfer the integration links the registration to the iPaaS.com customer with the same email (letter case is ignored). When no customer has the email, a new customer is added. When more than one customer already has it, nothing is linked and the transfer fails with a message naming the customers to merge or correct.

Unmapped Field Overwrite Risk

Warning — Unmapped Field Overwrite Risk: An update replaces the whole iPaaS.com customer, and each of its addresses. Every standard Customer field is mapped in the default template for Add/Update Eventbrite Attendee TO iPaaS.com, and four of them only carry the existing value forward: FirstName and LastName (kept when the customer already has a value) and Company and Comment (always kept). Removing one of these mappings overwrites that field with an empty value each time an inbound transfer runs. The following Customer Address fields are not mapped in the default template for Add/Update Eventbrite Attendee Address TO iPaaS.com, so any value entered in iPaaS.com on an Eventbrite address is overwritten with an empty value at the person's next transfer:

  • Type

  • Address3

  • Company

To preserve a customer field another system owns, keep a Dynamic Formula mapping that carries the existing iPaaS.com value forward with the DestinationValue function, for example return DestinationValue != null ? DestinationValue.Company : null; mapped to Company. To fill one of the address fields, add a mapping for it; for example, a Field mapping from the Eventbrite AddressType field (bill, home, ship or work) to Type.

Supported Child Collections

  • Add/Update Eventbrite Attendee Address TO iPaaS.com (child of Add/Update Eventbrite Attendee TO iPaaS.com): writes the addresses on the person's Eventbrite profile as the customer's addresses, as part of the parent's transfer. Each address is linked by the person's email and the address type.

System Caveats

Eventbrite Caveats

  • One attendee per ticket. The Eventbrite API reference describes one attendee for each ticket sold (Attendee object), so the same person has a new attendee at every event, and the integration treats the email address as the person.

  • Buyer-only events. As the Eventbrite API reference describes (Attendee object), when an event collects details from the buyer only, every ticket of the order carries the buyer's name and email. Those tickets become one customer (the buyer), registered once for the event and attended when any of the buyer's tickets is checked in. To receive each guest as their own customer, set the event's order form to collect information from each attendee.

  • Order form questions. In the Eventbrite organizer screens observed when this documentation was written, an event's order form offered one address question (Work, Home or Shipping) and one phone question. The free-ticket orders observed when this documentation was written carried no billing address. Job title arrives only when the form asks for it. At the time this documentation was written, Eventbrite's order-form builder did not offer a Company question (Eventbrite's API reference does list a "Company / Organization" question type), so Eventbrite Company stays empty unless Eventbrite supplies a company on the person's profile.

  • Addresses and phone. Eventbrite collects an address only when the event's order form asks for it; many events collect none, and the customer then transfers without addresses and without an error. The Eventbrite API reference places phone numbers on the attendee's profile, not on an address (Attendee object).

  • No email, no customer. An attendee with no email address is skipped with a warning that it has no email address ("… has no email address, so it can't be an iPaaS.com customer; skipped."). Their ticket stays on the order's transaction, and they have no attendance record.

  • Email opt-in. The integration takes the opt-in choice from the order, so a guest registered on another person's order shows the buyer's choice.

  • Rate limiting. Eventbrite allows a default of 2,000 API calls per hour per private token, shared by everything that uses the token. When the limit is reached, iPaaS.com holds the transfer and sends it automatically once the hour resets; no subscriber action is required. A person transfer usually reads Eventbrite two or three times.

iPaaS.com Caveats

  • One customer per email. The integration treats the email address as the person and links each registration to the iPaaS.com customer with the same email; when several customers share the email, the transfer fails with a message naming them. A person whose email changes in Eventbrite becomes a second customer, with their own addresses.

  • Phone on the address. iPaaS.com keeps the phone number on the address, so the person's mobile phone (else work phone) is written on the first address only.

  • Receiving systems. The attendance summary reaches another system only when that system's customer collection FROM iPaaS.com maps the Eventbrite custom fields; the attendance records only when its transaction collection FROM iPaaS.com takes them. Eventbrite people also reach the customer collections FROM iPaaS.com of your other subscriptions, such as a store or point of sale.

Setup Requirements

  • Eventbrite: the Private Token of an owner or admin of your Eventbrite organization (Eventbrite: Account Settings → Developer Links → API Keys, "Your private token"). Fill Organization Id only when that user belongs to several organizations. See the Eventbrite Installation Instructions for the full steps.

  • Eventbrite events: for events whose guests should be individual customers, set the order form to collect information from each attendee. To receive addresses, a phone number or a job title, ask for them on the order form.

  • iPaaS.com scopes: under Inbound Data Flows, turn on attendee.updated, attendee.checked_in and attendee.checked_out. Turn on attendee/registered only when the Order collection's order.placed scope is off. No partner-side webhook setup is needed: the integration creates the webhooks in Eventbrite.

  • Initialization: set Initialization Days (default 7, at most 365), turn on customer/initialize and run it to bring in recent attendees. One run reads at most about 10,000 attendee tickets; for a large organization, lower Initialization Days.

  • Receiving systems: to pass attendance on, map the Eventbrite custom fields in each receiving system's customer collection FROM iPaaS.com.

Integration Flow

  1. Trigger. A webhook, the initialization run, a Manual Sync or an order's transfer names an attendee ({event id}|{attendee id}) or an order (its buyer).

  2. Read. The integration reads the attendee, or the order's buyer, and the event from Eventbrite, together with the person's other tickets at the event. A person with no email address is skipped here with a warning that the person has no email address.

  3. Other people of a new order. For attendee/registered, the order's other attendees with a different email are queued as their own transfers before the buyer is written.

  4. Link by email. If the registration is not linked yet, the integration finds the iPaaS.com customer with the same email and links the registration to it. With no match, a new customer is added. With several matches, the transfer fails with a message naming the customers that share the email.

  5. Merge attendance. The integration reads the customer's current attendance fields and applies this registration: registered unless cancelled or refunded, attended when a ticket the person holds was checked in. The lists, counts and Last fields are recalculated, so a repeated or late delivery gives the same result. A buyer who holds no ticket changes no attendance.

  6. Addresses. Each address on the profile becomes one child record (billing, home, shipping, work), identified by the person's email and the address type. The first address carries the person's phone, and the primary billing and shipping flags are decided as described under the child mappings.

  7. Write. The person is mapped through this collection, with the address child collection, and written TO iPaaS.com as an Add for a new person or an Update for a linked one.

  8. Refresh the order. After an attendee.* event (changed, checked in, checked out), if the person's order is already in iPaaS.com for this subscription, the order is sent again so its ticket line follows the attendance. A failure here is only a warning; the person is already updated.

  9. Attendance record. After the person transfer, the person's attendance record at the event is sent through Add/Update Eventbrite Attendance TO iPaaS.com. Every person transfer, whatever started it (a webhook scope, an initialization, an order's people or a Manual Sync), is followed by that person's attendance record for the event, unless no ticket at the event carries the person's email (cancelled and refunded tickets still count, giving a Cancelled or Refunded record), for example a buyer who bought tickets only for others. A buyer who holds no ticket has none. A failure of this or any other transfer the integration starts on its own is only a warning, and the person's transfer is not affected.

Mappings

Add/Update Eventbrite Attendee TO iPaaS.com

iPaaS.com data type: Customer

Description: Eventbrite attendees and order buyers become iPaaS.com customers, one per email address, with a summary of their event attendance.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Field

EmailAddress

EmailAddress

Required. The person's email address, trimmed and lowercased: the person in iPaaS.com. The integration links the registration to the customer with the same email before the transfer; several customers with the email fail with a message naming the customers that share the email.

Field

CustomerNumber

CustomerNumber

Required. The customer number the customer already has, else EB- and the Eventbrite registration the person first arrived with (for example EB-2004666506485-22902212230, or EB-16096958843 for a buyer). Shown for reference; it is not what links the person.

Dynamic Formula

return DestinationValue != null && !string.IsNullOrWhiteSpace(DestinationValue.FirstName) ? DestinationValue.FirstName : FirstName;

FirstName

Required. The first name as typed at registration, used only when the customer has none, so a name another system keeps is never overwritten. A full name alone is split at the last space. Keep this mapping: removing it clears the first name on every update. Subscribers should validate this behavior in a staging environment before relying on it in production.

Dynamic Formula

return DestinationValue != null && !string.IsNullOrWhiteSpace(DestinationValue.LastName) ? DestinationValue.LastName : LastName;

LastName

Required. The last name as typed at registration, used only when the customer has none. Keep this mapping: removing it clears the last name on every update. Subscribers should validate this behavior in a staging environment before relying on it in production.

Dynamic Formula

return DestinationValue != null ? DestinationValue.Company : null;

Company

Required. Keeps the customer's existing company; a new customer gets none. Eventbrite's company goes to Eventbrite Company. Keep this mapping: removing it clears the company on every update. Subscribers should validate this behavior in a staging environment before relying on it in production.

Dynamic Formula

return DestinationValue != null ? DestinationValue.Comment : null;

Comment

Required. Keeps the customer's existing comment; Eventbrite has none. Keep this mapping: removing it clears the comment on every update. Subscribers should validate this behavior in a staging environment before relying on it in production.

Field

EventsRegistered

Eventbrite Events Registered (Custom Field)

Required. Every event the person registered for, newest event date first (newest 50). Do not remove or rename it: the integration reads it back to rebuild the attendance lists, counts and Last fields.

Field

EventsAttended

Eventbrite Events Attended (Custom Field)

Required. Every event the person checked in to, newest event date first (newest 50). Do not remove or rename it: the integration reads it back to rebuild the attendance lists, counts and Last fields.

Field

EventsRegisteredCount

Eventbrite Events Registered Count (Custom Field)

Recommended. How many events are in Eventbrite Events Registered.

Field

EventsAttendedCount

Eventbrite Events Attended Count (Custom Field)

Recommended. How many events are in Eventbrite Events Attended.

Field

LastRegisteredEvent

Eventbrite Last Registered Event (Custom Field)

Recommended. The event with the latest date the person is registered for.

Field

LastRegisteredDate

Eventbrite Last Registered Date (Custom Field)

Recommended. That event's local start date (yyyy-MM-dd).

Field

LastAttendedEvent

Eventbrite Last Attended Event (Custom Field)

Recommended. The event with the latest date the person checked in to.

Field

LastAttendedDate

Eventbrite Last Attended Date (Custom Field)

Recommended. That event's local start date (yyyy-MM-dd).

Field

AttendanceStatus

Eventbrite Attendance Status (Custom Field)

Recommended. The person's state at the event of this transfer: Attended, Registered, Cancelled or Refunded, worked out across all their tickets for the event. Kept when a transfer carries no ticket.

Field

Company

Eventbrite Company (Custom Field)

Optional. The company on the person's Eventbrite profile; empty unless Eventbrite supplies one (at the time this documentation was written, the order-form builder offered no Company question).

Field

JobTitle

Eventbrite Job Title (Custom Field)

Optional. The job title given at registration, when the event asks for it.

Field

EmailOptIn

Eventbrite Email Opt In (Custom Field)

Optional. true or false for the person's opt-in to your marketing emails, taken from the order; empty when Eventbrite does not say.

Translations: none.

Add/Update Eventbrite Attendee Address TO iPaaS.com (Child)

iPaaS.com data type: Customer Address

Description: The addresses on an Eventbrite attendee's profile, written as the customer's addresses with every transfer of the parent attendee.

External ID format: the person's lowercased email and the address type joined by a vertical bar: {email}|bill, {email}|home, {email}|ship or {email}|work (for example jane.doe@example.com|home). Addresses have no Manual Sync id of their own; resend the parent attendee.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Field

Address1

Address1

Recommended. The first line of the street address.

Field

Address2

Address2

Optional. The second line of the street address.

Field

City

City

Recommended. The city.

Field

Region

Region

Recommended. The state, province or region, as an ISO 3166-2 region code.

Field

PostalCode

PostalCode

Recommended. The postal code.

Field

Country

Country

Recommended. The country, as a two-letter ISO 3166 code (for example US).

Field

FirstName

FirstName

Optional. The person's first name.

Field

LastName

LastName

Optional. The person's last name.

Field

Phone

PhoneNumber

Optional. The person's mobile phone (else work phone), on the first address only.

Dynamic Formula

return DestinationValue != null ? DestinationValue.IsPrimaryBilling : IsPrimaryBilling;

IsPrimaryBilling

Required. Whether the address is the customer's primary billing address, decided by the integration as described below. Keep this mapping, or no Eventbrite address is marked as primary billing.

Dynamic Formula

return DestinationValue != null ? DestinationValue.IsPrimaryShipping : IsPrimaryShipping;

IsPrimaryShipping

Required. Whether the address is the customer's primary shipping address, decided by the integration as described below. Keep this mapping, or no Eventbrite address is marked as primary shipping.

Primary address flags: the integration decides the flags before mapping. An address this subscription already wrote keeps its flags. A customer with no primary billing address gets the billing address, else the home address, else the first address as primary billing; primary shipping goes the same way to the shipping address, else home, else the first. A customer that already has a primary address of a kind, for example from another system connected to iPaaS.com, keeps it, and the new Eventbrite address is added without that flag. Because, in the Eventbrite organizer screens observed when this documentation was written, an event's order form offered one address question, a person's addresses often arrive in separate transfers; the first address to arrive then keeps both flags, and later addresses are added without either.

First address: the addresses are taken in the order billing, home, shipping, work; the first one present carries the person's phone.

Translations: none.

Error Handling

Errors from this collection appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs; warnings appear in the transfer's activity log and do not fail the transfer. The full list of the integration's error codes and their resolutions is in the Eventbrite Error Messages article. The messages most often seen with people (integration error codes are omitted):

  • "… is not an Eventbrite attendee or order id. Use the order number (for example 1234567890) or, for an attendee, "{event id}|{attendee id}".": a Manual Sync id is in neither form. Resolution: enter the order number, or the event id and attendee id joined by a vertical bar.

  • "Eventbrite … has no email address, so it can't be an iPaaS.com customer; skipped. Its ticket stays on the order." (warning): the person has no email address. Resolution: nothing is required; to include them, add their email in Eventbrite and update the attendee.

  • "… iPaaS.com customers have the email … (ids …), so Eventbrite … was not linked. Merge or correct them in iPaaS.com, then transfer it again.": several iPaaS.com customers share the person's email. Resolution: merge the duplicates or correct the wrong email in iPaaS.com, then resend the attendee from Manual Sync.

  • "Looking up or linking the iPaaS.com customer for Eventbrite … failed (…). The transfer will be retried.": an iPaaS.com lookup before the transfer failed. Resolution: nothing is required; the transfer is retried. If it repeats, contact your MiSP or iPaaS.com Support.

  • "Order … was not refreshed after …; its ticket refreshes with the next order change." (warning): the order could not be sent again after an attendee change, check-in or check-out. The customer is already updated. Resolution: nothing is required, or resend the order from Manual Sync.

  • "Eventbrite … (…) was not sent TO iPaaS.com as a …: …. Resend it from Manual Sync." (warning): a transfer the integration started on its own (another person on the order, the order refresh, the person's attendance record) failed. The person's transfer is not affected. Resolution: fix what the message names, then resend that record from Manual Sync.

  • "Eventbrite's hourly API limit was reached during …; the transfer resumes at … UTC.": the first gap names what the integration was reading (for example, reading Eventbrite order 16096958843) and the second the date and time, in UTC, when the limit resets (for example, 2026-12-20 15:00). Eventbrite's hourly call limit for the private token was reached. Resolution: no action is needed; iPaaS.com holds the transfer and sends it automatically at the time shown.

The connection, webhook and organization messages apply to every Eventbrite collection and are described in the Eventbrite Installation Instructions and Eventbrite Connections and Settings.

Testing & Validation

Test Scenarios

  1. New person. Register one person for an event. Verify one customer with the lowercased EmailAddress, FirstName and LastName, a CustomerNumber starting EB-, the event in Eventbrite Events Registered, counts 1 and 0, and Eventbrite Attendance Status Registered.

  2. Check-in and undo. Check the person in. Verify the event in Eventbrite Events Attended, attended count 1, Eventbrite Last Attended Event and Eventbrite Last Attended Date set, and Eventbrite Attendance Status Attended. Undo the check-in and verify the event leaves Eventbrite Events Attended and the status returns to Registered.

  3. Second event. Register the same email for a second event. Verify the same customer, both events in Eventbrite Events Registered and Eventbrite Events Registered Count 2.

  4. Guest on another person's order. Place one order with two attendees who have different emails, on an event that collects details from each attendee. Verify each person is their own customer.

  5. Existing customer. Register an email that already belongs to an iPaaS.com customer from another system. Verify that customer is updated, not duplicated, and its FirstName, LastName, CustomerNumber, Company and Comment are kept.

  6. Replay. Resend the same attendee from Manual Sync with {event id}|{attendee id}. Verify the same customer and unchanged counts.

  7. Cancellation. Cancel an attendee's free order in Eventbrite. Verify the event leaves both lists, the counts go down, Eventbrite Attendance Status is Refunded, and the customer is kept.

  8. Addresses. Register a person on an event that asks for an address, then the same person on an event that asks for another address type. Verify one address per type, the first address holds both primary flags and the phone, and no duplicate address on the second event.

  9. No address. Register a person on an event that asks no address question. Verify the customer transfers without addresses and without an error.

  10. No email. Register a person without an email address. Verify no customer is created and the attendee transfer's activity log shows the warning that the person has no email address ("… has no email address, so it can't be an iPaaS.com customer; skipped.").

  11. Two customers with one email. Create two iPaaS.com customers with the same email address, then register that email in Eventbrite. Verify the transfer fails with a message that names both customers, and that nothing is linked; merge them and resend the attendee from Manual Sync.

Validation Checklist

  • The Private Token is set, and Organization Id when the token's user belongs to several organizations.

  • The attendee scopes you need are turned on (attendee/registered only when order.placed is off), and Eventbrite shows a webhook for each.

  • The twelve Eventbrite customer custom fields exist with their exact names.

  • Events whose guests should be individual customers collect details from each attendee.

  • Receiving systems' customer collections FROM iPaaS.com map the Eventbrite custom fields you want them to show.

Additional Notes

  • Buyers who hold no ticket become customers but change no attendance and carry no addresses.

Known Limitations

  • Newest 50 events. At the time this documentation was written, each attendance list keeps the newest 50 events; the attendance records keep every event.

  • Simultaneous deliveries. At the time this documentation was written, two deliveries for the same person in the same moment can overlap, so one event may be missing from the lists. The event returns the next time that registration is transferred; running customer/initialize rebuilds the lists for the period it covers. When the person has no customer yet, the two deliveries can also create two customers with the same email, and later transfers for that person can fail until only one remains; contact iPaaS.com support to merge them.

  • Empty address values. At the time this documentation was written, an address field left empty in Eventbrite is sent as empty and replaces the value on the Eventbrite address in iPaaS.com.

Out of Scope

  • Nothing is written to Eventbrite by these collections; the integration only reads attendees and orders, and manages its own webhooks for the scopes you turn on.

Related Documents

Related Mapping Documentation

External References

Did this answer your question?