Skip to main content

Propose Guardrail Signal Fix

POST 

/api/advertising/signals/:signal/propose

Plans the signal's own fix now, as a change set waiting for approval, even when guardrails for its product are set to Monitor (which otherwise only flags problems). Use it for a signal whose decision card has details.proposable: true; once created, the set appears on the signal's decision with approve and reject actions.

Required scope: advertising:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

The proposal is never applied automatically: it always waits for approval, whatever the mode. The usual safeguards still apply: nothing is proposed when guardrails, the ad account's automation or the product's campaigns are set to Off, while the kill switch is on, during an event freeze (except Critical signals when the freeze allows them), for a product in the comparison group of a running guardrail test, when the platform does not support the change for the ad type, for ads SKU.io already paused or someone changed by hand recently, or when the account needs reconnecting. Calling it again while the set is still waiting for approval returns that same set (created: false) instead of a duplicate.

No request body. Responds 201 Created with the new set, 200 OK with the set already waiting, or 422 with a plain-English message and a machine-readable reason when nothing can be proposed. Reason codes: not_open, cleared, not_actionable, mode_off, account_off, campaigns_off, needs_reconnect, kill_switch, frozen, holdout_control, read_only_access, no_capabilities, already_held, cooldown, guardrail_disabled, unsupported, no_live_ads, already_acted_on, nothing_found, stale_data, busy, failed.

Requires the advertising.manage permission. Personal access tokens need the advertising:write scope.

Request​

Responses​

OK

Response Headers
    Content-Type