> 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/consent-proof.md).

# Collect proof of cookie consent

Learn how to collect, view and export proof of cookie consent with Dastra, and how to follow the banner statistics.

Once the cookie consent banner is installed on your website, the **Cookie consent** module collects, keeps and exports **proof of consent**. It also shows the **statistics** of the banner.

## Prerequisites

You must have installed the banner on your website.

{% content-ref url="/pages/-M378oB2HodWBFfDdJsg" %}
[Set up the cookie consent banner](https://doc.dastra.eu/en/features/cookies/banner/configure.md)
{% endcontent-ref %}

## View the proof of consent

Once the banner is installed, Dastra automatically collects proof of consent from the visitors of your website. To view it:

1. In the menu, click **Cookie consent** > **Cookie consents**.
2. Use the filters above the list: the period (the last 7 days by default), the banner (**All banners**) and, once a banner is chosen, the consented services.
3. Click a row to open the proof.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a288cbc2b383ca61c372f28c433c73c7efa6f978%2Fcookies-consent-proof-1.png?alt=media" alt="The list of consents with the period and banner filters"><figcaption><p>The list of consents</p></figcaption></figure>

The cookie consent proof shows the date, the country, the consent fingerprint and the list of services, each marked **Consented** or **Refused**. You can print or delete it.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-9e50fe6a8e06a34101891555ee70abfd20751f5a%2Fcookies-consent-proof-2.png?alt=media" alt="The detail of a proof of consent"><figcaption><p>The detail of a proof of consent</p></figcaption></figure>

From the list, the **Export** button downloads the proof for the selected period and banner. To delete proof, use the row menu or the **Delete** batch action.

The lifespan of the proof of consent is one year.

{% hint style="info" %}
The collection of proof depends on the **Save consent proof** option in the **Settings** section of the banner. When it is disabled, no proof is kept. To match a proof with a user of your system, see [User identification](https://doc.dastra.eu/en/features/cookies/integration/identification.md).
{% endhint %}

## View the statistics

The **Reporting** page follows the activity of your banners.

1. In the menu, click **Cookie consent** > **Reporting**. You can also open the menu of a banner in the list of banners and choose **Stats report**.
2. Choose the period (the last 7 days by default) and, if needed, a banner in **All banners**.

Three charts are displayed, each compared with the previous period:

* **Collected consents**: the volume of choices recorded, with the **Total**, **Full consent**, **Partial consent** and **Refused** indicators;
* **Widget's display**: the number of sessions during which the banner was displayed. The counter increases once per visitor session, and a session lasts at least one hour;
* a third chart counts the times a visitor closed the banner with the close cross.

{% hint style="info" %}
In preview mode, no statistics are collected. Displays are also not counted when the **Save consent proof** option is disabled.
{% endhint %}

To actually apply visitors' choices on your website, go to the next page:

{% content-ref url="/pages/-M4IkkyAbXfmeKH-g7Bb" %}
[Go further on cookie consent](https://doc.dastra.eu/en/features/cookies/banner/go-further.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/consent-proof.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.
