> 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/banner/go-further.md).

# Go further on cookie consent

The pages that describe how to apply visitors' choices and use the proof of consent.

Once the banner is in place, consent must be applied on your website and the proof you collect must be usable. The following pages describe these steps.

* [Blocking cookies](https://doc.dastra.eu/en/features/cookies/integration/blocking.md): prevent third-party services from setting cookies before consent, using the banner's JavaScript events.
* [Google Tag Manager](https://doc.dastra.eu/en/features/cookies/integration/blocking/google-tag-manager.md) and [Google Consent Mode V2](https://doc.dastra.eu/en/features/cookies/integration/blocking/google-consent-mode.md): trigger Google tags according to visitors' choices.
* [Manage consent programmatically](https://doc.dastra.eu/en/features/cookies/integration/programmatic-consent.md): read and change consent with the JavaScript SDK.
* [User identification](https://doc.dastra.eu/en/features/cookies/integration/identification.md): match a proof of consent with a pseudonymous identifier from your system.
* [Generate the cookie policy](https://doc.dastra.eu/en/features/cookies/banner/configure.md#generate-the-cookie-policy): produce the cookie policy from the banner configuration.
* [View the statistics](https://doc.dastra.eu/en/features/cookies/banner/consent-proof.md#view-the-statistics): follow displays, consents and refusals.

{% content-ref url="/pages/-M4QG9ZVdB2DnGlZ\_uPd" %}
[Technical integration](https://doc.dastra.eu/en/features/cookies/integration.md)
{% endcontent-ref %}


---

# 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/banner/go-further.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.
