Quick configuration

🛠️ Default Behavior of Quick Configuration

When you create a quick configuration in the platform, the interface comes pre-configured with several common settings and integrations already enabled to ensure compliance and maximize interoperability out of the box.

✅ Enabled by Default

The following options are activated automatically when a quick configuration is created:

---

1. Pre-selected Vendor Integrations

The following major platforms are pre-configured and enabled by default:

• Google Advertising & Analytics

• Microsoft Advertising & Microsoft Clarity

• Meta / Facebook

These vendors are declared for transparency and are active immediately, so that consent signals can be collected and shared with them.

The consent banner includes the appropriate purposes of processing aligned with them.

---

2. Relevant Purposes Are Declared

The consent banner includes the appropriate purposes of processing aligned withthe declared Vendors.

Each purpose (e.g. ad personalization, analytics, audience measurement) is properly linked to vendors, and declared accordingly in the UI.

---

3. Google Consent Mode Enabled

The Google Advanced Consent Mode is automatically:

• enabled,

• connected to Google Tag Manager and "dataLayer" global variable,

• and configured to use consent signals for analytics_storage,ad_storage , ad_personalization, ad_user_data, personalization_storage, functionality_storage, and security_storage.

This ensures compatibility with Google Ads, GA4, Google Merchant Center, Floodlight, etc. and allow data modelization.

---

4. Microsoft Consent Mode Enabled

The Microsoft UET Consent Mode is also enabled by default, which allows Microsoft Ads to defer tracking until consent is granted.

---

5. Microsoft Clarity Consent Mode Enabled

The Microsoft Clarity Consent Mode is also enabled by default, which allows Microsoft Clarity to defer tracking until consent is granted.

---

6. IAB TCF Framework Activated

The Transparency and Consent Framework (TCF) by IAB Europe is enabled, and:

• a valid TC string is generated,

• all declared vendors are mapped according to the latest TCF version,

• purpose and legal basis are communicated to vendors in compliance with GDPR.

---

7. Consent Withdrawal / UI Resurfacing Available

An inline or persistent control is added by default to allow:

• users to change their consent or withdraw it at any time,

• from a floating icon, footer link, or button (based on the selected design).

This improves UX and ensures compliance with regulations requiring "easy withdrawal".

---

🔧 Customization

All default options can be customized in the portal:

• You can add or remove vendors, toggle platforms like Meta or TikTok,

• You can enable or disable Consent Modes,

• You can disable or modify the design and placement of the UI resurfacing element.

---

✅ This default setup ensures fast deployment with privacy compliance and ecosystem compatibility, while remaining fully editable according to your needs.