@getlatedev/node 0.2.1442 → 0.2.1444

package/dist/index.d.mts

@@ -3305,6 +3305,15 @@ type AdFunnelCounts = {
      * Messaging threads where the person sent a first reply.
      */
     messagingFirstReplies?: number;
+    /**
+     * Booked appointments (Meta `Schedule` pixel event). Pair with `spend` for cost per booked meeting.
+     *
+     * **Meta** reports Schedule in its `conversions` insight field, never in `actions`. This takes the FIRST present of `offsite_conversion.fb_pixel_schedule`, `omni_schedule`, `app_custom_event.fb_mobile_schedule`, `onsite_conversion.schedule`, `schedule`, `schedule_total`, `schedule_mobile_app`, `schedule_website`, `schedule_offline`. With none of those, a single `offsite_schedule_add_<dataset>` key counts. Two such keys (two datasets) leave it at 0, since one booking can reach both.
+     *
+     * Added 2026-11-03. Days synced before then read 0 until re-fetched: each sync restates the last 30 days.
+     *
+     */
+    schedules?: number;
 };
 type AdKeyword = {
     /**
@@ -3547,6 +3556,9 @@ type AdMetrics = {
      * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Keys differ by platform, so branch on the ad's platform when interpreting them. Empty object when no actions are reported.
      *
      * - Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...), covering both engagement and conversion events.
+     * - Meta newer standard events (Schedule, SubmitApplication, Contact, StartTrial, Subscribe and the like) come only from Meta's `conversions` insight field, under keys such as schedule_total, schedule_website or offsite_schedule_add_<dataset>.
+     * - Since 2026-11-03 every `conversions` key that `actions` lacks is added here, rounded per key, and its `conversion_values` value to `actionValues`. A key both fields report keeps its `actions` value.
+     * - Days synced before 2026-11-03 lack those keys until re-fetched. Each sync restates the last 30 days.
      * - TikTok: conversion events plus the paid-engagement family (follow, post_reaction for paid likes, comment, share). Follow is how FOLLOWERS-goal campaigns report their result.
      * - TikTok website (pixel) events: complete_payment (website purchase, counted in `conversions` by SHOPPING-optimised campaigns), place_order, initiate_checkout, add_to_cart, view_content, lead (website form submissions plus TikTok instant-form leads).
      * - TikTok place_order is Place an Order, the website purchase of pixels set up with the legacy ON_WEB_ORDER event. It is absent from days synced before this metric was added until the ad is re-synced.
@@ -18747,7 +18759,6 @@ type current = 'active' | 'restricted' | 'disabled' | 'closed';
  *
  * - Meta `WITH_ISSUES` (payment, policy and account problems)
  * - TikTok account punishment or missing balance
- * - LinkedIn removals
  * - any platform status Zernio does not recognize yet (check `issue.raw`)
  *
  * Ads seen for the first time by a sync never fire it.
@@ -18809,14 +18820,18 @@ type event9 = 'ad.delivery_issue';
  */
 type level4 = 'AD';
 /**
- * Webhook payload for the `ad.review.approved` and `ad.review.rejected` events. Emitted for every ad network Zernio syncs (Meta, Google, TikTok, LinkedIn, Pinterest, X and the rest).
+ * Webhook payload for the `ad.review.approved` and `ad.review.rejected` events. Emitted for every ad network Zernio syncs (Meta, Google, TikTok, LinkedIn, Pinterest, X, Reddit and the rest).
  *
  * Fires when an ad Zernio already tracked changes review outcome:
  *
  * - `approved`: it leaves review as deliverable, or a rejection is overturned.
  * - `rejected`: the platform rejects it.
  *
- * Ads seen for the first time by a sync, including the history loaded when an account is connected, never fire it. An ad that leaves review paused (for example its ad set is paused) sends no `approved` event.
+ * Ads seen for the first time by a sync, including the history loaded when an account is connected, never fire it.
+ *
+ * On X, Pinterest and LinkedIn, Zernio reads the review apart from the delivery status. An ad that leaves review while paused (for example under a paused campaign) still sends `approved`.
+ *
+ * On the other networks the review shows only in the delivery status, so an ad that leaves review paused sends no `approved` event.
  *
  * Detected by Zernio's own ad sync (and, for Meta, the review poll), so it arrives within one sync cycle of the platform's decision, not instantly. Each outcome is delivered at most once per ad per 24 hours.
  *
@@ -18859,7 +18874,7 @@ type WebhookPayloadAdReview = {
          */
         raw: string;
         /**
-         * Why the platform rejected the ad, when it says. Always empty on `approved`. Most networks only return a generic message today.
+         * Why the platform rejected the ad, when it says. Always empty on `approved`. Pinterest, LinkedIn and Reddit send their own reasons, X sends none, and most other networks only return a generic message.
          */
         reasons: Array<{
             message: string;

package/dist/index.d.ts

@@ -3305,6 +3305,15 @@ type AdFunnelCounts = {
      * Messaging threads where the person sent a first reply.
      */
     messagingFirstReplies?: number;
+    /**
+     * Booked appointments (Meta `Schedule` pixel event). Pair with `spend` for cost per booked meeting.
+     *
+     * **Meta** reports Schedule in its `conversions` insight field, never in `actions`. This takes the FIRST present of `offsite_conversion.fb_pixel_schedule`, `omni_schedule`, `app_custom_event.fb_mobile_schedule`, `onsite_conversion.schedule`, `schedule`, `schedule_total`, `schedule_mobile_app`, `schedule_website`, `schedule_offline`. With none of those, a single `offsite_schedule_add_<dataset>` key counts. Two such keys (two datasets) leave it at 0, since one booking can reach both.
+     *
+     * Added 2026-11-03. Days synced before then read 0 until re-fetched: each sync restates the last 30 days.
+     *
+     */
+    schedules?: number;
 };
 type AdKeyword = {
     /**
@@ -3547,6 +3556,9 @@ type AdMetrics = {
      * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Keys differ by platform, so branch on the ad's platform when interpreting them. Empty object when no actions are reported.
      *
      * - Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...), covering both engagement and conversion events.
+     * - Meta newer standard events (Schedule, SubmitApplication, Contact, StartTrial, Subscribe and the like) come only from Meta's `conversions` insight field, under keys such as schedule_total, schedule_website or offsite_schedule_add_<dataset>.
+     * - Since 2026-11-03 every `conversions` key that `actions` lacks is added here, rounded per key, and its `conversion_values` value to `actionValues`. A key both fields report keeps its `actions` value.
+     * - Days synced before 2026-11-03 lack those keys until re-fetched. Each sync restates the last 30 days.
      * - TikTok: conversion events plus the paid-engagement family (follow, post_reaction for paid likes, comment, share). Follow is how FOLLOWERS-goal campaigns report their result.
      * - TikTok website (pixel) events: complete_payment (website purchase, counted in `conversions` by SHOPPING-optimised campaigns), place_order, initiate_checkout, add_to_cart, view_content, lead (website form submissions plus TikTok instant-form leads).
      * - TikTok place_order is Place an Order, the website purchase of pixels set up with the legacy ON_WEB_ORDER event. It is absent from days synced before this metric was added until the ad is re-synced.
@@ -18747,7 +18759,6 @@ type current = 'active' | 'restricted' | 'disabled' | 'closed';
  *
  * - Meta `WITH_ISSUES` (payment, policy and account problems)
  * - TikTok account punishment or missing balance
- * - LinkedIn removals
  * - any platform status Zernio does not recognize yet (check `issue.raw`)
  *
  * Ads seen for the first time by a sync never fire it.
@@ -18809,14 +18820,18 @@ type event9 = 'ad.delivery_issue';
  */
 type level4 = 'AD';
 /**
- * Webhook payload for the `ad.review.approved` and `ad.review.rejected` events. Emitted for every ad network Zernio syncs (Meta, Google, TikTok, LinkedIn, Pinterest, X and the rest).
+ * Webhook payload for the `ad.review.approved` and `ad.review.rejected` events. Emitted for every ad network Zernio syncs (Meta, Google, TikTok, LinkedIn, Pinterest, X, Reddit and the rest).
  *
  * Fires when an ad Zernio already tracked changes review outcome:
  *
  * - `approved`: it leaves review as deliverable, or a rejection is overturned.
  * - `rejected`: the platform rejects it.
  *
- * Ads seen for the first time by a sync, including the history loaded when an account is connected, never fire it. An ad that leaves review paused (for example its ad set is paused) sends no `approved` event.
+ * Ads seen for the first time by a sync, including the history loaded when an account is connected, never fire it.
+ *
+ * On X, Pinterest and LinkedIn, Zernio reads the review apart from the delivery status. An ad that leaves review while paused (for example under a paused campaign) still sends `approved`.
+ *
+ * On the other networks the review shows only in the delivery status, so an ad that leaves review paused sends no `approved` event.
  *
  * Detected by Zernio's own ad sync (and, for Meta, the review poll), so it arrives within one sync cycle of the platform's decision, not instantly. Each outcome is delivered at most once per ad per 24 hours.
  *
@@ -18859,7 +18874,7 @@ type WebhookPayloadAdReview = {
          */
         raw: string;
         /**
-         * Why the platform rejected the ad, when it says. Always empty on `approved`. Most networks only return a generic message today.
+         * Why the platform rejected the ad, when it says. Always empty on `approved`. Pinterest, LinkedIn and Reddit send their own reasons, X sends none, and most other networks only return a generic message.
          */
         reasons: Array<{
             message: string;

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -1065,6 +1065,15 @@ export type AdFunnelCounts = {
      * Messaging threads where the person sent a first reply.
      */
     messagingFirstReplies?: number;
+    /**
+     * Booked appointments (Meta `Schedule` pixel event). Pair with `spend` for cost per booked meeting.
+     *
+     * **Meta** reports Schedule in its `conversions` insight field, never in `actions`. This takes the FIRST present of `offsite_conversion.fb_pixel_schedule`, `omni_schedule`, `app_custom_event.fb_mobile_schedule`, `onsite_conversion.schedule`, `schedule`, `schedule_total`, `schedule_mobile_app`, `schedule_website`, `schedule_offline`. With none of those, a single `offsite_schedule_add_<dataset>` key counts. Two such keys (two datasets) leave it at 0, since one booking can reach both.
+     *
+     * Added 2026-11-03. Days synced before then read 0 until re-fetched: each sync restates the last 30 days.
+     *
+     */
+    schedules?: number;
 };
 
 export type AdKeyword = {
@@ -1319,6 +1328,9 @@ export type AdMetrics = {
      * Per-action-type counts summed over the date range, keyed by the platform's action-type names. Keys differ by platform, so branch on the ad's platform when interpreting them. Empty object when no actions are reported.
      *
      * - Meta: raw Insights action_type keys (link_click, offsite_conversion.fb_pixel_purchase, onsite_conversion.lead_grouped, ...), covering both engagement and conversion events.
+     * - Meta newer standard events (Schedule, SubmitApplication, Contact, StartTrial, Subscribe and the like) come only from Meta's `conversions` insight field, under keys such as schedule_total, schedule_website or offsite_schedule_add_<dataset>.
+     * - Since 2026-11-03 every `conversions` key that `actions` lacks is added here, rounded per key, and its `conversion_values` value to `actionValues`. A key both fields report keeps its `actions` value.
+     * - Days synced before 2026-11-03 lack those keys until re-fetched. Each sync restates the last 30 days.
      * - TikTok: conversion events plus the paid-engagement family (follow, post_reaction for paid likes, comment, share). Follow is how FOLLOWERS-goal campaigns report their result.
      * - TikTok website (pixel) events: complete_payment (website purchase, counted in `conversions` by SHOPPING-optimised campaigns), place_order, initiate_checkout, add_to_cart, view_content, lead (website form submissions plus TikTok instant-form leads).
      * - TikTok place_order is Place an Order, the website purchase of pixels set up with the legacy ON_WEB_ORDER event. It is absent from days synced before this metric was added until the ad is re-synced.
@@ -17224,7 +17236,6 @@ export type current = 'active' | 'restricted' | 'disabled' | 'closed';
  *
  * - Meta `WITH_ISSUES` (payment, policy and account problems)
  * - TikTok account punishment or missing balance
- * - LinkedIn removals
  * - any platform status Zernio does not recognize yet (check `issue.raw`)
  *
  * Ads seen for the first time by a sync never fire it.
@@ -17289,14 +17300,18 @@ export type event9 = 'ad.delivery_issue';
 export type level4 = 'AD';
 
 /**
- * Webhook payload for the `ad.review.approved` and `ad.review.rejected` events. Emitted for every ad network Zernio syncs (Meta, Google, TikTok, LinkedIn, Pinterest, X and the rest).
+ * Webhook payload for the `ad.review.approved` and `ad.review.rejected` events. Emitted for every ad network Zernio syncs (Meta, Google, TikTok, LinkedIn, Pinterest, X, Reddit and the rest).
  *
  * Fires when an ad Zernio already tracked changes review outcome:
  *
  * - `approved`: it leaves review as deliverable, or a rejection is overturned.
  * - `rejected`: the platform rejects it.
  *
- * Ads seen for the first time by a sync, including the history loaded when an account is connected, never fire it. An ad that leaves review paused (for example its ad set is paused) sends no `approved` event.
+ * Ads seen for the first time by a sync, including the history loaded when an account is connected, never fire it.
+ *
+ * On X, Pinterest and LinkedIn, Zernio reads the review apart from the delivery status. An ad that leaves review while paused (for example under a paused campaign) still sends `approved`.
+ *
+ * On the other networks the review shows only in the delivery status, so an ad that leaves review paused sends no `approved` event.
  *
  * Detected by Zernio's own ad sync (and, for Meta, the review poll), so it arrives within one sync cycle of the platform's decision, not instantly. Each outcome is delivered at most once per ad per 24 hours.
  *
@@ -17339,7 +17354,7 @@ export type WebhookPayloadAdReview = {
          */
         raw: string;
         /**
-         * Why the platform rejected the ad, when it says. Always empty on `approved`. Most networks only return a generic message today.
+         * Why the platform rejected the ad, when it says. Always empty on `approved`. Pinterest, LinkedIn and Reddit send their own reasons, X sends none, and most other networks only return a generic message.
          */
         reasons: Array<{
             message: string;