No signal from TraceLog on the verification page

What was observed

In the tab opened from Installation for verification, the page answered that TraceLog's code is not there. The snippet may be missing, may have failed to load, or something may have stopped it before it ran.

If the code does not answer within 10 seconds, TraceLog cannot tell a missing snippet from a consent setup that keeps it from running. That is why this row asks you to check both.

Check that the TraceLog snippet is installed and that your consent setup is not preventing it from loading.

What to check

1. View source on the page and confirm the script tag is there, on every page of your site — not only the checkout.
2. Open the browser's network tab and confirm the TraceLog file loads. A 404 usually means the pinned version in the path was edited by hand.
3. Check whether a consent platform, tag manager, or content-blocking extension is preventing the script from running at all.
4. If your consent platform holds scripts until acceptance, accept in the test tab. If the code then reports that consent is pending, see consent_blocked.

Effect on verification

It reports. Verification cannot complete until TraceLog's code answers from the page.