@zernio/node 0.2.553 → 0.2.555

package/dist/index.d.mts

@@ -1790,20 +1790,24 @@ type AdDailyMetrics = AdMetrics & {
  * Use these fields when you need a specific interaction, and `engagement`
  * only as the coarse total it has always been.
  *
- * Meta-only; other platforms leave these at 0.
+ * Populated for Meta and, since 2026-08, TikTok (`reactions` = paid
+ * likes, `comments`, `shares`; TikTok's `follow` count lives in
+ * `actions.follow`, not here). Other platforms leave these at 0.
+ * TikTok history note: paused TikTok ads are not re-synced, so
+ * campaigns that ended before the rollout keep 0s here.
  *
  */
 type AdEngagementCounts = {
     /**
-     * Meta's own post-engagement total (`post_engagement`).
+     * Meta's own post-engagement total (`post_engagement`). Meta-only.
      */
     postEngagement?: number;
     /**
-     * Meta's own page-engagement total (`page_engagement`).
+     * Meta's own page-engagement total (`page_engagement`). Meta-only.
      */
     pageEngagement?: number;
     /**
-     * Reactions on the ad's post (`post_reaction`).
+     * Reactions on the ad's post (`post_reaction`). For TikTok these are its paid likes.
      */
     reactions?: number;
     /**
@@ -1811,7 +1815,7 @@ type AdEngagementCounts = {
      */
     comments?: number;
     /**
-     * Shares of the ad's post. Meta reports these under the action type literally named `post`.
+     * Shares of the ad's post. Meta reports these under the action type literally named `post`; TikTok under `share`.
      */
     shares?: number;
     /**
@@ -1933,7 +1937,7 @@ type AdMetrics = {
      */
     costPerConversion?: number;
     /**
-     * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...) — both engagement and conversion events. X: conversion types (purchase, sign_up, site_visit, download, custom). LinkedIn: conversion types (post_click, post_view, lead_gen). Google returns {} (its per-action names aren't synced per ad). Empty object when no actions are reported. NOTE: keys differ by platform, so branch on the ad's platform when interpreting them.
+     * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...) — both engagement and conversion events. TikTok: pixel conversions (purchase, add_to_cart, initiate_checkout, view_content, complete_payment, lead) plus the paid-engagement family (follow, post_reaction for paid likes, comment, share) — follow is how FOLLOWERS-goal campaigns report their result. X: conversion types (purchase, sign_up, site_visit, download, custom). LinkedIn: conversion types (post_click, post_view, lead_gen). Google returns {} (its per-action names aren't synced per ad). Empty object when no actions are reported. NOTE: keys differ by platform, so branch on the ad's platform when interpreting them.
      */
     actions?: {
         [key: string]: (number);
@@ -30102,6 +30106,22 @@ type CreateStandaloneAdData = {
          *
          */
         identityType?: 'TT_USER' | 'CUSTOMIZED_USER';
+        /**
+         * TikTok only. Creates the ad as a TikTok Upgraded Smart+
+         * campaign: TikTok automates targeting, bidding and delivery. Supports goals
+         * `conversions` (Smart+ Web Conversions), `lead_generation` (Smart+ Lead
+         * Generation with a website form on `linkUrl`; TikTok Instant Forms not supported)
+         * and `app_promotion` (Smart+ App installs; the ad's destination is the app store,
+         * so `linkUrl` is not used). The web goals require `promotedObject.pixelId` AND
+         * `promotedObject.customEventType`; `app_promotion` requires
+         * `promotedObject.applicationId` instead.
+         * Targeting works like on any TikTok ad (defaults to `countries: ["US"]` when
+         * omitted); TikTok automates delivery within it.
+         * The budget lives on the Smart+ campaign (Campaign Budget Optimization); a `lifetime`
+         * budget additionally requires `endDate`. Cannot be combined with `adSetId`.
+         *
+         */
+        smartPlus?: boolean;
         /**
          * What the ad optimises against. Behaviour depends on the platform.
          *
@@ -30115,12 +30135,15 @@ type CreateStandaloneAdData = {
          *
          * Other Meta goals (engagement, traffic, awareness, video_views) ignore this field.
          *
-         * **TikTok**: only `goal: conversions` uses it.
+         * **TikTok**: used by `goal: conversions` and the Smart+ goals (`smartPlus: true`).
          * - `pixelId` maps to the ad group's `pixel_id`. Required: a TikTok website-conversion
          * ad group without a pixel is rejected with `40002: Please select a pixel`.
          * - `customEventType` maps to the ad group's `optimization_event` (the pixel event to
-         * optimise for). Optional: TikTok accepts a pixel-only auto-bid conversion ad group.
+         * optimise for). Optional on the regular conversions flow, required on Smart+.
          * See the `customEventType` field below for the valid TikTok codes.
+         * - `applicationId` (Smart+ `goal: app_promotion` only) maps to the ad group's `app_id`:
+         * the App ID of an app registered on the TikTok Ads account (Assets → Events →
+         * App Events). Install optimization needs the app's MMP tracking configured.
          *
          * The remaining `promotedObject.*` fields are Meta-only. Platforms other than
          * Meta and TikTok ignore `promotedObject` entirely.

package/dist/index.d.ts

@@ -1790,20 +1790,24 @@ type AdDailyMetrics = AdMetrics & {
  * Use these fields when you need a specific interaction, and `engagement`
  * only as the coarse total it has always been.
  *
- * Meta-only; other platforms leave these at 0.
+ * Populated for Meta and, since 2026-08, TikTok (`reactions` = paid
+ * likes, `comments`, `shares`; TikTok's `follow` count lives in
+ * `actions.follow`, not here). Other platforms leave these at 0.
+ * TikTok history note: paused TikTok ads are not re-synced, so
+ * campaigns that ended before the rollout keep 0s here.
  *
  */
 type AdEngagementCounts = {
     /**
-     * Meta's own post-engagement total (`post_engagement`).
+     * Meta's own post-engagement total (`post_engagement`). Meta-only.
      */
     postEngagement?: number;
     /**
-     * Meta's own page-engagement total (`page_engagement`).
+     * Meta's own page-engagement total (`page_engagement`). Meta-only.
      */
     pageEngagement?: number;
     /**
-     * Reactions on the ad's post (`post_reaction`).
+     * Reactions on the ad's post (`post_reaction`). For TikTok these are its paid likes.
      */
     reactions?: number;
     /**
@@ -1811,7 +1815,7 @@ type AdEngagementCounts = {
      */
     comments?: number;
     /**
-     * Shares of the ad's post. Meta reports these under the action type literally named `post`.
+     * Shares of the ad's post. Meta reports these under the action type literally named `post`; TikTok under `share`.
      */
     shares?: number;
     /**
@@ -1933,7 +1937,7 @@ type AdMetrics = {
      */
     costPerConversion?: number;
     /**
-     * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...) — both engagement and conversion events. X: conversion types (purchase, sign_up, site_visit, download, custom). LinkedIn: conversion types (post_click, post_view, lead_gen). Google returns {} (its per-action names aren't synced per ad). Empty object when no actions are reported. NOTE: keys differ by platform, so branch on the ad's platform when interpreting them.
+     * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...) — both engagement and conversion events. TikTok: pixel conversions (purchase, add_to_cart, initiate_checkout, view_content, complete_payment, lead) plus the paid-engagement family (follow, post_reaction for paid likes, comment, share) — follow is how FOLLOWERS-goal campaigns report their result. X: conversion types (purchase, sign_up, site_visit, download, custom). LinkedIn: conversion types (post_click, post_view, lead_gen). Google returns {} (its per-action names aren't synced per ad). Empty object when no actions are reported. NOTE: keys differ by platform, so branch on the ad's platform when interpreting them.
      */
     actions?: {
         [key: string]: (number);
@@ -30102,6 +30106,22 @@ type CreateStandaloneAdData = {
          *
          */
         identityType?: 'TT_USER' | 'CUSTOMIZED_USER';
+        /**
+         * TikTok only. Creates the ad as a TikTok Upgraded Smart+
+         * campaign: TikTok automates targeting, bidding and delivery. Supports goals
+         * `conversions` (Smart+ Web Conversions), `lead_generation` (Smart+ Lead
+         * Generation with a website form on `linkUrl`; TikTok Instant Forms not supported)
+         * and `app_promotion` (Smart+ App installs; the ad's destination is the app store,
+         * so `linkUrl` is not used). The web goals require `promotedObject.pixelId` AND
+         * `promotedObject.customEventType`; `app_promotion` requires
+         * `promotedObject.applicationId` instead.
+         * Targeting works like on any TikTok ad (defaults to `countries: ["US"]` when
+         * omitted); TikTok automates delivery within it.
+         * The budget lives on the Smart+ campaign (Campaign Budget Optimization); a `lifetime`
+         * budget additionally requires `endDate`. Cannot be combined with `adSetId`.
+         *
+         */
+        smartPlus?: boolean;
         /**
          * What the ad optimises against. Behaviour depends on the platform.
          *
@@ -30115,12 +30135,15 @@ type CreateStandaloneAdData = {
          *
          * Other Meta goals (engagement, traffic, awareness, video_views) ignore this field.
          *
-         * **TikTok**: only `goal: conversions` uses it.
+         * **TikTok**: used by `goal: conversions` and the Smart+ goals (`smartPlus: true`).
          * - `pixelId` maps to the ad group's `pixel_id`. Required: a TikTok website-conversion
          * ad group without a pixel is rejected with `40002: Please select a pixel`.
          * - `customEventType` maps to the ad group's `optimization_event` (the pixel event to
-         * optimise for). Optional: TikTok accepts a pixel-only auto-bid conversion ad group.
+         * optimise for). Optional on the regular conversions flow, required on Smart+.
          * See the `customEventType` field below for the valid TikTok codes.
+         * - `applicationId` (Smart+ `goal: app_promotion` only) maps to the ad group's `app_id`:
+         * the App ID of an app registered on the TikTok Ads account (Assets → Events →
+         * App Events). Install optimization needs the app's MMP tracking configured.
          *
          * The remaining `promotedObject.*` fields are Meta-only. Platforms other than
          * Meta and TikTok ignore `promotedObject` entirely.

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -538,20 +538,24 @@ export type AdDailyMetrics = AdMetrics & {
  * Use these fields when you need a specific interaction, and `engagement`
  * only as the coarse total it has always been.
  *
- * Meta-only; other platforms leave these at 0.
+ * Populated for Meta and, since 2026-08, TikTok (`reactions` = paid
+ * likes, `comments`, `shares`; TikTok's `follow` count lives in
+ * `actions.follow`, not here). Other platforms leave these at 0.
+ * TikTok history note: paused TikTok ads are not re-synced, so
+ * campaigns that ended before the rollout keep 0s here.
  *
  */
 export type AdEngagementCounts = {
     /**
-     * Meta's own post-engagement total (`post_engagement`).
+     * Meta's own post-engagement total (`post_engagement`). Meta-only.
      */
     postEngagement?: number;
     /**
-     * Meta's own page-engagement total (`page_engagement`).
+     * Meta's own page-engagement total (`page_engagement`). Meta-only.
      */
     pageEngagement?: number;
     /**
-     * Reactions on the ad's post (`post_reaction`).
+     * Reactions on the ad's post (`post_reaction`). For TikTok these are its paid likes.
      */
     reactions?: number;
     /**
@@ -559,7 +563,7 @@ export type AdEngagementCounts = {
      */
     comments?: number;
     /**
-     * Shares of the ad's post. Meta reports these under the action type literally named `post`.
+     * Shares of the ad's post. Meta reports these under the action type literally named `post`; TikTok under `share`.
      */
     shares?: number;
     /**
@@ -683,7 +687,7 @@ export type AdMetrics = {
      */
     costPerConversion?: number;
     /**
-     * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...) — both engagement and conversion events. X: conversion types (purchase, sign_up, site_visit, download, custom). LinkedIn: conversion types (post_click, post_view, lead_gen). Google returns {} (its per-action names aren't synced per ad). Empty object when no actions are reported. NOTE: keys differ by platform, so branch on the ad's platform when interpreting them.
+     * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...) — both engagement and conversion events. TikTok: pixel conversions (purchase, add_to_cart, initiate_checkout, view_content, complete_payment, lead) plus the paid-engagement family (follow, post_reaction for paid likes, comment, share) — follow is how FOLLOWERS-goal campaigns report their result. X: conversion types (purchase, sign_up, site_visit, download, custom). LinkedIn: conversion types (post_click, post_view, lead_gen). Google returns {} (its per-action names aren't synced per ad). Empty object when no actions are reported. NOTE: keys differ by platform, so branch on the ad's platform when interpreting them.
      */
     actions?: {
         [key: string]: (number);
@@ -30638,6 +30642,22 @@ export type CreateStandaloneAdData = {
          *
          */
         identityType?: 'TT_USER' | 'CUSTOMIZED_USER';
+        /**
+         * TikTok only. Creates the ad as a TikTok Upgraded Smart+
+         * campaign: TikTok automates targeting, bidding and delivery. Supports goals
+         * `conversions` (Smart+ Web Conversions), `lead_generation` (Smart+ Lead
+         * Generation with a website form on `linkUrl`; TikTok Instant Forms not supported)
+         * and `app_promotion` (Smart+ App installs; the ad's destination is the app store,
+         * so `linkUrl` is not used). The web goals require `promotedObject.pixelId` AND
+         * `promotedObject.customEventType`; `app_promotion` requires
+         * `promotedObject.applicationId` instead.
+         * Targeting works like on any TikTok ad (defaults to `countries: ["US"]` when
+         * omitted); TikTok automates delivery within it.
+         * The budget lives on the Smart+ campaign (Campaign Budget Optimization); a `lifetime`
+         * budget additionally requires `endDate`. Cannot be combined with `adSetId`.
+         *
+         */
+        smartPlus?: boolean;
         /**
          * What the ad optimises against. Behaviour depends on the platform.
          *
@@ -30651,12 +30671,15 @@ export type CreateStandaloneAdData = {
          *
          * Other Meta goals (engagement, traffic, awareness, video_views) ignore this field.
          *
-         * **TikTok**: only `goal: conversions` uses it.
+         * **TikTok**: used by `goal: conversions` and the Smart+ goals (`smartPlus: true`).
          * - `pixelId` maps to the ad group's `pixel_id`. Required: a TikTok website-conversion
          * ad group without a pixel is rejected with `40002: Please select a pixel`.
          * - `customEventType` maps to the ad group's `optimization_event` (the pixel event to
-         * optimise for). Optional: TikTok accepts a pixel-only auto-bid conversion ad group.
+         * optimise for). Optional on the regular conversions flow, required on Smart+.
          * See the `customEventType` field below for the valid TikTok codes.
+         * - `applicationId` (Smart+ `goal: app_promotion` only) maps to the ad group's `app_id`:
+         * the App ID of an app registered on the TikTok Ads account (Assets → Events →
+         * App Events). Install optimization needs the app's MMP tracking configured.
          *
          * The remaining `promotedObject.*` fields are Meta-only. Platforms other than
          * Meta and TikTok ignore `promotedObject` entirely.