# Meta Ads New Campaign Monitor — New Facebook Ads Alerts (`bovi/meta-ads-new-campaign-monitor`) Actor

Watch a list of Meta advertiser page IDs and get ONLY the ads that are new since the last check — first-seen timestamps, pay per new ad detected, built on the proven token-free Ad Library transport.

- **URL**: https://apify.com/bovi/meta-ads-new-campaign-monitor.md
- **Developed by:** [Vitalii Bondarev](https://apify.com/bovi) (community)
- **Categories:** Marketing
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.55 / 1,000 meta ads new campaign monitor — new facebook ads alerts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Meta Ads New Campaign Monitor

Watch a list of Meta advertiser page IDs and get notified only about the ads that are
**new since the last check** — no manual re-searching, no re-reading a full result set to
spot what changed.

Built on the same token-free public Ad Library transport as our
[Meta Ads Library Scraper](../meta-ads-library-scraper) — no login, no Graph API token.
This actor adds a state layer on top: each run diffs the advertiser's current ads against
what was seen last time, and only the genuinely new ones are pushed and charged.

### How it works

1. Give it a list of advertiser `pageIds` you want to watch.
2. Each run fetches the advertiser's current ads and compares `ad_archive_id`s against the
   snapshot saved from the previous run (stored in the actor's own key-value store).
3. Ads not seen before are pushed to the dataset with `first_seen_run_at` and
   `is_new_since_last_check`, and charge `new_ad_detected` once each.
4. The very first run for a `pageId` establishes a baseline (no charge) — you start
   tracking new campaigns from that point forward, not a retroactive backfill.

Schedule the actor daily or weekly via a standard Apify Schedule to turn it into a standing
alert on a competitor's or client's ad activity.

### Input

- `pageIds` (required) — advertiser Facebook page IDs to watch.
- `countries` — ISO-2 country codes searched per page (Ad Library requires one; default `US`).
- `checkFrequency` — informational label (`daily`/`weekly`); actual cadence is your Apify
  Schedule.
- `proxyConfiguration` — standard Apify proxy input, defaults to RESIDENTIAL (Meta blocks
  datacenter IPs).

### Output fields

Same rich record as the Meta Ads Library Scraper (creative copy, CTA, media URLs, delivery
dates, `is_scaled`/`collation_count`/`days_active` "winning ad" signals) plus:

- `first_seen_run_at` — when this actor first observed the ad.
- `is_new_since_last_check` — always `true` on emitted rows.

### Pricing

Pay per newly-detected ad (`new_ad_detected`). No charge for ads you've already seen, no
charge on the cold-start baseline run.

# Actor input Schema

## `pageIds` (type: `array`):

Numeric Facebook page IDs of advertisers to monitor (find the numeric id in the Ad Library URL of an advertiser page).

## `countries` (type: `array`):

Two-letter ISO country codes searched per page. The Ad Library requires a country.

## `checkFrequency` (type: `string`):

This field is INFORMATIONAL only — actual run cadence is set by the buyer's Apify Schedule on this actor.

## `proxyConfiguration` (type: `object`):

Recommend Apify RESIDENTIAL proxy because Meta blocks datacenter IPs.

## Actor input object example

```json
{
  "pageIds": [
    "123456789012345"
  ],
  "countries": [
    "US"
  ],
  "checkFrequency": "daily",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset with the scraped records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "countries": [
        "US"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("bovi/meta-ads-new-campaign-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "countries": ["US"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("bovi/meta-ads-new-campaign-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "countries": [
    "US"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call bovi/meta-ads-new-campaign-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bovi/meta-ads-new-campaign-monitor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/C95GhtmEdXzEdKeaD/builds/wgjoTufpEJJ6ozijy/openapi.json