# Ads webhooks

Events for ad, campaign and ad set changes, reviews, delivery issues, ad account status and sync health, Meta leads, and ad rule runs.

## Events

### Ads

| Event | Description |
| --- | --- |
| [`ad.created`](/webhooks/ads/ad-created) | An ad was created through Zernio or detected by the sync. |
| [`ad.updated`](/webhooks/ads/ad-updated) | An ad was edited through Zernio or outside it. |
| [`ad.review.approved`](/webhooks/ads/ad-review-approved) | An ad passed platform review, or a rejection was overturned. |
| [`ad.review.rejected`](/webhooks/ads/ad-review-rejected) | The platform rejected an ad. |
| [`ad.delivery_issue`](/webhooks/ads/ad-delivery-issue) | An ad stopped delivering for a platform reason. |
| [`ad.status_changed`](/webhooks/ads/ad-status-changed) | A Meta ad, ad set or campaign changed status. |
| [`ad.video.processed`](/webhooks/ads/ad-video-processed) | Meta finished processing an async-uploaded video. |

### Campaigns

| Event | Description |
| --- | --- |
| [`campaign.created`](/webhooks/ads/campaign-created) | A campaign was created through Zernio or detected by the sync. |
| [`campaign.updated`](/webhooks/ads/campaign-updated) | A campaign was edited through Zernio or outside it. |
| [`campaign.budget.depleted`](/webhooks/ads/campaign-budget-depleted) | A TikTok campaign ran out of budget. |
| [`campaign.status_changed`](/webhooks/ads/campaign-status-changed) | A campaign's platform status, or Google's reasons for it, changed. |

### Ad sets

| Event | Description |
| --- | --- |
| [`ad_set.created`](/webhooks/ads/ad-set-created) | An ad set was created through Zernio or detected by the sync. |
| [`ad_set.updated`](/webhooks/ads/ad-set-updated) | An ad set was edited through Zernio or outside it. |

### Ad accounts and leads

| Event | Description |
| --- | --- |
| [`account.ads.initial_sync_completed`](/webhooks/ads/account-ads-initial-sync-completed) | The 90-day ad backfill finished for an ads-enabled account. |
| [`account.ads.sync_failed`](/webhooks/ads/account-ads-sync-failed) | An ad account stopped syncing. Once per episode. |
| [`account.ads.sync_recovered`](/webhooks/ads/account-ads-sync-recovered) | An ad account reported as failing is syncing again. |
| [`ad_account.status_changed`](/webhooks/ads/ad-account-status-changed) | An ad account became active, restricted, disabled or closed. |
| [`lead.received`](/webhooks/ads/lead-received) | A new lead was submitted on a Meta Lead Gen form. |

### Conversions

| Event | Description |
| --- | --- |
| [`conversion.received`](/webhooks/ads/conversion-received) | Zernio stored an event, with the campaign it counts for. |
| [`tracking_site.ready`](/webhooks/ads/tracking-site-ready) | A tracked website's tag is confirmed: by its install, or by its first visit for a pasted line. |

### Ad rules

| Event | Description |
| --- | --- |
| [`ad_rule.triggered`](/webhooks/ads/ad-rule-triggered) | An ad rule run found objects meeting every condition. |
| [`automation.check.completed`](/webhooks/ads/automation-check-completed) | A scheduled automation finished a check. |
| [`automation.action.applied`](/webhooks/ads/automation-action-applied) | An automation made a change, with the value before and after. |
| [`automation.action.failed`](/webhooks/ads/automation-action-failed) | An automation change failed or was refused. |
| [`automation.action.unknown`](/webhooks/ads/automation-action-unknown) | The platform did not answer; the next check reads the result back. |
| [`automation.alert.opened`](/webhooks/ads/automation-alert-opened) | An alert was confirmed and its object acted on. |
| [`automation.alert.escalated`](/webhooks/ads/automation-alert-escalated) | An open alert turned critical. |
| [`automation.alert.resolved`](/webhooks/ads/automation-alert-resolved) | An alert ended; `reason` says why. |

## How it behaves

<Accordions>
<Accordion title="The initial sync reports success or failure once" id="the-initial-sync-reports-success-or-failure-once">

Zernio runs the initial sync after an ads-capable account is connected. Outcome, scoped connects and failure fields are on [`account.ads.initial_sync_completed`](/webhooks/ads/account-ads-initial-sync-completed).

