> 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/cookie-widget/how-to-manually-add-any-cookies.md). # Manually add any cookies {% embed url="" %} Short Video guide on adding cookies manually to Openli {% endembed %} ## Step 1: Add cookie Select on "**Cookies**" in the Openli dashboard, and click on the "Add cookie" button. ![](/files/isZaE0ko7ZbxOlsoI2kO) Fill out the required fields. Remember to select the correct domain, and write the name of the cookie you want to add (*this must be the technical name of the cookie when it is placed in the browser*). 1. Select the correct domain 2. Write the name of the cookie you want to add - this must be the technical name of the cookie when it is placed in the browser 3. Add the information about which domain hosts the cookie 4. Select the amount of days before the cookie expires 5. Select the correct cookie provider from the drop down menu, or add a new provider if you cannot find the correct cookie provider in the menu 6. Click on the green button “Save cookie” --- # 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/cookie-widget/how-to-manually-add-any-cookies.md?ask=&goal= ``` `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.