Skip to main content
Adclear can send nine kinds of event. Each one arrives with the same outer details, like which event it is and when it happened. The details about what happened are inside data. Most events include the same few things: the promotion, the version of it, and who did it. Those are explained once under Shared details. Each event below then lists only what’s different about it.

A full example

Here is everything Adclear sends when a reviewer rejects a promotion.
To link back to the promotion in Adclear, use both IDs: https://app.adclear.ai/v2/promotion/{data.promotion.id}/version/{data.version.id}.

Shared details

The promotion the event is about. The promotion’s actual wording and images are not included.
One version of the promotion. promotionId points back to the parent.
The person who took the action.
One problem Adclear found when it checked a promotion.

Status values

status, previousStatus and newStatus use these values: saved, pending, expired, in_review, approved, rejected, changes_needed, conditionally_approved, escalated, reviewing_risk, risk_accepted. See Promotion statuses for what each one means.

Events

Every event includes promotion and version. The tables show what each one adds.
A promotion was created, along with its first version. Nothing extra is added. The test event you send from Settings is one of these, with IDs made of zeros.
A promotion version moved to a new status, for example from in_review to approved.
A new version was added to an existing promotion.
A version was submitted and is waiting on a reviewer.
A reviewer approved a version, either outright or with conditions.
A reviewer asked for changes before the version can be approved.
A reviewer rejected a version. Same fields as review.changes_requested. See A full example.
Someone added a comment to a version.
Adclear finished checking a promotion, whether the check worked or not.

Webhooks

How webhooks are sent, checked and retried.

Webhook recipes

Examples in Zapier, Slack and Jira.