List custom conversions
The ad account's Meta custom conversions, including archived ones (isArchived).
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Path Parameters
Meta ads SocialAccount id.
Query Parameters
Meta ad account id (act_).
Response Body
application/json
application/json
application/json
application/json
{ "adAccountId": "string", "data": [ { "id": "string", "name": "string", "rule": {}, "customEventType": "string", "pixelId": "string", "isArchived": true } ]}Replace negative list keywords
Replaces the full desired keyword set. Existing keywords are diffed by normalized text and match type; creates and removals are applied atomically in one mutation. Unchanged criteria retain their ids. Send an empty keywords array to clear the list. Changes affect every campaign using this list. Each create or removal consumes one daily operation; the entire batch must fit the remaining quota.
Create custom conversion
Provision the Meta custom conversion an ads flow optimises toward, and hand back the `customConversionId` for `promotedObject.customConversionId` on POST /v1/ads/create. Removes the manual "create it in Ads Manager first" step. **Reuse is ours, not Meta's.** Meta's create is not idempotent, so a retried request would otherwise mint a duplicate carrying none of the original's optimisation history. A non-archived conversion with the same `name` on the same `pixelId` is returned instead of created, with `reused: true` and a 200 rather than a 201. `rule` is forwarded verbatim in Meta's own grammar (e.g. `{"url": {"i_contains": "thank-you"}}`); Meta validates it and rejects a malformed one with "A conversion rule is required at creation time".