Facebook Page Followers Scraper – Visible Profiles

Collect the follower profiles Facebook makes visible for a public Page. Facebook Page Followers Scraper returns profile names, IDs, links, pictures and source-Page context, with one row per visible follower.

Start from Page usernames or URLs and set how many result pages to attempt. The result is a visible collection, not a complete audience export or a guarantee that every follower can be retrieved. No Facebook login or cookies are required.

At a glance	Details
📥 Input	Page usernames, numeric IDs as strings, or Page URLs
📤 Output	Visible follower identities with the source Page and available collection summary
🔐 Login required	No Facebook credentials or cookies
📄 Collection	Pagination; pagesPerProfile defaults to 1
💾 Delivery	One row per distinct follower returned for each source Page; JSON, CSV, Excel or API

What the Facebook Page Followers Scraper extracts 🔎

The Actor reads the public Followers collection for each submitted Page and keeps every returned profile connected to its source.

• Follower ID, username when available, display name and profile URL
• Profile picture, visible subtitle, profile type and verification flag
• Source Page identity, Page ID, username, URL and profile picture
• Collection total and any public notice supplied by Facebook
• Additional pages of visible followers when continuation is available

How to scrape Facebook Page followers 🚀

1. Add the Page usernames or URLs whose visible Followers collections you want to inspect.
2. Set pagesPerProfile; start with 1 to inspect the available collection.
3. Start the Actor and inspect the dataset’s status column.
4. Export successful rows or connect the results to your workflow.

{
  "inputList": [
    "Meta"
  ],
  "pagesPerProfile": 1
}

Facebook Page followers data fields and output 📦

Field group	Included data
Follower identity	ID, username, name, profile URL and picture
Profile context	Subtitle, public profile type and verification flag
Source Page	source_profile.* identity, URL, picture and verification columns
Collection	source_total and notice
Run result	Original input and success or failed status

Complete representative success item. All names, counts and media addresses below are illustrative, not a live result; every current output field is included.

{
  "input": "HarborCoffee",
  "status": "success",
  "id": "100098765432101",
  "username": "MorganLee",
  "name": "Morgan Lee",
  "url": "https://www.facebook.com/MorganLee/",
  "profile_picture_url": "https://media.example.com/morgan-lee.jpg",
  "subtitle": "Portland, Maine",
  "type": "user",
  "is_verified": false,
  "source_profile.id": "100091234567890",
  "source_profile.page_id": "104567890123456",
  "source_profile.username": "HarborCoffee",
  "source_profile.name": "Harbor Coffee",
  "source_profile.url": "https://www.facebook.com/HarborCoffee/",
  "source_profile.profile_picture_url": "https://media.example.com/harbor-coffee-profile.jpg",
  "source_profile.is_verified": false,
  "source_total": 2800,
  "notice": ""
}

The table and JSON use the same flat keys and values, with one row per result. Dots in keys such as source_profile.name are literal parts of the field name.

source_total is a source-reported collection figure, not the number of rows this run will necessarily return. notice retains any collection message supplied by Facebook.

Successful rows may contain empty strings, zeroes, false flags, empty lists or nulls when optional information is unavailable. Do not interpret a default count or flag as a confirmed source fact. Failed rows retain input, set status to failed, and use null result fields.

Input requirements and coverage ⚙️

Parameter	Type	Required	Rules
inputList	array of strings	Yes	At least one Page username, numeric ID as a string, or supported Page URL; no default target.
pagesPerProfile	integer	No	Default 1; minimum 1, maximum 100. Maximum result pages to attempt per input.

Page usernames, numeric IDs as strings, standard Facebook Page URLs, profile.php?id=... links and legacy /pages/NAME/ID links are accepted. Submit the Page itself, not a follower’s profile or a post link.

The initial results count as page 1. Further pages are requested only while Facebook supplies a usable continuation. Page size is controlled by the source, so this is not an exact record limit.

Provide an array of strings, not URL objects. An invalid overall input structure stops processing without dataset rows; an invalid target within a valid list is recorded as a failed result. The input schema does not set a maximum list length; choose batch sizes appropriate to your run limits.

Facebook Page followers use cases 🎯

Visible audience research

Review the identities and public profile labels shown in a Page’s accessible follower list.

Source-linked profile records

Keep each returned follower connected to the Page where it was listed when combining several Page collections.

Collection monitoring

Compare repeated exports to see changes in the visible collection while treating each export as a partial public snapshot.

Pricing and billable follower rows 💰

Check the Actor’s Pricing tab for the current model and rate. That configuration is authoritative.

Under dataset-item pricing, saved success and failed rows can count toward charges. Each distinct returned follower saves a success row. Invalid inputs, an empty first collection or a persistently unavailable result page can save failed rows; a later failure does not remove earlier results. Retries do not independently add dataset rows. All details remain in their result row.

Facebook Page Followers Scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["Meta"],"pagesPerProfile":1}'

Start runs through the Apify API, schedules or client libraries. Use webhooks for completion events and export the dataset to spreadsheets, Make, Zapier, storage or your own application.

Reliability and limits ⚠️

Facebook may expose only a small portion of a Page’s followers or withhold the collection entirely. A Page’s displayed follower count does not imply that the same number of identities is accessible.

The Actor saves available rows as pages are processed and skips repeated profile IDs within the same source collection. Pagination can end before the requested limit when Facebook has no more accessible results. An empty first collection or a request that remains unavailable can create a failed row.

Frequently asked questions ❓

Will I receive every follower of a Page?

No. Only the follower identities exposed in the accessible public collection can be collected, even if the displayed follower total is much larger.

Does pagesPerProfile specify a follower count?

No. It limits result pages to attempt. Each page can return a different number of profiles, or no accessible results.

What does source_total represent?

It is the total reported with the source collection. It can be missing or default to zero and is not an export-size guarantee.

Can this collect the profiles a Page follows?

Use Facebook Page Following Scraper for that outgoing relationship.

Does it include private contact details?

No. It returns the public profile fields present in the collection, without private emails, phone numbers or account access.

Support, responsible use, and related actors 🛟

For help with missing or unexpected results, open an Issue on this Actor’s Apify page with the run link, a public example input and the fields you expected. Keep tokens and credentials out of support messages.

Use public data only for purposes you are authorized to pursue, respecting privacy, platform terms and content rights.