> 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/goals/building-an-all-touchpoints-channel-goal.md).
# Building an All Touchpoints (Channel) Goal
Sometimes, you want to identify a point in time when a user interacted with your channels or to measure customers' engagement as a goal itself, not as a means to achieving another goal. To do that, you need to build an **All-Touchpoints Goal (Channel Goal).**
Simply go to **Definitions → Goals → New Goal.** Pick the **"Defined Property Mapping"** type, and check all of the options inside your **Channel** (previously **Unified Channel**) defined property. Don't check any other mappings inside any other defined properties.
Save the goal, and you can use it in your analyses!
---
# 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/goals/building-an-all-touchpoints-channel-goal.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.