New here? This page is a configuration reference for teams implementing the Eventbrite integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.
These are the known limitations of the Eventbrite integration. They are inherent to the current design of the integration and the capabilities of the Eventbrite API and organizer tools, and they apply to all subscribers at the time this documentation was written.
Areas covered: Across the Integration · Attendees and Customers · Orders · Attendance Records
Platform Scope and Tested Versions
Platform: This integration is built for Eventbrite, the event ticketing and registration platform, and works with the orders, attendees and events of one Eventbrite organization.
API: It calls the Eventbrite Platform API at https://www.eventbriteapi.com/v3. See the Eventbrite API reference at https://www.eventbrite.com/platform/api.
API version: The integration targets the Eventbrite Platform API v3 namespace and was built and tested against the documented production v3 endpoints as of November 10, 2026.
Eventbrite user: The integration works through the private token of an owner or admin of the organization that runs the events.
Not built for: Other ticketing or event-management platforms. If Eventbrite introduces a separate product line or a materially different API version in the future, this integration will not automatically support it.
Across the Integration
Related mapping documentation: Eventbrite to iPaaS.com Attendee Mapping Documentation, Eventbrite to iPaaS.com Order Mapping Documentation, Eventbrite to iPaaS.com Attendance Mapping Documentation
Data flows TO iPaaS.com only
At the time this documentation was written, the integration reads attendees and orders from Eventbrite and writes them TO iPaaS.com. Nothing is created, changed, cancelled, refunded or deleted in Eventbrite, except the webhooks the integration manages for the scopes you turn on.
What this means for you: Make registrations, check-ins, cancellations and refunds in Eventbrite; they reach iPaaS.com from there. Changes made in iPaaS.com or in another connected system do not reach Eventbrite. If your workflow needs data sent back to Eventbrite, submit a feature request to your iPaaS.com partner channel describing the requirement; input like this informs future enhancement releases.
Changes arrive by Eventbrite webhook
At the time this documentation was written, orders and people arrive by webhook, order refresh, initialization or Manual Sync; there is no scheduled poll. A scope receives changes only after it is turned on under Inbound Data Flows, and only while the webhook the integration created for it exists in Eventbrite. The Eventbrite API reference names the check-in webhook actions attendee.checked_in and attendee.checked_out (https://www.eventbrite.com/platform/api, 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.
What this means for you:
After an outage of iPaaS.com or Eventbrite, run the initializations (transaction/initialize and customer/initialize) again from the subscription over the days affected. They update the existing records and create no duplicates.
Load registrations made before a scope was turned on with the same initializations.
Do not delete the integration's webhooks in Eventbrite. If one was deleted, turn its scope off and on again under Inbound Data Flows to create it again.
An initialization run appears as one run
At the time this documentation was written, an initialization run appears in Integration Monitoring as one run; the orders and people it sends do not appear one by one. Each initialization also needs its scope turned on under Inbound Data Flows, although it registers no webhook in Eventbrite.
What this means for you: Confirm in Integration Monitoring that the run completed, then check the records in iPaaS.com. To follow a single order or person, resend it from Manual Sync.
Each initialization run reads about 10,000 records
At the time this documentation was written, one transaction/initialize run reads at most about 10,000 orders, and one customer/initialize run at most about 10,000 attendee tickets (one per ticket, not per person). Records beyond that are not read in that run.
What this means for you: For a large organization, lower Initialization Days so that one run covers fewer records. Resend any order or attendee the run did not reach from Manual Sync.
Eventbrite allows 2,000 calls per hour per private token
Eventbrite's API reference gives "Default rate limits are 2,000 calls per hour" for each token (https://www.eventbrite.com/platform/api, Errors). At the time this documentation was written, everything that uses the same private token shares that limit. 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, and an attendance record adds little Eventbrite traffic, because it reuses what the person's transfer read moments before.
What this means for you:
Use one Eventbrite private token per iPaaS.com subscription, and do not share it with other tools.
A large initialization can use the hour's calls by itself: run it when few registrations are arriving.
If the limit is reached at the moment the integration connects, the transfer can fail as a connection failure instead of being held. Resend it from Manual Sync after the hour resets.
One Eventbrite subscription per Eventbrite organization
At the time this documentation was written, each order and each attendance record is linked to its iPaaS.com transaction by an external ID record. If another transaction already holds the same transaction number without being linked to the record, iPaaS.com refuses the transfer as a duplicate rather than linking to it, so a second Eventbrite subscription connected to the same organization would have its copies refused.
What this means for you: Keep one Eventbrite subscription per Eventbrite organization. To send Eventbrite data to more systems, add those systems' collections FROM iPaaS.com; they all read the same customers and transactions. Subscribers should validate this behavior in a staging environment before relying on it in production.
The Organization Id is Eventbrite's organization id
At the time this documentation was written, the Organization Id setting takes the id of the Eventbrite organization. Eventbrite's API reference states that the organization id is not the same as the organizer id shown in an Organizer Profile URL (https://www.eventbrite.com/platform/api, Organization). When the setting is blank, the integration uses the only organization the token's user belongs to. With a wrong value, or a blank value while the user belongs to several organizations, the integration cannot connect. The failed transfer's message appears in Dashboard / Integration Monitoring / Error Logs, and its reason is one of the integration's connection messages, which lists the organizations the token can see by name and id (see Eventbrite Connections and Settings).
What this means for you: Leave Organization Id blank when the token's user belongs to one organization. Otherwise copy the right id from that reason, not from an Organizer Profile page. See Eventbrite Connections and Settings for the full settings checklist.
The private token acts as the Eventbrite user who created it
At the time this documentation was written, the private token works with the rights of the Eventbrite user who created the API key. If that user leaves the organization or loses the owner or admin role, the integration can no longer read the organization's orders and attendees, and transfers fail as connection failures (see Eventbrite Connections and Settings for the reasons shown).
What this means for you: Create the API key while signed in to a shared owner or admin account. To replace the token with a new one for the same organization, sign in as an owner or admin, create an API key, paste its private token into Private Token and click Apply, then turn each webhook scope off and on again, and run the initializations over the period since the old key stopped working.
Moving a subscription to another Eventbrite organization
At the time this documentation was written, the integration registers its webhooks in the organization the settings name when a scope is turned on, and removes them when the scope is turned off. Pointing an existing subscription at a different organization through Private Token or Organization Id leaves its webhooks in the previous organization: records that still arrive from there are skipped without an error, and the new organization sends nothing until its webhooks are created. The orders, people and attendance records already in iPaaS.com stay linked to the previous organization's Eventbrite ids.
What this means for you: Do not change the organization on an existing subscription. If a change is unavoidable, follow Changing the organization in Eventbrite Connections and Settings: while the current settings are still saved, turn every webhook scope off; change the settings and click Apply; turn the scopes on again; then run the initializations over the period the scopes were off. If the settings were changed first, the integration can no longer remove the webhooks in the previous organization, and they remain there. If you are unsure, consult your MiSP before proceeding.
Some records are skipped without an error
At the time this documentation was written, a record is skipped, and nothing appears in Dashboard / Integration Monitoring / Error Logs, when a collection's filter excludes it (including attendance records while the Attendance collection is off), when the person has no email address, when it belongs to another Eventbrite organization than the subscription's, or when Eventbrite no longer has it. For an order number Eventbrite does not know, or no longer has, the transfer's activity log shows the iPaaS.com message "TransferRequest is missing the payload data. This likely means the data no longer exists in the source system."
What this means for you: If a record neither arrives nor shows an error, check the collection filters, the person's email address in Eventbrite, the event's organization, and whether the record still exists in Eventbrite.
Deletions in Eventbrite are reflected as statuses
At the time this documentation was written, deletions are not transferred. A cancelled, refunded or deleted Eventbrite attendee never deletes the iPaaS.com customer, and an address removed from an Eventbrite profile stays on the customer. A cancelled or refunded order keeps its transaction with the matching status. An attendance record is never deleted: a person who no longer holds a ticket keeps the record with status Cancelled or Refunded.
What this means for you: Use the transaction and line statuses, and the attendance fields on the customer, to find cancelled and refunded registrations. Remove a customer or an address in iPaaS.com yourself when it is no longer wanted.
Updates replace the whole record
At the time this documentation was written, an update replaces the whole iPaaS.com customer, customer address or transaction, lines included. A field the collection does not map is cleared each time the record transfers again, and a few mappings exist only to carry the existing iPaaS.com value forward:
Add/Update Eventbrite Attendee TO iPaaS.com: every standard Customer field is mapped. FirstName and LastName are kept when the customer already has a value, and Company and Comment are always kept.
Add/Update Eventbrite Attendee Address TO iPaaS.com: Type, Address3 and Company are not mapped. IsPrimaryBilling and IsPrimaryShipping are required: keep them, or no Eventbrite address is marked as primary.
Add/Update Eventbrite Order TO iPaaS.com: every transaction field subscribers can map is mapped; for ShippingAmount, see Shipping amounts, and attendance discounts, are kept from iPaaS.com.
Add/Update Eventbrite Attendance TO iPaaS.com: Subtotal and TaxAmount are not mapped and are 0 by design; for DiscountAmount and ShippingAmount, see Shipping amounts, and attendance discounts, are kept from iPaaS.com.
Add/Update Eventbrite Order Ticket TO iPaaS.com and Add/Update Eventbrite Attendance Ticket TO iPaaS.com: the line fields DiscountAmount, DiscountPercent, EstimatedTaxAmount, LineInfo, OriginalUnitPrice, QtyShipped, SequenceNumber, TaxPercent and Weight are not mapped.
What this means for you: For every mapped field, Eventbrite is the source of truth. Keep the mappings that carry existing values forward: removing one clears that field on every update. If another system or a user fills an unmapped field, subscribers or their MiSP can add a Dynamic Formula mapping that keeps the existing value with the DestinationValue function, in the same form as the ShippingAmount mapping, for example DestinationValue.DiscountAmount for a line's DiscountAmount. Subscribers should validate this behavior in a staging environment before relying on it in production.
Some Eventbrite fields stay in Eventbrite
At the time this documentation was written, the default mappings carry the fields described in the mapping documentation. The integration offers more Eventbrite order, ticket, attendee and event details as fields to map than the default mappings use; subscribers or their MiSP can add a mapping for any of them in the mapping collection. Some Eventbrite details (Eventbrite API reference, https://www.eventbrite.com/platform/api) are not read at all:
Ticket types: each ticket carries its ticket type's name and id; the ticket type's own details, such as its price, capacity and sales dates, are not read.
Security, payment and display settings: ticket barcode contents, event passwords, checkout and payment settings, event and organizer images, the event's listing, display and seat-map settings, organizer event counts, and the details of the Eventbrite organization itself (the integration reads the organization only to find its id).
What this means for you: Map the fields the mapping documentation lists, and add mappings for any other offered field your workflow needs. If your workflow needs one of the details that are not read, submit a feature request to your iPaaS.com partner channel describing the field and how you use it; input like this informs future enhancement releases.
Event registrations reach other systems' transaction collections
At the time this documentation was written, Eventbrite orders and attendance records are iPaaS.com transactions, so the transaction collections FROM iPaaS.com of your other subscriptions (for example a store, ERP, accounting, point-of-sale or donor database system) can pick them up. Attendance records have the transaction type Ticket, so a filter that takes only type Order already skips them.
What this means for you: Review the filters of every transaction collection FROM iPaaS.com in your company before turning the Eventbrite collections on. On any collection that must not receive event registrations, add a condition to its filter that skips transactions whose Eventbrite Event Id custom field is filled; the Eventbrite to iPaaS.com Order Mapping Documentation shows the condition. Orders and attendance records both carry Eventbrite Event Id, so the same condition keeps both out. Subscribers should validate this behavior in a staging environment before relying on it in production.
Attendees and Customers
Related mapping documentation: Eventbrite to iPaaS.com Attendee Mapping Documentation
One customer per email address
At the time this documentation was written, the Eventbrite API reference describes one attendee for each ticket sold (https://www.eventbrite.com/platform/api, Attendee object), so the same person has a new attendee at every event, and the integration treats the email address as the person. Before each transfer, the integration links the registration to the iPaaS.com customer with the same email address (letter case is ignored), so the same person on several tickets, at several events, or as both buyer and attendee stays one customer.
What this means for you:
An email change makes a new customer. A person whose email changes in Eventbrite, or who registers with a second address, becomes a second customer with their own addresses, and their attendance is split between the two. Merge them in iPaaS.com if needed.
People who share an email are one customer, for example a couple registering with one email address.
Several customers with the same email block the link. When more than one iPaaS.com customer already has the email, nothing is linked and the transfer fails with a message that names the customers, and an order from that buyer is written with no customer set. Merge or correct them, then resend the person and the order from Manual Sync.
People without an email address are not sent as customers. 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.
Values other systems own are kept. FirstName, LastName and CustomerNumber are filled only when the customer has none, so a name corrected in Eventbrite does not change an existing customer. Correct the name on the iPaaS.com customer, or in the system that owns it.
Buyer-only events give every ticket the buyer's details
At the time this documentation was written, as the Eventbrite API reference describes (https://www.eventbrite.com/platform/api, 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; the guests have no customer or attendance record of their own.
What this means for you: To receive each guest as their own customer, set the event's order form to collect information from each attendee before registrations open (see Eventbrite Installation Instructions). Orders placed before the change keep the buyer's details on every ticket.
Turn on attendee/registered only when order.placed is off
At the time this documentation was written, the attendee/registered scope and the order.placed scope both start from Eventbrite's order placed event. order.placed already sends each new order's buyer and attendees before the order, so with both on, each person is sent twice.
What this means for you: Use order.placed to bring orders and their people. Turn on attendee/registered only to bring people without their orders, with order.placed off.
Order-form questions decide which details arrive
At the time this documentation was written, the integration receives only the details the event's order form asks for. 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.
What this means for you: Set up each event's order form in Eventbrite to ask for the details you need before registrations open. Many events collect no address, and the customer then transfers without addresses and without an error.
Company and job title arrive in custom fields
At the time this documentation was written, the attendee's company and job title are written to the customer custom fields Eventbrite Company and Eventbrite Job Title. The customer's Company mapping keeps the value the customer already has, so a company another system set is never replaced from Eventbrite.
What this means for you: To fill the customer's Company from Eventbrite instead, subscribers or their MiSP can change the Company mapping to a Dynamic Formula that uses the Eventbrite company when one is given and otherwise keeps the existing value with the DestinationValue function. A plain field mapping would blank the company whenever an event does not ask for it, because an update replaces the whole customer. Check first how your receiving systems treat a customer that has a company. Subscribers should validate this behavior in a staging environment before relying on it in production.
Attendance lists keep the newest 50 events
At the time this documentation was written, each attendance list (Eventbrite Events Registered and Eventbrite Events Attended) keeps the newest 50 events; the attendance records in Add/Update Eventbrite Attendance TO iPaaS.com keep every event. The counts count the kept entries, so they stop at 50.
What this means for you: For a person with more than 50 events, the oldest drop off the lists. Use the person's attendance records for their full history. If a receiving system's field holds fewer characters than a full list, map the list to a longer field there, or map the count and Last fields instead.
Two deliveries for the same person at the same moment
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. For example, two check-ins at two events at once can each miss the other's event. When the person has no iPaaS.com customer yet, the two deliveries can also each create one, so the person has two customers with the same email. This happens most often when a new person places an order, because Eventbrite sends the attendee and the order deliveries together.
What this means for you: A missing event returns the next time that registration is transferred. Running customer/initialize rebuilds the lists for the period it covers, and resending the attendee from Manual Sync repairs one person at once. Check new people for a second customer with the same email; later transfers for that person can fail until only one remains. Contact iPaaS.com support to merge the two customers.
Events Registered and Events Attended are read back by name
At the time this documentation was written, the integration reads Eventbrite Events Registered and Eventbrite Events Attended back from the customer to rebuild the attendance lists, counts and Last fields, and reads Eventbrite Attendance Status, Eventbrite Company, Eventbrite Job Title and Eventbrite Email Opt In back by name to keep their values when a transfer carries none.
What this means for you: Keep these custom fields and their mappings, with their exact names. A renamed or removed field restarts the attendance lists or loses the value kept when a transfer carries none.
Attendance reaches receiving systems through custom fields and attendance records
At the time this documentation was written, the integration does not assign customer categories (such as one per event). Attendance travels two ways instead: as a summary in custom fields on the iPaaS.com customer, and as one attendance record per person per event (a transaction of type Ticket on the person's customer). 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.
What this means for you:
In a CRM or donor database whose customer collection FROM iPaaS.com maps custom fields, add the mappings you need, for example Eventbrite Events Attended, Eventbrite Last Attended Event and Eventbrite Attendance Status, and segment people there.
A receiving system that takes transactions FROM iPaaS.com can receive the attendance records when its filter lets transactions of type Ticket with Eventbrite Event Id through. Whether it shows them as event attendance depends on that system and its mappings.
A system that takes only standard customer fields receives the person but not their attendance.
Eventbrite people reach other systems' customer collections
At the time this documentation was written, Eventbrite people are iPaaS.com customers, so the customer collections FROM iPaaS.com of your other subscriptions (for example a store or point of sale) can receive them too. No field marks a customer as coming only from Eventbrite: a person already known from another system who registers gets the same Eventbrite fields.
What this means for you: Decide for each receiving system whether it should take event attendees. A filter on the Eventbrite fields in another system's customer collection would also exclude that system's own customers who attended an event.
Each address type is kept once, and the first address keeps the primary flags
At the time this documentation was written, each Eventbrite address is linked by the person's email address and the address type (billing, home, shipping or work), so a returning person keeps one address of each type, updated when it changes. An address this subscription already wrote keeps its primary flags, and a customer that already has a primary address of a kind (for example from another system) keeps it. 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 the primary billing and the primary shipping flag, and later addresses are added without either.
What this means for you: If a different address should be primary, change the flags on the customer in iPaaS.com; a later transfer keeps the flags of addresses it already wrote. The person's phone number is placed on the first address only, because iPaaS.com keeps the phone number on the address.
Empty Eventbrite address values replace the iPaaS.com value
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.
What this means for you: Treat Eventbrite as the source of truth for the addresses this integration writes, and correct an address in Eventbrite rather than in iPaaS.com. Addresses that other systems write on the same customer are not changed.
Orders
Related mapping documentation: Eventbrite to iPaaS.com Order Mapping Documentation
Orders carry Eventbrite's totals, and payments stay in Eventbrite
At the time this documentation was written, no transaction payment is written. An order's Total, Subtotal, TaxAmount and Eventbrite Fee figures are Eventbrite's own for the order, as Eventbrite reports them, in the order's currency (given in Eventbrite Currency) with no exchange rate applied; they are 0 on a free order.
What this means for you:
A receiving system that needs a payment on each transaction (for example an accounting system posting event revenue) cannot take Eventbrite orders as paid sales. Record event revenue from Eventbrite's own payout reports.
If your events use several currencies, check how your receiving systems treat amounts in a currency other than their own.
Subscribers who sell paid tickets should validate this behavior on a paid order in a staging environment before relying on it in production.
Refunds and cancellations are reflected as statuses
At the time this documentation was written, a refund or a cancellation changes statuses only; no refund transaction, credit or negative payment is written. An order is Placed while any of its tickets is still held, Refunded when every ticket was refunded, and otherwise Cancelled. Cancelling one ticket of a multi-ticket order changes only that ticket's line; the order stays Placed and the transaction Complete. In the orders observed when this documentation was written, Eventbrite recorded a cancelled free order as refunded, so it arrived as Refunded, with every line Refunded.
What this means for you: Account for refunds from Eventbrite's own reports. To skip cancelled orders in the Order collection's filter, skip Refunded too; the Eventbrite to iPaaS.com Order Mapping Documentation shows the full filter and what it changes.
Shipping amounts, and attendance discounts, are kept from iPaaS.com
At the time this documentation was written, the integration does not write a shipping total from Eventbrite. The ShippingAmount mapping of Add/Update Eventbrite Order TO iPaaS.com and Add/Update Eventbrite Attendance TO iPaaS.com keeps the amount the transaction already has in iPaaS.com and writes 0 on a new transaction. The order's DiscountAmount is Eventbrite's discount for the order; an attendance record carries no amounts, so its DiscountAmount mapping keeps the existing value the same way.
What this means for you: Keep these mappings: removing one resets that amount to 0 on every update. A discount entered on an order's transaction in iPaaS.com is replaced by Eventbrite's discount on the next transfer of the order. Subscribers should validate this behavior in a staging environment before relying on it in production.
Fees and tax stay on the order, not on the lines
At the time this documentation was written, each ticket line carries the ticket's price before fees and tax. The order's fees are summed in Eventbrite Fee, and its tax is in TaxAmount; each individual tax is also written as a transaction tax by Add/Update Eventbrite Order Cost Component TO iPaaS.com. Fees and shipping charges are not written as taxes.
What this means for you: Use the order's TaxAmount, its transaction taxes and Eventbrite Fee for tax and fees. A receiving system that expects tax on each line receives it on the transaction instead. A receiving system that sums transaction taxes and also reads TaxAmount should use one or the other. Subscribers should validate this behavior in a staging environment before relying on it in production.
One event-ticket product for every ticket
At the time this documentation was written, ticket types are not mapped to separate iPaaS.com products. Every order line and every attendance line uses the one iPaaS.com product whose SKU is set in the Sku mapping of Add/Update Eventbrite Order Ticket TO iPaaS.com and Add/Update Eventbrite Attendance Ticket TO iPaaS.com. The ticket type travels in the line's Description and in Eventbrite Ticket Class. iPaaS.com refuses a line whose SKU is not an existing product, and the whole transaction fails with it.
What this means for you: Create the event-ticket product in iPaaS.com, or choose an existing one, before turning the order and attendance collections on, and put its SKU in both Sku mappings (see Placeholder Values to Replace Before Go-Live). Report by ticket type from Description or Eventbrite Ticket Class.
Event Start appears as a US-formatted date and time
At the time this documentation was written, Eventbrite Event Start appears in iPaaS.com as a US-formatted date and time (for example 03/15/2027 10:00:00), not in ISO 8601 form. It is in the event's local time, with no time zone. This applies to both order and attendance transactions.
What this means for you: Read the value as month/day/year and the event's local time. A receiving system that expects another date format needs a formula or a conversion in its own collection.
Registration answers arrive as order notes
At the time this documentation was written, each answer to an event's custom registration questions is written as a transaction note on the order by Add/Update Eventbrite Order Answer TO iPaaS.com, for example Dietary requirements: Vegetarian; questions nobody answered are skipped. In a custom field, EventbriteAnswer returns one answer: on an order, the first answer to that question on the order; on an attendee transfer, the attendee's own answer; on an attendance record, the answer of the person's first ticket for the event.
What this means for you: Use the order notes to see every answer, and a custom field with EventbriteAnswer when a receiving system needs one answer in a fixed field. On an order with several attendees, map the answer on the customer or the attendance record when each person's own answer matters.
Attendance Records
Related mapping documentation: Eventbrite to iPaaS.com Attendance Mapping Documentation
Attendance records carry no amounts
At the time this documentation was written, attendance records and their lines carry no prices, fees, tax, discounts or payments: totals and line prices are 0 on every attendance record. Event revenue, as Eventbrite reports it, is on the order's transaction, so it is counted once.
What this means for you: Use the order's transaction for amounts and the attendance record for who registered and who came. Keep UnitPrice and ExtendedPrice at 0 on attendance lines: mapping an amount there would count the ticket's revenue a second time.
Check-ins reach iPaaS.com within a few minutes
At the time this documentation was written, a check-in reaches iPaaS.com within a few minutes of Eventbrite reporting it, not at the door. The systems connected to iPaaS.com then receive it on their own schedules.
What this means for you: Do not rely on the integration for live door decisions. Use Eventbrite's own check-in tools at the door.
Undoing a check-in and checking out look the same
In the Eventbrite organizer screens observed when this documentation was written, undoing a check-in and checking an attendee out both reset the ticket in Eventbrite and left the same trace. At the time this documentation was written, after either, the line returns to Pending, its Eventbrite Checked In is false, and the attendance record returns to Pending while the person holds the ticket. If Eventbrite still reports the barcode as used after a check-out, the ticket still counts as attended.
What this means for you: Receiving systems cannot tell an undone check-in from a check-out. If you need to record people leaving an event, record it outside the integration.
An attendance record holds the tickets its person transfer saw
At the time this documentation was written, an attendance record holds the tickets the person's transfer just read, plus the tickets on the orders the person placed for the event. The integration finds the person's orders by the email of the person who placed them, so a ticket someone else bought for the person is included when the person is sent from that order or ticket, not when the record is sent on its own later. The email is part of the record's transaction number: people who share an email share one record, and a person whose email changes gets new records under the new email.
What this means for you: To refresh a person's attendance record with every ticket, resend the attendee (under Customer) or the order from Manual Sync, not the attendance record on its own. To stop attendance records altogether, turn Add/Update Eventbrite Attendance TO iPaaS.com off; orders and customers are not affected. An attendance record that succeeds inside a person or order transfer has no Integration Monitoring entry of its own: check the record in iPaaS.com, or resend the attendee from Manual Sync to follow it in the activity log.
Tickets that share an email look alike at check-in
In the Eventbrite check-in screen observed when this documentation was written, only each ticket holder's name and email were shown, so tickets that share an email (for example two tickets a person bought in their own name) could not be told apart when checking in. At the time this documentation was written, those tickets are also one person and one attendance record in iPaaS.com.
What this means for you: To check guests in individually and receive them as separate people, set the event's order form to collect information from each attendee, with each guest's own email address.
Placeholder Values to Replace Before Go-Live
One shipped mapping carries an instruction value that each subscriber replaces before going live. The mapping collection descriptions carry the same instruction in their placeholder callouts.
Where | Placeholder value | Replace with |
Sku in Add/Update Eventbrite Order Ticket TO iPaaS.com and Add/Update Eventbrite Attendance Ticket TO iPaaS.com | REPLACE with your event ticket SKU | The SKU of your iPaaS.com event-ticket product, exactly as it is in iPaaS.com, for example EVENT-TICKET or GA-ADMISSION, or the SKU of an existing product. Use the same SKU in both. |
Until both are replaced, every order and every attendance record is refused with "NFND-1003 - Product Id: REPLACE with your event ticket SKU does not exist or can not be found." in Dashboard / Integration Monitoring / Error Logs; the people are still sent as customers.
Summary
This document covers 38 known limitations, grouped by feature, plus one placeholder value to replace before go-live. For detailed, per-collection behavior, see the mapping collection descriptions in iPaaS.com and the mapping documentation named at the start of each feature section.
