# Event Sponsorship Prospecting — Organizers & Sponsors (`memo23/event-sponsorship-prospecting`) Actor Find event organizers, observed sponsors, and public contacts from event pages. Built for sponsorship prospecting and BD outreach. JSON or CSV out. - **URL**: https://apify.com/memo23/event-sponsorship-prospecting.md - **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $10.00 / 1,000 scraped items This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Event Sponsorship Prospecting — Organizers & Sponsors

Event Sponsorship Prospecting

Find event organizers, observed sponsors, and public contacts from event pages. Built for sponsorship prospecting and BD outreach. One row per event, clean JSON out. *** ### Why use this scraper - **Organizer extraction.** Pulls the organizer name and profile URL from event pages (Eventbrite-style `/o/` links, schema.org JSON-LD, and meta tags). - **Sponsor detection.** Scans for sponsor/partner sections using keyword matching (sponsor, partner, supported by, powered by, brought to you by, thanks to) and extracts linked sponsor names and URLs. - **Contact enrichment.** Extracts emails, phones, and social media profiles from each event page. - **Any event platform.** Works with Eventbrite, Meetup, Lu.ma, Dice.fm, and most event pages with public HTML. - **No login, no API key.** Reads the public event page, no credentials needed. *** ### Overview This actor takes event page URLs, extracts the organizer, any sponsors/partners mentioned on the page, and contact information (emails, phones, socials). Each event becomes one prospect record with everything you need to start sponsorship outreach. *** ### Use cases - **Sponsorship sales** — find events that already have sponsors, then pitch competing brands. - **Sponsor prospecting** — identify events in your niche and their existing sponsors for partnership outreach. - **Organizer outreach** — extract organizer names and contact info to pitch sponsorship deals. - **Competitive intelligence** — see which brands sponsor which events. *** ### How it works

How it works

1. You provide event page URLs. 2. The actor fetches each page with impit (real Chrome TLS fingerprint). 3. It extracts the organizer (from Eventbrite-style links, schema.org JSON-LD, or meta tags). 4. It scans for sponsor/partner sections using keyword matching and extracts linked sponsor names and URLs. 5. It extracts emails, phones, and social media profiles from the page. 6. Each event becomes one prospect record in the dataset. *** ### Input | Field | Type | Default | Notes | |---|---|---|---| | `startUrls` | array | — | Event page URLs to analyze. | | `maxItems` | integer | 1000 | Maximum events to process. | | `maxConcurrency` | integer | 10 | How many pages to fetch in parallel. | | `proxy` | object | Apify proxy | Proxy configuration. | ```json { "startUrls": [ { "url": "https://www.eventbrite.com/e/your-event-tickets-1234567890" } ] } ``` *** ### Output One row per event: ```json { "type": "sponsorship-prospect", "eventUrl": "https://www.eventbrite.com/e/...", "eventTitle": "Tech Conference 2026", "organizer": "Tech Events Inc", "organizerUrl": "https://www.eventbrite.com/o/tech-events-inc-12345", "sponsors": [ { "name": "Acme Corp", "url": "https://acme.com", "source": "sponsored by" }, { "name": "Beta LLC", "url": "https://beta.com", "source": "partner" } ], "sponsorCount": 2, "emails": ["contact@techevents.com"], "phones": [], "socials": [ { "platform": "linkedin", "url": "https://linkedin.com/company/tech-events" } ] } ``` #### Key output fields - **`organizer` / `organizerUrl`** — the event organizer's name and profile URL. - **`sponsors`** — array of `{ name, url, source }` for each sponsor/partner found. - **`emails` / `phones` / `socials`** — contact data from the event page. *** ### FAQ **What event platforms are supported?** Any event page with public HTML. The organizer extraction works best with Eventbrite (via `/o/` links) but also falls back to schema.org JSON-LD and meta tags for other platforms. **How are sponsors detected?** The actor scans for HTML sections containing sponsor-related keywords (sponsor, partner, supported by, powered by, brought to you by, thanks to) and extracts links within those sections. It also checks image alt text for sponsor keywords. **What if an event has no sponsors listed?** The `sponsors` array will be empty and `sponsorCount` will be 0. The organizer and contact data are still extracted. *** ### ⚠️ Disclaimer This Actor scrapes publicly available event data from web pages. It does not access authenticated or private content. You are responsible for using the output in line with the target websites' terms and any applicable law in your jurisdiction. *** ### SEO Keywords event sponsorship prospecting, sponsor finder, event organizer scraper, sponsorship leads, event sponsor extractor, sponsorship outreach, event partner finder, sponsor database, event lead generation, sponsorship sales tool, organizer contact scraper, event sponsorship research, sponsor identification, event sponsorship data, sponsorship prospect list # Actor input Schema ## `startUrls` (type: `array`): Event page URLs to analyze. Works with Eventbrite, Meetup, and most event platforms. ## `maxItems` (type: `integer`): Maximum event pages to process. ## `maxConcurrency` (type: `integer`): How many event pages to fetch in parallel. ## `proxy` (type: `object`): Apify proxy to use. ## Actor input object example ```json { "startUrls": [ { "url": "https://www.eventbrite.com/" } ], "maxItems": 1000, "maxConcurrency": 10, "proxy": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://www.eventbrite.com/" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("memo23/event-sponsorship-prospecting").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://www.eventbrite.com/" }] } # Run the Actor and wait for it to finish run = client.actor("memo23/event-sponsorship-prospecting").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://www.eventbrite.com/" } ] }' | apify call memo23/event-sponsorship-prospecting --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/event-sponsorship-prospecting" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/pzfmsSqf1tRPiaBCm/builds/KInJh9x0AZbhMb8av/openapi.json