> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/goals/how-do-i-measure-conversion.md).
# Measuring conversion rates
There are a few options to measure conversion rate in HockeyStack, pick the one that fits your use case the best!\
\
**1. Number Divided by Number:**
This straightforward approach to measuring conversion between two goals is to divide the count of one goal by another.
*Example*: To calculate the conversion rate from Marketing Qualified Leads (MQLs) to Sales Qualified Leads (SQLs):
* Go to: Definitions → Report → New Report
* Select SQL → times done **over** MQL → times done
* Format the ratio as a percent to view the conversion rate
**2. Cohorted Conversion Rate:**
The Number Divided by Number Conversion doesn’t take into account that we are only interested in customers who have performed both goals. To tackle this nuance, you will want to use the Cohorted Conversion Rate.
*Example*: To determine the conversion rate from Marketing Lead to Passed Lead you only want to count Marketing Lead for customers who has done Passed Lead afterwards (and not all the Marketing Leads).
* Go to: Definitions → Report → New Report
* Select Marketing Lead → times done, and filter it to “the user has done” → Passed Lead
* **Over:** Marketing Lead → times done
* Format the ratio as a percent to view the conversion rate
**3. Attributed Conversion Rate:**
To calculate the conversion between a goal and a touchpoint, you need to use the Attributed Conversion Rate.
*Example*: To calculate the conversion rate from "Paid Social - LinkedIn Ads" to Marketing Lead
* Go to: Definitions → Report → New Report
* Select the goal of your choice (e.g. Marketing Lead) **over** Any action → unique users
* In the Attribution Options on the left, select Channel (previously Unified Channel) and filter it to the channel of your choice (here: Paid Social - LinkedIn Ads)
* This way, Any Action → times done is interaction with the Channel you chose
* Apply the "Uniform" attribution model
---
# 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://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/goals/how-do-i-measure-conversion.md?ask=&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.
