Facebook Followers Scraper — Page Follower Counts & Growth avatar

Facebook Followers Scraper — Page Follower Counts & Growth

Pricing

from $5.00 / 1,000 page trackeds

Go to Apify Store
Facebook Followers Scraper — Page Follower Counts & Growth

Facebook Followers Scraper — Page Follower Counts & Growth

Track public Facebook page follower counts and growth in bulk: handles, ids or URLs, optional page details and contacts, change since last run. No login. Counts only, not follower lists.

Pricing

from $5.00 / 1,000 page trackeds

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

0

Bookmarked

36

Total users

6

Monthly active users

10 days ago

Last modified

Features

Limited permissions

Share

What is Facebook Followers Scraper?

Facebook Followers Scraper reads public Facebook pages in bulk and returns one row per page: name, follower count, talking-about count and growth since your last run. Paste page URLs, plain handles (Microsoft, @nasa) or numeric page ids. Everything works from public pages, so there is nothing to sign in to and no cookies or API keys to supply.

Counts come first. Turn on page details when you also need like count, category, website, creation date, ad status, rating and public contact details. Pages are read eight at a time, so a list of hundreds finishes in minutes.

The Actor is built for counts and page facts: how big a page is, how fast it grows and who it is. Facebook keeps the list of individual followers private, so the output is always the aggregate numbers.

Best fit and connected workflows

Use this Actor when you track many Facebook pages on a schedule and care about size and growth: competitor benchmarking, agency client reports, influencer and brand shortlists, market maps, or a dashboard that needs one clean number per page.

It sits at the start of a Facebook research flow: start with this Actor to rank pages by size and growth, then use the tools listed under 'More tools that work well with this one' on the pages that matter.

Example workflow

A social media manager lists 40 competitor and partner pages and schedules the Actor every Monday. Each Monday the dataset shows followerCount, followerDelta and followerGrowthPerDay for all 40. She sorts by followerGrowthPerDay, sees two pages growing fastest, turns on includeDetails for just those two, and reads their category, website and ad status before the weekly review.

Best results

  • Keep one list per trackChangesStoreName, so each tracked list has its own history.
  • Schedule runs at the same time of day; growth per day is then easy to compare.
  • Run with includeDetails off for the full list and on only for the shortlist you want to study.
  • Use numeric page ids when a page has no short handle; they always resolve to one page.

What data you get

FieldAlwaysWith page details
name, pageUrl, followerCount, talkingAboutCount, profilePicUrlyesyes
previousFollowerCount, followerDelta, followerDeltaPct, followerGrowthPerDay, previousCheckedAt (second run onward)yesyes
likeCount, category, creationDate, adStatus, adLibraryPageId, pageIntro, rating, ratingCount, priceRange, coverPhotoUrl, isBusinessPageActiveyes
website, email, phone, address, links (when the page shows them)with contact details
businessHourswith business hours

Why use it

  • Track growth, not just a number. Change tracking is on by default. From the second run each row shows the change in followers, the percentage and the growth per day.
  • Low cost for plain counts. The default route reads only what a follower tracker needs. You pay for deeper details only on the pages where you ask for them and they are found.
  • Ready for scheduled runs. Put 20 competitor pages on a daily schedule and read the followerGrowthPerDay column.
  • Built for AI agents. The run summary includes a plain-sentence agentSummary (largest page, biggest mover, anything unavailable), and the input accepts the standard startUrls and maxItems names.
  • Honest results. Pages that are unavailable return no row, cost nothing and are listed in unavailablePageUrls, so every charged row is a real page.

Input

FieldTypeDefaultWhat it does
pageUrlsarraytwo examplesPage URLs, handles or numeric ids. Duplicates are removed.
startUrlsarraynoneSame as pageUrls, merged with it.
maxItemsinteger100Stop after this many distinct pages. Extra pages are skipped and counted in the run summary.
includeDetailsbooleanfalseAdds likes, category, website, creation date, ad status, intro, rating.
includeContactDetailsbooleanfalseAdds public address, email, phone, website and links. Switches page details on.
includeBusinessHoursbooleanfalseAdds published opening hours. Switches page details on.
trackChangesbooleantrueKeeps the last counts in a named store in your account and adds change fields.
trackChangesStoreNamestringfacebook-followers-historyUse one name per tracked list.

Input fields marked in the form as optional can all stay at their defaults; the only thing you must supply is at least one page.

Example input

