> For the complete documentation index, see [llms.txt](https://docs.smaq.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smaq.io/documentation/features/creative-intelligence/competitor-ads-meta.md).

# Competitor Ads Monitor (Meta)

The Competitor Ads Monitor scans the **Meta Ad Library** (Meta's public ads transparency archive) for ads currently running by competitor Pages you specify. SMAQ pulls the creative, copy, and platforms each ad runs on; the AI surfaces themes, new launches, and shifts in messaging.

### What you need

* A Meta Ads connection isn't required — the Ad Library is public.
* The exact Facebook Page URL or Page name for each competitor (e.g. `https://facebook.com/nike` or just `nike`).
* The country whose Ad Library to scan (Meta partitions by country).

### Configuration

> **\[Screenshot needed]** Competitor Ads Monitor configuration form with three competitor Page URLs entered and country set to "United States".

#### Competitor Pages

Add one or more competitor Pages. Each entry includes:

* **Page name or URL**
* **Label** (optional — how you want to refer to them in the email)

You can monitor up to 10 competitor Pages per automation. For more, create multiple automations.

#### Country

Pick the country whose Ad Library to scan. Meta partitions ads geographically — a brand running ads in the US and Germany shows different sets of ads in each.

#### Schedule

Weekly is the standard cadence. Creative trends don't move fast enough to need daily.

### Output

Every run produces:

* **An email** with grouped ad creatives per competitor, themes the AI extracted, and any "new this week" callouts.
* **A snapshot** with the full creative grid — viewable in-app under the automation's Snapshots tab.

> **\[Screenshot needed]** Example email output showing three competitor sections, each with 4–6 ad thumbnails and one-paragraph theme summaries.

### Tips

* **Pick true competitors, not aspirational ones.** Tracking a Nike-sized brand is interesting but rarely actionable.
* **Track 2–5 competitors per monitor.** Beyond 5, the email gets too long to read.
* **Use the labels.** "Direct competitor — local SEO" beats "competitor #3" when you're scanning the email.
* **Watch for new copy angles**, not just new visuals. A competitor shifting from product-led to lifestyle-led copy is signal.

### Limitations

* **Only ads currently running.** Past ads are visible in the Ad Library but SMAQ focuses on live ones.
* **Spend isn't visible.** The Ad Library doesn't share spend (with rare political-ads exceptions).
* **Audience info isn't visible.** You see the ad, not who it's targeted at.

### Tier availability

* **Scale & Agency** — fully available.
* **Starter, Growth** — not available.

### Related

* [Google Competitor Ads Monitor](/documentation/features/creative-intelligence/google-competitor-ads.md) — the equivalent for Google Ads.
* [Ad Fatigue Detector](/documentation/features/creative-intelligence/ad-fatigue-detector.md) — for your own ads, not competitors'.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.smaq.io/documentation/features/creative-intelligence/competitor-ads-meta.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.