> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/troubleshooting/pixel-not-connected.md).

# 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](https://support.sayprimer.com/primer/connections/website-tracking/pixel-connection-status.md)). 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](https://support.sayprimer.com/primer/connections/website-tracking/pixel-connection-status.md#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](https://support.sayprimer.com/primer/connections/website-tracking/installing-the-pixel.md#content-security-policy).

## 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](https://support.sayprimer.com/primer/connections/website-tracking/installing-the-pixel.md).

## Still Not connected

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.sayprimer.com/primer/troubleshooting/pixel-not-connected.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
