Segment Events Not Showing in Debugger
Quick answer
The Source Debugger only samples real-time events (max 500), so missing rows are often normal; if nothing appears, analytics.js likely is not loading or the write key is wrong.
Most likely fix: Confirm the library loads
How to fix it
Try these in order — the most common fix is first.
1. Confirm the library loads
- Open the browser console and type analytics
- If undefined, check the snippet for missing characters
- Clear cache and reload
Did this fix it?2. Inspect network requests
- Open DevTools > Network and filter for segment.io
- Look for the p (page) request after reload
- Install the Segment Inspector Chrome extension
Did this fix it?3. Fire a test call
- Run analytics.identify('test') in the console
- Check the Debugger on the correct source
Did this fix it?4. Allow the debugger stream
- Make sure app.segment.com/debugger-stream is reachable on your network or VPN
Did this fix it?5. Use raw storage for full data
- Add a warehouse or S3 destination
- Query it instead of relying on the Debugger sample
Did this fix it?
Symptoms
You send track/page calls but the Debugger is empty or missing events.
Why it happens
- Debugger shows only a sample, capped at 500 events
- Analytics.js not loaded or snippet broken
- Wrong write key or wrong source
- Network blocks the debugger stream endpoint
- Profile destination routing without Unify/Engage plan
This guide also covers
- segment events not showing in debugger
- segment debugger empty
- segment source debugger not loading
Still not working?
If Segment keeps failing, you're not alone. See every Segment problem users report or the alternatives people switch to.
Done fighting Segment? Our small team builds your own Segment alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to us