Verifying your installation
Pasted the snippet? Here is a 60-second checklist to confirm data is flowing, plus what to do when the verifier disagrees with you.
- Key takeaways
- Verification needs to succeed once; after that, live data is the ongoing proof.
- Test in a private window or from mobile data if your own IP is excluded.
- The only request to look for is a ~300-byte POST to api.bobray.com/e.
The quick check
- Open your site in a normal browser window.
- In your BobRay dashboard, open the site and press Verify installation.
- Within a few seconds the verifier should report Snippet detected and your visit should appear in the live counter.
Do a manual live test
Open your site in a private window, browse two or three pages, and watch the Live panel. You should appear as one visitor with your route changes counting as pageviews. If you excluded your own IP, use a phone on mobile data instead.
If verification fails
- Confirm the snippet is inside
<head>and thedata-sitevalue matches the dashboard exactly. - Hard-refresh to bypass a cached page (Ctrl/Cmd+Shift+R).
- Check the browser console for a blocked request to
cdn.bobray.com, usually an ad blocker or a Content-Security-Policy, see CSP setup and Ad blockers.
Verification only needs to succeed once. After that, the dashboard's data itself is the proof; you do not need to re-verify after deployments.
Common pitfalls
The mistakes we see most often on this topic, so you can skip them entirely.
- Checking DevTools Elements instead of raw view-source, tag managers can inject late or not at all.
- Testing from an excluded office IP and concluding the install is broken.
- Verifying against staging while the snippet carries the production site ID.
Quick reference
| Data delay | ~30–60 seconds after first view |
| Beacon | POST api.bobray.com/e, ~300 B |
| Hard refresh | Ctrl/Cmd+Shift+R |
| Common blockers | Ad blockers, CSP, wrong site ID |
Did this solve it? If not, write to support with your site ID, a real person replies within one business day.