Instagram, Facebook & Threads Post Metrics Tracker
Pricing
from $3.00 / 1,000 post trackeds
Track Instagram, Facebook and Threads post metrics over time. Put your post URLs on a schedule and every run returns likes, comments, shares, views and followers, plus the change since the last run and since the first. Export to CSV, Excel or JSON, or use the API.
Public Instagram post and reel URLs, Threads post URLs and Facebook post, reel and video URLs, mixed freely in one list. Add or remove URLs between runs: a new URL starts its own history, and a removed one keeps its history in case it comes back. See the README for accepted URL shapes. Up to 5,000 per run.
Names the history this run reads and adds to, kept in a key-value store called post-tracker-{name}. Use one name per campaign so their histories never mix, and keep it the same on every run of the Schedule. Letters, digits and hyphens, up to 40 characters.
Append every successful reading to a dataset called post-tracker-{name}-history, one row per post per run, so a chart of a post over time can be drawn from a single table. Off by default: the history itself is kept either way, and this dataset only grows.
How many readings of each post to keep. The first reading is always kept, so change since the first stays exact; the oldest of the rest are dropped beyond this. 1000 is almost three years of daily runs.
Look up the author's follower count, so follower growth is tracked too. This costs one extra request per account, so turn it off if you only need post metrics.
Ends the run early when a platform stops responding, so a broken run cannot burn through your whole list. Deleted posts do not count. Set to 0 to never stop early.
Store the raw response of failed URLs in the run's key-value store. For diagnosing why a proxy or platform change broke extraction.
For Instagram and Threads, which Apify's datacenter proxy reads fine. Residential and Google SERP proxy groups are not used here: the price per post is set for datacenter traffic, so a run that asks for them falls back to the datacenter proxy and says so in RUN_SUMMARY. Proxy URLs of your own are used as given.
{ "useApifyProxy": true}Facebook serves a login wall to datacenter IPs, so it needs residential proxies. This only applies to Facebook URLs, so Instagram and Threads in the same run stay on the cheap proxy.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}