From ae0b99cc15c73ebeace86a43301e138dfe01cd7f Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 8 Oct 2025 13:12:37 -0400 Subject: [PATCH 1/6] Update debug mode instructions in web-setup.md Clarify the process for enabling debug mode and collecting user activity. --- src/connections/auto-instrumentation/web-setup.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md index e14fe6fb75..a3bf289082 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -214,8 +214,7 @@ After integrating the SDK and running your app, verify that Segment is collectin #### Enable debug mode -Values sent to the signals API are redacted by default. -This adds a local storage key. To disable redaction, add a magic query string: +User activity is not collected by default after SDK installation. To collect activity for use in building event rules, append the segment_signals_debug=true URL parameter. ``` https://my-website.com?segment_signals_debug=true From d8e64e02f6e501bda8c219ad58cf19bca8244d98 Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 8 Oct 2025 13:15:15 -0400 Subject: [PATCH 2/6] Update web-setup.md with debug URL details Added information about debug URL parameter and cookie behavior. --- src/connections/auto-instrumentation/web-setup.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md index a3bf289082..89f77929af 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -219,6 +219,7 @@ User activity is not collected by default after SDK installation. To collect act ``` https://my-website.com?segment_signals_debug=true ``` +Loading the site with this debug URL parameter saves a cookie onto that device that sends activities and expires in 24 hours. The URL parameter does not need to be present on each page load. You can _turn off debugging_ by doing: From b7b9a7c0149d764ca6965a9e7acc1f0ad470eb15 Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 8 Oct 2025 13:59:56 -0400 Subject: [PATCH 3/6] Update signal detection duration in documentation --- src/connections/auto-instrumentation/event-builder.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/auto-instrumentation/event-builder.md b/src/connections/auto-instrumentation/event-builder.md index c52f14a8de..34cd31f46e 100644 --- a/src/connections/auto-instrumentation/event-builder.md +++ b/src/connections/auto-instrumentation/event-builder.md @@ -47,7 +47,7 @@ Segment collects and displays activity as signals. These signals are grouped int Segment separates signal collection from event creation. Signals represent raw user interactions, like a button click or screen view. Events, on the other hand, are analytics calls you define based on those signals. This two-step process lets you observe user behavior first, and then decide how and when to turn that behavior into structured analytics events, without needing to modify your code. -Signal detection is active for 24 hours after you generate activity. Detected signals are available in the Event Builder for 72 hours. +Signal detection is active for 24 hours after you load the app or website in debug mode. Detected signals are available in the Event Builder for 7 days. ## Create an event @@ -86,4 +86,4 @@ For example, to track a login flow, you might define an Identify event that maps Segment uses the event name and any mapped properties to format each event according to the Segment Spec. Events you create in the Event Builder behave the same way as events sent through Segment SDKs or APIs. > info "Event type behavior in destinations" -> While Segment handles these event types consistently, downstream tools may treat them differently. For example, Identify events often update user profiles, while Page or Screen events may be handled as pageviews instead of custom events. \ No newline at end of file +> While Segment handles these event types consistently, downstream tools may treat them differently. For example, Identify events often update user profiles, while Page or Screen events may be handled as pageviews instead of custom events. From 85994d13b638b034a2279a7f28cc4ebf3c1751f7 Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 8 Oct 2025 14:34:19 -0400 Subject: [PATCH 4/6] Clarify signal detection duration in documentation --- src/connections/auto-instrumentation/event-builder.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/auto-instrumentation/event-builder.md b/src/connections/auto-instrumentation/event-builder.md index 34cd31f46e..f165a81d04 100644 --- a/src/connections/auto-instrumentation/event-builder.md +++ b/src/connections/auto-instrumentation/event-builder.md @@ -47,7 +47,7 @@ Segment collects and displays activity as signals. These signals are grouped int Segment separates signal collection from event creation. Signals represent raw user interactions, like a button click or screen view. Events, on the other hand, are analytics calls you define based on those signals. This two-step process lets you observe user behavior first, and then decide how and when to turn that behavior into structured analytics events, without needing to modify your code. -Signal detection is active for 24 hours after you load the app or website in debug mode. Detected signals are available in the Event Builder for 7 days. +Signal detection is active after you load the app or website in debug mode and until the tab or window is closed. Detected signals are available in the Event Builder for 7 days. ## Create an event From 60fac2cb2b8a89fbf9ed0caf0a5b19cb5a673bcf Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 8 Oct 2025 14:35:32 -0400 Subject: [PATCH 5/6] Clarify debug URL parameter behavior in documentation Updated the explanation of the debug URL parameter behavior to clarify that it stays active in session storage until the tab or window is closed. --- src/connections/auto-instrumentation/web-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md index 89f77929af..c22a7afb3c 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -219,7 +219,7 @@ User activity is not collected by default after SDK installation. To collect act ``` https://my-website.com?segment_signals_debug=true ``` -Loading the site with this debug URL parameter saves a cookie onto that device that sends activities and expires in 24 hours. The URL parameter does not need to be present on each page load. +Loading the site with this debug URL parameter stays active in session storage until the tab or window is closed. Within a session the URL parameter does not need to be present on each page load. You can _turn off debugging_ by doing: From 3dd9f0ed889daa4469132ed9c321921d86df2344 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 9 Oct 2025 00:14:42 -0500 Subject: [PATCH 6/6] Update web-setup.md --- src/connections/auto-instrumentation/web-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md index c22a7afb3c..7a29993bd6 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -214,7 +214,7 @@ After integrating the SDK and running your app, verify that Segment is collectin #### Enable debug mode -User activity is not collected by default after SDK installation. To collect activity for use in building event rules, append the segment_signals_debug=true URL parameter. +User activity is not collected by default after SDK installation. To collect activity for use in building event rules, append the `segment_signals_debug=true` URL parameter. ``` https://my-website.com?segment_signals_debug=true