> 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/gerer-le-consentement-aux-cookies/configuration-du-widget/classifiez-les-cookies-par-categories-de-consentement.md).

# Classify cookies by consent categories

Learn how to classify cookies by consent categories.

With DASTRA, you can classify via a simple "drag and drop" the cookies deposited on your website, by broad category of purpose:

* "**Strictly necessary**" cookies: these are cookies that are exempt from consent by their nature (for example, session or consent cookies)
* "**Preferences**" type cookies
* "**Audience analysis**" type cookies
* "**Marketing and user experience**" cookies
* Other cookies.

{% content-ref url="/pages/1T5zJslQz7mvpsDUKYB2" %}
[The purposes of cookies](/en/features/gerer-le-consentement-aux-cookies/configuration-du-widget/the-purposes-of-cookies.md)
{% endcontent-ref %}

To do this, simply select the cookie to be classified from the Classification interface, then move it by simply "clicking and dropping" it to the category of your choice.

![The "Cookie to classify" cookie being classified](https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvBxs22wUMicv9uWp6C%2F-M4FPvNvDfF2DGqqoa4D%2F-M4FSB7Vcd5Nr7Bpv3Os%2Fimage.png?alt=media\&token=0d2cac69-f3e2-4fcb-ab32-248b6d58ebab)

![The "Cookie to be filed" cookie filed in the "Preferences" category](https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvBxs22wUMicv9uWp6C%2F-M4FPvNvDfF2DGqqoa4D%2F-M4FSRWt6BpcaGp7olHM%2Fimage.png?alt=media\&token=b625a31e-5a53-4dd9-a9cf-5dfb9783b2fc)

{% hint style="info" %}
You can define whether or not consent is required for each cookie on a case-by-case basis.
{% endhint %}

{% hint style="warning" %}
A cookie detected by the scan but not linked to any service (unclassified cookie) is never displayed in the public banner. Add it to an existing service or create a service from it: see [Handle unclassified cookies](/en/features/gerer-le-consentement-aux-cookies/configuration-du-widget/scannez-les-cookies-deposes-sur-votre-site-web.md#handle-unclassified-cookies).
{% endhint %}

Once you have categorized all your cookies, you can implement the corresponding consent widget.

{% content-ref url="/pages/-M378oB2HodWBFfDdJsg" %}
[Implement a cookie consent widget](/en/features/gerer-le-consentement-aux-cookies/configuration-du-widget/implementez-un-widget-de-consentement-aux-cookies.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/gerer-le-consentement-aux-cookies/configuration-du-widget/classifiez-les-cookies-par-categories-de-consentement.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.