Extract exhibitor company and booth fields from public event pages you supply

Trade Show Exhibitor Intelligence structures public event, sponsor, and trade show exhibitor pages into company, booth, category, country/region, URL, and social fields. V1 is direct-source only: it uses URLs or domains you provide plus same-domain exhibitor links found on those pages. It is not a confs.tech developer conference / CFP calendar and not a contact-page business-channel inventory — those jobs belong on Tech Events & CFP Calendar Scraper and Contact Page Audit & Business Channel Extractor.

$30.00 per 1,000 exhibitor_profile_enriched events; $12.00 per 1,000 exhibitor_partial events

Open Trade Show Exhibitor Intelligence on Apify

Exhibitor company and booth fields, not a CFP calendar or contact-page audit

Use this page when the job is company and booth extraction from public exhibitor directory, profile, sponsor, or booth listing URLs you already have. Use Tech Events & CFP Calendar Scraper when the job is a dated developer conference, meetup, and Call for Papers calendar from confs.tech topic search. Use Contact Page Audit & Business Channel Extractor when the job is public support paths, phones, and social profiles on contact, about, or support pages.

This Actor Tech Events & CFP Calendar Scraper Contact Page Audit & Business Channel Extractor
Intent Exhibitor company, booth, category, country/region, URL, and social fields Developer conference, meetup, and CFP deadline calendar Public business contact-channel inventory
Primary input Direct-source urls and/or domains (at least one) Required topics; optional year Required urls (contact, about, support, or company pages; max 100)
What it reads Public event/exhibitor/sponsor/booth pages you supply, plus same-domain exhibitor links Public conference, meetup, and CFP listings (schema: aggregate from confs.tech by topic) Public contact / about / support / policy / company pages
Deliverable Exhibitor rows with company, booth, category, country/region, URLs, socials, plus diagnostics Deduplicated dated event records with CFP URL/deadline when present public_contact_channel rows: support path, phone, social URLs
Not this job confs.tech speaking calendars; contact-page channel audits; search-engine discovery Exhibitor booth directories from supplied event URLs Booth hall/number extraction from exhibitor directories

The published Store description is: Extract company names, categories, countries/regions, URLs, social links, and booth information from public event and exhibitor pages using direct-source URLs only, with PPE charged events and no-charge diagnostics. The README positions this as an experimental lead-generation lane that is intentionally lighter than browser-based event scraping.

Use cases

Pass public exhibitor directory or profile URLs in urls, or bare event domains in domains. V1 does not discover events via search engines.

How is Trade Show Exhibitor Intelligence different from Tech Events & CFP Calendar Scraper and Contact Page Audit & Business Channel Extractor?

This Actor extracts exhibitor company and booth fields from public event, sponsor, and exhibitor pages using direct-source URLs or domains you supply, plus same-domain exhibitor links found on those pages. Live schema sources are urls (event exhibitor directory, exhibitor profile, sponsor, or booth listing URLs; maxItems 100) and domains (optional bare event domains, maxItems 100). Published Store description: company names, categories, countries/regions, URLs, social links, and booth information. Tech Events & CFP Calendar Scraper aggregates developer conferences, meetups, and Call for Papers deadlines from confs.tech by topic; required input is topics, not exhibitor page URLs. Contact Page Audit & Business Channel Extractor inventories public business contact channels (support paths, phones, socials) from contact, about, and support pages; person-level emails are suppressed. This Actor is booth and company extraction from supplied exhibitor sources, not a developer speaking calendar and not a contact-page channel audit.

What input is required?

The published input schema has an empty required list. Schema description: provide at least one public event/exhibitor URL or event domain. Live fields:

