Find Event Sponsors and Recurring Event Organizers

Find recurring event organizers and explicit sponsor or partner mentions from Eventbrite, Meetup, Luma, and Posh. Get source-linked accounts, representative events, sponsor evidence, and public people already shown by the selected source.

This Actor reports observed facts, not a guessed “sponsor fit” score. Every sponsor mention includes the page where it was found.

Use cases

• Build a prospect list of organizers that run events repeatedly.
• Find brands already sponsoring or partnering with relevant events.
• Research sponsorship opportunities by topic, category, and location.
• Monitor new and disappeared sponsor mentions across comparable searches.
• Export organizer, event, evidence, and public host/member/attendee data to a CRM or spreadsheet.

Quick start

For normal discovery, enter:

1. Keywords or topic — for example, technology networking.
2. City and country — optional for Eventbrite; required for Meetup.
3. Maximum accounts — the number of organizer accounts you want returned.

No API key, dataset ID, or JSON is required.

Example input

{
  "keywords": "technology networking",
  "city": "New York",
  "country": "US",
  "sourcePlatform": "auto",
  "maxAccounts": 25,
  "maxCostUsd": 5
}

auto searches Eventbrite and also searches Meetup when both city and a two-letter country code are supplied. Choose a specific source when you need narrower coverage.

For a particular Luma calendar or Posh organizer, open Advanced: organizer searches and raw seeds.

What you get

The run provides separate views for:

• Accounts — deduplicated organizers, recurrence evidence, event count, locations, venues, public scale signals, and billing status.
• Sponsor evidence — named sponsor or partner, source URL, excerpt, confidence rule, and change status.
• Events — representative events linked to each organizer.
• People / attendees — public hosts, organizers, members, attendees, guests, or speakers returned by the selected source.
• Summary — delivered totals, charges, coverage status, and any limitations affecting the run.

Example account output

{
  "recordType": "account",
  "accountId": "7f2b6c194b9f301a",
  "snapshotId": "4f432c09bf974d7d6da4",
  "accountName": "Community Tech",
  "sourcePlatforms": ["eventbrite"],
  "sourceUrls": [
    "https://www.eventbrite.com/e/community-tech-night-tickets-123456789"
  ],
  "website": "https://community.example.org/",
  "city": "New York",
  "country": "US",
  "categories": ["Science & Technology"],
  "venues": ["Community Hall"],
  "eventsObserved": 2,
  "firstObservedEventAt": null,
  "lastObservedEventAt": null,
  "isRecurring": true,
  "recurrenceRule": "At least two distinct public events were observed.",
  "scaleSignalMax": 245,
  "scaleSignalLabel": "aggregate public organizer follower count (Eventbrite)",
  "businessContact": null,
  "sponsorEvidenceCount": 1,
  "publicPeopleObserved": 0,
  "publicPeopleTruncated": false,
  "billed": true,
  "observedAt": "2026-09-22T18:00:00.000Z",
  "origin": "live",
  "freshness": "fresh",
  "collectedAt": "2026-09-22T18:00:00.000Z"
}

Example sponsor-evidence output

{
  "recordType": "sponsorEvidence",
  "evidenceId": "9a1b2c3d4e5f6071",
  "snapshotId": "4f432c09bf974d7d6da4",
  "accountId": "7f2b6c194b9f301a",
  "accountName": "Community Tech",
  "sponsorNameRaw": "Acme Cloud",
  "sponsorNameNormalized": "acme cloud",
  "sourceUrl": "https://www.eventbrite.com/e/community-tech-night-tickets-123456789",
  "excerpt": "Sponsored by Acme Cloud.",
  "extractionMethod": "explicit_sponsor_phrase",
  "confidence": "high",
  "confidenceRule": "Explicit sponsor wording with a named organization.",
  "observedAt": "2026-09-22T18:00:00.000Z",
  "deltaStatus": "new",
  "billed": true,
  "origin": "live",
  "freshness": "fresh",
  "collectedAt": "2026-09-22T18:00:00.000Z"
}

