@apex-inc/sdk 0.17.1 → 0.17.2
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/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@apex-inc/sdk",
|
|
3
|
-
"version": "0.17.
|
|
4
|
-
"description": "Event tracking and identity SDK for Apex
|
|
3
|
+
"version": "0.17.2",
|
|
4
|
+
"description": "Event tracking and identity SDK for Apex \u2014 currently in private beta.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"module": "dist/esm/index.js",
|
|
7
7
|
"types": "dist/index.d.ts",
|
|
@@ -183,8 +183,16 @@ data: { order_id: "ord_123", value: 99.0, currency: "USD", cost: 48.5 }
|
|
|
183
183
|
|
|
184
184
|
`unit_cost` aliases: `cost`, `cogs`, `cost_of_goods`, `item_cost`. Cost is
|
|
185
185
|
never inferred — omit it and every channel is measured and ranked on LTV:CAC,
|
|
186
|
-
which is a complete answer on its own.
|
|
187
|
-
|
|
186
|
+
which is a complete answer on its own.
|
|
187
|
+
|
|
188
|
+
**Cost is all-or-nothing per order.** Every line item that carries a price or a
|
|
189
|
+
product id must also carry a cost, or Apex treats that order as cost-unknown
|
|
190
|
+
and it contributes to LTV:CAC only. This matters most during a rollout: if you
|
|
191
|
+
instrument 70 of 100 SKUs, a mixed order would otherwise report the cost of the
|
|
192
|
+
70% as if it were the whole order, which inflates gross profit rather than
|
|
193
|
+
leaving it blank. Send `cost` at the order level if per-item cost isn't
|
|
194
|
+
available for every line. Each channel's LTGP:CAC states the share of revenue
|
|
195
|
+
behind it, so partial rollouts read as a small sample instead of a wrong number.
|
|
188
196
|
|
|
189
197
|
## Event naming conventions
|
|
190
198
|
|