Instagram, Facebook & Threads Post Metrics

You ran a campaign across Instagram, Facebook and Threads. Now you need one report, and the tools you would normally reach for cover one platform each.

Paste the post URLs, all three mixed together, and get back a single table with the same columns for every row.

Built for checking posts you already know about: campaign reporting, influencer delivery checks, monthly performance decks. If instead you need to find posts by hashtag, keyword or account, use a platform-specific scraper; this one takes URLs and nothing else.

Why one Actor instead of three

Running a separate scraper per platform leaves you joining three tables with three different column names before you can add anything up. This returns likeCount, replyCount, shareCount and viewCount under the same names whether the URL was Instagram, Facebook or Threads.

Two more things matter once you start computing on the numbers:

Unknown is null, never 0. A post whose author hid its like count reports likeCount: null. Instagram's own embed returns 0 for those posts and its post page returns a different number again — both are fabrications. Summing a fabricated 0 silently understates your total, so this Actor refuses to emit one.

Failed URLs still appear. A deleted post comes back as a row with status: "not_found" and null metrics, not as a row that quietly vanishes. 100 URLs in, 100 rows out. A missing row is invisible; a marked row is something you can account for.

Input

Field	Description
postUrls	Post URLs. Platforms can be mixed freely in one run.
fetchFollowers	Look up each author's follower count. Costs one extra request per account.
abortAfterConsecutiveFailures	Stops the run when a platform stops responding, so a broken run cannot burn through a long list. Deleted posts do not count toward this.
proxyConfiguration	For Instagram and Threads. Datacenter proxies are enough.
facebookProxyConfiguration	For Facebook only, which needs residential proxies — see below.

Accepted URL shapes:

• Instagram — /p/{code}/, /reel/{code}/
• Threads — threads.com/@user/post/{code} and threads.net equivalents
• Facebook — {pageId}_{postId}, permalink.php, /posts/pfbid…, /reel/{id}, /videos/{id}, /photo/?fbid=

Output

One row per input URL:

Field	Notes
status	success, not_found, login_required, parse_failed, unsupported_url
platform	Instagram, Facebook or Threads
postUrl, username, authorUrl
mediaType	image, video, carousel, text
likeCount	Reactions on Facebook
replyCount	Comments
shareCount	Facebook shares; reposts plus quotes on Threads. Instagram does not expose shares.
repostCount, quoteCount	Threads only, kept separate as well
viewCount	Video and reel plays. Image and carousel posts have none.
followerCount	Exact on Facebook and Threads. Exact on Instagram carousels and reels; single-image posts fall back to the displayed figure, which is rounded above ~10K
createdAt	ISO 8601, UTC
text, hashtags, mentions	Hashtags and mentions are parsed from the caption

Facebook needs residential proxies

Facebook serves a login wall to datacenter IP ranges. Measured on this platform: 0 of 4 posts readable through datacenter proxies, 3 of 4 through residential, where the fourth was a page that really had been removed.

Instagram and Threads have no such restriction, which is why they get their own proxy setting. Leaving them on datacenter keeps a mixed run cheap — paying residential rates for all three platforms would cost roughly forty times more for the two that do not need it.

What it cannot return

• Reach and impressions. Visible only to a page's own administrators. No public scraper can produce these; anything claiming otherwise is estimating.
• Private accounts, and posts behind a login.
• Comment text, follower lists, hashtag search, account crawling. This Actor reads posts you name; it does not discover them.
• Paid-partnership labels. The field exists in Meta's data but is empty for logged-out requests.

Limits worth knowing

• Instagram single-image posts are the one place a follower count comes from displayed text rather than data, so it is rounded above ~10K. Facebook and Threads are exact.
• Some news accounts gate their Threads profile behind a login; those rows return login_required rather than a guess.
• Extraction depends on undocumented internal JSON, which Meta can change without notice. Failures are reported per URL rather than crashing the run.