Facebook Followers Scraper — Page Follower & Like Counts

What is Facebook Followers Scraper?

Facebook Followers Scraper is an Apify Actor for marketing teams, agencies, analysts, and AI agents that need public Facebook page data in bulk. It accepts one or more public Facebook page or profile URLs and returns one record per page, with fields such as page name, follower count, like count, category, page intro, contact details, and profile and cover photo URLs. With change tracking on, each record also shows how followers and likes moved since the previous run. The outcome is a flat dataset record that can be used for monitoring, enrichment, dashboards, and Apify MCP workflows.

Best fit and connected workflows

This Actor fits workflows that start with a public Facebook page URL and end with a structured page snapshot.

It routes well into:

• competitor monitoring, where you track follower and like counts across many pages
• brand and category dashboards, where page metadata and public contact details are useful
• lead enrichment, where public website, email, phone, and address fields matter
• AI-agent tooling through Apify MCP, where a narrow page-level record is easier to interpret than a broader page scrape

This Actor returns page-level counts and metadata. It does not list the individual accounts that follow a page; it is a follower and like count tracker.

Practical scenario

A social media manager has a spreadsheet with public Facebook URLs for three local competitors. They want follower count, like count, category, and any public contact details before a weekly review.

They submit the URLs and keep contact details enabled. The dataset returns fields like name, followerCount, likeCount, category, website, and pageUrl. After reviewing the records, the manager can sort by follower count, compare page categories, and copy the public website into a competitor tracking sheet.

Input

Use one or more public Facebook page or profile URLs. The input accepts plain URL strings or objects in the form { "url": "..." }.

Input fields

Field	Type	Required	Default	Description
pageUrls	array	Yes	-	One or more public Facebook page or profile URLs to track.
includeContactDetails	boolean	No	true	Returns public contact details when visible, including address, email, phone, website, and outbound links.
includeBusinessHours	boolean	No	false	Returns published opening hours for business pages that publish them.
trackChanges	boolean	No	false	Saves each page's counts in a named key-value store in your account and adds run-over-run change fields on the next run.
trackChangesStoreName	string	No	facebook-followers-history	Name of that history store. Use one name per tracked list.

Focused JSON example

{
  "pageUrls": [
    "https://www.facebook.com/Microsoft"
  ],
  "includeContactDetails": true,
  "includeBusinessHours": false,
  "trackChanges": true
}

Output

The Actor writes one dataset record per tracked page. Required output fields are pageUrl, scrapeSource, and scrapedAt. Other fields are included when available from the public page and selected settings.

Output fields

Field	Type	Description
pageUrl	string	The Facebook page or profile URL that was tracked.
name	string or null	Display name of the page.
pageId	string or null	Facebook numeric page or profile ID.
adLibraryPageId	string or null	Meta Ad Library page identifier.
followerCount	integer or null	Public follower count at scrape time.
likeCount	integer or null	Public like count at scrape time.
category	string or null	Page category.
isBusinessPageActive	boolean or null	Whether Facebook marks the page as an active business page.
adStatus	string or null	Ad-running status shown by Facebook.
creationDate	string or null	Page creation date as displayed by Facebook.
pageIntro	string or null	Short page intro shown on the profile header.
address	string or null	Public business address when published.
email	string or null	Public contact email when published.
phone	string or null	Public contact phone number when published.
website	string or null	Public website link when published.
rating	number or null	Average star rating when the page exposes one.
ratingCount	integer or null	Number of ratings behind the average rating.
priceRange	string or null	Facebook price-range bucket.
profilePicUrl	string or null	Direct URL to the profile photo.
coverPhotoUrl	string or null	Direct URL to the cover photo.
businessHours	object or null	Published opening hours when enabled and available.
links	array or null	Outbound page links when contact details are enabled.
previousFollowerCount, previousLikeCount	integer or null	Counts from the previous tracked run (change tracking only).
followerDelta, likeDelta	integer or null	Change since the previous tracked run.
followerDeltaPct	number or null	Follower change as a percentage of the previous count.
previousCheckedAt	string or null	Time of the previous tracked run for this page.
scrapeSource	string	primary or fallback: which data route returned the record.
scrapedAt	string	ISO 8601 timestamp when the record was emitted.

Example dataset record

Illustrative values; change fields appear only on tracked runs after the first.

{
  "pageUrl": "https://www.facebook.com/Microsoft",
  "name": "Microsoft",
  "pageId": "11320376584",
  "adLibraryPageId": "11320376584",
  "followerCount": 13800000,
  "likeCount": 13200000,
  "category": "Software Company",
  "isBusinessPageActive": true,
  "adStatus": "This Page is currently running ads.",
  "creationDate": "November 16, 2009",
  "website": "https://www.microsoft.com",
  "profilePicUrl": "https://...",
  "coverPhotoUrl": "https://...",
  "previousFollowerCount": 13790000,
  "followerDelta": 10000,
  "followerDeltaPct": 0.07,
  "previousCheckedAt": "2026-06-20T06:50:11.004Z",
  "scrapeSource": "primary",
  "scrapedAt": "2026-06-27T06:51:23.512Z"
}

