> 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/abm/stackadapt.md).
# Stackadapt
HockeyStack integrates with StackAdapt to directly ingest the impression and engagement data as well as send any custom segment you built on HockeyStack back to StackAdapt as an audience.
To integrate with StackAdapt, go to you settings and click on Integrations:
You will need your Graph API key to integrate with StackAdapt.
HockeyStack pulls the following metrics from StackAdapt:
* Account ID
* Campaign Group ID
* Campaign Group Name
* Campaign ID
* Campaign Name
* Ad ID
* Ad Name
* UTM Parameters for Click URLs (Source. Medium, Campaign etc.)
* Clicks
* Cost
* Impressions
Tracked per day for every account you connect to HockeyStack
* Company ID
* Company Name
* Company Domain
* Company Industry
* Campaign ID
* Campaign Name
* Impressions
* Clicks
Also tracked per day and it shows the clicks/impressions every company that saw this campaign that day.
Bear in mind that for privacy reasons, ad platforms can hide any datapoint that is too specific for a company that can identify the personally binding data about any individual
---
# 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/abm/stackadapt.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.
