Learn more about the Eventbrite Integration with Alpine
OVERVIEW
Your Alpine database can be configured to automatically integrate with your Eventbrite account, pulling transactions and Constituents on a nightly basis into your database. With the Eventbrite integration for Humanitru you can sync event registrations and ticket purchases directly to your Alpine database.
WHAT WE PUSH INTO EVENTBRITE
Since the goal of this integration is to pull information from Eventbrite, your Humanitru Alpine database will not push any information into your Eventbrite account, it will only pull information.
WHAT WE PULL FROM EVENTBRITE
On a nightly basis, Alpine will fetch a list of Eventbrite event registrations. If the integration has never been run before, it will sync all historical transactions.
Constituent Profile
|
Eventbrite Field |
Alpine Constituent Field |
|
|
|
|
|
Name |
|
|
Email Salutation |
|
|
Added to custom field (if present) |
|
|
Added to custom field (if present) |
Note: If an order lacks a name, the system will use "Contact for [email]" as the Constituent name
Action Mapping
All Alpine Actions will be associated with one Constituent, that is matched / de-duplicated by the email address given in the Eventbrite Order. This means that any Eventbrite Order without an email address will be skipped, and not synced into Alpine.
|
Eventbrite Field |
Humanitru Alpine Field |
|
order.created |
Action Date |
|
order.costs.gross.major_value |
Amount |
|
attendee.answers
|
Added to the notes section |
|
attendee.profile.company |
Added to the notes section (if present) |
|
attendee.profile.job_title |
Added to the notes section (if present) |
|
event.name |
The Campaign “Eventbrite Events: Event ID” will be attached |
Note: Each attendee, including the main reserver, receives an "Action" record for their ticket/registration. Attendee Actions include a note referencing the main reserver.
SYNC DETAILS
Timing: Nightly
Data is synchronized nightly from Eventbrite to Alpine. This is not a real-time sync.
Constituent Matching: Email, then Name
When matching Eventbrite registrations to existing Constituents, Alpine first checks for a matching email address. If none is found, it attempts to match by name. If still no match, a new Constituent record is created.
Skip Logic for Duplicates
Attendees are skipped if their email matches the purchaser or if they have the same name as the purchaser (when no email provided)
Action Matching: Yes
Each Eventbrite order or ticket is imported with its unique Eventbrite ID to prevent duplicate Actions and ensure reliable, idempotent syncing.
CONNECTING YOUR EVENTBRITE ACCOUNT
-
Go to the following link to register the Humanitru Alpine integration to your Eventbrite account: https://developer.Eventbrite.com/developer/applications/
-
In the upper right hand corner, click the blue “Log in to Dashboard” and log in with the Eventbrite account you wish to connect to Alpine
-
Under “My apps & credentials”, click on “Live” to make it selected
-
Under REST API apps, click the blue “Create App” button
-
Under “App Name”, fill in “Humanitru Alpine Integration”, and click “Create App”
-
Please record the “Client ID” token to send to your Customer Success Manager
-
Click “Show” under “Secret”, and record the “Secret” token to send to your Customer Success Manager
-
[IMPORTANT] Scroll down to the very bottom, under “Live App Settings”, and make sure the checkbox next to “Transaction Search” is checked (if it is not already checked, check the checkbox and click “Save”)
-
In conclusion: send your Customer Success Manager the “Client ID” token, the “Secret” token, and the date starting from which you wish your Eventbrite transactions to sync to Alpine
TECHNICAL CAVEATS
-
Only completed registrations/orders are imported. Cancelled, refunded, or incomplete registrations are skipped.
-
Each individual event in Eventbrite is mapped to a Campaign in Alpine; all Actions for that event are linked accordingly.
-
Custom registration answers are imported and stored in Action notes.
-
Duplicate attendees and Actions are minimized by strict email and Eventbrite ID matching.