From 25702664b38a65d45378e74dd7dc6a779cfcaf98 Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Mon, 3 Nov 2025 12:21:06 -0500 Subject: [PATCH 1/4] Add troubleshooting tips for Segment signals Added troubleshooting section for common misconfigurations. --- src/connections/auto-instrumentation/web-setup.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md index 052ee9733d..346ab868b9 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -357,6 +357,14 @@ Network signals emit when an HTTP Request is made, or an HTTP Response is receiv - First party domain (for example, if on `foo.com`, then `foo.com/api/products`, but not `bar.com/api/products`) - Contains the content-type: `application/json` +## Troubleshooting + +Here are the most common misconfigurations preventing signals from reaching Segment. + +- Not enabling signals with the URL parameter: you must start each debug session by appending `?segment_signals_debug=true` to your URL parameters. +- Running debug mode with an ad blocker: an active ad blocker will prevent signals from reaching Segment. Disable your ad blocker and start a new session. +- Content Security Policies: in addition to the [default Analytics.js Content Security Policies](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/faq/#does-segment-support-using-strict-content-security-policy-csp-on-the-page), you must add `cdn.jsdelivr.net` to your allowlist, or `https://cdn.jsdelivr.net/npm/@segment/analytics-signals@latest/dist/umd/analytics-signals.umd.js` if your policies require the full path. + ## Next steps This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers example rules. From 9e747d5dc1ff3f93d0b2b5aa2a4516c6054d06d1 Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 5 Nov 2025 10:51:19 -0500 Subject: [PATCH 2/4] Update src/connections/auto-instrumentation/web-setup.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- 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 346ab868b9..1f0ce2f30c 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -362,7 +362,7 @@ Network signals emit when an HTTP Request is made, or an HTTP Response is receiv Here are the most common misconfigurations preventing signals from reaching Segment. - Not enabling signals with the URL parameter: you must start each debug session by appending `?segment_signals_debug=true` to your URL parameters. -- Running debug mode with an ad blocker: an active ad blocker will prevent signals from reaching Segment. Disable your ad blocker and start a new session. +- Running debug mode with an ad blocker: An active ad blocker prevents signals from reaching Segment. Disable your ad blocker and start a new session. - Content Security Policies: in addition to the [default Analytics.js Content Security Policies](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/faq/#does-segment-support-using-strict-content-security-policy-csp-on-the-page), you must add `cdn.jsdelivr.net` to your allowlist, or `https://cdn.jsdelivr.net/npm/@segment/analytics-signals@latest/dist/umd/analytics-signals.umd.js` if your policies require the full path. ## Next steps From 007f3929297d625e91b52ef4d859939d89f4298c Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 5 Nov 2025 10:51:32 -0500 Subject: [PATCH 3/4] Update src/connections/auto-instrumentation/web-setup.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- 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 1f0ce2f30c..56401ab7ec 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -363,7 +363,7 @@ Here are the most common misconfigurations preventing signals from reaching Segm - Not enabling signals with the URL parameter: you must start each debug session by appending `?segment_signals_debug=true` to your URL parameters. - Running debug mode with an ad blocker: An active ad blocker prevents signals from reaching Segment. Disable your ad blocker and start a new session. -- Content Security Policies: in addition to the [default Analytics.js Content Security Policies](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/faq/#does-segment-support-using-strict-content-security-policy-csp-on-the-page), you must add `cdn.jsdelivr.net` to your allowlist, or `https://cdn.jsdelivr.net/npm/@segment/analytics-signals@latest/dist/umd/analytics-signals.umd.js` if your policies require the full path. +- Content Security Policies: In addition to the [default Analytics.js Content Security Policies](/docs/connections/sources/catalog/libraries/website/javascript/faq/#does-segment-support-using-strict-content-security-policy-csp-on-the-page), you must add `cdn.jsdelivr.net` to your allowlist, or `https://cdn.jsdelivr.net/npm/@segment/analytics-signals@latest/dist/umd/analytics-signals.umd.js` if your policies require the full path. ## Next steps From c7c6b57dc31facdf43b6a3d7373d4ed7d457697d Mon Sep 17 00:00:00 2001 From: maxmilhan <34718789+maxmilhan@users.noreply.github.com> Date: Wed, 5 Nov 2025 10:51:41 -0500 Subject: [PATCH 4/4] Update src/connections/auto-instrumentation/web-setup.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- 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 56401ab7ec..f2bd2bdbc8 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -361,7 +361,7 @@ Network signals emit when an HTTP Request is made, or an HTTP Response is receiv Here are the most common misconfigurations preventing signals from reaching Segment. -- Not enabling signals with the URL parameter: you must start each debug session by appending `?segment_signals_debug=true` to your URL parameters. +- Not enabling signals with the URL parameter: You must start each debug session by appending `?segment_signals_debug=true` to your URL parameters. - Running debug mode with an ad blocker: An active ad blocker prevents signals from reaching Segment. Disable your ad blocker and start a new session. - Content Security Policies: In addition to the [default Analytics.js Content Security Policies](/docs/connections/sources/catalog/libraries/website/javascript/faq/#does-segment-support-using-strict-content-security-policy-csp-on-the-page), you must add `cdn.jsdelivr.net` to your allowlist, or `https://cdn.jsdelivr.net/npm/@segment/analytics-signals@latest/dist/umd/analytics-signals.umd.js` if your policies require the full path.