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

WP Super Cache WordPress Plugin

WP Super Cache is a popular caching plugin for WordPress that generates static HTML files for faster page loading. To ensure the proper functioning of Sirdata CMP scripts, it’s essential to exclude them from caching and other optimizations.


Steps to Exclude Sirdata CMP Scripts in WP Super Cache

  1. Access WP Super Cache Settings

    • Log in to your WordPress Admin Dashboard.

    • Navigate to Settings > WP Super Cache.

  2. Disable Caching for Sirdata CMP Scripts

    • Go to the Advanced tab in WP Super Cache settings.

    • Scroll to the Accepted Filenames & Rejected URIs section.

    • In the field labeled "Add here strings (not a filename) that forces a page not to be cached", add the following domains or scripts:

      .consentframework.com
      .abconsent.net
  3. Exclude Pages Using Sirdata CMP Scripts (if necessary)

    • If specific pages rely on Sirdata CMP scripts, add their URLs to the "Rejected URIs" field. For example:

      /page-with-cmp
  4. Save Changes

    • After adding the exclusions, click Save Settings to apply the changes.

  5. Clear the Cache

    • In the WP Super Cache settings, go to the Contents tab.

    • Click on Delete Cache to ensure the exclusions take effect immediately.

  6. Verify the Exclusions

    • Test your website to ensure that the Sirdata CMP scripts are working correctly. Use browser developer tools to verify that the scripts are being loaded properly and are not cached.


Why Exclude Sirdata CMP Scripts?

  • Dynamic and Geolocated Behavior: Sirdata CMP scripts dynamically adapt based on the user’s location and preferences. Caching these scripts can result in outdated or incorrect content being served.

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


By following these steps, WP Super Cache will exclude Sirdata CMP scripts from its caching processes, ensuring proper functionality and compliance.

PrécédentSG Optimizer WordPress PluginSuivantW3 Total Cache WordPress Plugin

Dernière mise à jour il y a 6 mois

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