@zernio/node 0.2.762 → 0.2.763

package/dist/index.d.mts

@@ -32722,7 +32722,7 @@ type GetCampaignTargetingResponse = ({
         device?: 'MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV';
         included?: boolean;
         /**
-         * Always null on this read (see description).
+         * Google's bid adjustment for this device: null when it has none, 0 when the device is switched off, otherwise 0.1 to 10.
          */
         bidModifier?: (number) | null;
     }>;
@@ -33485,12 +33485,12 @@ type UpdateAdData = {
                 matchType?: 'exact' | 'phrase' | 'broad';
             })>;
             /**
-             * Google only. The FULL new set of device criteria for the campaign; devices not listed are excluded. Entries are a device name alone (included, no bid adjustment) or { device, bidModifier }.
+             * Google only. The FULL new set of device bid modifiers for the campaign. Entries are a device name alone (targeted, bid modifier reset to 1) or { device, bidModifier }. A supported device you leave out is switched off, written as a bid modifier of 0. Google never removes a device criterion, so an excluded device reads back as bidModifier 0 rather than disappearing, and a set that switches every device off returns 422. Which devices a campaign carries depends on its channel: Search campaigns have MOBILE, DESKTOP and TABLET, Display campaigns also have CONNECTED_TV, and sending a device the campaign does not carry returns 422.
              */
             devices?: Array<('MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV' | {
                 device: 'MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV';
                 /**
-                 * Google device bid modifier, 0.1 to 10 (minus 90% to plus 900%). Omit a device to exclude it.
+                 * Google device bid modifier. 0 switches the device off (minus 100%); otherwise 0.1 to 10 (minus 90% to plus 900%). Google rejects any value between 0 and 0.1.
                  */
                 bidModifier?: number;
             })>;
@@ -36795,11 +36795,11 @@ type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Meta, TikTok, and LinkedIn: publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
+         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Google Search and Display, Meta, TikTok, and LinkedIn: publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. Google Search and Display follow the same rule, and because Google keeps an independent switch at campaign, ad group and ad level, a PAUSED create leaves the campaign it creates PAUSED at Google. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
-         * Meta only. Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
+         * Meta and Google. Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
          */
         campaignStatus?: 'ACTIVE' | 'PAUSED';
         /**
@@ -37802,7 +37802,7 @@ type CreateStandaloneAdResponse = ({
         node?: 'campaign' | 'adSet' | 'creative' | 'ad' | 'performanceMaxCampaign';
         status?: 'validated' | 'skipped';
         /**
-         * Why the node could not be validated (only on skipped).
+         * Why the node could not be validated (on skipped), or what the dry run could not check and what the request would do as sent (on validated). A Performance Max validation with no location targeting reports here that the campaign would run worldwide.
          */
         reason?: string;
     }>;

package/dist/index.d.ts

@@ -32722,7 +32722,7 @@ type GetCampaignTargetingResponse = ({
         device?: 'MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV';
         included?: boolean;
         /**
-         * Always null on this read (see description).
+         * Google's bid adjustment for this device: null when it has none, 0 when the device is switched off, otherwise 0.1 to 10.
          */
         bidModifier?: (number) | null;
     }>;
@@ -33485,12 +33485,12 @@ type UpdateAdData = {
                 matchType?: 'exact' | 'phrase' | 'broad';
             })>;
             /**
-             * Google only. The FULL new set of device criteria for the campaign; devices not listed are excluded. Entries are a device name alone (included, no bid adjustment) or { device, bidModifier }.
+             * Google only. The FULL new set of device bid modifiers for the campaign. Entries are a device name alone (targeted, bid modifier reset to 1) or { device, bidModifier }. A supported device you leave out is switched off, written as a bid modifier of 0. Google never removes a device criterion, so an excluded device reads back as bidModifier 0 rather than disappearing, and a set that switches every device off returns 422. Which devices a campaign carries depends on its channel: Search campaigns have MOBILE, DESKTOP and TABLET, Display campaigns also have CONNECTED_TV, and sending a device the campaign does not carry returns 422.
              */
             devices?: Array<('MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV' | {
                 device: 'MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV';
                 /**
-                 * Google device bid modifier, 0.1 to 10 (minus 90% to plus 900%). Omit a device to exclude it.
+                 * Google device bid modifier. 0 switches the device off (minus 100%); otherwise 0.1 to 10 (minus 90% to plus 900%). Google rejects any value between 0 and 0.1.
                  */
                 bidModifier?: number;
             })>;
