> 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/reporting/percentage-of-high-quality-job-titles-by-channel.md).
# Measuring percentage of high quality job titles by Channel
To understand which touchpoints are reaching the correct target audience, you can use a report that shows you the percentage of "high quality" job titles by each type of touchpoint. For this example we will use Channel as our touchpoint type, but you can use anything, including Campaign, Page URL, Asset Type, etc.
First, we have to define our high quality job titles. An easy way to define it would be checking if the title contains words like "Director,Head,Chief,CMO,CRO,CEO,COO,CISO,CTO,VP" etc.
Then, create a new report.
**Breakdown:** Channel
**Columns:** % of high quality job titles.
* defined by \
"any action" - "unique users", filtered to "User Properties > contact\_title contains one of Director,Head,Chief,CMO,CRO,CEO,COO,CISO,CTO,VP"
* divided by\
"any action" - "unique users", filtered to "User Properties > contact\_title is not empty"
Filtering for "contact\_title is not empty" in the denominator is important because we can't know the job title of every visitor, and we don't want differences in how much we can identify job titles across different touchpoints to affect our ranking of touchpoints.
**Full Definition:**
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/reporting/percentage-of-high-quality-job-titles-by-channel.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.