> For the complete documentation index, see [llms.txt](https://docs.openli.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openli.com/docs/cookie-consent-management/categorise-your-cookies.md).

# Categorise your cookies

{% embed url="<https://www.loom.com/share/b7154dbca71549afa591b7bebf5deaaa>" %}

Openli automatically scans your website for new cookies on a regular basis.&#x20;

We may recognise some of the found cookies and in these cases the system will categorize them in the category most often used. However, it might not fit your purpose and in some cases we don’t know the cookies. So it is very important that you check if your cookies are categorized correctly. It’s also very important that you categorize the uncategorised cookies. &#x20;

Here is how you can categorize the cookies:&#x20;

* Go to Cookies in the navigation menu.&#x20;

You can here see if you have uncategorised cookies and you can also see the categorized ones.&#x20;

For the uncategorised cookies you will have the option to add a cookie to an existing provider, by clicking the provider in the Select provider dropdown, or to add a new provider if needed.&#x20;

When adding a new provider, you need to provide the provider's full name, address, the description (what you do with the provider), the provider's privacy-policy URL and more (see the article: “How to add information to your vendors”# .&#x20;

After a provider is added, it can be selected in the list as described above, allowing for quicker categorisation of more cookies.

For the already categorized cookies, you can move them to another category by clicking on the vendor’s name and then select another category at the top of the page.&#x20;


---

# 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.openli.com/docs/cookie-consent-management/categorise-your-cookies.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.
