@zernio/node 0.2.518 → 0.2.519

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.
@@ -1623,6 +1623,15 @@ export type ConversionEvent = {
1623
1623
  * Meta advanced matching (ge). 'f' or 'm'; hashed server-side. Meta only.
1624
1624
  */
1625
1625
  gender?: string;
1626
+ /**
1627
+ * Meta lead ID from a Lead Ad submission, as a string. Required
1628
+ * for Conversion Leads CRM events: send it with
1629
+ * `actionSource: 'crm'` and
1630
+ * `platformData: { event_source: 'crm', lead_event_source: '<CRM name>' }`.
1631
+ * Forwarded unhashed to Meta's `user_data.lead_id`. Meta only.
1632
+ *
1633
+ */
1634
+ leadId?: string;
1626
1635
  /**
1627
1636
  * Platform click identifiers captured from the originating ad click.
1628
1637
  */
@@ -1678,7 +1687,13 @@ export type ConversionEvent = {
1678
1687
  */
1679
1688
  actionSource?: 'web' | 'app' | 'offline' | 'crm' | 'phone_call' | 'system_generated';
1680
1689
  /**
1681
- * Escape hatch for platform-specific fields we haven't normalized. Forwarded as-is.
1690
+ * Escape hatch for platform-specific fields we haven't normalized.
1691
+ * On Meta, keys are shallow-merged into `custom_data` only: fields
1692
+ * Zernio already builds (`value`, `currency`, `contents`,
1693
+ * `num_items`) always win on collision, and `user_data` (hashed
1694
+ * match keys) is never touched. Use first-class fields (e.g.
1695
+ * `user.leadId`) for anything that must reach `user_data`.
1696
+ *
1682
1697
  */
1683
1698
  platformData?: {
1684
1699
  [key: string]: unknown;