@getlatedev/node 0.2.1322 → 0.2.1324

package/dist/index.d.mts

@@ -7797,7 +7797,7 @@ type CtwaMultiResponse = {
     platformAdSetId: string;
     message: string;
     /**
-     * Present when Meta created the ad set differently from the request: Meta kept the ad set without the requested `whatsappPhoneNumber` in its promoted_object (the ads still carry it on their WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
+     * Present when Meta created the ad set differently from the request: a multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change (a WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
      */
     warnings?: Array<(string)>;
 };
@@ -7818,7 +7818,7 @@ type CtwaSingleResponse = {
     };
     message: string;
     /**
-     * Present when Meta created the ad set differently from the request: Meta kept the ad set without the requested `whatsappPhoneNumber` in its promoted_object (the ads still carry it on their WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
+     * Present when Meta created the ad set differently from the request: a multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change (a WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
      */
     warnings?: Array<(string)>;
 };
@@ -44748,7 +44748,7 @@ type UpdateAdSetData = {
             lifetimeMinSpendTarget?: number;
             customerLifecycle?: MetaCustomerLifecycle;
             /**
-             * Meta ad-set promoted_object, forwarded verbatim (same shape as /v1/ads/create). Unknown keys are rejected with 400.
+             * Meta ad-set promoted_object (same shape as /v1/ads/create). Meta makes promoted_object immutable once the ad set exists, so only `pixelId`, `customEventType`, `customEventStr` (with `customEventType` OTHER), `applicationId` and `productCatalogId` can be sent here. Any other key (`pageId`, `whatsappPhoneNumber`, `customConversionId`, `objectStoreUrl`, `productSetId`, `offlineConversionDataSetId`) is a 400 with `param: platformSpecificData.promotedObject` and nothing is written; changing them needs a new ad set (POST /v1/ads/create). Unknown keys are rejected with 400.
              */
             promotedObject?: {
                 pixelId?: string;
@@ -50084,10 +50084,25 @@ type BoostPostData = {
          * "engagement"` to objective `OUTCOME_AWARENESS`, which accepts
          * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values, and
          * rejects `POST_ENGAGEMENT` (that value is only valid under
-         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name).
+         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name, and
+         * which `metaObjective` selects on a boost).
          *
          */
         optimizationGoal?: string;
+        /**
+         * Meta only, with `goal: engagement` and without `adSetId` (400 otherwise).
+         * `OUTCOME_ENGAGEMENT` creates the campaign with objective `OUTCOME_ENGAGEMENT`
+         * and the ad set with `optimization_goal` `POST_ENGAGEMENT` (unless
+         * `optimizationGoal` is set) and `destination_type` `ON_POST` (unless
+         * `destinationType` is set), the shape Ads Manager uses to boost an existing
+         * post. When omitted, an engagement boost keeps `OUTCOME_AWARENESS` with
+         * `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
+         * is not `OUTCOME_ENGAGEMENT` (`CALL_NOW`); messaging CTAs keep their own
+         * `CONVERSATIONS` ad set. Verified against Meta on Facebook posts; Instagram posts
+         * are accepted but not yet verified.
+         *
+         */
+        metaObjective?: 'OUTCOME_ENGAGEMENT';
     };
     headers?: {
         /**

package/dist/index.d.ts

@@ -7797,7 +7797,7 @@ type CtwaMultiResponse = {
     platformAdSetId: string;
     message: string;
     /**
-     * Present when Meta created the ad set differently from the request: Meta kept the ad set without the requested `whatsappPhoneNumber` in its promoted_object (the ads still carry it on their WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
+     * Present when Meta created the ad set differently from the request: a multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change (a WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
      */
     warnings?: Array<(string)>;
 };
@@ -7818,7 +7818,7 @@ type CtwaSingleResponse = {
     };
     message: string;
     /**
-     * Present when Meta created the ad set differently from the request: Meta kept the ad set without the requested `whatsappPhoneNumber` in its promoted_object (the ads still carry it on their WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
+     * Present when Meta created the ad set differently from the request: a multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change (a WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
      */
     warnings?: Array<(string)>;
 };
@@ -44748,7 +44748,7 @@ type UpdateAdSetData = {
             lifetimeMinSpendTarget?: number;
             customerLifecycle?: MetaCustomerLifecycle;
             /**
-             * Meta ad-set promoted_object, forwarded verbatim (same shape as /v1/ads/create). Unknown keys are rejected with 400.
+             * Meta ad-set promoted_object (same shape as /v1/ads/create). Meta makes promoted_object immutable once the ad set exists, so only `pixelId`, `customEventType`, `customEventStr` (with `customEventType` OTHER), `applicationId` and `productCatalogId` can be sent here. Any other key (`pageId`, `whatsappPhoneNumber`, `customConversionId`, `objectStoreUrl`, `productSetId`, `offlineConversionDataSetId`) is a 400 with `param: platformSpecificData.promotedObject` and nothing is written; changing them needs a new ad set (POST /v1/ads/create). Unknown keys are rejected with 400.
              */
             promotedObject?: {
                 pixelId?: string;
@@ -50084,10 +50084,25 @@ type BoostPostData = {
          * "engagement"` to objective `OUTCOME_AWARENESS`, which accepts
          * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values, and
          * rejects `POST_ENGAGEMENT` (that value is only valid under
-         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name).
+         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name, and
+         * which `metaObjective` selects on a boost).
          *
          */
         optimizationGoal?: string;
+        /**
+         * Meta only, with `goal: engagement` and without `adSetId` (400 otherwise).
+         * `OUTCOME_ENGAGEMENT` creates the campaign with objective `OUTCOME_ENGAGEMENT`
+         * and the ad set with `optimization_goal` `POST_ENGAGEMENT` (unless
+         * `optimizationGoal` is set) and `destination_type` `ON_POST` (unless
+         * `destinationType` is set), the shape Ads Manager uses to boost an existing
+         * post. When omitted, an engagement boost keeps `OUTCOME_AWARENESS` with
+         * `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
+         * is not `OUTCOME_ENGAGEMENT` (`CALL_NOW`); messaging CTAs keep their own
+         * `CONVERSATIONS` ad set. Verified against Meta on Facebook posts; Instagram posts
+         * are accepted but not yet verified.
+         *
+         */
+        metaObjective?: 'OUTCOME_ENGAGEMENT';
     };
     headers?: {
         /**

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1322",
+  version: "0.2.1324",
   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: "@getlatedev/node",
-  version: "0.2.1322",
+  version: "0.2.1324",
   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": "@getlatedev/node",
-  "version": "0.2.1322",
+  "version": "0.2.1324",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -5943,7 +5943,7 @@ export type CtwaMultiResponse = {
     platformAdSetId: string;
     message: string;
     /**
-     * Present when Meta created the ad set differently from the request: Meta kept the ad set without the requested `whatsappPhoneNumber` in its promoted_object (the ads still carry it on their WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
+     * Present when Meta created the ad set differently from the request: a multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change (a WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
      */
     warnings?: Array<(string)>;
 };
@@ -5966,7 +5966,7 @@ export type CtwaSingleResponse = {
     };
     message: string;
     /**
-     * Present when Meta created the ad set differently from the request: Meta kept the ad set without the requested `whatsappPhoneNumber` in its promoted_object (the ads still carry it on their WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
+     * Present when Meta created the ad set differently from the request: a multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change (a WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button), or the ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy` or a `roasAverageFloor` that strategy cannot take was not applied.
      */
     warnings?: Array<(string)>;
 };
@@ -45318,7 +45318,7 @@ export type UpdateAdSetData = {
             lifetimeMinSpendTarget?: number;
             customerLifecycle?: MetaCustomerLifecycle;
             /**
-             * Meta ad-set promoted_object, forwarded verbatim (same shape as /v1/ads/create). Unknown keys are rejected with 400.
+             * Meta ad-set promoted_object (same shape as /v1/ads/create). Meta makes promoted_object immutable once the ad set exists, so only `pixelId`, `customEventType`, `customEventStr` (with `customEventType` OTHER), `applicationId` and `productCatalogId` can be sent here. Any other key (`pageId`, `whatsappPhoneNumber`, `customConversionId`, `objectStoreUrl`, `productSetId`, `offlineConversionDataSetId`) is a 400 with `param: platformSpecificData.promotedObject` and nothing is written; changing them needs a new ad set (POST /v1/ads/create). Unknown keys are rejected with 400.
              */
             promotedObject?: {
                 pixelId?: string;
@@ -50990,10 +50990,25 @@ export type BoostPostData = {
          * "engagement"` to objective `OUTCOME_AWARENESS`, which accepts
          * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values, and
          * rejects `POST_ENGAGEMENT` (that value is only valid under
-         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name).
+         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name, and
+         * which `metaObjective` selects on a boost).
          *
          */
         optimizationGoal?: string;
+        /**
+         * Meta only, with `goal: engagement` and without `adSetId` (400 otherwise).
+         * `OUTCOME_ENGAGEMENT` creates the campaign with objective `OUTCOME_ENGAGEMENT`
+         * and the ad set with `optimization_goal` `POST_ENGAGEMENT` (unless
+         * `optimizationGoal` is set) and `destination_type` `ON_POST` (unless
+         * `destinationType` is set), the shape Ads Manager uses to boost an existing
+         * post. When omitted, an engagement boost keeps `OUTCOME_AWARENESS` with
+         * `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
+         * is not `OUTCOME_ENGAGEMENT` (`CALL_NOW`); messaging CTAs keep their own
+         * `CONVERSATIONS` ad set. Verified against Meta on Facebook posts; Instagram posts
+         * are accepted but not yet verified.
+         *
+         */
+        metaObjective?: 'OUTCOME_ENGAGEMENT';
     };
     headers?: {
         /**