Google Events Live Query Actor

What does Google Events Live Query Actor do?

This Google Events Actor uses current Google Search results to discover event publishers, then extracts actual events from their live structured metadata. Each record contains a named event, a published date, venue or address, and its source or ticket link.

The legacy Google Events ibp=htl;events page now reports that the browser, device or location is unsupported. This Actor therefore identifies its output as google-search-publisher-event-live, rather than claiming it came from that retired event-card route. It does not create event records from autocomplete or generic search snippets.

Why use this Actor?

Use it for concert discovery, event research, venue calendars and schedule aggregation. Apify adds API access, scheduling, integrations, monitoring and downloadable datasets. Each event retains the original query, discovery page, publisher URL and retrieval time so you can inspect its live source.

How to use this Actor

1. Enter a query with the event type and location, such as concerts in New York.
2. Keep maxItems and minItems at 10 for a small verification run.
3. Keep GOOGLE_SERP discovery enabled, or explicitly disable it to try direct Google access.
4. Start the Actor and check the dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Input

query drives Google discovery and event relevance checks. Include the city or other location terms you need. maxItems limits distinct events; minItems requires a minimum count. The effective minimum cannot exceed the maximum.

hl and gl set language and country. requestTimeoutSecs defaults to 45 and accepts 5–60 seconds; publisher requests have a 20-second ceiling. proxyConfiguration defaults to {"useApifyProxy":true,"groups":["GOOGLE_SERP"]}. Other service-specific fields inherited by the input form are ignored.

Output and data fields

Field	Meaning
title, description	Publisher event name and description
url, sourceUrl	Event or ticket URL and metadata source
details.startDate, endDate	Dates exactly as published
details.venueOrLocation, address	Venue and structured address
details.latitude, longitude	Coordinates when published
details.organizer, performers	Publisher-provided participants
details.price, currency	Ticket price only when published
details.availability, ticketUrl	Offer details when available
details.googleSearchUrl	Discovery query page
sourceType, scrapedAt	Extraction method and retrieval time

Unknown prices, times and organizers remain absent. A date without a time stays a date; the Actor does not invent a timezone. Events are deduplicated by name, date and location. Separate dates for the same artist are separate events.

Pricing and cost estimation

The configured Store fee is $0.00199 per result ($1.99 per 1,000), plus the $0.00005 Actor Start event. Users pay Apify platform usage and proxy costs. Ten requested events use at most three paid Google discovery pages; larger limits can use up to twelve. Each discovered publisher page is fetched directly. A publisher calendar can contain several distinct events. Check current Apify rates for platform and proxy charges.

Tips and limitations

Use a specific event type and city. Live structured Event metadata is required, so some visible events cannot be extracted. Dates older than the current day are omitted unless the query explicitly requests a past year. Source errors, challenges and blocked publishers can reduce the count. The Actor fails below the minimum and does not add generated filler.

FAQ and support

Run apify validate-schema and apify run locally. Local storage is separate from cloud datasets. Deploy and test in production to verify cloud output. The Actor accesses public pages and does not solve CAPTCHAs or access private accounts. Review applicable source terms and use the Issues tab with your input and run URL when reporting a problem.