The exact fields and values depend on what each public source exposes. The Actor does not invent missing dates, people, contacts, sponsors, or relationships.

Pricing

The Actor uses pay-per-event pricing:

• $0.06 per qualified account.
• A qualified account is a deduplicated recurring organizer delivered from complete, current coverage.
• Recurrence requires at least two distinct observed events, or an explicit organizer/group account observation.
• Sponsor evidence, representative events, and public people are included with the account.

You are not charged for:

• non-recurring context accounts;
• duplicate accounts;
• stale results;
• missing or failed searches;
• incomplete or capped source coverage;
• accounts excluded by maxAccounts or maxCostUsd;
• a charge rejected by the platform.

Apify platform usage or upstream source execution costs may be charged separately according to your Apify plan. Use maxCostUsd to cap qualified-account charges for a run.

Inputs

Normal search

• keywords or topic — public search terms.
• sourcePlatform — auto, Eventbrite, Meetup, or both for normal discovery.
• city, country, category — location and category filters. Use a two-letter country code for Meetup.
• dateFrom, dateTo — optional inclusive UTC calendar dates.

Result and cost limits

• maxAccounts — maximum organizer accounts returned; default 25.
• maxEvents — maximum observations processed; default 200.
• maxCostUsd — maximum qualified-account charges; default $5.
• maxPeoplePerEvent and maxPeople — limits for public people returned by sources.
• includeBusinessContacts — include public organizer business contacts already present in source data.

Advanced options

Advanced users can search a particular Luma calendar or Posh organizer, control freshness, or provide private inline observations. The standard keyword/location workflow does not require these options.

Coverage and limitations

• Source pages change, disappear, or limit the fields they expose.
• A search can return no sponsors even when it finds organizers and events.
• Public people lists may be samples or partial lists; truncation and completeness are reported.
• Incomplete runs can still return validated results, but those results are unbilled and are not used to declare sponsor evidence “lost”.
• A single event does not prove that an organizer runs events repeatedly.
• Sponsor evidence means an explicit observed mention or named sponsor link; it does not prove an active commercial relationship today.

Data handling and privacy

Search terms and public-source results are processed by a creator-operated service so current public results can be reused and stale coverage can be refreshed. Public results may be retained for reuse in later searches.

Private inline observations stay within your Actor run. They are not added to the shared public-results corpus. Keep your Apify run private if its input or output is sensitive.

The Actor preserves only publicly available data returned by the selected sources. It does not infer identities, guess private contact details, or enrich people beyond the source output.

FAQ

Does this find companies likely to sponsor my event?

It finds recurring organizers and explicit sponsor or partner evidence. It does not claim to predict buying intent or sponsorship probability.

Why did I receive organizers without sponsor evidence?

Those accounts provide useful event-market context, but the inspected source text did not contain a qualifying named sponsor or partner mention.

When is an account considered recurring?

When at least two distinct events are observed for the organizer, or when the source explicitly represents a recurring organizer/group account. One Meetup event alone is not enough.

Can a partial run charge me?

No. Qualified-account charging is suppressed when source coverage is incomplete, capped, or cannot be saved reliably.

Are attendees and members included?

Yes, when the selected public source returns them. Rows include their association and available completeness/truncation information. The Actor does not reconstruct hidden lists.

Why are some event dates empty?

The Actor only emits a date when the source provides a trustworthy canonical timestamp. It does not guess a timezone for local date strings.

Can I use my own observations?

Yes. Add them under Advanced: private inline observations. They remain local to that run and do not enter the shared public-results corpus.

Related Actors

• Eventbrite Scraper — Event & Organizer Data for raw Eventbrite event discovery.
• Luma Events Scraper — Event & Host Data for Luma calendars, events, and public hosts.
• Posh Events Scraper — Nightlife & Organizer Data for Posh events and organizer data.