> For the complete documentation index, see [llms.txt](https://support.happydemics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.happydemics.com/launch/exposure-data/when-and-why-do-we-use-exposure-data.md).

# When and why do we use exposure data?

Depending on the media channel you use in your campaign, it may be possible to “retarget” respondents who are likely to have been exposed to your ad. This can be done using tools such as tracking pixels, user IDs, broadcasting frameworks, or geographic coordinates.

**Exposure data can be seen as:**

* It helps reassure you and your clients about the ad recall status of respondents within a specific environment.
* It increases the comparability between ad recall and non-ad recall respondents, since both groups are targeted with the same broadcasting strategies.

**Please note:** when you provide exposure data, respondents collection is based on this data, including participants in the control group. This approach is different from most other brand lift providers. However, because our methodology is centered on ad recall, this is not an issue. Our goal is to measure the impact of **actually remembering an ad**, not just the effect of potential exposure.

Depending on the media channels used in your campaigns, different types of exposure data may be available. The table below provides an overview of which data types you can use for each media channel.

<figure><img src="/files/5iSSvqn6r497uf346QKF" alt=""><figcaption></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 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://support.happydemics.com/launch/exposure-data/when-and-why-do-we-use-exposure-data.md?ask=<question>&goal=<endgoal>
```

`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.