Field Type Default Notes
urls string[] [] Public event exhibitor directory, exhibitor profile, sponsor, or booth listing URLs to fetch directly. No search engine discovery is used. maxItems 100. Schema prefill is https://www.ces.tech/exhibitors/, https://www.bio.org/events/bio-international-convention/exhibitor-directory.
domains string[] [] Optional bare event domains. Domains are normalized to https://domain/ and inspected for same-domain exhibitor or directory links only. maxItems 100. Schema prefill is ces.tech, bio.org.
eventName string empty Optional event or trade show name used as a parsing hint and fallback eventName field
countryRegionHint string empty Optional country, state, or region used only as a local classification hint when that text appears on the page
maxLinkedPages integer 2 When a supplied page links to same-domain exhibitor, sponsor, booth, directory, or company profile pages, fetch up to this many extra direct-source pages as evidence. Minimum 0, maximum 8.
maxResults integer 25 Maximum normalized direct sources and extracted exhibitor rows to emit. Minimum 1, maximum 250.
dryRun boolean false Validate input and write local output without sending dataset rows or charging custom PPE events

additionalProperties is false. The published input schema does not include delivery, webhookUrl, search queries, topics, or authentication fields. Use urls for exact exhibitor directory/profile pages, or domains when you want the actor to inspect an event domain for same-domain exhibitor links.

Published schema prefill (first-run shape):

{
  "urls": [
    "https://www.ces.tech/exhibitors/",
    "https://www.bio.org/events/bio-international-convention/exhibitor-directory"
  ],
  "domains": [
    "ces.tech",
    "bio.org"
  ],
  "maxLinkedPages": 2,
  "maxResults": 25,
  "dryRun": false
}

Keep maxLinkedPages low for cheap proof runs. Use dryRun: true before charging custom PPE events.

Run Trade Show Exhibitor Intelligence on Apify

What does a result row contain?

The published Store README lists company name, event name, profile URL, and website; categories, country or region, social URLs, booth hall, booth number, and booth label; and description, confidence, status, chargedEvent, sourceUrls, and errors on every dataset row. The published dataset overview view (Trade Show Exhibitor Profiles) lists companyName, eventName, profileUrl, website, categories, countryRegion, booth, boothHall, boothNumber, socialUrls, confidence, status, chargedEvent, sourceUrls, and errors. There is no published output JSON schema sample object on the Store README. The overview field list is the published dataset view, not a live coverage guarantee for every source page.

For a developer conference / CFP calendar instead of exhibitor booth rows, use Tech Events & CFP Calendar Scraper. For public contact-channel inventory on contact pages, use Contact Page Audit & Business Channel Extractor.

Does it use search engines or private exhibitor databases?

No. The live Store README states V1 is direct-source only: it uses URLs or domains you provide plus same-domain exhibitor links found on those pages. It does not use search engines, private portals, authentication, or paid event databases. The live schema description repeats: no search engines, no private portals, no authentication, and no paid/private exhibitor data collection. urls are fetched directly; domains are inspected for same-domain exhibitor or directory links only.

How is Trade Show Exhibitor Intelligence priced?

Billing is pay per event. Live Store events are Exhibitor profile enriched at $0.03 ($30.00 / 1,000): a public exhibitor page or directory entry was structured into company, booth, category, country, URL, or social fields; Partial exhibitor profile at $0.012 ($12.00 / 1,000): a public exhibitor source produced partial but useful exhibitor intelligence fields; and Actor Start at $0.00005, charged when the Actor starts running (number of events depends on Actor memory, one event per GB, minimum one event). Platform usage is listed as included on the pricing page.

The README PPE section matches those charged events as exhibitor_profile_enriched (useful enriched exhibitor profile) and exhibitor_partial (useful partial exhibitor evidence). invalid, blocked, not_found, not_exhibitor_page, and error are no-charge diagnostic rows.

$30.00 / 1,000 exhibitor_profile_enriched; $12.00 / 1,000 exhibitor_partial; Actor Start $0.00005

See Trade Show Exhibitor Intelligence pricing on Apify

How do dry runs and no-charge diagnostic rows work?

dryRun true validates input and writes local output without sending dataset rows or charging custom PPE events. Enriched and useful partial rows are charged with custom PPE events; invalid, blocked, not_found, not_exhibitor_page, and error rows are no-charge diagnostics. The published input schema does not include delivery or webhookUrl. The README says keep maxLinkedPages low for cheap proof runs.

Open Trade Show Exhibitor Intelligence on Apify

Limits to keep in mind

Open Trade Show Exhibitor Intelligence on Apify

Related pages