10times Events Scraper for Trade Shows avatar

10times Events Scraper for Trade Shows

Pricing

$29.00/month + usage

Go to Apify Store
10times Events Scraper for Trade Shows

10times Events Scraper for Trade Shows

Discover 10times events, trade shows, conferences, expos, dates, locations, ratings, source snippets, and lead scores for event research.

Pricing

$29.00/month + usage

Rating

5.0

(1)

Developer

scraping automation

scraping automation

Maintained by Community

Actor stats

2

Bookmarked

49

Total users

2

Monthly active users

8 days ago

Last modified

Share

10times Events & Trade Shows Scraper

Discover event, conference, and trade show leads from 10times pages and public search results.

Who this is for

  • Event lead generation teams
  • B2B sales teams looking for trade show exhibitors
  • Market researchers tracking conferences by city or industry

What it helps you do

  • Find relevant events by category, city, country, or keyword
  • Collect event URLs, titles, dates, locations, ratings, and source evidence
  • Build prospect lists around conferences, expos, and trade shows

Inputs you can use

  • Category or 10times URL
  • City and country
  • Keywords
  • Maximum results

Data you get

  • event name
  • event URL
  • date
  • venue
  • city
  • country
  • category
  • rating
  • source URL

How to get better results

  • Start with a narrow, specific query or a small list of source URLs.
  • Use realistic limits for the first run, then increase the volume once the output looks right.
  • Keep source URLs, dates, and location context when you need repeatable market monitoring.
  • Review a few sample records before connecting the dataset to a larger workflow.

Notes

  • Results depend on what the public source exposes at run time.
  • Some pages may hide, delay, rename, or remove fields, so individual records can have partial data.
  • Use the built-in output table to inspect results before exporting to spreadsheets, dashboards, or automation tools.

Support

If a run returns unexpected data, open an issue from the Actor page with the input used, the run ID, and the result you expected.