# 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.

<figure><img src="/files/LU5fTfvXKLNXLDu7GK0f" alt=""><figcaption></figcaption></figure>

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 \
&#x20; "any action" - "unique users", filtered to "User Properties > contact\_title contains one of Director,Head,Chief,CMO,CRO,CEO,COO,CISO,CTO,VP"\
&#x20; divided by\
&#x20; "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:**

<figure><img src="/files/nfBF4uldOOUWX6wXlk4n" alt=""><figcaption></figcaption></figure>

<div align="left"><figure><img src="/files/ahhsgQCyyNcVvtPZUHhM" alt=""><figcaption></figcaption></figure></div>

<figure><img src="/files/Klzv91dnjJcA6Cz18S54" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/percentage-of-high-quality-job-titles-by-channel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.