> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/cookies/integration/test.md).

# Test the integration of a banner

Learn how to test the integration of a consent banner.

## Enable the preview mode

In the **Settings** section of the banner, open the advanced settings block and enable **Preview mode**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6ffdcfd46c1f34c74aad8adb7a6136566ceb5628%2Fcookies-test-1.png?alt=media" alt="The Preview mode switch in the Settings section"><figcaption><p>The "Preview mode" switch</p></figcaption></figure>

The preview mode disables the cache of the banner configuration: you see your changes live. It also disables the collection of statistics.

{% hint style="warning" %}
Do not leave the preview mode enabled in production: it degrades the performance of the banner.
{% endhint %}

`localhost` addresses with a port, for example `http://localhost:3000`, are always accepted, with or without the preview mode.

## Preview the banner on your website

Click **Preview banner** at the top of the editor. The button is disabled until an address is set in **Urls authorized (Allowed origins)**. Choose the website, enter the path of a page and the language if needed, then click **Launch preview**. The banner code must already be installed on the targeted website.

## Use the following API key

```
dastra00-0testing1-key
```

{% hint style="info" %}
This key displays an example consent banner. You cannot change its configuration. It is used for integration tests, for example in a jsFiddle.
{% endhint %}


---

# 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://doc.dastra.eu/en/features/cookies/integration/test.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.
