List value rule sets
Lists the ad account's value rule sets (Meta's /act_X/value_rule_set). A value rule
set adjusts the auction bid up or down for audience segments you value differently;
attach one to an ad set with valueRuleSetId on POST /v1/ads/create or
PUT /v1/ads/ad-sets/{adSetId}.
Rows are returned in the same camelCase shape the PUT body takes, ids included, so a
set round-trips 1:1: the update is a full replace, not a patch, so you GET, mutate
and send the whole thing back.
Limits: 6 rule sets per ad account, 10 rules per set, 4 criteria per rule.
Rule order is semantic. Rules are evaluated in array order and only the FIRST matching rule adjusts the bid for an overlapping audience. The order you send is the order that is stored and returned.
Eligibility: value rule sets apply only to ad sets on the LOWEST_COST_WITHOUT_CAP
(auto-bid) or COST_CAP bid strategies. Meta rejects the rest server-side.
API key authentication - use your Zernio API key as a Bearer token
In: header
Query Parameters
Zernio SocialAccount id (posting or ads variant) used to resolve the Meta token.
Meta ad account id (act_).
Rows per page
251 <= value <= 100Cursor from paging.after of the previous page. Meta does not document paging on this edge; after comes back null when it omits cursors.
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.adaccounts.listValueRuleSets({ query: { accountId: 'account_abc123', adAccountId: 'adaccount_abc123', },});console.log(data);{
"adAccountId": "string",
"data": [
{
"id": "string",
"name": "string",
"rules": [
{
"id": "string",
"name": "string",
"adjustSign": "INCREASE",
"adjustValue": 1,
"status": "string",
"criteria": [
{
"id": "string",
"criteriaType": "AGE",
"operator": "CONTAINS",
"criteriaValues": [
"string"
],
"criteriaValueTypes": [
"string"
]
}
]
}
]
}
],
"paging": {
"after": "string"
}
}{
"error": "Unauthorized"
}Businesses list GET
Business Manager portfolios the connected Meta user belongs to (Meta's `/me/businesses`), rows returned verbatim (id, name, verification_status, created_time). Token-scoped, so no `adAccountId` is needed. For TikTok Business Centers use `GET /v1/ads/business-centers`.
Create or reuse a custom conversion POST
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".