Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

The pixel shows Not connected

Why the website pixel stays Not connected after you install it, and how to get it receiving traffic.

Not connected means Primer hasn't received an event from your site in the last 24 hours (see Pixel connection status). These are the usual reasons.

No one has visited the live site since you installed it

The status changes only once a real visit reaches Primer. Open a page on your live site with the snippet in place, then check Connections → Website Tracking again.

You're testing on a staging, local or preview site

The pixel sends nothing from test hosts or bots, so a test copy of your site never turns the status to Connected — see which visits count. Check it on your live domain.

Your site's Content Security Policy blocks it

Open your browser's developer console on your live site. A Content Security Policy error naming one of Primer's domains means the browser is blocking the pixel. Add that domain to your policy's script-src or connect-src — the full list is in Installing the pixel.

The snippet on your site isn't the current one

A snippet typed out or copied from elsewhere may load the pixel from a host Primer doesn't serve. Replace it with the one from Copy Snippet in Connections → Website Tracking — see Installing the pixel.

Still Not connected

Confirm the snippet is on the live page's HTML, then contact support@sayprimer.com.

Last updated