Update Meta Conversions API destination config
Partially updates the tenant’s Meta Conversions API (CAPI) destination config — enable/disable, set the pixel id or test-event code, tune the per-tenant daily forward cap, or rotate the access token (encrypted at rest; plaintext is never persisted and an empty string clears it). Only the supplied fields are merged, so an absent key is left untouched, and the worker-owned last_run_* status fields the delivery loop writes are never accepted. Use it as the connect-form save for the Meta CAPI destination. Returns the same sanitised shape as GET. Owner / admin / developer only; every write emits a key-names-only audit event.
Response
The updated Meta CAPI destination config after the merge, with the encrypted access-token blob replaced by the access_token_configured boolean.
The updated Meta CAPI destination config after the merge, with the encrypted access-token blob replaced by the access_token_configured boolean.