Scoping sync to specific ad accounts is covered in [Connecting accounts](/guides/connecting-accounts#scoping-sync-to-specific-ad-accounts). Run [Connect ads](/connect/connect-ads) again to retry a failed sync.

</Accordion>
<Accordion title="Stalled ad accounts: reported once, again on recovery" id="stalled-ad-accounts-reported-once-again-on-recovery">

After the initial sync, Zernio keeps each ad account's ads and metrics fresh on a schedule. An hourly check reports a failing ad account once, then reports recovery once.

Details are on [`account.ads.sync_failed`](/webhooks/ads/account-ads-sync-failed) and [`account.ads.sync_recovered`](/webhooks/ads/account-ads-sync-recovered).

</Accordion>
<Accordion title="Leads arrive in real time" id="leads-arrive-in-real-time">

Zernio forwards each lead from the Page `leadgen` webhook as [`lead.received`](/webhooks/ads/lead-received). Payload, consents, deduplication and the ads requirement are on that page.

With [zero content retention](/security/zero-content-retention) on for the team or the profile, `lead.received` is the only copy of the answers Zernio sends you. Store it when it arrives.

Check a Page's subscription with [Get Page webhook subscription](/connect/get-page-webhook-subscription), and re-send it with [Resync Page webhook subscription](/connect/resync-page-webhook-subscription).

</Accordion>
<Accordion title="Review outcomes come from the sync" id="review-outcomes-come-from-the-sync">

[`ad.review.approved`](/webhooks/ads/ad-review-approved) and [`ad.review.rejected`](/webhooks/ads/ad-review-rejected) fire when the ad sync sees a tracked ad change review outcome, so they arrive within one sync cycle, not instantly.

</Accordion>
<Accordion title="Delivery issues and budgets come from the sync" id="delivery-issues-and-budgets-come-from-the-sync">

[`ad.delivery_issue`](/webhooks/ads/ad-delivery-issue) and [`campaign.budget.depleted`](/webhooks/ads/campaign-budget-depleted) fire when the sync sees a tracked ad move into an error or depleted state. Ads seen for the first time never fire them.

</Accordion>
<Accordion title="Video processing is watched for about 13 minutes" id="video-processing-is-watched-for-about-13-minutes">

Polling and the long-video fallback are on [`ad.video.processed`](/webhooks/ads/ad-video-processed).

</Accordion>
<Accordion title="Coverage by ad network" id="coverage-by-ad-network">

| Event | Meta | Google | TikTok | LinkedIn | Pinterest | X | Reddit |
| --- | --- | --- | --- | --- | --- | --- | --- |
| `ad.review.approved`, `ad.review.rejected` | Yes | Yes, Performance Max per asset group | Yes | Yes | Yes | Yes | Yes |
| `ad.delivery_issue` | Yes | Unrecognized statuses only | Yes | Unrecognized statuses only | Unrecognized statuses only | Unrecognized statuses only | Unrecognized statuses only |
| `campaign.budget.depleted` | No, the ad stays `ACTIVE` | No, the ad stays `ACTIVE` | Yes | No | No | No | No |
| `ad_account.status_changed` | Yes | Yes | Yes | No, only active ad accounts are listed | No, the API exposes no account status | Yes | No, the API exposes no account status |
| `campaign.status_changed` | Yes, `effective_status` | Yes, `primary_status` and its reasons | Yes, `operation_status` | Yes | Yes | Yes | Yes, `effective_status` |
| `account.ads.sync_failed`, `account.ads.sync_recovered` | Yes | Yes | Yes | Yes | Yes | Yes | Yes |

</Accordion>
<Accordion title="Ad account statuses are normalized" id="ad-account-statuses-are-normalized">

[`ad_account.status_changed`](/webhooks/ads/ad-account-status-changed) uses one status vocabulary on every network: `active`, `restricted`, `disabled` and `closed`. `status.raw` keeps the platform's own value.

</Accordion>
<Accordion title="Campaign statuses are the platform's own" id="campaign-statuses-are-the-platforms-own">

[`campaign.status_changed`](/webhooks/ads/campaign-status-changed) carries raw platform values. On Google `status` is the `primary_status`, such as `LIMITED`, and `reasons` its sorted reasons, such as `BUDGET_CONSTRAINED`. Elsewhere `reasons` is empty.

</Accordion>
<Accordion title="Ad rules report what they acted on" id="ad-rules-report-what-they-acted-on">

[`ad_rule.triggered`](/webhooks/ads/ad-rule-triggered) lists the objects a rule run acted on. The `automation.*` events report each check, action and alert episode.

</Accordion>
<Accordion title="Status changes come from two Meta fields" id="status-changes-come-from-two-meta-fields">

[`ad.status_changed`](/webhooks/ads/ad-status-changed) is Meta only and comes from Meta's `ad_account` webhook fields. Fields, `error` handling and fan-out are on that page.

</Accordion>
<Accordion title="Ads access is required" id="ads-access-is-required">

Subscribing to any ad, campaign, ad set, `ad_account`, `lead` or `ad_rule` event needs ads access on the team. Without it, `POST /v1/webhooks/settings` answers `403` with code `ads_addon_required`.

Usage-based billing includes ads on every account ([pricing](/pricing)).

</Accordion>
</Accordions>

## Related

- [Webhooks](/webhooks): create an endpoint, retries, signatures.
- [Meta Ads](/platforms/meta-ads): campaigns, boosting and lead forms.
- [Connecting accounts](/guides/connecting-accounts#scoping-sync-to-specific-ad-accounts): scope the sync to specific ad accounts.
- [List leads](/lead-gen/list-leads): the same leads on demand.