List ad sets
Ad sets (Google ad groups) synced for the connection, optionally
filtered by platform and campaignId. Reads the ad_sets table
directly, independent of the ads rollup GET /v1/ads/tree uses, so a
newly created standalone ad group with no ad yet (POST /v1/ads/ad-sets,
Google only) is visible here even though it is invisible in the tree
until an ad joins it via adSetId on POST /v1/ads/create. Returns at most 500
rows, newest first.
Status freshness. status, configuredStatus, platformStatus, platformAdSetStatus
and platformCampaignStatus are the values Zernio last stored. Background sync refreshes
them, typically within 15 to 60 minutes (Google up to about 3 hours), and ended or
long-paused objects may be refreshed less often. Zernio's own status writes re-read the
switches they change. A change made in the platform's own ads manager therefore shows up
here only after the next sync. Controllers that act on a switch should pass live=true,
which reads the switches from the platform now, stores them, and returns statusReadAt
(null when the read failed and the stored values were returned).
With live=true (which needs a campaignId or adSetId filter) each listed ad set's own
switch (platformAdSetStatus) is read live, for the first 20 rows; later rows keep their
synced value with statusReadAt: null. Live reads cover TikTok, Meta, Google and OpenAI.
The rolled-up status is not re-derived by a live read. On TikTok the same live read also
returns the ad group's applied optimizationGoal and billingEvent, as TikTok's adgroup/get
reports them, so you can verify the goal TikTok applied rather than the one you requested.
It also returns nativeSettings: TikTok's own adgroup/get record for the ad group, verbatim and
read in that same call (budget, budget_mode, schedule, placements, locations, ages, gender,
languages, interests, actions, audiences and exclusions), plus the advertiser's currency and
timezone. TikTok's schedule_start_time / schedule_end_time are UTC wall clocks
("YYYY-MM-DD HH:MM:SS", no offset); Ads Manager displays them in advertiser_timezone. configReadAt says when it was read; it
is null on every row whose native settings were not read now, so never treat a null as a match.
These are read, not retained create payloads, and are not stored.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Query Parameters
Account ID
Platform campaign ID
Platform ad set ID
Value in
- "facebook"
- "instagram"
- "tiktok"
- "linkedin"
- "pinterest"
- "google"
- "twitter"
- "openai"
Read the on/off switches live from the platform instead of returning the synced values. The fresh values are stored (so later reads return them too) and the response carries statusReadAt, the time of the read. At most 20 platform objects are read per request. Where a read fails (credentials, platform error, no reader on that platform), the stored values come back with statusReadAt: null. See "Status freshness" in the operation description.
falseResponse Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.adcampaigns.listAdSets();console.log(data);{ "adSets": [ { "platformAdSetId": "string", "platform": "string", "adSetName": "string", "status": "string", "platformAdSetStatus": "string", "platformCampaignId": "string", "platformAdAccountId": "string", "accountId": "string", "profileId": "string", "currency": "string", "budget": { "amount": 0, "type": "daily", "daily": 0, "lifetime": 0, "pacing": "string" }, "schedule": { "startDate": "2019-08-24T14:15:22Z", "endDate": "2019-08-24T14:15:22Z" }, "targeting": { "include": {}, "exclude": {}, "audienceExpansionEnabled": true, "offsiteDeliveryEnabled": true }, "isExternal": true, "platformCreatedAt": "2019-08-24T14:15:22Z", "statusReadAt": "2019-08-24T14:15:22Z", "optimizationGoal": "string", "billingEvent": "string", "nativeSettings": {}, "configReadAt": "2019-08-24T14:15:22Z" } ]}Replace an asset group's listing-group tree
Replace the product (listing-group) tree of a Performance Max retail asset group. The current tree is removed and the new one created in one atomic request. Read the current tree with GET on the asset group. Requires a campaign linked to Merchant Center; other campaigns return 400 LISTING_SOURCE_NOT_ALLOWED from Google. validateOnly: true validates without writing.
Create a standalone ad group
Google Ads compliance row C.190: creates an ad group WITHOUT an ad, under an existing campaign. Ads join it later via `adSetId` on POST /v1/ads/create. Google only; every other platform returns 501. Created `PAUSED` unless `status: ACTIVE`. The new ad group has no ad yet, so it will not appear in GET /v1/ads/tree (built purely from `ads` rows) until one is added; use GET /v1/ads/ad-sets to see it in the meantime. **Idempotency:** send an `Idempotency-Key` header to make retries safe.