# CMP ABconsent default settings

<figure><img src="/files/tY5yrfbUjGlLJcrXaakF" alt="" width="375"><figcaption></figcaption></figure>

When setting up a new configuration in the **ABconsent by Sirdata** CMP, several default settings are applied to ensure optimal compliance and user experience. These defaults are detailed below and can be fully customized via the administration interface.

***

#### 1. **Cookie and Tag Blocking**

**🛑 Automatic Blocking**

* Cookies and trackers that require consent (e.g., Google, Microsoft) are **automatically blocked** until valid and explicit consent is given.
* Only **strictly necessary** cookies or those **not subject to consent** are allowed by default.

**🔧 Tagging Methods**

* **Automatic tagging** (auto-blocking) is enabled for many standard services.
* **Manual tagging** is also supported via `type="text/plain"` and the `data-consent` attribute for more granular control.

***

#### 2. **Recommended Integration Method**

**⚙️ Integration Mode**

* For optimal performance, the CMP should be implemented **in the page header**:
  * either via the **provided JavaScript script**,
  * or through **Google Tag Manager** using the dedicated template.

***

#### 3. **Banner Behavior**

**⏳ Consent Expiry**

* Consent is valid for **180 days** by default, in line with CNIL recommendations.
* This duration can be **customized** in the admin interface.

**✅ Consent Type**

* The CMP uses **explicit consent**: **no non-essential cookies** are set until the user makes a choice.

**🌍 Geographic Targeting**

* By default, the banner is shown only to visitors located in the **European Economic Area (EEA)**, the **United Kingdom**, and **Switzerland**.
* A specific banner is displayed to visitors covered by the **CCPA/CPRA** regulations.
* An option is available to **display the banner to all visitors**, regardless of location.

***

#### 4. **Banner Content and Customization**

**🗣️ Language**

* The banner language is automatically set based on the **browser language**.
* Standard texts are provided in **English** and **French**, and can be **customized to match your brand’s tone**.

**🧭 Banner Type**

* The default format is a **granular multi-choice** banner with access to **purposes** and **partners**.
* Alternative formats include:
  * “Accept / Reject”
  * “Accept / Customize / Reject”
  * “Continue without accepting”

**📂 Purpose Categories**

* Purposes are grouped according to the **TCF v2.2** standard: storage, personalization, measurement, advertising, etc.
* **No category is pre-selected** by default (except strictly necessary cookies).

***

#### 5. **Banner Layout and Design**

**📍 Position**

* By default, the banner appears **centered on the screen**.
* This can be **customized via the ABconsent console**.

**🎨 Visual Theme**

* The default theme is **light**, and it adapts to the user’s browser theme.
* Other options are available: **dark**, **custom**, etc.

**🖱️ Button Text**

* Default buttons:
  * “Accept All”
  * “Manage Your Preferences”
  * “Continue without Accepting”
* Button labels are **fully customizable** via the admin console.

**❌ Close Icon**

* By default, **no close button** is displayed (except in certain modal formats).
* A user choice acts as a closing action.
* An optional **close button** can be enabled via the admin interface.

***

#### 6. **Additional Information**

* All of the above settings can be **modified through the CMP administration interface**.
* The **ABconsent CMP is IAB Europe certified** and compliant with **TCF v2.2** standards.
* A **developer documentation** is available for advanced or custom integration use cases.


---

# Agent Instructions: 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:

```
GET https://cmp.docs.sirdata.net/en/install/via-a-tag-manager/cmp-abconsent-default-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.