> For the complete documentation index, see [llms.txt](https://addressable.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://addressable.gitbook.io/knowledge-base/integrations/data-sources-and-integrations.md).

# Data Sources & Integrations

Addressable ingests and processes data across all user touch points to include:

1. [**Engagement data**](/knowledge-base/integrations/data-sources-and-integrations/engagement-data-tracking.md) **from your sites and apps**. Addressable supports a variety of methods to collect, process and present engagement data to best suite your business needs and set up (website, mobile and server to server APIs). 
2. [**Performance data**](/knowledge-base/integrations/data-sources-and-integrations/performance-data-tracking.md) **from your social and programatic campaigns.** Connect your Ad networks to allow Addressable to generate paid campaigns, track their performance over time and automatically optimize them to drive your goals.
3. **Full on-chain data of 7 EVM compatible blockchains**; Avalanche, Arbitrum, Optimism, Polygon, Etherium, Base, Binance Smart Chain. 

Together, these sources of data are the basis for user behaviour analysis & insights, market share, opportunities and trends, campaign optimization and impactful targeting.

<figure><img src="https://2800906092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlmvdGU0ER07OAwIyiroz%2Fuploads%2FECO56nMxzgloVHTgvNzF%2FData%20%26%20Integrations.png?alt=media&amp;token=d97e46dd-afda-4367-99b3-fb981e3d26f2" alt=""><figcaption><p>Data Sources &#x26; Integrations</p></figcaption></figure>


---

# 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://addressable.gitbook.io/knowledge-base/integrations/data-sources-and-integrations.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.