@zernio/node 0.2.864 → 0.2.865

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.mts CHANGED
@@ -43040,9 +43040,13 @@ type SendWhatsAppConversionError = (unknown | {
43040
43040
  type CreateMessagingAdData = {
43041
43041
  body: (CtwaAdRequestBody & {
43042
43042
  /**
43043
- * Where the conversation opens when the ad is tapped.
43043
+ * Where the conversation opens when the ad is tapped. Set this OR `destinations`, not both.
43044
43044
  */
43045
- destination: 'whatsapp' | 'messenger' | 'instagram_direct';
43045
+ destination?: 'whatsapp' | 'messenger' | 'instagram_direct';
43046
+ /**
43047
+ * Two or three messaging apps on ONE ad set, like Ads Manager's "all messaging apps": the ad set gets Meta's combined destination_type (e.g. MESSAGING_INSTAGRAM_DIRECT_MESSENGER_WHATSAPP) and the creative one CTA per app, so Meta opens the app each viewer is likeliest to answer from. WhatsApp in the list still needs the Page paired with a WhatsApp Business number. With `adSetId`, the existing ad set must already use that combined destination_type. Set this OR `destination`, not both.
43048
+ */
43049
+ destinations?: Array<('whatsapp' | 'messenger' | 'instagram_direct')>;
43046
43050
  });
43047
43051
  };
43048
43052
  type CreateMessagingAdResponse = ((CtwaSingleResponse | CtwaMultiResponse));
package/dist/index.d.ts CHANGED
@@ -43040,9 +43040,13 @@ type SendWhatsAppConversionError = (unknown | {
43040
43040
  type CreateMessagingAdData = {
43041
43041
  body: (CtwaAdRequestBody & {
43042
43042
  /**
43043
- * Where the conversation opens when the ad is tapped.
43043
+ * Where the conversation opens when the ad is tapped. Set this OR `destinations`, not both.
43044
43044
  */
43045
- destination: 'whatsapp' | 'messenger' | 'instagram_direct';
43045
+ destination?: 'whatsapp' | 'messenger' | 'instagram_direct';
43046
+ /**
43047
+ * Two or three messaging apps on ONE ad set, like Ads Manager's "all messaging apps": the ad set gets Meta's combined destination_type (e.g. MESSAGING_INSTAGRAM_DIRECT_MESSENGER_WHATSAPP) and the creative one CTA per app, so Meta opens the app each viewer is likeliest to answer from. WhatsApp in the list still needs the Page paired with a WhatsApp Business number. With `adSetId`, the existing ad set must already use that combined destination_type. Set this OR `destination`, not both.
43048
+ */
43049
+ destinations?: Array<('whatsapp' | 'messenger' | 'instagram_direct')>;
43046
43050
  });
43047
43051
  };
43048
43052
  type CreateMessagingAdResponse = ((CtwaSingleResponse | CtwaMultiResponse));
package/dist/index.js CHANGED
@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
36
36
  // package.json
37
37
  var package_default = {
38
38
  name: "@zernio/node",
39
- version: "0.2.864",
39
+ version: "0.2.865",
40
40
  description: "The official Node.js library for the Zernio API",
41
41
  main: "dist/index.js",
42
42
  module: "dist/index.mjs",
package/dist/index.mjs CHANGED
@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
5
5
  // package.json
6
6
  var package_default = {
7
7
  name: "@zernio/node",
8
- version: "0.2.864",
8
+ version: "0.2.865",
9
9
  description: "The official Node.js library for the Zernio API",
10
10
  main: "dist/index.js",
11
11
  module: "dist/index.mjs",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zernio/node",
3
- "version": "0.2.864",
3
+ "version": "0.2.865",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -11743,6 +11743,7 @@ export const sendWhatsAppConversion = <ThrowOnError extends boolean = false>(opt
11743
11743
  * Create messaging ad
11744
11744
  * Creates a click-to-message ad; `destination` selects where the tapped ad opens a
11745
11745
  * conversation: WhatsApp, the Page's Messenger inbox or the linked Instagram account's Direct inbox.
11746
+ * `destinations` puts two or three of them on one ad set and lets Meta pick the app per viewer.
11746
11747
  * The ad set is created with the matching destination_type and
11747
11748
  * CONVERSATIONS optimization; the campaign objective defaults to OUTCOME_ENGAGEMENT.
11748
11749
  * Supports single-creative and multi-creative shapes. Supersedes POST /v1/ads/ctwa
@@ -43874,9 +43874,13 @@ export type SendWhatsAppConversionError = (unknown | {
43874
43874
  export type CreateMessagingAdData = {
43875
43875
  body: (CtwaAdRequestBody & {
43876
43876
  /**
43877
- * Where the conversation opens when the ad is tapped.
43877
+ * Where the conversation opens when the ad is tapped. Set this OR `destinations`, not both.
43878
43878
  */
43879
- destination: 'whatsapp' | 'messenger' | 'instagram_direct';
43879
+ destination?: 'whatsapp' | 'messenger' | 'instagram_direct';
43880
+ /**
43881
+ * Two or three messaging apps on ONE ad set, like Ads Manager's "all messaging apps": the ad set gets Meta's combined destination_type (e.g. MESSAGING_INSTAGRAM_DIRECT_MESSENGER_WHATSAPP) and the creative one CTA per app, so Meta opens the app each viewer is likeliest to answer from. WhatsApp in the list still needs the Page paired with a WhatsApp Business number. With `adSetId`, the existing ad set must already use that combined destination_type. Set this OR `destination`, not both.
43882
+ */
43883
+ destinations?: Array<('whatsapp' | 'messenger' | 'instagram_direct')>;
43880
43884
  });
43881
43885
  };
43882
43886