Probe test does not complete

Start a new test, keep its page open, and inspect the browser Network panel.

No request for p.js

The current probe snippet is not on the published page, a tag-manager container was not published, or a browser extension blocked it. Confirm the page source contains the current site key.

p.js is blocked

Check the browser console for Content Security Policy and privacy-tool messages. Allow the exact collection hostname for scripts. Disable an ad blocker only long enough to distinguish blocking from an installation problem.

Probe configuration returns 404

The site key is wrong, the site was removed, or the hostname points to another JuicyTraffic environment. Copy a fresh snippet from the saved site instead of editing the key manually.

Configuration loads but the event fails

Confirm that the page origin exactly matches the origin saved in JuicyTraffic, including HTTPS and subdomain. Check connect-src, CORS errors, and whether the site and probe are enabled.

Requests succeed but the UI keeps waiting

The test token may have expired or an older test page was reused. Close it, start a new test, and keep the new tab open. If it still fails, record the test ID, UTC time, request status, and non-sensitive error code for support.