ZEzernio
Webhook Events

Campaign updated event

A campaign was edited through Zernio (source: "zernio"), or outside Zernio and detected by the sync (source: "platform").

When it fires

Fires after the platform and Zernio both accepted the edit. Outside edits arrive up to one sync interval late, and only to the user whose sync saw them.

Deduplication

Events are not deduplicated, so every edit is announced. Use the event id to drop repeats.

Payload notes

changes lists the edited fields: name, status (the campaign's own on/off switch), budget, bid or settings. Ignore unknown values. It never carries old or new values, so read the campaign.

What the sync detects

From the sync, changes covers only name, status and schedule. Schedule is detected only on Google, LinkedIn, Pinterest and OpenAI Ads.

When it does not fire

Budget edits made outside Zernio and history loaded at connect are not announced. Ad set edits arrive as ad_set.updated. Ad rule changes arrive as ad_rule.triggered.

Google sub-resources

Edits to ad schedule, targeting, negative keywords, conversion goals, assets, asset groups and listing group filters are not announced.

postWebhookcampaign.updated

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.updated' required
changesstring[] required

Fields edited by this request. status is the campaign's own on/off switch. Ignore values you do not know.

source'zernio' | 'platform' required

Where the edit was made. zernio for edits through Zernio, platform for edits the sync detected outside Zernio.

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.