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

# Conversion metrics

Tie website visits and form fills back to your audiences, with cost and lift metrics.

Conversion metrics connect the traffic your [website pixel](/primer/connections/website-tracking/installing-the-pixel.md) sees to the audiences you're running, so you can tell which audiences drive conversion events — visits and form fills.

## The funnel

Each report is a two-stage funnel:

1. **Website Visitors** — people who viewed a page.
2. **Leads** — people who filled out a form.

## Attribution window

You choose the attribution window: **30, 60, 90 or 180 days**. Primer attributes a conversion to the most recent touch within the window.

## Metrics

Two controls in the header set what the report shows: the **funnel stage selector** (switch between the Website Visitors and Leads stages) and the **Conversion Domains** button (top-right) for scoping which domains count:

![Conversion report: the funnel stage selector switches between the Website Visitors and Leads stages, and the Conversion Domains button sits in the top-right of the header.](https://2005909474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyNQPXI6WokgTBADFvkpG%2Fuploads%2Fgit-blob-9e02f69cfc15e41365deb30c77258765631bdcc0%2Fconversion-report.png?alt=media)

The dashboard shows **All Visits**, **Revealed** (identified visitors), **Form Fills**, and **In Audience** counts. For a single audience, Primer also computes:

* **Cost Per Visit** — ad spend divided by exposed pageview conversions.
* **Cost Per Lead** — ad spend divided by exposed lead conversions.
* **Lift** — conversions among people exposed to your ads vs. those not exposed. See [Conversion lift](/primer/audiences/conversion-lift.md) for how it's computed and read.

The person-level table lists each visitor with columns like company, seniority, headcount, visits, session time, first/last seen, form fills, UTM source and an **intent score**. You can export the table to CSV.

> **Deals Created** and **Deals Won** appear as tiles but aren't populated yet — that data isn't wired in. Ignore them for now.

## Conversion analysis report

A conversion analysis report is a **finished, published analysis** — a snapshot of your conversions frozen at a point in time. It's different from the live metrics above, which you filter yourself.

A conversion analysis report moves through **building → ready → published**. You only see it once it's **published**; while it's still building it isn't shown.


---

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