> 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/integration/identification.md).

# User identification

This page explains how to trace the organization's internal identifiers in the proof of consent.

## How it works

You send the **unique identifier of the authenticated user** of your intranet to the Dastra banner, which passes this identifier when collecting the user's consent. You can then match the proof of consent with your customer base (CRM, customer repository, etc.). The identifier you passed is displayed in the area where you view proof of consent.

## Step 1: Choose the user ID

To make this match, choose a pseudonymous identifier to pass to the banner, such as the customer's internal ID or CRM ID. This variable must be available in the web page and is sent in plain text: it must not contain any direct personal data (last name, first name, email address), not even base64-encoded, since base64 can be reversed.

## Step 2: Adapt the integration code

```html
<div id="cookie-consent"></div>
<script src="https://cdn.dastra.eu/sdk/dastra.js?key={YOUR PUBLIC KEY HERE}" async></script>
<script>

// Dastra's array initialization
window.dastra = window.dastra || [];

// Load the cookie consent in page
dastra.push(['loadCookieConsent', {
    widgetId: {Paste your widgetId here (digit)},
    selector: '#cookie-consent',
    userId: '{your user pseudonymous id}'
}]);
</script>
```

{% hint style="info" %}
Depending on the hosting region of your organization, the address of the script changes (`cdn-bleu.dastra.eu` instead of `cdn.dastra.eu`). Use the address of the code copied from the **Installation** section of the banner.
{% endhint %}


---

# 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/integration/identification.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.
