Event Discovery Feed
Pricing
from $2.10 / 1,000 event founds
Go to Apify Store
Event Discovery Feed
Deduped B2B event feed from Luma, Meetup, conferences & iCal — venue, tickets, organizers, speakers/sponsors/exhibitors, ICP score & change tracking.
Event Discovery Feed
Pricing
from $2.10 / 1,000 event founds
Deduped B2B event feed from Luma, Meetup, conferences & iCal — venue, tickets, organizers, speakers/sponsors/exhibitors, ICP score & change tracking.
Which source adapters to run. iCal feeds run whenever iCal feed URLs are set, even if this list omits them.
[ "luma", "meetup"]Topics to search for, e.g. AI, SaaS, fintech. An event is kept when its public name, description, or topics match at least one keyword. Leave empty to skip the keyword filter.
[ "AI", "SaaS"]City or country names, e.g. Bengaluru, London, United States. Leave empty for global results. Online events are kept when Include online events is on.
[ "San Francisco"]Include virtual events. When cities are set, online events are still kept if this is on. Hybrid and in-person events must match a city or country.
Latest event start (YYYY-MM-DD). Default: 90 days from today (UTC).
Optional public lu.ma or luma.com calendar or event URLs to always include.
Optional public Meetup group URLs to track. The actor reads the public events listing and does not open attendee lists.
Public conference or calendar pages (JSON-LD, iCal, or HTML listings). A row may be a URL, or a JSON object string with url, listSelector, nameSelector, dateSelector, and optional linkSelector.
Built-in industry listing adapters to run. confs.tech and dev.events are enabled. Eventbrite, AllEvents, and 10times stay disabled until their Terms allow them.
Public .ics feed URLs. Each feed is fetched with a plain GET and parsed as iCalendar.
Open each event detail page and linked public /speakers, /sponsors, and /exhibitors pages, then fill those arrays. Charges event-enriched when the detail fetch succeeds. Turn off for listing-only runs.
Cap how many events get speaker, sponsor, and exhibitor enrichment this run. 0 enriches none.
Describe your ICP or product. Each event gets a 0-100 relevanceScore and a short reason. When LLM_API_KEY is set, scoring uses that model and charges event-relevance-scored. Otherwise a lexical overlap score is used and that event is not charged.
Drop events below this score when ICP description is set. 0 keeps every scored event. Typical range: 60-75.
Push the highest relevanceScore first when ICP description is set.
Output only events that are new or changed since the last run with the same state key. Changed rows also charge change-detected.
Key inside the named key-value store event-discovery-state. Use one stable key per schedule so change tracking compares the same feed.
Hard cap on events written to the dataset. Also caps event-found charges.
Politeness throttle per domain. Source adapters may use a lower cap than this.