How to bring Eventbrite registrations, ticket orders, custom question answers and check-ins into HubSpot as contacts, marketing events and revenue, and how HubSpot can hand discount and access codes back to Eventbrite.
Eventbrite is a self-serve ticketing and registration platform. Every registration carries an identified buyer and attendee, which makes it one of the cleanest event sources a HubSpot portal can have.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Self-serve: the API is documented publicly, with OAuth apps or a private token.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
HubSpot's Eventbrite app covers registration and attendance; the custom build adds ticket revenue, answers and check-in detail on top.
Campaign Creators assessment
HubSpot's own Eventbrite app is the starting point. It creates or updates contacts from registrants, adds registration, attendance, cancellation and order-update events to the contact timeline, and syncs Eventbrite events to HubSpot marketing events. CC's custom build extends it on the Eventbrite REST API v3 and organization webhooks: orders and ticket types as HubSpot orders and line items, custom question answers as contact properties, check-in timing, event series, sponsor and exhibitor attribution, and discount and access codes created from HubSpot. The main decision is which process owns marketing events, so no event is written twice.
Ratings are CC judgments from Eventbrite's public API documentation and HubSpot's app documentation. Webhook behavior and rate limits are confirmed against the client's Eventbrite organization during discovery.
Every order has a buyer email and every attendee has a profile. Organization webhooks announce new orders, attendee updates and check-ins, so HubSpot does not wait on nightly exports.
HubSpot's app writes contacts, timeline events and marketing event participation. It does not sync custom contact properties, ticket revenue or line items. The custom build adds those without duplicating what the app already writes.
If HubSpot's app already syncs an event, the custom build attaches orders and properties to it rather than creating a second marketing event. The client signs off which events each process owns.
Seven parts of Eventbrite matter to HubSpot. HubSpot's app covers registration and attendance; the custom build uses the rest of the API for revenue, answers and write-back.
Creates or updates contacts from Eventbrite registrants and syncs events to HubSpot marketing events, with a sync toggle per event.
Eventbrite posts a small notice to a URL CC hosts. The notice carries an api_url and the action, and the integration fetches the full record from that URL.
order.placed, order.updated, order.refundedattendee.updated, attendee.checked_in, attendee.checked_outevent.* and ticket_class.* changesThe buyer, the order total and each ticket holder, with answers to the event's registration questions.
The event catalog: single events, recurring series with their dates, and the ticket types sold for each.
Coded discounts and access codes that unlock hidden tickets, created from HubSpot for a contact, list or sponsor.
One Eventbrite account can hold several organizations, each with its own events, webhooks and discounts.
HubSpot's app and the custom build can both write marketing events. Each Eventbrite event gets one owner, recorded in the SOW.
Eventbrite notifies a CC-hosted endpoint. The integration layer fetches the full order or attendee from the API, matches the contact, and writes orders, line items and properties to HubSpot beside what HubSpot's app already syncs. HubSpot workflows call back into Eventbrite for codes.
Every attendee lives once in HubSpot as a contact. Eventbrite data enriches that record; the integration never creates a second contact for the same email.
Webhook notices carry only a link. The integration always reads the current record from the API, so a late or repeated notice cannot write stale data.
HubSpot's app keeps what it already syncs. The custom build writes orders, line items and custom properties, and never rewrites the app's timeline events.
Each phase ends on a gate the client signs off before the next begins. HubSpot's app is configured first where it fits, then the custom build adds revenue, answers and write-back.
List the Eventbrite organizations, event types and series in use, the registration questions asked, and whether HubSpot's app is installed. Create an OAuth app or private token for an account admin of every organization in scope.
Pull recent orders and attendees through the API and document every ticket class, registration question and promo code pattern. Agree which questions become HubSpot properties.
Decide which events HubSpot's app syncs and which the custom build creates, how sponsors and exhibitors are tracked, and who sends confirmation and reminder emails.
Configure HubSpot's Eventbrite app for the events it covers. Create products for ticket classes, the order pipeline, custom properties and the Eventbrite property group in a sandbox.
Build the webhook receiver, API fetch, identity resolver, order builder, code bridge and error replay queue. Register webhooks per organization.
Load past orders and attendees for an agreed window of events through the paged API, then compute attendance rollups once.
Build follow-up, no-show and sponsor workflows with sends paused, run one live event in parallel, then switch on.
Field names follow Eventbrite's API v3 objects as publicly documented. Exact paths and expansions are confirmed against the client's organization during the event audit.
| Eventbrite field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Attendees · contacts | ||||
| attendee.profile.email | Contact | EB → HS | Match key. HubSpot's app also uses it. | |
| attendee.profile.first_name / last_name | firstname, lastname | Contact | EB → HS | Fill blanks only; HubSpot edits stay in HubSpot. |
| attendee.profile.company / job_title | company, jobtitle | Contact | EB → HS | Fill blanks only. |
| attendee.profile.cell_phone | mobilephone | Contact | EB → HS | Normalize to E.164. |
| attendee.id | eb_last_attendee_id | Contact | EB → HS | Stored as text for replay checks. |
| attendee.answers[] | eb_ question properties | Contact | EB → HS | One property per agreed question; dropdowns map to dropdowns. |
| count(attendees, checked in) | eb_events_attended | Contact | EB → HS | Computed in the integration layer. |
| Orders & tickets · revenue | ||||
| order.id | hs_external_order_id | Order | EB → HS | Native HubSpot order, one per Eventbrite order. |
| order.email (buyer) | Order → Contact association | Order | EB → HS | Buyer can differ from attendees; both are associated. |
| order.costs.gross | hs_total_price | Order | EB → HS | Confirm which cost field the client reports on (gross or net of fees). |
| order.created | hs_external_created_date | Order | EB → HS | |
| order.status / order.refunded | hs_pipeline_stage | Order | EB → HS | Placed, refunded or cancelled stages. |
| ticket_class.id, name | Product (hs_sku, name) | Product | EB → HS | One product per ticket class. |
| attendee ticket and cost | Line item | Line item | EB → HS | Quantity and price per ticket type. |
| promo or discount code used | eb_discount_code | Order | EB → HS | Confirm field path in discovery. |
| sum(order.costs) per contact | eb_lifetime_ticket_spend | Contact | EB → HS | Computed in the integration layer. |
| Events, series & check-in | ||||
| event.id, name, start, end | Marketing event | Marketing event | EB → HS | Created by the build only for events the app does not sync. |
| event.series_id | eb_series_id | Marketing event | EB → HS | Groups recurring dates for reporting. |
| organization.id | eb_organization_id | Marketing event | EB → HS | Separates brands or regions. |
| attendee.checked_in + check-in time | eb_last_checkin_at | Contact | EB → HS | From attendee.checked_in; confirm timestamp field in discovery. |
| attendee.status (cancelled / refunded) | Participation: cancelled | Marketing event | EB → HS | Matches HubSpot's cancel state. |
| Sponsors, exhibitors & write-back | ||||
| sponsor or exhibitor code | eb_attribution_source | Contact | EB → HS | Each sponsor gets its own access or discount code; confirm tracking method. |
| Sponsor company | Company + Deal | Deal | EB → HS | Sponsor packages tracked as deals in a sponsorship pipeline. |
| HubSpot workflow action | discount (coded) | Discount | HS → EB | Code created per contact or list, scoped to event and ticket classes. |
| HubSpot workflow action | discount (access) | Discount | HS → EB | Unlocks hidden VIP, speaker or partner tickets. |
| eb_issued_code | Code shown in HubSpot email | Contact | HS → EB | Stored so HubSpot emails can use it as a token. |
Eventbrite access is self-serve under the client's account. Values Eventbrite does not publish are marked for confirmation.
| Topic | Eventbrite | HubSpot |
|---|---|---|
| Authentication | OAuth 2.0 for apps, or a private token for a single account. The token's user must be an admin of each organization in scope. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Interfaces | Eventbrite REST API v3 at eventbriteapi.com: organizations, events, series, ticket classes, orders, attendees, discounts, webhooks. | REST APIs: CRM objects, commerce objects, marketing events, associations. |
| Webhooks | Created per organization, optionally per event. The POST body carries api_url and a config with the action and webhook ID; the full record is fetched from the API. Signing is not documented; CC uses a secret endpoint URL and the fetch-back. Confirm in discovery. | HubSpot signs its own webhooks with a v3 signature. |
| Retries | Eventbrite engineering describes retries every 10 minutes, up to 10 attempts. Delivery order is not documented, so a scheduled check by order update time runs as a safety net. | Client retries with backoff on 429. |
| Rate limits | Hourly and daily limits apply per OAuth token. Exact values: confirm with Eventbrite. Webhooks and expansions keep call volume low. | Per-10-second burst and daily limits by subscription tier. |
| Pagination & backfill | List endpoints return pages with a continuation token; expansions return answers and related records in one call. | Paged search and list APIs; CRM imports for large loads. |
| App requirements | HubSpot's app needs an Eventbrite Essentials, Professional or Premium plan, and the connecting user must be the Eventbrite account admin. | App installs with Super Admin or App Marketplace access. Marketing event workflows need Professional or Enterprise. |
Severity reflects impact on the SOW, not technical difficulty alone.
If HubSpot's app and the custom build both create the same event, participation splits across two records. The ownership matrix decides, per event, who writes it.
One buyer often registers a team. The order associates to the buyer, each ticket holder becomes a contact, and only identified attendees count toward attendance.
HubSpot's app syncs events created by the connected user. Events created by other team members are covered by the custom build or moved to the right owner.
Each event can ask different questions. The client agrees a standard question set; only those answers become HubSpot properties, and the rest stay on the timeline.
HubSpot's app does not recreate a deleted contact who registers again. The custom build follows the same rule, so privacy deletions are respected.
Eventbrite does not document a signature header. The endpoint uses a secret URL and always re-reads data from the API, so a forged notice cannot write data.
Orders and line items by ticket type let marketing see revenue per event, per campaign and per source, next to pipeline from the same contacts.
Role, company size, interests and dietary needs become contact properties for lists, lead scoring and sales follow-up.
Attendees get a thank-you and next step within hours; no-shows get the recording or the next date in the series.
Each sponsor's code shows who registered through them, so sponsorship renewals are sold on numbers.
Workflows create a discount or access code for a contact or list, so VIP and partner offers run from HubSpot targeting.
Recurring events roll up per series, so frequent attendees surface for community and loyalty programs.
HubSpot's app and the custom build each handle part of the journey, and every step lands on the same contact.
All custom properties use the eb_ prefix in an Eventbrite property group, separate from the group HubSpot's app creates. Totals are computed in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| eb_last_attendee_id | Last Eventbrite Attendee ID | Contact | Single-line text | attendee.id of latest ticket |
| eb_events_registered | Events Registered | Contact | Number | Count of attendee records |
| eb_events_attended | Events Attended | Contact | Number | Count of checked-in attendee records |
| eb_last_checkin_at | Last Check-in | Contact | Date and time | attendee.checked_in webhook |
| eb_lifetime_ticket_spend | Lifetime Ticket Spend | Contact | Number (currency) | Sum of order costs as buyer |
| eb_attribution_source | Sponsor / Exhibitor Source | Contact | Dropdown | Code used at registration |
| eb_issued_code | Issued Eventbrite Code | Contact | Single-line text | Discount created from HubSpot |
| eb_discount_code | Discount Code Used | Order | Single-line text | Promo or access code on the order |
| eb_series_id | Eventbrite Series ID | Marketing event | Single-line text | event.series_id |
| eb_organization_id | Eventbrite Organization ID | Marketing event | Single-line text | organization.id |
| eb_role | Role (registration answer) | Contact | Dropdown | Example question mapped from attendee.answers[] |
Choose the Eventbrite data for this engagement and the direction each field syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Webhook actions, field paths and rate limits are confirmed against the client's Eventbrite organization in the event audit.
Yes, two ways. HubSpot's own Eventbrite app is self-serve and covers registration and attendance. Campaign Creators' custom build extends it on the Eventbrite REST API v3 and organization webhooks, authenticated with OAuth 2.0 or a private token, for revenue, question answers and check-in detail the native app does not carry.
HubSpot's app creates contacts from registrants and logs registration, attendance, cancellation and order-update events, plus syncing Eventbrite events to HubSpot marketing events. The custom build adds orders and ticket types as HubSpot orders and line items, custom question answers as contact properties, check-in timing, event series, and sponsor or exhibitor attribution.
Eventbrite owns the registration and order record: ticket sales, refunds and attendee lists are worked there. HubSpot owns the contact and the marketing event, holding attendance and revenue detail the native app and custom build write to it, with one process designated to own each marketing event so it is never created twice.
Seven phases, each closed by a client sign-off: discovery and access through the client's own Eventbrite account, an audit of the events and custom registration questions in scope, ownership rules so marketing events are not duplicated, HubSpot setup alongside the native app, the build, a backfill of recent orders and attendees, and a parallel run before workflows and launch.
Timeline and cost depend on how many Eventbrite organizations are in scope, the custom questions and ticket types to map, and how sponsor or series attribution is handled. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.