diff --git a/src/connections/auto-instrumentation/event-builder.md b/src/connections/auto-instrumentation/event-builder.md
index c52f14a8de..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 generate activity. Detected signals are available in the Event Builder for 72 hours.
+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
 
@@ -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.
diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md
index e14fe6fb75..7a29993bd6 100644
--- a/src/connections/auto-instrumentation/web-setup.md
+++ b/src/connections/auto-instrumentation/web-setup.md
@@ -214,12 +214,12 @@ 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
 ```
+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: