@zernio/node 0.2.78 → 0.2.79

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
@@ -928,6 +928,20 @@ type AdMetrics = {
928
928
  actions?: {
929
929
  [key: string]: (number);
930
930
  };
931
+ /**
932
+ * Monetary mirror of `actions`, from Meta's Insights `action_values[]` array. Same keying — values are the revenue attributed to each action_type, in ad-account native currency (same unit as `spend`; see the campaign node's `currency` field). Use this to compute revenue-per-event (e.g. avg purchase value). Meta-only; other platforms return {}.
933
+ */
934
+ actionValues?: {
935
+ [key: string]: (number);
936
+ };
937
+ /**
938
+ * Convenience sum of purchase-type action values — picked from `actionValues` via the same priority list as `conversions` so both fields describe the same events. In ad-account native currency. 0 when the campaign has no purchase event configured. Meta-only.
939
+ */
940
+ purchaseValue?: number;
941
+ /**
942
+ * Return on ad spend — derived as `purchaseValue / spend`. 0 when `spend` is 0. Equivalent to Meta's `purchase_roas` under default attribution. At ad-set and campaign levels this is recomputed from summed purchaseValue + spend (NOT averaged across children) so it's mathematically correct at every rollup level.
943
+ */
944
+ roas?: number;
931
945
  /**
932
946
  * Present on individual ads only, not on campaign aggregations
933
947
  */
package/dist/index.d.ts CHANGED
@@ -928,6 +928,20 @@ type AdMetrics = {
928
928
  actions?: {
929
929
  [key: string]: (number);
930
930
  };
931
+ /**
932
+ * Monetary mirror of `actions`, from Meta's Insights `action_values[]` array. Same keying — values are the revenue attributed to each action_type, in ad-account native currency (same unit as `spend`; see the campaign node's `currency` field). Use this to compute revenue-per-event (e.g. avg purchase value). Meta-only; other platforms return {}.
933
+ */
934
+ actionValues?: {
935
+ [key: string]: (number);
936
+ };
937
+ /**
938
+ * Convenience sum of purchase-type action values — picked from `actionValues` via the same priority list as `conversions` so both fields describe the same events. In ad-account native currency. 0 when the campaign has no purchase event configured. Meta-only.
939
+ */
940
+ purchaseValue?: number;
941
+ /**
942
+ * Return on ad spend — derived as `purchaseValue / spend`. 0 when `spend` is 0. Equivalent to Meta's `purchase_roas` under default attribution. At ad-set and campaign levels this is recomputed from summed purchaseValue + spend (NOT averaged across children) so it's mathematically correct at every rollup level.
943
+ */
944
+ roas?: number;
931
945
  /**
932
946
  * Present on individual ads only, not on campaign aggregations
933
947
  */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zernio/node",
3
- "version": "0.2.78",
3
+ "version": "0.2.79",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -343,6 +343,20 @@ export type AdMetrics = {
343
343
  actions?: {
344
344
  [key: string]: (number);
345
345
  };
346
+ /**
347
+ * Monetary mirror of `actions`, from Meta's Insights `action_values[]` array. Same keying — values are the revenue attributed to each action_type, in ad-account native currency (same unit as `spend`; see the campaign node's `currency` field). Use this to compute revenue-per-event (e.g. avg purchase value). Meta-only; other platforms return {}.
348
+ */
349
+ actionValues?: {
350
+ [key: string]: (number);
351
+ };
352
+ /**
353
+ * Convenience sum of purchase-type action values — picked from `actionValues` via the same priority list as `conversions` so both fields describe the same events. In ad-account native currency. 0 when the campaign has no purchase event configured. Meta-only.
354
+ */
355
+ purchaseValue?: number;
356
+ /**
357
+ * Return on ad spend — derived as `purchaseValue / spend`. 0 when `spend` is 0. Equivalent to Meta's `purchase_roas` under default attribution. At ad-set and campaign levels this is recomputed from summed purchaseValue + spend (NOT averaged across children) so it's mathematically correct at every rollup level.
358
+ */
359
+ roas?: number;
346
360
  /**
347
361
  * Present on individual ads only, not on campaign aggregations
348
362
  */