> 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/before-the-set-up/how-to-prepare-my-creative-s.md).

# How to prepare my creative(s)?

Because our methodology focuses on ad recall, every brand lift you launch with Happydemics requires a creative asset. This creative is shown to respondents as part of the contextualized ad recall question, making it an essential part of the survey experience.

<figure><img src="/files/vrRdv0Qg0gLjP59L8SLP" alt=""><figcaption></figcaption></figure>

Preparing and submitting the right creative is a crucial step, so it’s important to give it special attention.\
This section of the Help Center is here to guide you through the process and help ensure your creative asset is set up for success.


---

# 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/before-the-set-up/how-to-prepare-my-creative-s.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.
