Invalid TraceLog configuration

What was observed

TraceLog's code loaded and reported that its configuration fails its own checks: the key is not a well-formed browser key, or the endpoint is not a usable http or https address. The page keeps working; the code captures nothing and reports the condition.

On Shopify, this row can also come from a signed install callback whose state or code fails.

Replace the installed configuration with the current pre-filled snippet for this project.

What to check

1. Copy the snippet again from Installation in the project. It arrives pre-filled and pinned; a key retyped by hand is the usual cause.
2. A browser key is tl_pk_ followed by 26 lowercase base32 characters. If what is on your page starts with tl_sk_, a server key has reached a browser bundle — rotate it immediately and replace it with the browser key.
3. If you set endpoint yourself, confirm it is an absolute https address or a path relative to your own origin.

A page served from an origin outside the project's allowed origins is refused without raising this row. While the verification session is open, the Installation page offers that as a separate possible explanation.

Effect on verification

It reports. Nothing is being stored under your project, so there is nothing to verify.