Civitatis Tours & Activities Scraper

Civitatis Tours & Activities Scraper

Collect publicly available Civitatis (civitatis.com) tours and activities as clean, structured records. Feed the actor city listing pages and/or direct activity pages; it returns one rich record per activity — price, rating, review count, duration, the languages it is offered in, meeting point, start coordinates and more.

Input

field	description
startUrls	Civitatis URLs to scrape. City listing pages (e.g. https://www.civitatis.com/en/madrid/) — the actor follows every activity-card link on them and paginates. Direct activity pages (e.g. https://www.civitatis.com/en/madrid/atletico-stadium-tour/) — scraped straight away. You can mix both.
maxItems	Cap on total activities returned (0 = no cap).
maxPagesPerCity	How many listing pages to follow per city (20 activities per page). Default 3.
proxyConfiguration	Uses Apify Residential by default — no external proxy key needed.

What you get (one record per activity)

field	description
id	stable numeric activity id
title	activity name
activity_url	activity page URL
city / country	location
category / categories	activity category (e.g. Guided Tours, Entrance Tickets)
price / currency	starting price and currency
rating	average rating (out of 10)
review_count	number of reviews
duration	human-readable duration (e.g. 2 hours)
languages	language codes the activity is offered in (e.g. en, es, fr)
meeting_point	where the activity starts
free_cancellation	whether free cancellation is available
lat / lng	start coordinates
image_url	lead image
description	short activity summary
review_images_count	number of user-uploaded review photos

How it works

Each activity page is server-rendered and carries first-party structured signals — schema.org microdata (price, priceCurrency, aggregateRating), Open-Graph meta (coordinates, image) and a small inline data object (city, country, languages). The scraper reads these directly, so it is resistant to cosmetic markup changes. City listing pages are parsed for their activity-card links, which are then followed to the detail pages and paginated. Requests use a residential proxy for reliable access; you only supply the URLs.

Pricing

Pay per result — you are charged once per activity record written to the dataset. Compute runs on your own Apify account.

Notes

This tool collects publicly available tour and activity data for research and aggregation.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.