> **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`). --- # Ad Tracker alerts and exports (https://www.socialfetch.dev/docs/tools/ad-tracker/alerts-and-exports) The Ad Tracker can email you when competitors launch ads, send the same news to other tools, and give you the ads as a spreadsheet or through the API. ## Email alerts To choose your emails, click the gear button (**Alerts and webhooks**) at the top right of the Ad Tracker, next to **Boards**. **Email alerts** has three settings, and they apply to the whole workspace's tracker. Changes save as you make them. | Setting | What you get | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **New ads** | An email when a competitor launches new ads, with a few of them and a link to the rest. At most one email per competitor a day, never one per ad. On to start. | | **Send when a competitor launches** | Holds the new-ads email until a competitor has launched this many: **Any new ad**, or **3**, **5**, **10** or **25 or more new ads**. Use a higher number for brands that launch a few ads every day. | | **Weekly digest** | An email every Monday with what each competitor launched and stopped, where they started advertising, and their longest-running ad. It's skipped in a week when nothing happened. On to start. | New-ad emails only count launches: ads that started within a week of being found. With **New ads** on, you also get one email when a new competitor's first check has finished, whatever the minimum. In a personal workspace, emails go to your account's address. In a shared workspace, each competitor's emails go to the person who added it, or to the workspace owners if that person has left. To share alerts with colleagues or a client, send them to a team channel with a webhook (below). Only owners and admins can change these settings; other roles can see them. Whatever your settings, if the workspace runs out of credits, the tracker sends one email to say so (at most once every three days). See [When credits run out](/docs/tools/ad-tracker/costs-and-limits#when-credits-run-out). ## Webhooks Webhooks are optional, and mainly for people who use Zapier, Make or their own code. A webhook sends each tracker event to a web address you choose, as a small data file (signed JSON) the receiving tool reads. With a Zapier or Make "catch hook" (a web address that starts a Zap or scenario), you can post each event to Slack, Teams or a spreadsheet without code. Webhooks don't follow the email settings: every check that finds a launch or a stop sends an event. 1. Create a webhook endpoint. On the settings page, under **Webhooks**, click **Create an endpoint** (or **Manage endpoints**), then add your URL. To try it first, choose **Test inbox**, which shows deliveries inside Social Fetch. 2. Go back to the Ad Tracker's settings (**Tools**, **Ad Tracker**, then the gear button) and switch on the endpoint. 3. Click **Send test event**. **Test event delivered.** means it arrived. There are four events: new ads launched, ads stopped, a monthly brief written, and the weekly digest. Each one has a plain-English `summary`, such as *Duolingo launched 12 new ads on Meta*, which is what to post to Slack. [Ad Tracker events](/docs/monitors/ad-tracker-events) has the payloads and a Slack recipe. ## Export to CSV To download ads as a CSV file, which opens in Excel, Google Sheets or Numbers, go to **All ads** on the dashboard or **All their ads** on a competitor's page, set the filters you want, and click **Export CSV**. The file has the ads you're looking at, in the same order, up to 5,000. If there are more, it says so; narrow the filters and export again. Each row is one ad, with these columns: Competitor, Library, Status, Format, Headline, Body, CTA, Landing page, Started, Stopped, Run days, Proven, Tags and Library URL. To keep an ad's image or video, open the ad and click **Download** under it. There's no download of every file at once. ## Use the API Everything the tracker collects comes from Social Fetch API endpoints, at the same prices. On a competitor's page or an ad's page, click **API** to see the exact call the tracker makes, in cURL, Node.js, Python or the TypeScript SDK, ready to copy. **Try it in the playground** runs it in the app; like any lookup, that spends credits. Use it to put the same data in your own dashboard, spreadsheet or AI agent. - [Use cases](/docs/tools/ad-tracker/use-cases) — Ways to use alerts and exports. - [Troubleshooting](/docs/tools/ad-tracker/troubleshooting) — Missing emails, webhooks and more.