> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration. ## This page - **On-site (HTML):** - **Markdown (.mdx) URL:** ## API base URL and authentication - **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev` - **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route). - **OpenAPI JSON:** ## Recommended docs entrypoints (this site) - [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown). - [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope. - [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`. - [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages. - [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples. - [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths. - [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install. - [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 264 endpoint tools, plus docs_search/docs_read for implementation help. - [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples. - [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start. - [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog. - [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI). - [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls). - [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist. - [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping. - [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages. - [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance. - [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs. - Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract. ## Markdown docs convention - Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`). - Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`). - Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`). --- # Read your X Follower Tracker results (https://www.socialfetch.dev/docs/tools/follower-tracker/read-your-results) Each tracked account has its own page, opened from the tracker home page. Along the top are the account, when it's checked, its status, **Export**, **Check now** and a **⋯** menu with **Pause tracking** and **Remove**. Below them are five tabs: **Overview**, **Changes**, **Audience**, **Posts** and **Settings**. ## The numbers at the top * **Followers**: the follower count X showed at the last check. If you set a follower goal, it shows how close you are. * **Since last check**: how much the count changed since the check before. * **Past 7 days**: the change over the last week, once there's a week of history. * **Collected audience**: how many followers the tracker has in its list, and how many of them have profile details. ## Follower history The chart shows the follower count at each check. Choose **7 days**, **30 days**, **90 days** or **All** once there's enough history. With **Post context** on, the account's own posts appear as dashed lines, so you can see whether follower jumps line up with particular posts. Lining up doesn't prove a post caused the change. Below the chart, the tracker says when the account was last checked and when the next check is due. If tracking was paused, a check stopped or a check was missed, the chart says **No checks ran for a while** from that date. Changes across the gap are grouped together, because the tracker can't tell exactly when they happened. ## Highlights With **AI insights** on, **Highlights** picks out what's worth knowing from the latest check, such as a jump in followers, people on your watchlist who changed, or how a segment grew. Each highlight comes from the account's own numbers, and **See the data** opens the list it's based on. ## Who followed and who left **Recent changes** on the Overview shows the latest few, and the **Changes** tab lists them all, newest first. Each person has a label: | Label | What it means | | ---------------- | ---------------------------------------------------- | | **New follower** | Started following since the check before. | | **Left** | Stopped following, and the tracker confirmed it. | | **Came back** | Followed again after an earlier confirmed departure. | **When** shows when the tracker saw the change. Someone who followed could have done so at any time since the check before, so with daily checks a change is accurate to the day. The **Change history** export has the exact window for each one. Search the Changes tab by name or handle. Click anyone to open their profile. The first check is the starting point, so it has no changes. They start with the second check. ### Why some people aren't counted as gone yet Sometimes a follower is missing from a check but the tracker can't confirm they left, for example because their account is suspended or temporarily hidden. The Changes tab then says how many people were **missing from the last check but not confirmed gone**. The tracker checks them again each time, and only counts them as **Left** once it's sure. This is why its numbers can differ from simple unfollower apps that count everyone who's missing. ## The account's status The badge next to **Export**, and the card on the tracker home page, show what the account is doing: | Status | Meaning | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Tracking** | Checks are running on schedule. | | **Up to date** | The last check finished. The next one runs on schedule. | | **Check queued** | A check is about to start. | | **Checking** | A check is running now. | | **Paused** | No checks run until you resume. Its history is kept. | | **Limit reached** | A check stopped at a credit limit. Raise it, then click **Check now**. See [Costs and limits](/docs/tools/follower-tracker/costs-and-limits#when-a-check-stops). | | **Needs credits** | A check stopped because your balance ran out. Add credits, then click **Check now**. | | **Needs attention** | Something went wrong. Click **Check again**. See [Troubleshooting](/docs/tools/follower-tracker/troubleshooting#this-check-needs-attention). | ## Change the settings Everything you chose when you started, and the alerts, live in the account's **Settings** tab: what to track, how often, the extras, the limits and **Alerts and goal**. Change what you need and click **Save settings**. The changes apply from the next check. ## Posts With **Post context** on, the **Posts** tab shows the account's posts from the last 30 days, with their replies, reposts, likes, bookmarks and views at the last check. Switch between **Posts** (its own posts and quotes) and **Replies, reposts and context**. Older posts have had longer to collect engagement, so compare like with like. ## Pause or remove an account Open **⋯** at the top of the account page, or use the buttons at the bottom of **Settings**: * **Pause tracking** stops checks and keeps everything. **Resume tracking** starts checking again within a few minutes. * **Remove** stops checks straight away. The account's history is kept for 30 days, then deleted. - [Explore the audience](/docs/tools/follower-tracker/explore-the-audience) — Search and filter everyone who follows. - [Use cases](/docs/tools/follower-tracker/use-cases) — What to do with the results. - [Costs and limits](/docs/tools/follower-tracker/costs-and-limits) — Keep checks running smoothly.