The basic Eventbrite - HS integration doesn’t give us the option to create the list based on Ticket Type purchased. I’d like to create custom API integration. It will only be one way API integration. Question:
1. We are on Marketing and Sales Pro licence. Is it enough to create integration like this?
2. We are not tech people and are looking for help in organising this. Can HubSpot help us to create something like this inhouse?
Thanks
Bart
Hey @Bartedi
You would want to use a developer account to create the integration. You would want to work with other members of the Community to build this app. There is a jobs board here as well as one on the developer slack group that you could post to
Good luck building it! Let us know when it is complete so we can see your handy work 
Perfect thank you Dennis
The short answer is:
Yes, your Marketing and Sales Pro licenses are more than sufficient to support a custom API integration, as both tiers grant full access to the HubSpot API needed for creating or updating contacts and lists.
Since the native integration doesn’t offer the ticket type segmentation you need, the best approach is a custom solution where Eventbrite webhooks are used to trigger a data transfer every time a ticket is purchased.
This data is processed by a middle layer, which then uses the HubSpot API to correctly map the specific ticket type to a custom contact property, allowing you to build the granular HubSpot list you require.
HubSpot’s in-house team won’t build this for you, but you should look for a certified HubSpot Solutions Partner developer 
The long answer is:
The native integration’s limitation, where you can only segment by broad properties like Last registered event and Last registered event date, is common because it’s designed to be a one-size-fits-all solution.
Your need to segment by specific ticket type (e.g., VIP vs. General Admission) requires a deeper, custom data payload, which is why a custom API integration is the way to go.
Regarding your first question, your Marketing and Sales Pro licenses are excellent foundations for this project.
They give you the necessary access to the HubSpot API, allow the creation of custom contact properties to store the ticket type, and include all the segmentation and workflow functionality needed to act on that data.
For your second question, HubSpot’s internal support or sales team will generally not build this custom code for you, as they focus on core product features.
You need to hire a developer or a certified HubSpot Solutions Partner.
The recommended custom solution involves setting up Eventbrite webhooks.
Instead of constantly polling the Eventbrite API for changes, a webhook is an automated message Eventbrite sends to a specific URL (your server) immediately after a key event, like an `order.placed` or `attendee.updated` event, which contains the specific ticket type data.
This is where an environment managed by Google Tag Manager and hosted on Stape or Google Cloud Platform becomes an excellent solution.
When the webhook hits your server (the Stape/GCP environment), a custom script processes the Eventbrite data, identifies the ticket type, and then uses the HubSpot API to either create a new contact or update an existing one, setting a dedicated custom contact property, such as `Eventbrite_Ticket_Type`, to the corresponding value.
Because you are on Pro, you can then easily create a smart list in HubSpot that dynamically includes all contacts where `Eventbrite_Ticket_Type` is, for example, “VIP Ticket.”
This API and webhook approach is far superior to simple API polling because it provides near real-time synchronization, reduces the load on your systems, and gives you the flexibility to map and transform any piece of Eventbrite data directly into HubSpot’s CRM fields, enabling your granular segmentation goals
This comment was generated with the assistance of an AI tool, incorporating my expertise in integrations 