# Changelog of Luma Event Scraper | Organizer Leads + Socials (`zrk1212/luma-organizer-leads`) Actor

- **URL**: https://apify.com/zrk1212/luma-organizer-leads/changelog.md
- **Full Actor documentation**: https://apify.com/zrk1212/luma-organizer-leads.md

## Changelog

### 1.0 (2026-11-17, pushed as private build, not published)

- First version: organizers mode and events mode, city (87 Luma cities or coordinates), category, calendar and host inputs.
- Local measurements (no proxy, US university IP):
  - Prefill (sf, tech, 25 organizers): 25 rows in 23 s, 33 requests, 0 blocks.
  - NYC tech organizers, all: 164 rows (120 calendars, 44 hosts) in 143 s, 214 requests, 0 blocks. Website 62%, any social 76%, site or social 81%, followers 100% of calendars.
  - NYC all events, maxEvents 1500: 1,322 unique events in 19 s, 29 requests, 0 blocks.
- Platform runs (Apify, 512 MB, no proxy unless noted), all SUCCEEDED, 0 x 403/429:
  - Prefill: 25 organizers, 23 s, $0.0008 total ($0.033 per 1k organizers), max mem 55 MB.
  - NYC tech 150 organizers, no proxy: 132 s, $0.0045 ($0.030 per 1k).
  - NYC tech 150 organizers, Apify datacenter proxy: 141 s, $0.0050 ($0.033 per 1k). Proxy not needed: default stays off.
  - NYC all events: 1,322 events, 86 s, $0.0088 ($0.007 per 1k events), max mem 94 MB.
  - Scaling 25 to 150 organizers: 6x rows, 5.7x time (linear).
- Default memory lowered to 256 MB (max observed 94 MB).
- Gate 2 review fixes: personal calendars always get the robots check, only Luma's verification 403 counts as a rate limit, events dedupe after filters, host rows survive an events-hosting failure, discovery skipped once maxOrganizers is met.
