Skip to content

Add troubleshooting tips for Segment signals #8127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 6, 2025
Merged

Add troubleshooting tips for Segment signals #8127

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2570266
Add troubleshooting tips for Segment signals
maxmilhan Nov 3, 2025
9e747d5
Update src/connections/auto-instrumentation/web-setup.md
maxmilhan Nov 5, 2025
007f392
Update src/connections/auto-instrumentation/web-setup.md
maxmilhan Nov 5, 2025
c7c6b57
Update src/connections/auto-instrumentation/web-setup.md
maxmilhan Nov 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/connections/auto-instrumentation/web-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.