> 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/integrations/marketing-automation/pardot.md).
# Pardot
> Before you connect your Pardot account, make sure that you’ve successfully connected your Salesforce account. Even though it is a separate integration, we have to pull your Pardot data through your Salesforce account.
In order to connect to your Pardot account, we need your Pardot Business Unit ID. Don’t get afraid by the long name though, the process of getting this ID is very simple.
First, log into Salesforce using the same account you use to log into Pardot. On the **Setup** tab, navigate to **Pardot > Pardot Account Setup**.
You may see multiple users here but select the Business Unit ID of the user you want to connect to HockeyStack.
> In order for us to pull the necessary data, this user should be an administrator.
The Pardot Business Unit ID (BUID) begins with "0Uv" and is 18 characters long. If the format is different, the integration won't work.
---
# 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/integrations/marketing-automation/pardot.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.
