Meetup Scraper for Group, Event, Topic and City Data

Meetup Dataset Fields: Group Profile, Event Listing and Counters

Public group and event pages embed the same GraphQL objects the API serves, so Meetup data collected from them keeps the platform's own field names.

• Group profile. Numeric id, urlname, name, description, topicCategory and activeTopics, city, state, country, IANA timezone, foundedDate, joinMode (OPEN, APPROVAL or CLOSED), the private flag and the Pro network, where there is one. Group coordinates are rounded to city level.
• Group activity. Member count, size of the leadership team, average event rating with the number of ratings, and totals of upcoming and past events. Event frequency comes from the dated event history: events per month and the usual gap between them.
• Event record. Every Meetup event listing carries a numeric id and stable token, title, description, dateTime and endTime with their UTC offset, createdTime, status (ACTIVE, PAST, CANCELLED and others) and topics. eventType reads PHYSICAL, ONLINE or HYBRID.
• Place. Venue name, street address, city, state, country and exact coordinates for in-person events; a hybrid event returns two venues.
• Attendance. Going count, waitlist count, the RSVP limit (maxTickets, zero when none is set), waitlistMode, whether guests may come and how many, and RSVP open and close times.
• Meetup event price and fees. A free event has no fee block. A paid one carries amount, currency, whether the fee is required, the accepted method (cash or PayPal), an early bird discount with its amount and cut-off, and a promo code flag. Group dues, where a group charges them, form a separate block.
• Series. A recurring event describes itself in plain words, such as every week on Monday until a given date.

Members are private people, so the dataset stops at numbers: we never collect member names, profiles, member lists or who signed up for an event. The organizer is recorded as a role - whether a group has one and how many people lead it - never as a person.

Local Group Events Data for Community Maps, Venues and B2B Marketing

Community maps by topic and city. Member counts, event cadence and group status turn a list of groups into a map of live communities. Status is telling: PAID means an organizer with an active subscription, GRACE a lapsed one that freezes after 15 days, FROZEN no active organizer, and DEAD a group frozen for 15 days more. Topic pages per country already publish a group count and a member total for each topic, and the group-level pull shows how many of those groups still hold events - forty on paper and ten active describe two different markets.

Venue sourcing. An in-person event names its venue with an address and exact coordinates, so venues can be ranked by how many events they host each month and for which topics - a shortlist of rooms that already welcome meetups.

B2B community marketing. Pro networks such as GDG and Docker User Group bundle their chapters under one brand, with totals of groups, countries and members and a list of sponsors, which shows where a developer or product audience already meets.

Details that change counts. A recurring event can get a new id once it has seen activity while its token stays put, so we deduplicate on the token. Online events share a placeholder venue called Online event, so their city comes from the group. The same night can also be listed on Meetup and Eventbrite, the Meetup page pointing to the ticket link, so cross-platform feeds match on title, date and venue. In the group sitemaps, lastmod is the founding date rather than the latest change, so freshness is read from events.