> 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/touchpoints/configuring-touchpoints.md).

# Configuring Touchpoints

### Prerequisites

Before configuring touchpoints, ensure the following are complete:

* Your **website tracking script** is installed and firing correctly
* Your **CRM integrations** are connected and actively syncing
* You know the exact **Integration → Object → Field** you want to use for any CRM-based touchpoints
* Your **ads integrations** (e.g. Google Ads and LinkedIn Ads) are connected and syncing data

***

#### Configuring Touchpoints

HockeyStack provides a set of default touchpoint types to help you get started quickly.

To configure touchpoints:

1. Navigate to **Definitions → Touchpoint Types**
2. Click **Configure** on a touchpoint type
3. Click **Add default touchpoint types**
4. Select the appropriate **Source Type** or **Touchpoint Type** and add any filtering
5. Map values consistently across integrations
6. Click **Save**

Repeat this process for **Channels** and **Touchpoint Groupings** as needed.

***

If you experience issues creating or mapping touchpoints:

* Confirm your integrations are actively syncing
* Double-check the **Integration → Object → Field** selection
* Ensure naming conventions are consistent across systems

For additional help, contact **<support@hockeystack.com>**.


---

# 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/touchpoints/configuring-touchpoints.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.