What it costs and what you need
There is no charge for the connection itself and no keys to copy. You need an Eventbrite account that holds your events, and permission on that account to approve an app. Everything else happens inside MyCo.
Your Eventbrite pricing, ticket fees and payouts are unaffected. MyCo reads your events and attendees, it does not sell tickets and it never changes anything on the Eventbrite side other than registering a notification for new orders.
What people use it for
The module is deliberately general, and organisations use it in quite different ways.
A conference organiser switches an event to live, attaches a welcome workflow, and every ticket buyer gets a joining email within seconds of paying, followed by a reminder a few days before the doors open, with nobody touching anything in between.
A church or ministry runs registration for a programme through Eventbrite because the public knows it, then brings everyone into MyCo so their follow up, groups and member records all live in one place.
A training provider pulls in the attendees for a specific workshop, adds them to a course list, and enrols them from there.
A membership body pulls attendees from three past events into one list, then uses that list to invite the regulars to join properly.
A small business records its paid ticket sales as income so that event revenue appears in MyCo reporting next to everything else it earns, without a separate reconciliation.
1. Connecting Eventbrite
Go to Calendar > Eventbrite and press Connect Eventbrite. You are taken to Eventbrite's own sign in page to approve access, and brought straight back. There are no API keys to find, copy or keep safe, and MyCo never sees your Eventbrite password.
Nothing is imported at the moment you connect. You choose which events take part, and registrations arrive only when you ask for them or when you switch an event to live.
Once connected, the Eventbrite screen shows the organisation that was read from your account, when the last sync ran, and any error worth knowing about. Test connection checks the stored access is still good without changing anything.
2. Choosing which events sync
The events screen lists the events held by your Eventbrite organisation. It opens on live and running events, since a long standing organiser can have hundreds and nobody wants to scroll through four years of history to find next month's conference. The status filter switches to drafts, past events, or all of them.
Press Start syncing on an event and two things are created: a calendar event in MyCo carrying the date, time and venue, and a list named after the event that its attendees will join. Press Stop and the feed stops, but the calendar event, the list and everyone already on it are all kept.
The attendees column shows how many people from that event are in MyCo, and the number links straight through to them.
3. On demand or live
Every syncing event runs in one of two modes, set from the cog beside it.
On demand is the default. The event has its list ready and waiting, and attendees arrive when you bring them in. This is the safe setting, and it is deliberately the one you get without choosing: connecting an established Eventbrite account should not silently drop three thousand contacts into your database.
Live adds each attendee as the ticket is bought. This is what makes an immediate welcome email possible, since a workflow can only act on someone who is actually there. MyCo is notified by Eventbrite as orders come in, and a daily sync runs behind that to catch anything the notification missed.
You can switch an event between the two at any time, and switching to live does not backfill the people who registered before you switched. Bring those in once, then let live handle the rest.
4. Workflows for new attendees
Each syncing event can have a workflow attached to it, chosen from your active standalone workflows. Registering on that event puts the person through it.
By default a workflow runs only for people who are new to your contact list. Someone already on file who buys a ticket still joins the event's list, but is not put through the welcome sequence they have had before. If you want it to run for everybody, open the workflow itself and change who it runs for, and that choice survives later edits on the events screen.
The workflow knows the event date, so a step set to send a few days before the event works without any extra setup.
A workflow needs attendees to actually be there when it fires, so pair it with live mode. On an on demand event, the workflow runs for the people your pull creates, at the moment you run the pull.
5. Recording ticket sales as income
Set per event, and off unless you turn it on. When on, each paid order is written into your accounts as income, at the price the buyer actually paid, dated the day they bought it. Free tickets never create a transaction. A refund on Eventbrite writes a matching expense rather than quietly deleting the original income, so your figures still reconcile to what happened.
Leave it off where ticket money already reaches your accounts another way, otherwise you will count it twice.
6. Bringing attendees in
The pull screen handles the on demand case, and is also how you backfill an event that has already happened. Choose an event, optionally set a registration date range, optionally choose a single ticket type, and press Preview.
Dates here are the Eventbrite registration date rather than today's date, so backfilling a past event works exactly as you would expect. Leave both empty to bring in everyone who ever registered.
The ticket type filter only appears where the event genuinely has more than one type, so a single ticket event is not cluttered with a control that does nothing.
Preview writes nothing at all. It reports how many attendees the event has, how many match your filters, how many were skipped as cancelled or refunded, and how many were skipped for having no email address. Only then does the run button become available, and changing a filter afterwards disables it again so nobody acts on counts that no longer describe what they are about to do. Anything over 500 people carries a warning to check the date range first.
When it runs, each attendee is either matched to a contact you already have or created as a new one, and recorded as an attendee of that event. The result tells you how many were new, how many matched, and how many attendee records were written.
7. Email consent
This one deserves reading properly.
Eventbrite only passes a marketing permission where the organiser has switched on the marketing opt in question in the order form settings. Most organisers have not, so most attendees arrive marked as having given no marketing consent. That is MyCo recording what Eventbrite actually said rather than inventing an answer.
You can always email these people about the event they bought a ticket for. That is service communication about their own order, not marketing.
The pull screen carries a tick box saying these attendees have agreed to hear from us. Ticking it is you asserting you have a basis to email them about other things, and it is recorded against your account along with who ticked it. It applies only to contacts that pull creates. Nobody already on your list has their consent changed by it, and an existing unsubscribe is never undone by anything the module does.
For future events, the better answer is to switch on the marketing opt in question in your Eventbrite order form before tickets go on sale. Then each attendee answers for themselves, MyCo brings in their real answer, and the tick box is never needed.
8. Working with attendees
The attendees screen searches people already in MyCo, filtered by event and registration date range. It makes no call to Eventbrite, which is why it returns straight away however large the event was. If somebody is missing, bring that event's registrations in from the events screen first.
Each row shows the name, email, mobile, organisation and registration date, flagged where the person has no marketing consent on file or has previously unsubscribed. The screen shows the 500 most recent matches, and the CSV export gives you every one of them.
Add these people to a list pushes the filtered result into any ordinary MyCo list. People already on the target list are skipped rather than duplicated. Eventbrite's own event lists are deliberately not offered as a target, since those mirror what Eventbrite says and hand adding to one would stop that being true.
Once attendees are in MyCo they are ordinary contacts on an ordinary list, so everything else in the platform works on them without knowing where they came from: compose an email, run a report, add them to a group, issue them a membership card.
9. Where everything lands
New contacts are given the contact type you choose on the Eventbrite settings screen, which starts as Uncategorised. It applies only to people who are new to your account: someone already on your contact list who buys a ticket keeps the type they already have.
Every contact created this way is stamped with Eventbrite as its source, so you can always tell later where a person came from.
What does not come across is Eventbrite's own check in data. Attendance in MyCo is recorded by MyCo, through the check in app or the attendance module, rather than mirrored from Eventbrite.
10. Activity and troubleshooting
The activity screen shows the connected organisation, when the last sync ran, whether the live notification is registered, the last error if there was one, and every event that has been synced with its current mode.
Where the live notification could not be registered, the module says so plainly and falls back to the daily sync. Nothing is lost, but attendees arrive on a daily rhythm rather than within seconds, which matters if a workflow is meant to greet them.
If events are missing from the list, check the status filter first and then check the event is published on Eventbrite. If nothing reads at all, use Test connection: an Eventbrite account can have access withdrawn from its own settings, which shows up here as a connection that no longer works.
11. Disconnecting
Disconnecting removes the connection to Eventbrite and nothing else. Your synced calendar events, your lists and every contact that arrived through them are all kept. No new registrations arrive after that point. You can reconnect later and pick up where you left off.
Eventbrite : your ticket buyers, in your CRM, the moment they buy
