> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/fr/fonctionnalites/sources/sources-catalog/web/containers/best-practices/tms-and-consent-banners-ids.md).

# IDs des bannières TMS & Consent

Voici comment récupérer les IDs des sites, des containers et de la privacy.

## ID du site et des Containers / versions

Pour pouvoir récupérer votre ID du site et les IDs des Containers, vous devez ouvrir votre DevTool sur votre navigateur et saisir

```
tC.containersLaunched
```

<figure><img src="https://3282103337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-4b13884c9364323d1aad8ef0ff5faeaa9876156e%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

**Ci-dessus :**

* **ID du site** : 4505
* **IDs des Containers** :
  * 20 *(version 155.04)*
  * 21 *(version 32.01)*

## Privacy ID et Privacy Version

Pour pouvoir récupérer votre Privacy ID et votre Privacy Version, vous devez ouvrir votre DevTool sur votre navigateur et saisir

```
tC.PrivacyID
```

```
tC.PrivacyVersion
```

<figure><img src="https://3282103337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-11042bd8cd896c4a3b07cac41e9454e48c8c077f%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

**Ci-dessus :**

* **Privacy** **ID** : 12
* **Privacy Version** : 005


---

# 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.commandersact.com/fr/fonctionnalites/sources/sources-catalog/web/containers/best-practices/tms-and-consent-banners-ids.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.