How it works

The Actor reads each public page through a primary data provider and falls back to a second provider automatically. You supply page URLs only; no Facebook login, cookies or API keys are needed.

Optional output controls:

• includeContactDetails for public contact data and outbound links
• includeBusinessHours for published weekday opening hours on business pages
• trackChanges for follower and like changes between scheduled runs

Outcome records

OUTPUT and RUN_SUMMARY in the default key-value store record the outcome and list any unavailablePageUrls:

Outcome	Run status	Meaning
COMPLETE	Succeeded	Every page returned a record.
PARTIAL	Succeeded	Some pages returned records; the rest were unavailable and are not charged.
VALID_EMPTY	Succeeded	None of the pages has a public profile (for example, a deleted page or a typo in the URL).
INVALID_INPUT	Succeeded	No valid Facebook page URL was provided.
UPSTREAM_FAILED	Failed	Every page failed and a check against a known public page also failed, so the data provider is not responding.

Pricing

Facebook Followers Scraper uses Pay per event with Apify platform usage included. The live Pricing tab shows the current pricing details.

The charged events in the contract are:

• Actor start
• Page tracked

As a simple event-count example in words, a run that tracks one hundred pages will charge one actor start event and one page tracked event for each page that returns a record. Change tracking adds no extra events. See the Pricing tab for current event prices.

Use with AI agents (MCP)

This Actor is usable through Apify MCP as a focused tool for retrieving public Facebook page follower counts and metadata from URLs.

Exact Actor identity: khadinakbar/facebook-followers-scraper

Tool description: given one or more public Facebook page or profile URLs, the tool returns one dataset record per page with follower count, like count, page metadata, and optional public contact details.

Please fetch public Facebook page data for these URLs and return the page name, follower count, like count, category and website for each record.

When you use the output in an AI workflow:

• pageUrl identifies the page that was tracked
• followerCount and likeCount provide the main public count signals
• category, pageIntro, and contact fields help with page classification and enrichment
• followerDelta and followerDeltaPct show growth since the previous tracked run when trackChanges is on
• scrapedAt gives the emission timestamp for point-in-time interpretation

Scope and pagination guidance:

• the Actor processes one record per submitted page URL
• the output is already flat, so agents can read dataset items directly
• the dataset is the main output location, with OUTPUT and RUN_SUMMARY outcome records in key-value storage
• pricing is event-based, so agent planners can estimate cost from the number of page URLs they send

Apify API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
    token: process.env.APIFY_TOKEN,
});

const actor = client.actor('khadinakbar/facebook-followers-scraper');

const run = await actor.call({
    pageUrls: [
        'https://www.facebook.com/Microsoft',
        'https://www.facebook.com/cocacola'
    ],
    includeContactDetails: true,
    includeBusinessHours: false,
    provider: 'auto',
});

const { items } = await client
    .dataset(run.defaultDatasetId)
    .listItems();

console.log(items);

Best results and outcome guidance

Use public page or profile URLs that represent the page itself, since the Actor is designed for page-level tracking. If you want a leaner dataset, keep only the count fields and turn off optional contact details. If you want business metadata, enable business hours for pages that publish them. For weekly competitor tracking, schedule the same input with trackChanges: true so each run reports the change since the last one.

Continue the workflow

• Then use Facebook Group Members Scraper to extend Facebook Followers Scraper research with a complementary engagement contract.
• Then use Facebook Group Posts Scraper — Text, Engagement & Comments to extend Facebook Followers Scraper research with a complementary content contract.

Design note

I found that this Actor is mostly run again and again on the same page lists, where the change in followers matters more than a single count. I designed trackChanges so the Actor keeps the previous counts in a named store and writes the change straight into each record, which removes that manual step while keeping one flat record per page.

FAQ

Can I use this Actor for a list of public Facebook pages?

Yes. The input accepts an array of public Facebook page or profile URLs, and the Actor returns one dataset record per URL.

Which fields are most useful for monitoring?

followerCount, likeCount, category, pageIntro, and scrapedAt are the main monitoring fields. website, email, phone, and address are useful for enrichment when they are publicly visible.

Does the Actor support business details?

Yes. The dataset schema includes contact fields, businessHours, and links. The input lets you choose whether to include contact details and business hours.

How do I track follower growth over time?

Set trackChanges to true and run the same page list on a schedule. From the second run on, each record includes previousFollowerCount, followerDelta, followerDeltaPct, likeDelta and previousCheckedAt.

Can I use the output in another Apify workflow?

Yes. The output includes a dataset link plus key-value store summaries, which makes it straightforward to consume in Apify API workflows, dashboards, and MCP-based agents.

Responsible use

Use this Actor only for public Facebook page data. Keep your usage aligned with applicable laws and the terms that govern the data you collect. Public contact details and profile metadata may still be personal or business data, so store and use them with care.