apify-google-events-trackinglisted

# Google Events Tracking: Watch Listings as Structured JSON Track Google Events with the Apify Google Events Scraper. Give it a search query, an optional location, and a date window, and get structured event rows you can export, diff across runs, and watch on a schedule. ## When to use this skill - The user wants google events tracking: watching a city, venue, artist, or competitor for new events. - They want to export Google Events results (concerts, conferences, festivals, sports, theater, virtual events) to JSON or CSV. - They want an event dataset for market research or a recurring scan of what is coming up. - They ask to "track events", "monitor Google Events", or "watch for new concerts in my city". Not for: ticket price history (`ticket_info` carries seller links, not numeric prices), attendance or RSVP data (Google Events does not publish it), or past events (the source lists upcoming events only). ## What you get (one row per results page) Each dataset row is one page of results holding a nested `events` array, about 10 events per page. Per event: `title`, `date` (`start_date` and `when` display strings), `address` (venue and city lines), `link`, `description`, `ticket_info` (per-seller `source`, `link`, `link_type`, `source_icon`), `venue` (`name`, `rating`, `reviews`, `link`, when present), and `image`. Page level: `search_parameters` (echo of your input), `search_metadata` (`events_count`, `total_results`, `pages_processed`, `pagination_limit_reached`, and r