@@ -36795,11 +36795,11 @@ type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Meta, TikTok, and LinkedIn: publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
+         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Google Search and Display, Meta, TikTok, and LinkedIn: publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. Google Search and Display follow the same rule, and because Google keeps an independent switch at campaign, ad group and ad level, a PAUSED create leaves the campaign it creates PAUSED at Google. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
-         * Meta only. Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
+         * Meta and Google. Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
          */
         campaignStatus?: 'ACTIVE' | 'PAUSED';
         /**
@@ -37802,7 +37802,7 @@ type CreateStandaloneAdResponse = ({
         node?: 'campaign' | 'adSet' | 'creative' | 'ad' | 'performanceMaxCampaign';
         status?: 'validated' | 'skipped';
         /**
-         * Why the node could not be validated (only on skipped).
+         * Why the node could not be validated (on skipped), or what the dry run could not check and what the request would do as sent (on validated). A Performance Max validation with no location targeting reports here that the campaign would run worldwide.
          */
         reason?: string;
     }>;

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.762",
+  version: "0.2.763",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.762",
+  version: "0.2.763",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zernio/node",
-  "version": "0.2.762",
+  "version": "0.2.763",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -8177,6 +8177,12 @@ export const createAdCampaign = <ThrowOnError extends boolean = false>(options:
  * On Meta this flips the campaign only. An ad set paused in its own right stays paused, so pair this with
  * PUT /v1/ads/ad-sets/{adSetId}/status when you also need the ad set switched back on.
  *
+ * Google keeps an independent on/off switch at campaign, ad group and ad level and the most restrictive
+ * one wins, so `active` switches the campaign on TOGETHER with the ad groups and ads Zernio tracks under
+ * it, in one mutate. Without that the campaign reads ENABLED while a paused ad group or ad keeps it from
+ * serving. `paused` writes the campaign alone, which already stops delivery and leaves each ad's own
+ * switch as you set it.
+ *
  */
 export const updateAdCampaignStatus = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAdCampaignStatusData, ThrowOnError>) => {
     return (options?.client ?? client).put<UpdateAdCampaignStatusResponse, UpdateAdCampaignStatusError, ThrowOnError>({
@@ -8374,10 +8380,11 @@ export const duplicateAdCampaign = <ThrowOnError extends boolean = false>(option
  * (10 minutes fresh, up to 7 days last-good), not always a live read. Google
  * only; every other platform returns 501.
  *
- * `devices` always lists all four device types with `included` reflecting
- * Google's negative device criteria (a device absent from any negative
- * criterion is included by default). This read has no bid-modifier source,
- * so `bidModifier` is always `null` even for a device with one configured.
+ * `devices` lists the device criteria the campaign carries, which depends on
+ * its channel: Search campaigns have MOBILE, DESKTOP and TABLET, Display
+ * campaigns also have CONNECTED_TV. `bidModifier` is Google's bid adjustment
+ * for that device, `null` when it has none, and `0` when the device is
+ * switched off; `included` is false for exactly that case.
  *
  */
 export const getCampaignTargeting = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetCampaignTargetingData, ThrowOnError>) => {
@@ -8396,6 +8403,11 @@ export const getCampaignTargeting = <ThrowOnError extends boolean = false>(optio
  * out of the body are untouched. Google only; every other platform returns
  * 501.
  *
+ * `devices` is the full set of device bid modifiers: a supported device you
+ * leave out is switched off with a bid modifier of 0, since Google cannot
+ * remove a device criterion. A device the campaign's channel does not carry,
+ * and a set that switches every device off, both return 422.
+ *
  * `locations` accepts the same shapes as campaign creation: a bare array of
  * ISO country codes, or an object with `countries`/`regions`/`cities`/`zips`/`metros`
  * key lists (`key` from GET /v1/ads/targeting/search?dimension=geo). Negative
@@ -8699,7 +8711,9 @@ export const getAd = <ThrowOnError extends boolean = false>(options: OptionsLega
  * `targeting.countries` / `regions` / `cities` / `zips` / `metros`), and LANGUAGE
  * edits via `targeting.languages`.
  * Each list you send becomes the FULL new set of its kind (criteria not in the
- * list are removed); a kind left out is untouched. Any other `targeting` field
+ * list are removed, except devices, which Google cannot remove and which are
+ * switched off with a bid modifier of 0 instead); a kind left out is untouched.
+ * Any other `targeting` field
  * returns 400: Google cannot mutate it post-create without recreating
  * the campaign. Creative edits are dispatched on the ad's `advertisingChannelType`,
  * and every supported field replaces a whole set; a field you omit is preserved.

package/src/generated/types.gen.ts

@@ -33059,7 +33059,7 @@ export type GetCampaignTargetingResponse = ({
         device?: 'MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV';
         included?: boolean;
         /**
-         * Always null on this read (see description).
+         * Google's bid adjustment for this device: null when it has none, 0 when the device is switched off, otherwise 0.1 to 10.
          */
         bidModifier?: (number) | null;
     }>;
@@ -33860,12 +33860,12 @@ export type UpdateAdData = {
     matchType?: 'exact' | 'phrase' | 'broad';
 })>;
             /**
-             * Google only. The FULL new set of device criteria for the campaign; devices not listed are excluded. Entries are a device name alone (included, no bid adjustment) or { device, bidModifier }.
+             * Google only. The FULL new set of device bid modifiers for the campaign. Entries are a device name alone (targeted, bid modifier reset to 1) or { device, bidModifier }. A supported device you leave out is switched off, written as a bid modifier of 0. Google never removes a device criterion, so an excluded device reads back as bidModifier 0 rather than disappearing, and a set that switches every device off returns 422. Which devices a campaign carries depends on its channel: Search campaigns have MOBILE, DESKTOP and TABLET, Display campaigns also have CONNECTED_TV, and sending a device the campaign does not carry returns 422.
              */
             devices?: Array<('MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV' | {
     device: 'MOBILE' | 'DESKTOP' | 'TABLET' | 'CONNECTED_TV';
     /**
-     * Google device bid modifier, 0.1 to 10 (minus 90% to plus 900%). Omit a device to exclude it.
+     * Google device bid modifier. 0 switches the device off (minus 100%); otherwise 0.1 to 10 (minus 90% to plus 900%). Google rejects any value between 0 and 0.1.
      */
     bidModifier?: number;
 })>;
@@ -37407,11 +37407,11 @@ export type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Meta, TikTok, and LinkedIn: publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
+         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Google Search and Display, Meta, TikTok, and LinkedIn: publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. Google Search and Display follow the same rule, and because Google keeps an independent switch at campaign, ad group and ad level, a PAUSED create leaves the campaign it creates PAUSED at Google. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
-         * Meta only. Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
+         * Meta and Google. Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
          */
         campaignStatus?: 'ACTIVE' | 'PAUSED';
         /**
@@ -38415,7 +38415,7 @@ export type CreateStandaloneAdResponse = ({
         node?: 'campaign' | 'adSet' | 'creative' | 'ad' | 'performanceMaxCampaign';
         status?: 'validated' | 'skipped';
         /**
-         * Why the node could not be validated (only on skipped).
+         * Why the node could not be validated (on skipped), or what the dry run could not check and what the request would do as sent (on validated). A Performance Max validation with no location targeting reports here that the campaign would run worldwide.
          */
         reason?: string;
     }>;