LogoLogo
Analytics HelperSirdata APISemantic APIA propos de Sirdata
English
English
  • Sirdata CMP
  • INSTALL
    • Web & Mobile web
    • AMP
    • Via a Tag Manager
      • Loading via Google Tag Manager
      • CMP ABconsent default settings
    • In a CMS
      • Loading in Shopify
      • Loading in Wordpress
      • Loading in Prestashop
      • Loading in Magento
      • Loading in Drupal
    • Cache Systems Exclusion
      • Autoptimize WordPress Plugin
      • Cloudflare WordPress Plugin
      • LiteSpeed WordPress Plugin
      • NitroPack WordPress Plugin
      • SG Optimizer WordPress Plugin
      • WP Super Cache WordPress Plugin
      • W3 Total Cache WordPress Plugin
      • WP Meteor Plugin for Wordpress
      • WP Rocket WordPress Plugin
    • Quick configuration
  • CONSENT TRANSMISSION STANDARDS
    • Introduction
    • Google Consent Mode
      • Mandatory Prerequisite
      • Activation of Advanced Google Consent Mode
        • Via the Sirdata CMP
        • Via Google Tag Manager
      • Activation of Basic Google Consent Mode
        • Via the Sirdata CMP
        • Via Google Tag Manager
      • Activation via Sirdata CMP
      • Activation via Google Tag Manager
    • Microsoft UET Consent Mode
    • Microsoft Clarity Consent
  • CMP API
    • How it works
    • Examples
    • Working with iframes
  • Advanced features
    • Passive mode
    • Set language per user
    • Manually display the CMP
  • Script management
    • Remote Tags Management without a Tag Manager
    • Remote Tags Management with a Tag Manager
    • Tag Management with Google Tag Manager
    • Local script Management
    • Advanced configuration
    • Examples
    • Share the TC String
    • Tag Management setup service
  • Analytics
    • Google Analytics
  • F.A.Q.
    • Integration
      • Is Abconsent compatible with Stape?
      • Is ABConsent compatible with Addingwell?
    • Google Consent Mode V2
      • Google Consent Mode V2 utility
      • News Google Consent Mode V2
      • Advanced mode or basic mode
    • Packaging
      • Cookies management
      • Tags packaging
    • Cookie settings
    • Button operation
    • Button color
    • A/B test
    • Mobile, tablets ...
    • Multi-sites
    • Mobile display
    • Private browsing
    • AMP consent
    • AMP consent button
    • Tags conditionning
    • Google Ads
    • Error 6.1 Google
    • Google PageSpeed
    • Refusal & Targeted ads
    • Mozilla and adblocks
    • Wordpress, Joomla, etc ...
    • Shopify
    • Pricing
      • The Two Types of Licenses
      • What happens when I reach the limit of my monthly plan?
      • Do you offer a trial period?
      • What are the accepted payment methods?
      • Do you offer packages for very high volumes of hits?
      • Are unused hits carried over to the next month?
      • What is considered a Hit?
      • Can I change plans?
    • Content Security Policy (CSP)
    • Google
      • Problem gclid google
      • Google extensions
    • How to Verify the Integration of My CMP?
    • How to Identify the Cookies Present on Your Website?
    • Abconsent CMP is compatible with Taggr ?
  • CMP Services
    • CMP Configuration
    • CMP Integration
    • Tag Conditioning
    • Compliance audit
    • Extra-vendorlist
    • Video-Wall
    • Inventory Partners
    • Consulting
  • Links
    • Configure your CMP
    • Sirdata API
    • Semantic API
    • About Sirdata
    • Analytics Helper
Propulsé par GitBook
Sur cette page

Cet article vous a-t-il été utile ?

  1. INSTALL
  2. Via a Tag Manager

CMP ABconsent default settings

PrécédentLoading via Google Tag ManagerSuivantIn a CMS

Dernière mise à jour il y a 1 jour

Cet article vous a-t-il été utile ?

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.