@unifold/analytics 0.1.77 → 0.1.78

package/dist/index.d.mts

@@ -97,6 +97,22 @@ interface AnalyticsProperties {
     wallet?: string;
     /** Transaction amount in USD. */
     amount_usd?: string;
+    /**
+     * Direct execution id (`exec_<ksuid>`) the flow produced, when one exists.
+     * High cardinality — this is a join key back to the execution row, not a
+     * breakdown dimension.
+     */
+    execution_id?: string;
+    /** Payment intent id (`pi_<ksuid>`) a checkout journey paid, when one exists. */
+    payment_intent_id?: string;
+    /**
+     * Deposit wallet id (`wallet_<ksuid>`) the flow is funding. Sent on
+     * `flow_started`, where no execution exists yet — an execution is created
+     * only once funds land on this wallet, and carries the same id, so this is
+     * how a started-but-never-completed journey is matched to whatever
+     * execution did (or didn't) follow.
+     */
+    deposit_wallet_id?: string;
     /** Human-readable token amount (standard unit, e.g. "0.5"). */
     amount?: string;
     /** Token amount in base units (smallest denomination). */
@@ -171,8 +187,9 @@ interface AnalyticsEvent {
      */
     sessionId?: string;
     /**
-     * Internal Unifold user.id (`user_<ksuid>`), typically obtained from the
-     * deposit-addresses response. Serialized to the wire as `user_id`.
+     * Internal Unifold user.id (`user_<ksuid>`), obtained from whichever API
+     * response resolves it first — deposit addresses, the execution query, a
+     * payment intent. Serialized to the wire as `user_id`.
      */
     userId?: string;
     properties: AnalyticsProperties;
@@ -246,8 +263,12 @@ declare class EventTracker {
     track(eventName: AnalyticsEventName, properties?: AnalyticsProperties): void;
     /**
      * Associate subsequent events with an internal Unifold user.id
-     * (`user_<ksuid>`). Pass `null` to clear. Usually called once the
-     * deposit-addresses response returns the id.
+     * (`user_<ksuid>`). Pass `null` to clear.
+     *
+     * The tracker is shared across flows and outlives any one journey, so a
+     * journey stamps its own user at the start — with the id if it already
+     * knows one, `null` if it doesn't — rather than inheriting whatever the
+     * previous journey left here.
      */
     setUserId(userId: string | null): void;
     /**
@@ -256,8 +277,8 @@ declare class EventTracker {
      * {@link EventTracker.endSession} carries it.
      *
      * Does not touch `userId`: the internal `user_<ksuid>` is attached separately
-     * via {@link EventTracker.setUserId} once the deposit-addresses response
-     * returns, and persists until the host replaces it.
+     * via {@link EventTracker.setUserId}, and persists until the host replaces
+     * it — which the SDK's modals do on every journey start.
      */
     startSession(): string;
     /**
@@ -324,6 +345,6 @@ declare function generateKSUID(): string;
  */
 declare function generatePrefixedKSUID(prefix: string): string;
 
-declare const PACKAGE_VERSION = "0.1.77";
+declare const PACKAGE_VERSION = "0.1.78";
 
 export { type AnalyticsConfig, type AnalyticsContext, type AnalyticsEvent, type AnalyticsEventName, AnalyticsEvents, type AnalyticsProperties, Emitter, EventTracker, PACKAGE_VERSION, createEventTracker, forwardEvent, generateKSUID, generatePrefixedKSUID };

package/dist/index.d.ts

@@ -97,6 +97,22 @@ interface AnalyticsProperties {
     wallet?: string;
     /** Transaction amount in USD. */
     amount_usd?: string;
+    /**
+     * Direct execution id (`exec_<ksuid>`) the flow produced, when one exists.
+     * High cardinality — this is a join key back to the execution row, not a
+     * breakdown dimension.
+     */
+    execution_id?: string;
+    /** Payment intent id (`pi_<ksuid>`) a checkout journey paid, when one exists. */
+    payment_intent_id?: string;
+    /**
+     * Deposit wallet id (`wallet_<ksuid>`) the flow is funding. Sent on
+     * `flow_started`, where no execution exists yet — an execution is created
+     * only once funds land on this wallet, and carries the same id, so this is
+     * how a started-but-never-completed journey is matched to whatever
+     * execution did (or didn't) follow.
+     */
+    deposit_wallet_id?: string;
     /** Human-readable token amount (standard unit, e.g. "0.5"). */
     amount?: string;
     /** Token amount in base units (smallest denomination). */
@@ -171,8 +187,9 @@ interface AnalyticsEvent {
      */
     sessionId?: string;
     /**
-     * Internal Unifold user.id (`user_<ksuid>`), typically obtained from the
-     * deposit-addresses response. Serialized to the wire as `user_id`.
+     * Internal Unifold user.id (`user_<ksuid>`), obtained from whichever API
+     * response resolves it first — deposit addresses, the execution query, a
+     * payment intent. Serialized to the wire as `user_id`.
      */
     userId?: string;
     properties: AnalyticsProperties;
@@ -246,8 +263,12 @@ declare class EventTracker {
     track(eventName: AnalyticsEventName, properties?: AnalyticsProperties): void;
     /**
      * Associate subsequent events with an internal Unifold user.id
-     * (`user_<ksuid>`). Pass `null` to clear. Usually called once the
-     * deposit-addresses response returns the id.
+     * (`user_<ksuid>`). Pass `null` to clear.
+     *
+     * The tracker is shared across flows and outlives any one journey, so a
+     * journey stamps its own user at the start — with the id if it already
+     * knows one, `null` if it doesn't — rather than inheriting whatever the
+     * previous journey left here.
      */
     setUserId(userId: string | null): void;
     /**
@@ -256,8 +277,8 @@ declare class EventTracker {
      * {@link EventTracker.endSession} carries it.
      *
      * Does not touch `userId`: the internal `user_<ksuid>` is attached separately
-     * via {@link EventTracker.setUserId} once the deposit-addresses response
-     * returns, and persists until the host replaces it.
+     * via {@link EventTracker.setUserId}, and persists until the host replaces
+     * it — which the SDK's modals do on every journey start.
      */
     startSession(): string;
     /**
@@ -324,6 +345,6 @@ declare function generateKSUID(): string;
  */
 declare function generatePrefixedKSUID(prefix: string): string;
 
-declare const PACKAGE_VERSION = "0.1.77";
+declare const PACKAGE_VERSION = "0.1.78";
 
 export { type AnalyticsConfig, type AnalyticsContext, type AnalyticsEvent, type AnalyticsEventName, AnalyticsEvents, type AnalyticsProperties, Emitter, EventTracker, PACKAGE_VERSION, createEventTracker, forwardEvent, generateKSUID, generatePrefixedKSUID };

package/dist/index.js

@@ -100,7 +100,7 @@ function generatePrefixedKSUID(prefix) {
 }
 
 // src/version.ts
-var PACKAGE_VERSION = "0.1.77";
+var PACKAGE_VERSION = "0.1.78";
 
 // src/tracker.ts
 var LIBRARY_NAME = "@unifold/analytics";
@@ -193,8 +193,12 @@ var EventTracker = class {
   }
   /**
    * Associate subsequent events with an internal Unifold user.id
-   * (`user_<ksuid>`). Pass `null` to clear. Usually called once the
-   * deposit-addresses response returns the id.
+   * (`user_<ksuid>`). Pass `null` to clear.
+   *
+   * The tracker is shared across flows and outlives any one journey, so a
+   * journey stamps its own user at the start — with the id if it already
+   * knows one, `null` if it doesn't — rather than inheriting whatever the
+   * previous journey left here.
    */
   setUserId(userId) {
     this.userId = userId || void 0;
@@ -205,8 +209,8 @@ var EventTracker = class {
    * {@link EventTracker.endSession} carries it.
    *
    * Does not touch `userId`: the internal `user_<ksuid>` is attached separately
-   * via {@link EventTracker.setUserId} once the deposit-addresses response
-   * returns, and persists until the host replaces it.
+   * via {@link EventTracker.setUserId}, and persists until the host replaces
+   * it — which the SDK's modals do on every journey start.
    */
   startSession() {
     this.sessionId = generatePrefixedKSUID(SESSION_PREFIX);

package/dist/index.mjs

@@ -98,7 +98,7 @@ function generatePrefixedKSUID(prefix) {
 }
 
 // src/version.ts
-var PACKAGE_VERSION = "0.1.77";
+var PACKAGE_VERSION = "0.1.78";
 
 // src/tracker.ts
 var LIBRARY_NAME = "@unifold/analytics";
@@ -191,8 +191,12 @@ var EventTracker = class {
   }
   /**
    * Associate subsequent events with an internal Unifold user.id
-   * (`user_<ksuid>`). Pass `null` to clear. Usually called once the
-   * deposit-addresses response returns the id.
+   * (`user_<ksuid>`). Pass `null` to clear.
+   *
+   * The tracker is shared across flows and outlives any one journey, so a
+   * journey stamps its own user at the start — with the id if it already
+   * knows one, `null` if it doesn't — rather than inheriting whatever the
+   * previous journey left here.
    */
   setUserId(userId) {
     this.userId = userId || void 0;
@@ -203,8 +207,8 @@ var EventTracker = class {
    * {@link EventTracker.endSession} carries it.
    *
    * Does not touch `userId`: the internal `user_<ksuid>` is attached separately
-   * via {@link EventTracker.setUserId} once the deposit-addresses response
-   * returns, and persists until the host replaces it.
+   * via {@link EventTracker.setUserId}, and persists until the host replaces
+   * it — which the SDK's modals do on every journey start.
    */
   startSession() {
     this.sessionId = generatePrefixedKSUID(SESSION_PREFIX);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unifold/analytics",
-  "version": "0.1.77",
+  "version": "0.1.78",
   "description": "Lightweight internal analytics for the Unifold SDK — zero external dependencies",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",