{
"pageUrls": ["https://www.facebook.com/Microsoft", "nasa", "100064903443387"],
"maxItems": 100,
"includeDetails": false,
"trackChanges": true
}

Output

Example row (counts only, second run)

{
"pageUrl": "https://www.facebook.com/Microsoft",
"name": "Microsoft",
"followerCount": 13253812,
"talkingAboutCount": 3407,
"previousFollowerCount": 13251100,
"followerDelta": 2712,
"followerDeltaPct": 0.02,
"followerGrowthPerDay": 904,
"previousCheckedAt": "2026-11-10T08:00:00.000Z",
"detailsIncluded": false,
"scrapeSource": "primary",
"scrapedAt": "2026-11-13T08:00:00.000Z"
}

Illustrative values. With page details on, the same row also carries likeCount, category, website and the other detail fields.

Run summary

OUTPUT and RUN_SUMMARY in the default key-value store hold the outcome, agentSummary, counts of rows and unavailable pages, and unavailablePageUrls.

OutcomeRun statusMeaning
COMPLETESucceededEvery page returned a row.
PARTIALSucceededSome pages returned rows; others were unavailable, over the maxItems limit or cut off by your spending limit.
VALID_EMPTYSucceededThe pages you gave have no public profile (deleted page, typo, private account); nothing is charged.
INVALID_INPUTSucceededThe input held no usable page URL, handle or id; add at least one.
UPSTREAM_FAILEDUnsuccessful runEvery page came back empty and a check against a known public page also came back empty, so the data source is not responding.

Run it from code

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~facebook-followers-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"pageUrls": ["Microsoft", "nasa"], "maxItems": 50, "trackChanges": true}'
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/facebook-followers-scraper').call({
pageUrls: ['Microsoft', 'nasa'],
includeDetails: false,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.map((row) => `${row.name}: ${row.followerCount} (${row.followerGrowthPerDay ?? 'n/a'}/day)`));

How it works

  1. Each input is turned into a page URL and de-duplicated.
  2. Pages are read eight at a time through the lowest-cost route that returns what you asked for. If a page is unavailable there, a backup route tries it before the page is reported as unavailable.
  3. With change tracking on, counts are compared with the previous run and the new counts are saved.
  4. Rows are written in your input order and the run summary is saved.

Pricing

Pay per event, with Apify platform usage included. The live Pricing tab shows current prices and the Store discount tiers.

Events charged:

  • Actor start: once per run.
  • Page tracked: once for each page that returns a row.
  • Profile details added: once for each page where optional details were requested and found. It is not charged for counts-only rows.

Example in event counts: a run over 100 pages with page details off charges one start event and up to 100 page tracked events. With page details on, it charges up to 100 page tracked events plus up to 100 profile details added events. Set maxItems or the run's maximum cost to cap your spend.

Use with AI agents (MCP)

Exact Actor identity: khadinakbar/facebook-followers-scraper. Call it from any MCP client through Apify with startUrls or pageUrls, then read agentSummary from the run's OUTPUT record for a one-paragraph answer and the dataset for per-page rows.

Example prompt:

Use khadinakbar/facebook-followers-scraper on these 25 competitor pages with change tracking on, then tell me which three grew fastest per day and which pages were unavailable.

Good to know for agents: results are public-page aggregates, each row carries scrapedAt and scrapeSource for provenance, the cost is the event counts shown under Pricing, and maxItems (default 100) caps both scope and spend. Pages beyond the limit are reported, not silently dropped.

More tools that work well with this one

FAQ

Does it list the people who follow a page? It returns the count and how it changes. Facebook keeps the follower list private, so individual followers are outside what any public-data tool can read.

Where is the like count? Counts-only runs focus on followers and talking-about numbers. Turn on includeDetails to get likeCount, category and the other detail fields.

Can I use a page name instead of a URL? Yes, if it is the page's handle, for example Microsoft or @nasa. Numeric page ids work too.

What if a page is private or deleted? It returns no row, costs nothing and is listed in unavailablePageUrls.

When do the change fields appear? From the second run for the same page and store name, once there is an earlier count to compare with.

Builder's note

I found that most follower-tracking jobs only need the follower count and its trend, so the default route reads just those and keeps the price low. I learned that buyers who also want likes, categories or contacts want them on a short list rather than on every page, which is why page details are a switch you turn on per run.

Responsible use

This Actor reads public page information only. Use the data in line with Facebook's terms and the privacy laws that apply to you, and treat any contact details you collect with care.