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
    • 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
  • 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

Cache Systems Exclusion

The CMP (Consent Management Platform) scripts provided by Sirdata are critical resources designed to be geolocated and customized for each user. This ensures that it adapts dynamically to the user’s location and preferences, delivering an experience that is both precise and fully compliant with evolving privacy regulations.

Due to the critical nature of this script in managing user consent and ensuring compliance with regulatory frameworks, it is vital that only the latest version of the script is served at all times. Using an outdated version could lead to serious consequences, including regulatory violations, improper consent management, and even revenue losses.

For this reason, Sirdata explicitly prohibits caching or modifying our CMP scripts in any way. These prohibitions are clearly outlined in our General Terms and Conditions (GTC). Modifying or caching the script introduces the risk of serving an outdated or incorrect version, which may no longer reflect updates, new functionalities, or regulatory adjustments. Such changes could compromise the effectiveness of the CMP and expose your organization to non-compliance risks.

Sirdata takes full responsibility for managing the script delivery process. We leverage industry-leading Content Delivery Networks (CDNs), including Cloudflare and BunnyCDN, to ensure optimal script performance. These CDNs are trusted globally for their speed, reliability, and robust security, enabling us to deliver the most up-to-date version of the CMP script to users worldwide without latency or reliability issues.

By relying on our proven and secure infrastructure, you can trust that the CMP script will always be compliant, high-performing, and secure. To ensure this level of quality and trust, we require all partners and clients to refrain from modifying or caching the script, as stipulated in our T&C. This policy is in place to protect you, your users, and the integrity of the CMP system.

Do not cache or modify Sirdata’s CMP script. Let Sirdata handle the delivery and updates, ensuring the highest levels of compliance, performance, and user trust at all times.

PrécédentLoading in DrupalSuivantAutoptimize WordPress Plugin

Dernière mise à jour il y a 5 mois

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