@walkeros/web-destination-tiktok 3.4.2 → 4.0.0-next-1777463920154

package/dist/dev.d.mts

@@ -149,19 +149,19 @@ type TikTokStepExample = Flow.StepExample & {
     configInclude?: string[];
 };
 /**
- * Default event forwarding — every walkerOS event becomes a ttq.track()
+ * Default event forwarding - every walkerOS event becomes a ttq.track()
  * call. With no mapping and no destination-level include, the params
  * object is empty. event_id is always passed as the 3rd argument (TikTok
  * dedup between pixel and Events API).
  *
  * NOTE: The raw walkerOS event name "product view" (with space) is NOT a
  * TikTok standard event. Without a mapping.name override, TikTok treats
- * it as a custom event — functional for audience building, no
+ * it as a custom event - functional for audience building, no
  * optimization. The next example shows the recommended override.
  */
 declare const defaultEventForwarding: TikTokStepExample;
 /**
- * Wildcard ignore — walkerOS's standard way to drop events. The rule
+ * Wildcard ignore - walkerOS's standard way to drop events. The rule
  * matches but does nothing. The destination fires zero SDK calls.
  */
 declare const wildcardIgnored: TikTokStepExample;
@@ -176,7 +176,7 @@ declare const productViewContent: TikTokStepExample;
 /**
  * Destination-level settings.include flattens the walkerOS `data` section
  * into prefixed TikTok event parameters on every push. This is the
- * "dump everything" mode — useful for custom events where TikTok won't
+ * "dump everything" mode - useful for custom events where TikTok won't
  * do optimization anyway, and no mapping.data is needed.
  */
 declare const destinationLevelInclude: TikTokStepExample;
@@ -191,7 +191,7 @@ declare const ruleIncludeReplaces: TikTokStepExample;
  * state cache is empty). Advanced Matching parameters (email,
  * phone_number, external_id) are passed to ttq.identify() which
  * auto-hashes them SHA256 before sending. Subsequent pushes with
- * unchanged values do NOT re-fire ttq.identify() — runtime state tracks
+ * unchanged values do NOT re-fire ttq.identify() - runtime state tracks
  * the last-resolved identity.
  *
  * walkerOS's default user fixture has user.id='us3r' and no email/phone,
@@ -216,7 +216,7 @@ declare const userRegisterCompleteRegistration: TikTokStepExample;
  *    is absent (here data.currency is 'EUR' so the key wins)
  *
  * The default "order complete" fixture has 3 nested entries: two
- * products (ers, cc) and one gift (Surprise — no id, no price).
+ * products (ers, cc) and one gift (Surprise - no id, no price).
  */
 declare const orderCompleteCompletePayment: TikTokStepExample;
 /**
@@ -227,7 +227,7 @@ declare const orderCompleteCompletePayment: TikTokStepExample;
 declare const searchSubmitSearch: TikTokStepExample;
 /**
  * Consent granted → ttq.enableCookie(). The destination checks the
- * consent keys declared in config.consent (here "marketing" — TikTok is
+ * consent keys declared in config.consent (here "marketing" - TikTok is
  * an ad platform, not analytics) and toggles cookie behavior.
  *
  * Uses the canonical StepExample.command='consent' pattern: the test

package/dist/dev.d.ts

@@ -149,19 +149,19 @@ type TikTokStepExample = Flow.StepExample & {
     configInclude?: string[];
 };
 /**
- * Default event forwarding — every walkerOS event becomes a ttq.track()
+ * Default event forwarding - every walkerOS event becomes a ttq.track()
  * call. With no mapping and no destination-level include, the params
  * object is empty. event_id is always passed as the 3rd argument (TikTok
  * dedup between pixel and Events API).
  *
  * NOTE: The raw walkerOS event name "product view" (with space) is NOT a
  * TikTok standard event. Without a mapping.name override, TikTok treats
- * it as a custom event — functional for audience building, no
+ * it as a custom event - functional for audience building, no
  * optimization. The next example shows the recommended override.
  */
 declare const defaultEventForwarding: TikTokStepExample;
 /**
- * Wildcard ignore — walkerOS's standard way to drop events. The rule
+ * Wildcard ignore - walkerOS's standard way to drop events. The rule
  * matches but does nothing. The destination fires zero SDK calls.
  */
 declare const wildcardIgnored: TikTokStepExample;
@@ -176,7 +176,7 @@ declare const productViewContent: TikTokStepExample;
 /**
  * Destination-level settings.include flattens the walkerOS `data` section
  * into prefixed TikTok event parameters on every push. This is the
- * "dump everything" mode — useful for custom events where TikTok won't
+ * "dump everything" mode - useful for custom events where TikTok won't
  * do optimization anyway, and no mapping.data is needed.
  */
 declare const destinationLevelInclude: TikTokStepExample;
@@ -191,7 +191,7 @@ declare const ruleIncludeReplaces: TikTokStepExample;
  * state cache is empty). Advanced Matching parameters (email,
  * phone_number, external_id) are passed to ttq.identify() which
  * auto-hashes them SHA256 before sending. Subsequent pushes with
- * unchanged values do NOT re-fire ttq.identify() — runtime state tracks
+ * unchanged values do NOT re-fire ttq.identify() - runtime state tracks
  * the last-resolved identity.
  *
  * walkerOS's default user fixture has user.id='us3r' and no email/phone,
@@ -216,7 +216,7 @@ declare const userRegisterCompleteRegistration: TikTokStepExample;
  *    is absent (here data.currency is 'EUR' so the key wins)
  *
  * The default "order complete" fixture has 3 nested entries: two
- * products (ers, cc) and one gift (Surprise — no id, no price).
+ * products (ers, cc) and one gift (Surprise - no id, no price).
  */
 declare const orderCompleteCompletePayment: TikTokStepExample;
 /**
@@ -227,7 +227,7 @@ declare const orderCompleteCompletePayment: TikTokStepExample;
 declare const searchSubmitSearch: TikTokStepExample;
 /**
  * Consent granted → ttq.enableCookie(). The destination checks the
- * consent keys declared in config.consent (here "marketing" — TikTok is
+ * consent keys declared in config.consent (here "marketing" - TikTok is
  * an ad platform, not analytics) and toggles cookie behavior.
  *
  * Uses the canonical StepExample.command='consent' pattern: the test