Facebook Events Scraper
7 days trial then $35.00/month - No credit card required now
Facebook Events Scraper
7 days trial then $35.00/month - No credit card required now
Facebook Events Scraper extracts data such as event name, location, description or number of users who are interested. You can use URLs of specific events or come up with search queries and explore pretty much unlimited number of events. Search queries can be combined with various search filters.
Do you want to learn more about this Actor?
Get a demoMissing "usersGoing" and "usersInterested" Fields in Scraping API Response
Closed
I am currently using the plugin for data scraping, which has been essential for gathering event-related information. Until recently, the API provided values for the following fields:
- usersGoing: indicating the number of users attending an event.
- usersInterested: indicating the number of users interested in an event.
These fields are crucial for our data analysis and reporting. However, as of 2024-11-13, these fields are no longer included in the API responses.
Details:
- Expected behavior: The API should return values for "usersGoing" and "usersInterested" as it did previously.
- Current behavior: The API responses are entirely missing the "usersGoing" and "usersInterested" fields.
- Impact: This change significantly disrupts our data processing and analysis, leading to incomplete event data and affecting key performance metrics for our operations.
Please investigate this issue and, if possible, restore the inclusion of the "usersGoing" and "usersInterested" fields in the API responses. Alternatively, any guidance on changes made or workarounds would be appreciated.
Thank you for your attention to this matter.
Hi!
Issue confirmed, caused by migration to new data format where some details are better, but, as you noticed, only usersResponded available, while usersGoing and usersInterested are missing.
For right now please use build 0.0.45 (in run settings fill in build number, then click "Use untagged build 0.0.45")
Sample run https://console.apify.com/view/runs/DJubocIWCaeMbXk4d and dataset https://api.apify.com/v2/datasets/aQOo9Zkh0rUgD18i8/items?clean=true&format=json
Please let us know if any of other properties are missing in the new version
Thanks a lot for your feedback
Tech note - in current Facebook web app now only usersResponded available as data value. Old version was based on Facebook mobile app data where only usersGoing and usersInterested available as data values and old version of actor calculated usersGoing as a sum of interested + going.
swingback
Hi,
I was using this as an API, but I couldn't find a way to include the build number in the request. Could you please guide me on how to pass it?
Hello, you can specify the build inside the URL params of your POST request, like:
https://api.apify.com/v2/acts/ACTOR_NAME_OR_ID/runs?token=YOUR_TOKEN&build=beta.
More documentation is available at https://docs.apify.com/academy/api/run-actor-and-retrieve-data-via-api :)
Hi!
Actor upgraded to unified data feed from both web and mobile app details, please use latest build from now on. In other words no need to specify build for each run, just call actor in the same way as it was done before.
Sample run https://console.apify.com/view/runs/afApveZm2EHmvBvxj
Thanks for your feedback and patience!
I´m going to close the issue now, but if there would be anything else we could help with, please let us know.
ApifyActor Metrics
92 monthly users
-
25 stars
>99% runs succeeded
1.7 days response time
Created in Mar 2023
Modified 5 days ago
