# Changelog of Facebook Page Events Scraper — Dates, Venue, Tickets, No Login (`foxlabs/facebook-page-events-scraper`) Actor

- **URL**: https://apify.com/foxlabs/facebook-page-events-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/foxlabs/facebook-page-events-scraper.md

## Changelog

### 0.1.5 — 2026-10-14 — event coordinates and street address filled

- `latitude`, `longitude` and `address` were null on every event in the 2026-10-14 volume run, though Facebook does carry them: the coordinates sit on a richer copy of the event's place than the one on the event node (the Met's event had `event_place` with no location; another copy of the same place id held `location.latitude`). The event's page now merges that copy by place id (never a suggested event's place), so a physical event gets its coordinates (measured 2026-10-14: the Met 40.77942, -73.96342; the British Museum 51.5203, -0.12614).
- `address` now reads a FreeformPlace's full postal address from its `contextual_name` ("1000 5th Ave, New York, NY, …") when it reads like an address (a number and a comma) and the event is not online — Facebook gives it there, not as a structured street. Online events keep null coordinates and address (they have no venue).

### 0.1.2 — 2026-10-11 — the shared core of the family

- The shared core was updated with the Page Reviews Actor; event rows are unchanged. The platform runs measured before publication are listed in the README.

### 0.1.1 — 2026-10-11 — recurring events

- A recurring event is listed as its series and as each of its dates, and the series' own page carries one date's record: the first build delivered that date twice under two ids (measured on the Met's film series). A row now keeps the id and address it was listed under; a date names its series in `parentEventId`.

### 0.1.0 — 2026-10-11 — first release

- Events of public Facebook Pages as a visitor who is not signed in sees them — the Page's upcoming events when it has any, its past ones otherwise, eight in the events tab and eight a call after that — and single events by address.
- With `withDetails` (on by default) each event's own page is read: exact start and end with the time zone, online or in person, past or upcoming, canceled, the place with its id, city, address and coordinates, the description, the ticket address, the cover. Without it, what the events tab shows: name, date sentence, place, host.
- Every row: the event's id and address, the host and the Page's id, `detailsRead` saying whether the event's page was read.
- `upcomingOnly` leaves events already over out without charging them.
- Lines that bring nothing get a free status row that says why (neither a Page nor an event address, no such Page or event, shown to signed-in users only, no data, no events, the same Page or event as another line); a run the platform starts again continues from the rows it already wrote; the spending limit is kept exactly.
- Standby mode prepared (`GET /events?page=…` and `GET /events?event=…`); published in batch mode.