Event Organiser Leads: Who Runs Events in Any City
Under maintenancePricing
from $10.00 / 1,000 organiser leads
Event Organiser Leads: Who Runs Events in Any City
Under maintenanceFind the companies and people running events in any city. Reads Eventbrite listings and rolls them up to one row per organiser: how many events they run, in which cities and categories, at which venues, and how often. No API key.
Pricing
from $10.00 / 1,000 organiser leads
Rating
0.0
(0)
Developer
Mariam Ahmed
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Find the companies and people who run events, not just the events themselves.
This Actor reads public Eventbrite and Meetup listings for the cities and keywords you name, then rolls every event up to one row per organiser: how many events they run, in which cities, in which categories, at which venues, how often, and how much of it is online.
What does this do?
Every other events Actor on the Store hands you a list of events. That is the raw material, not the answer. If you sell to the events industry — a venue, a caterer, an AV company, a ticketing platform, a sponsorship desk — the question is never "what is on in Austin next week". It is "who puts on events here every month, and how do I reach them".
So this Actor inverts the data, across both of the platforms that matter. 268 Eventbrite events in one test run became 60 organisers; a two-city, two-platform run returned 47 Eventbrite organisers and 33 Meetup groups side by side.
Strive Networking 17 events Austin + London every 28 days 2 venuesBusiness Minds Events 9 events Austin every 6 days Business & ProfessionalThe Founders Club 9 events Austin every 6 days Business & ProfessionalLondon FinTechs 8 events London every 13 days Business & ProfessionalAstra Tech Hub, LLC 6 events Austin every 7 days Science & Technology
That first row is the point. "Strive Networking" runs seventeen events across two countries on a monthly cycle. You will not see that by reading a list of events, and it is the difference between a cold contact and a qualified one.
Who is it for?
- Venues and event spaces — find the organisers already running events in your city, and how often
- Caterers, AV, staffing and production — a list of repeat buyers rather than one-off hosts
- Ticketing and event software — organisers running enough volume to be worth a demo
- Sponsorship and partnerships — who reaches your audience, in which categories, at what cadence
- Market researchers — how many events a city supports, and how concentrated the organisers are
What data do you get?
One row per organiser:
| Field | What it tells you |
|---|---|
organiser, organiserUrl | Name and their page on whichever platform they run on |
events | How many of their events this run read |
primaryCity, cities, cityCount | Where they operate, and whether they cross cities |
primaryCategory, categories, subCategories | What kind of events they run |
venues, venueCount | Which venues they use — a direct signal for venue sales |
medianDaysBetweenEvents | Cadence. A 7 is a weekly operator; a null is a one-off |
upcomingFrom, upcomingTo, spanDays | The window their events cover |
onlineEvents, inPersonEvents, onlineSharePercent | Whether they are a physical-venue buyer at all |
seriesEvents | How many are recurring series |
sampleEventName, sampleEventUrl | A concrete example to open |
platform | Eventbrite or Meetup |
totalRsvps, medianRsvpsPerEvent | Meetup only. Actual attendance, which Eventbrite does not publish |
organiserRating, organiserRatingCount | Meetup only. How the group's own attendees rate it |
Every event read is also written to a second dataset (events), so you can keep the underlying rows.
Example: Austin and London, September 2026
Input: two cities, keywords tech and networking, 4 pages per search.
| Measured | Result |
|---|---|
| Search pages read | 16, no refusals |
| Events read | 268 (after removing duplicates across keywords) |
| Organisers found | 60 |
| Organiser names resolved | 60 of 60 |
| Run time | 141 s, 67 MB |
Keyword overlap is real and handled: the networking pages in Austin returned 20 events of which only 5 were new, because tech had already found the rest. Events are deduplicated by id, so an organiser's count is never inflated by searching twice.
What it refuses to do
These are deliberate, and each one is a thing the data cannot honestly support:
- No ticket prices. Organic Eventbrite search results carry no price data at all — only paid promoted listings do, and those are excluded. A price column here would be built from adverts, so there is not one.
- No organiser email, phone or website. Those fields were empty on every organiser measured. A blank column that looks like a contact field is worse than no column. You get the organiser's own page on the platform, which is where the contact route actually is.
- No follower counts. Same reason.
- Promoted listings are excluded. They are paid placements and repeat across pages, which would inflate an organiser's event count.
- No claim about an organiser's full history. Every row says so: counts cover the events this run read, nothing more.
- The two platforms are not merged into one organiser. A company running events on both appears once per platform, because nothing published by either side proves they are the same entity, and guessing from a name would quietly merge two different organisations. Each row states its platform.
A limit worth knowing
Eventbrite starts refusing at roughly 26 to 31 search requests, answering HTTP 429. This was measured, not guessed, and it shapes how the Actor behaves:
- Requests are paced under that threshold, and a 429 makes the Actor back off and retry rather than hammer a closed door.
- Depth and breadth share one budget. 49 pages of one city uses the whole allowance. So if you ask for more than fits, the Actor spreads the pages evenly across your cities and says so in the log, rather than reading the first city deeply and silently ignoring the last.
- Eventbrite offers at most 49 pages of 20 events per search, about 980 events, so that is the ceiling for any one city and keyword.
- Organiser name lookups are on a separate budget and keep working through a search 429.
Raising Maximum search requests above the default does not reliably read more — it just meets the refusal sooner.
Meetup has a different limit, and it is about place names. Meetup will not accept a city
as free text: asking it for "London, United Kingdom" returns HTTP 200 with about half the
results and no venue cities at all, rather than an error. It needs its own location code
(gb--17--London, us--tx--Austin, de--Berlin). This Actor ships codes for the major
event cities, and for any city outside that list it reads Eventbrite only and names the
skipped city in the run summary — because a silently half-empty answer is worse than a
stated gap.
Meetup returns about 20 to 30 events per city and keyword and was not rate limited in testing.
Popular organiser searches
Ready-made runs you can open and start, or copy as a starting point:
- Event Organisers in London
- Event Organisers in New York
- Event Organisers in Austin
- Event Organisers in Toronto
- Event Organisers in Sydney
- Event Organisers in Chicago
- Event Organisers in Berlin
- Event Organisers in Los Angeles
- Tech Event Organisers
- Business Networking Event Organisers
- Conference Organisers
- Workshop and Training Organisers
- Music Event Promoters
- Repeat Event Organisers
- Venue Sales Leads
Pricing
$0.01 per organiser and $0.0005 per event read.
The Austin and London run above — 268 events, 60 organisers — costs about $0.73.
Input
| Field | Meaning |
|---|---|
| Cities | "Austin, United States", "London, United Kingdom", or an Eventbrite slug like united-states--austin. A bare city name is rejected, because "Springfield" alone would resolve to the wrong country |
| Sources | Eventbrite, Meetup, or both. Both by default |
| Keywords | Searched separately in every city. Leave empty for everything on in the city |
| Pages per search | 20 events each, up to 49 |
| Maximum search requests | Default 24, just under where Eventbrite starts refusing |
| Include online events | Online events have no venue city; turn off for physical events only |
| Minimum events per organiser | Set to 2 or 3 to drop one-off hosts and keep the regulars |
| Look up organiser names | Costs one request each. Turn off for a faster run returning ids and links only |
| Maximum organisers | How many rows to return, most events first |
Integrations
Results export to JSON, CSV, Excel and Google Sheets, or go straight to your CRM through the Apify API, webhooks, Make, Zapier and n8n.