> 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/conversion-sources.md).

# Conversion sources

Define which pages count as a conversion, up to 50 rules.

A conversion source is a rule that tells Primer which page visits count as a conversion — for example a demo-request or pricing page. Primer uses these to attribute conversions to the audiences and companies driving them.

## Choosing which pages count

You pick one of two modes:

* **Accept all** — every page on the domain counts, with no rules to set up.
* **Specific pages** — you add a domain and Primer analyzes it, then suggests rules for you to review and confirm.

Under **Specific pages**, each rule targets a domain and can narrow it further by path: **include** only certain paths (for example `/pricing` or `/demo/*`) or **exclude** paths you don't want counted (for example `/blog/*`). Paths support a `*` wildcard.

## Limit

You can define up to **50 conversion source rules**.

Conversion sources rely on the [website pixel](/primer/connections/website-tracking/installing-the-pixel.md), so make sure it's [Connected](/primer/connections/website-tracking/pixel-connection-status.md) before you count on the data.


---

# 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/conversion-sources.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.