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
  2. Cache Systems Exclusion

Cloudflare WordPress Plugin

The Cloudflare plugin for WordPress allows easy integration and configuration of Cloudflare’s services, including caching and resource optimization. To ensure the proper functionality of Sirdata CMP scripts, it’s crucial to exclude them from caching and optimization processes.


Steps to Exclude Sirdata CMP Scripts in the Cloudflare Plugin

  1. Access Cloudflare Plugin Settings

    • Log in to your WordPress Admin Dashboard.

    • Go to Settings > Cloudflare.

  2. Configure Cache Exclusions

    • In the plugin interface, click on Page Rules in the Cloudflare dashboard.

    • Click Create Page Rule.

    • In the URL field, enter the following domains or paths to exclude them from caching:

      *consentframework.com/*
      *abconsent.net/*
    • Under the rule settings, choose Cache Level: Bypass.

  3. Disable Automatic Optimizations

    • Navigate to the Speed tab in the Cloudflare plugin.

    • Disable features like Auto Minify for JavaScript, CSS, and HTML if they are enabled.

  4. Add Specific Rules for Sirdata Scripts (if applicable)

    • If specific optimizations are enabled (e.g., Cloudflare’s Rocket Loader), you can exclude Sirdata scripts.

    • Go to Settings > Optimization in the Cloudflare dashboard.

    • Disable Rocket Loader or add an exclusion for Sirdata scripts using the data-cfasync="false" attribute in the script tag.

  5. Save and Apply Changes

    • After configuring the exclusions, click Apply Settings to save the changes.

  6. Purge Cache

    • In the Cloudflare plugin, navigate to the Cache tab.

    • Click Purge Everything to clear the cache and immediately apply the new rules.

  7. Verify Exclusions

    • Test your website to ensure that the Sirdata CMP scripts are functioning correctly. Use tools like browser DevTools to confirm that the scripts are loading without interference.


Why Exclude Sirdata CMP Scripts?

  • Dynamic and Geolocated Behavior: Sirdata CMP scripts dynamically adapt to users’ locations and preferences. Caching or optimizing these scripts can result in incorrect or outdated content being served.

  • Regulatory Compliance: These scripts are critical for adhering to privacy regulations. Any interference from caching or optimization may lead to non-compliance, complaints, or revenue loss.


By following these steps, the Cloudflare plugin will exclude Sirdata CMP scripts from caching and optimization processes, ensuring proper functionality and compliance.

PrécédentAutoptimize WordPress PluginSuivantLiteSpeed WordPress Plugin

Dernière mise à jour il y a 6 mois

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