> 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/connections/website-tracking/pixel-connection-status.md).

# Pixel connection status

What Connected and Not connected mean for the website pixel, and which visits count toward it.

After you [install the pixel](https://support.sayprimer.com/primer/connections/website-tracking/installing-the-pixel.md), **Connections → Website Tracking** shows whether Primer is receiving traffic from it. The status refreshes on its own while the page is open.

## Connected vs. Not connected

* **Connected** — Primer received at least one event from your site in the **last 24 hours**.
* **Not connected** — no event has arrived in the last 24 hours. If you just installed the snippet, open a page on your live site to generate one.

## Which visits count

Only visits to your live site count. The pixel sends nothing from bots, or from local, staging and preview hosts — for example `localhost`, or a host name containing `staging`, `dev`, `test` or `preview` — so installing it on a test copy of your site won't turn the status to Connected. See [what the pixel collects](https://support.sayprimer.com/primer/account-and-security/data-and-privacy.md#what-the-website-pixel-collects).

Still Not connected after a visit to your live site? See [The pixel shows Not connected](https://support.sayprimer.com/primer/troubleshooting/pixel-not-connected.md).


---

# 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/connections/website-tracking/pixel-connection-status.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.
