Webhook Events

Campaign status changed event

A campaign Zernio already tracked changed its platform status or, on Google, the reasons behind it.

When it fires

Fires when the ads sync reads a tracked campaign with a different status than it stored, up to one sync interval late. Covers every ad network.

Status values

On Google, status is the campaign's primary_status (ELIGIBLE, LIMITED, NOT_ELIGIBLE, PAUSED, ...) and reasons its sorted primary_status_reasons, so a campaign turning budget limited fires. Elsewhere status is the campaign's own platform status (Meta effective_status) and reasons is empty.

When it does not fire

A campaign seen for the first time, or the same change from the same previous status again within an hour (a retried sync). A change made through Zernio, such as a pause, fires on the next sync, once the sync reads it from the platform.

postWebhookcampaign.status_changed

Payload

idstring required

Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery.

testboolean

Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.

event'campaign.status_changed' required
platformstring required

The ad network, as the ads endpoints name it (google, facebook, tiktok, ...).

adAccountIdstring required

Platform-native ad account ID.

timestampstring date-time required

UTC time at which Zernio generated this event.

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ],
  "account": {
    "platform": "tiktokads"
  }
}

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.