TourRadar Email Scraper
Pricing
from $2.49 / 1,000 results
TourRadar Email Scraper
TourRadar Email Scraper SD - TourRadar Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from TourRadar results by keyword, location and email domain - TourRadar email extractor.
Pricing
from $2.49 / 1,000 results
Rating
0.0
(0)
Developer
Leads Scraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
TourRadar Email Scraper
The TourRadar Email Scraper collects publicly indexed contact emails, account names and operator profile URLs connected to TourRadar listings, and writes them to an Apify dataset you can export as CSV, JSON or Excel.
The TourRadar Email Scraper is built for travel-tech vendors, tour aggregators recruiting supply, destination marketing organisations, travel PR teams and partnership managers who need travel trade contacts they can actually email.
TourRadar is a marketplace for multi-day, small-group and adventure tours. The businesses listed on it are independent tour operators running real itineraries, not single-activity tickets, which makes the TourRadar Email Scraper a useful starting point for B2B travel prospecting.
The TourRadar Email Scraper never logs in, never opens TourRadar itself, and never touches private data. Every row comes from public Google search results, parsed and filtered.
Why TourRadar is a strong audience for supplier recruitment
Most travel marketplaces index products. TourRadar indexes operators. Its /o/ pages are literally operator pages, which is why the TourRadar Email Scraper returns a decent share of rows with a usable handle.
That matters if you are building a tour operator contact database. A row with an operator handle is a company you can research, qualify and route to a salesperson. A row with only an email is a guess.
The commercial profile is good too: multi-day trips carry higher ticket prices than day tours, the operators run staffed booking desks, and many of them publish partnership addresses because they actively want trade business.
If you sell a booking engine, channel manager, reservation system or CRM, or you run an OTA doing supplier recruitment, these are the group tour operators you want in the pipeline, and the TourRadar Email Scraper is a sensible first pass at finding them.
Compare that with the Viator Email Scraper, which indexes single tour products. Viator tends to surface more emails per run but far less operator identity, because a product page rarely names the company behind it in a handle-shaped way.
Run both if you want coverage: use TourRadar for identity-rich adventure travel contacts and Viator for raw volume. The GetYourGuide Email Scraper and Klook Email Scraper cover the same day-tour territory in Europe and Asia-Pacific respectively.
TourRadar Email Scraper features
Everything below is a real behaviour of the Actor, not a roadmap item.
| Feature | What it does |
|---|---|
| Google SERP parsing | Builds site:tourradar.com queries and parses each result block structurally, not by CSS class names |
| Query expansion | Runs base, quoted and intitle: variants plus one variant per query modifier; base queries run first |
| Domain filter | Keeps only emails ending in the domains you list, with boundary-correct matching |
| Global deduplication | One row per unique email across every query and every page of the run |
| Email normalisation | Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width at sign |
| Junk filter | Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals |
| Soft-wrap repair | Drops a hit that is only the tail of another email found in the same block |
| Concurrency | An asyncio worker pool with a shared stop signal once maxEmails is reached |
| Retries and block detection | Up to 3 attempts per page with exponential backoff and a fresh proxy session; CAPTCHA, "unusual traffic" and consent pages are detected and retried |
| Re-queueing | Blocked or failed queries are retried once at the end of the run |
| Resumable runs | State is stored in the key-value store keyed by an input hash, and saved on PERSIST_STATE, MIGRATING and ABORTING |
| Fallback parser | If Google's markup changes, the run degrades to "emails without account details" rather than "no emails" |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |
How the TourRadar Email Scraper works
The pipeline is deliberately simple, and understanding it explains both the strengths and the limits of the TourRadar Email Scraper.
- It reads your input: keywords, optional location, email domains and run limits.
- It builds Google search queries with the
site:operator againsttourradar.com, for examplesite:tourradar.com "tour operator" "@gmail.com" "Peru". - It fetches Google result pages through the Apify GOOGLE_SERP proxy using async
aiohttprequests. - It parses each result block structurally by locating the
<h3>title and then the smallest surrounding block. - It extracts emails from that block text with a domain-filtered regex.
- It deduplicates globally and pushes each lead to the dataset immediately, so partial results survive an abort.
There is no browser, no JavaScript rendering, no authentication and no cookies. The TourRadar Email Scraper is a Google reader with a very specific filter, and everything it returns was already public.
TourRadar Email Scraper input fields
These are the only inputs the Actor accepts, with the defaults it ships with.
| Field | Type | Default | Meaning |
|---|---|---|---|
keywords | array (required) | ["tour operator", "adventure tours"] | Search terms describing the accounts you want |
location | string | "" | Optional location phrase added to every query |
customDomains | array | ["@gmail.com","@yahoo.com"] | Only emails on these domains are kept; the @ is optional |
maxEmails | integer 1-10000 | 20 | Stop after this many unique emails |
countryCode | string | "" | Two-letter country for the search proxy (US, GB, DE...) |
expandQueries | boolean | true | Search each keyword x domain pair in several phrasings |
queryModifiers | array | ["email","contact","bookings","group tours","partnerships"] | Extra words combined with each keyword when expansion is on |
maxPagesPerQuery | integer 1-50 | 30 | Page cap per query |
maxConcurrency | integer 1-20 | 5 | Parallel queries |
JSON input example for the TourRadar Email Scraper
This is a realistic starting configuration for travel lead generation using the platform defaults.
{"keywords": ["tour operator", "adventure tours"],"location": "Cusco","customDomains": ["@gmail.com", "@yahoo.com"],"maxEmails": 200,"countryCode": "US","expandQueries": true,"queryModifiers": ["email", "contact", "bookings", "group tours", "partnerships"],"maxPagesPerQuery": 30,"maxConcurrency": 5}
The partnerships and bookings modifiers are the ones that matter most for supplier recruitment, because those are the words operators put next to the address they actually want the trade to use.
Output fields from the TourRadar Email Scraper
Every dataset item written by the TourRadar Email Scraper has all fourteen of these fields.
| Field | Meaning |
|---|---|
network | Platform name |
keyword | The keyword that produced the lead |
query | The exact Google query used |
title | Raw result title |
accountName | Account label Google prints |
fullName | Display name parsed from a profile-style title; empty for snippet-only rows |
username | URL-safe handle when the platform exposes one; otherwise null |
profileUrl | Canonical https://www.tourradar.com/o/{username} URL when a handle is known; otherwise empty |
url | Direct platform link when exposed, else the profile URL |
description | Bio or snippet text, cleaned of labels and counters |
email | Lower-cased email address |
emailDomain | The matched domain, for example @gmail.com |
possiblyTruncated | true when Google's snippet ellipsis touched the email |
foundAt | ISO 8601 UTC timestamp |
JSON output example from the TourRadar Email Scraper
Two of these rows carry an operator handle and a real /o/ profile URL. The third shows what a snippet-only row from the TourRadar Email Scraper honestly looks like.
[{"network": "TourRadar","keyword": "tour operator","query": "site:tourradar.com \"tour operator\" \"@gmail.com\" \"Cusco\"","title": "Andes Trail Expeditions - Tour Operator on TourRadar","accountName": "Andes Trail Expeditions","fullName": "Andes Trail Expeditions","username": "andes-trail-expeditions","profileUrl": "https://www.tourradar.com/o/andes-trail-expeditions","url": "https://www.tourradar.com/o/andes-trail-expeditions","description": "Small-group trekking and multi-day adventures in Peru. Bookings: andestrail.bookings@gmail.com","email": "andestrail.bookings@gmail.com","emailDomain": "@gmail.com","possiblyTruncated": false,"foundAt": "2026-02-11T09:24:51Z"},{"network": "TourRadar","keyword": "adventure tours","query": "site:tourradar.com intitle:\"adventure tours\" \"@yahoo.com\" partnerships","title": "Sierra Wild Adventures | Adventure Tours","accountName": "Sierra Wild Adventures","fullName": "Sierra Wild Adventures","username": "sierra-wild-adventures","profileUrl": "https://www.tourradar.com/o/sierra-wild-adventures","url": "https://www.tourradar.com/o/sierra-wild-adventures","description": "Group tours and guided hiking itineraries. Trade partnerships: sierrawild.partners@yahoo.com","email": "sierrawild.partners@yahoo.com","emailDomain": "@yahoo.com","possiblyTruncated": false,"foundAt": "2026-02-11T09:26:02Z"},{"network": "TourRadar","keyword": "adventure tours","query": "site:tourradar.com \"adventure tours\" \"@gmail.com\" contact","title": "Adventure Tours in Nepal - 12 Day Itinerary","accountName": "Adventure Tours in Nepal","fullName": "","username": null,"profileUrl": "","url": "https://www.tourradar.com/","description": "12 day trekking itinerary. Contact for group departures: himalaya.trips@gmail.com ...","email": "himalaya.trips@gmail.com","emailDomain": "@gmail.com","possiblyTruncated": true,"foundAt": "2026-02-11T09:27:44Z"}]
The third row is not a failure. Google simply did not expose a handle in that result, so the Actor reports null rather than guessing a URL.
Use cases for the TourRadar Email Scraper
This Actor suits any team whose customer is an independent multi-day operator.
| Audience | What they do with the data |
|---|---|
| Booking engine and reservation system vendors | Build a tour operator contact database of multi-day operators and pitch software that fits itinerary-based inventory |
| Channel managers and connectivity providers | Reach group tour operators who need distribution across several marketplaces at once |
| OTAs and tour aggregators | Supplier recruitment: find independent operators who are not yet listed on your platform |
| Destination marketing organisations | Assemble adventure travel contacts operating in a specific region for campaigns and famil trips |
| Destination management companies | Identify inbound partners already selling multi-day product in your destination |
| Travel PR and media teams | Build travel trade contacts lists for press releases, award nominations and product launches |
| Affiliate and partnership managers | Find operators publishing a partnerships address, which signals appetite for B2B travel prospecting |
| Insurance, payments and gear suppliers | Target higher-ticket adventure operators whose customers travel for a week or more |
Targeting tips for the TourRadar Email Scraper
location and countryCode are the two levers that change your results most, and they do different jobs.
location is a phrase appended to every query. Destination-led prospecting works well here: try Patagonia, Kilimanjaro, Vietnam or Iceland rather than a head office city, because operator pages describe where the trips go.
countryCode steers the search proxy, which changes which results Google considers locally relevant. Set GB or DE for European inbound operators, US for North American outbound sellers.
Keep keywords narrow. adventure tours plus a destination beats a broad sweep, and narrow keywords give you a multi-day tour operator email list you can actually segment.
Add your own modifiers if you have a niche. Words like trekking, expedition, cycling or safari combine cleanly with the defaults.
Widen customDomains beyond the two defaults if you want business addresses too. Many operators publish a role address on their own domain, and the TourRadar Email Scraper will keep it if you list that domain.
For adjacent supply, the Tripadvisor Attractions Email Scraper covers attraction operators. If you only need one specific brand, the G Adventures Email Scraper and Intrepid Travel Email Scraper are single-operator tools rather than marketplace tools.
Limitations of the TourRadar Email Scraper
Read these before you plan a campaign. They are structural, not bugs.
- The TourRadar Email Scraper only finds accounts whose email is publicly visible in Google's index. If nobody published it, it is not there.
- Google caps a single query at roughly 300 results. That is exactly why query expansion exists in the TourRadar Email Scraper and why leaving
expandQuerieson is recommended. possiblyTruncated: truemeans Google's snippet ellipsis may have cut the email short. Verify those rows before sending.- The TourRadar Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
- Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
usernameandprofileUrlare only populated when Google exposes a handle in the result. Rows without one still carryaccountNameand oftenfullName. This is a Google limitation, not a bug.- Results vary with keywords, domains and location. No volume is guaranteed.
Responsible use and GDPR
The addresses the TourRadar Email Scraper collects are business contacts that operators published deliberately so that travellers and trade partners can reach their booking desk.
Treat them that way. Identify yourself and your company in the first line, state plainly why you are writing, and make the relevance to their business obvious.
Honour opt-outs immediately and keep a record of them. Keep a lawful basis for your outreach under GDPR, CAN-SPAM and any local rules that apply, and do not use these contacts for consumer marketing.
Data collected with the TourRadar Email Scraper is for legitimate B2B travel prospecting, not for resale as a bulk consumer list.
TourRadar Email Scraper FAQ
How many results should I expect from the TourRadar Email Scraper?
In a measured live run, roughly every 10 parsed Google result blocks produced about 5 identities, 5 profile URLs and 6 unique emails. That is a moderate but well balanced return: roughly half of rows carry an operator handle, and the email rate is among the better ones in this family of Actors. It is not a volume promise, and your numbers will move with keywords, domains and location.
Why does the TourRadar Email Scraper get better operator identity than the Viator one?
Because TourRadar's /o/ pages are operator pages. The Viator Email Scraper indexes individual tour products, so it tends to return more emails but much less company identity.
Does the TourRadar Email Scraper log into TourRadar?
No. It builds Google site: queries, reads the public result pages through the Apify GOOGLE_SERP proxy and parses them. There is no login, no cookies, no browser and no platform API.
Is TourRadar a marketplace or a single operator?
It is a marketplace. The listings belong to many independent tour operators, which is what makes it useful for supplier recruitment rather than research into one brand.
Why is username null on some rows?
Google did not expose a handle in that result block. The TourRadar Email Scraper reports null and an empty profileUrl rather than fabricating a URL that may not resolve.
Can the TourRadar Email Scraper collect business-domain emails instead of Gmail and Yahoo?
Yes. Put any domains you want into customDomains, with or without the leading @. The domain filter is boundary-correct, so @gmail.com will not match @gmail.company.
What is the best keyword set for a multi-day tour operator email list?
Start with the defaults, tour operator and adventure tours, then add an activity word such as trekking, safari or expedition. Narrow keywords give the TourRadar Email Scraper cleaner blocks to parse and give you a segment you can write to properly.
How do I get more travel trade contacts out of one TourRadar Email Scraper run?
Leave expandQueries on, raise maxEmails, add destination phrases in location, and add niche words to queryModifiers. Each expansion is a separate query, so it sidesteps Google's per-query ceiling.
What happens if a TourRadar Email Scraper run is interrupted?
State is saved in the key-value store keyed by a hash of your input, and rows are pushed to the dataset as they are found. A migrated or resumed run picks up rather than starting over.
Does the TourRadar Email Scraper deduplicate?
Yes, globally. One row per unique email address across every query and page in the run.
Can I export the results?
Yes. The TourRadar Email Scraper writes to a standard Apify dataset, which exports to CSV, JSON, XML or Excel from the console, or streams through the API into your CRM for travel lead generation.
Which other Actors pair well with the TourRadar Email Scraper?
For day tours and activities, the Klook Email Scraper covers Asia-Pacific and the GetYourGuide Email Scraper covers Europe. Running them alongside the TourRadar Email Scraper gives you both multi-day and single-activity supply.
Is the TourRadar Email Scraper affiliated with TourRadar?
No. It is an independent tool that reads public Google search results and is not connected to, endorsed by or supported by the platform.
Related Actors
Actors built on the same engine as the TourRadar Email Scraper, for travel and hospitality lead generation.
| Actor | What it collects |
|---|---|
| Airbnb Email Scraper | Public contact emails from Airbnb |
| Booking.com Email Scraper | Public contact emails from Booking.com |
| Caviar Email Scraper | Public contact emails from Caviar |
| ChowNow Email Scraper | Public contact emails from ChowNow |
| Contiki Email Scraper | Public contact emails from Contiki |
| Craigslist Email Scraper | Public contact emails from Craigslist |
| Delivery.com Email Scraper | Public contact emails from Delivery.com |
| DoorDash Email Scraper | Public contact emails from DoorDash |
| EatStreet Email Scraper | Public contact emails from EatStreet |
| G Adventures Email Scraper | Public contact emails from G Adventures |
| GetYourGuide Email Scraper | Public contact emails from GetYourGuide |
| Grubhub Email Scraper | Public contact emails from Grubhub |
| Hostelbookers Email Scraper | Public contact emails from Hostelworld |
| HotelsCombined Email Scraper | Public contact emails from HotelsCombined |
| Intrepid Travel Email Scraper | Public contact emails from Intrepid Travel |
| Just Eat Email Scraper | Public contact emails from Just Eat |
| Klook Email Scraper | Public contact emails from Klook |
| OpenTable Email Scraper | Public contact emails from OpenTable |
| Resy Email Scraper | Public contact emails from Resy |
| TheFork Email Scraper | Public contact emails from TheFork |
| Toast Restaurant Email Scraper | Public contact emails from Toast |
| Traveloka Email Scraper | Public contact emails from Traveloka |
| Tripadvisor Attractions Email Scraper | Public contact emails from Tripadvisor |
| Tripadvisor Hotels Email Scraper | Public contact emails from Tripadvisor |
| Tripadvisor Restaurants Email Scraper | Public contact emails from Tripadvisor |
| Uber Eats Email Scraper | Public contact emails from Uber Eats |
| Viator Email Scraper | Public contact emails from Viator |
| Wanderlog Email Scraper | Public contact emails from Wanderlog |
| Wego Email Scraper | Public contact emails from Wego |
| Zomato Email Scraper | Public contact emails from Zomato |
| Airbnb Email and Phone Number Scraper | Emails and phone numbers from Airbnb |
| Booking.com Email and Phone Number Scraper | Emails and phone numbers from Booking.com |
| Caviar Email and Phone Number Scraper | Emails and phone numbers from Caviar |
| ChowNow Email and Phone Number Scraper | Emails and phone numbers from ChowNow |
| Contiki Email and Phone Number Scraper | Emails and phone numbers from Contiki |
| Craigslist Email and Phone Number Scraper | Emails and phone numbers from Craigslist |
| Delivery.com Email and Phone Number Scraper | Emails and phone numbers from Delivery.com |
| DoorDash Email and Phone Number Scraper | Emails and phone numbers from DoorDash |
| EatStreet Email and Phone Number Scraper | Emails and phone numbers from EatStreet |
| G Adventures Email and Phone Number Scraper | Emails and phone numbers from G Adventures |
| Grubhub Email and Phone Number Scraper | Emails and phone numbers from Grubhub |
| Hostelworld Email and Phone Number Scraper | Emails and phone numbers from Hostelworld |
Leave a review
If the TourRadar Email Scraper saved you time, please leave a star rating and a short review on the Actor page.
Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.
If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.