> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/optimize-your-setup/consent-management/ideal-cookiebanner-setup.md).

# Ideal cookiebanner setup

As a marketer, you want the highest possible percentage of accepted cookies. A cookie banner that's big and hard to ignore gives you the best shot at getting a yes right away, so you don't lose that data from a session that often decides everything.

Here's the thing about asking for explicit consent. You can't track anyone until they actually click accept. So if your banner is easy to brush off, visitors will happily wander around your site while you sit there measuring nothing. And once they click through to the second page, that referrer and those campaign parameters are gone for good. Getting your marketing scripts to load on that first page, and starting to measure the journey right there, matters a lot more than most people realize.

#### **Cookiebot Manager**

1. Select **Explicit Consent** so you ask for opt-in consent.
2. Select **Overlay** or **Pop-up** so the cookie banner can't be ignored on the first page for new site visitors.
3. Select **Multilevel** so visitors can give or refuse consent for different categories.
4. Select **Allow all / Selection** if you don't want a button to reject all cookies in one simple click. But you are required to have a "deny all" or "reject all" button on your cookie banner.
5. Leave the **Close icon** option unchecked, so visitors can't close the banner without giving or refusing consent.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FdcUgcijDmnSdTUCfgGWD%2Fimage.png?alt=media&amp;token=94b2583b-9e7b-4fc0-be22-505f350dbc80" alt="" width="563"><figcaption></figcaption></figure>

#### **Cookiebot Admin**

* Under **Layout**, choose **Dialog** to make the banner as hard to ignore as possible.&#x20;
* For **Style effect**, choose **Overlay**. That way the rest of the page is blocked off and visitors can't click around the banner.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2Fd45abtntGjLo1cxoQNP3%2Fimage.png?alt=media&amp;token=a1ec88a7-991a-44bc-a2ce-2281a6532d12" alt=""><figcaption></figcaption></figure>

* Under **Compliance**, choose **Explicit Consent** as the **Method**, so you ask visitors for opt-in consent.
* Under **Type**, choose **Inline multilevel** to give visitors a choice between consent categories.
* Under **Buttons**, choose **Allow All / Selection** if you don't want a button that lets visitors reject everything in a single click. But you are required to have a "deny all" or "reject all" button on your cookie banner.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FkwXa1RldqSLA6xq61k8l%2Fimage.png?alt=media&amp;token=e53bcdf8-cf06-464d-82f6-0ecbc3ee1784" alt=""><figcaption></figcaption></figure>

#### **Consent Studio**

* In your Consent Studio account, go to the **Styling** options under **Web CMP**.
* Make sure the **Position** is **Centered**.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FDF72hgdwrPfv6cDHrkLm%2Fimage.png?alt=media&amp;token=091de5c6-f04d-4ac1-84cb-a015f9c2e30c" alt=""><figcaption></figcaption></figure>

* Enable the option **Enable Overlay Behind Banner** in the **Overlay** options to make the cookiebanner unignorable.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2F6044GC3zmcfwcWzgbuDD%2Fimage.png?alt=media&amp;token=e673099a-2e9a-462a-acef-f5b508211178" 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://docs.adpage.io/optimize-your-setup/consent-management/ideal-cookiebanner-setup.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.
