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

SG Optimizer WordPress Plugin

SG Optimizer is a performance optimization plugin provided by SiteGround to enhance website speed and efficiency. To ensure the proper functionality of Sirdata CMP scripts, it’s essential to exclude them from SG Optimizer’s caching and optimization processes.


Steps to Exclude Sirdata CMP Scripts in SG Optimizer

  1. Access SG Optimizer Settings

    • Log in to your WordPress Admin Dashboard.

    • Navigate to SG Optimizer in the left-hand menu.

  2. Exclude Sirdata CMP Scripts from JavaScript Optimization

    • In the Frontend Optimization tab, locate the Exclude JavaScript Files section.

    • Add the following entries (one per line):

      .consentframework.com
      .abconsent.net
  3. Exclude Sirdata CMP Scripts from Caching

    • Go to the Caching tab in SG Optimizer.

    • Under Exclude URLs from Caching, add any pages where Sirdata CMP scripts are critical, or use the following patterns to exclude scripts directly:

      *consentframework.com*
      *abconsent.net*
  4. Disable Additional Optimizations (if applicable)

    • If features such as Minify JavaScript or Combine JavaScript Files are enabled, ensure the scripts listed above are excluded from these processes. You can manage this in the Frontend Optimization tab.

  5. Purge Cache

    • After making changes, return to the Caching tab.

    • Click Purge Cache to clear all cached files and ensure the new rules are applied.

  6. Test the Exclusions

    • Visit your website and verify that Sirdata CMP scripts are working as expected. Use browser DevTools to ensure these scripts are loading correctly without interference.


Why Exclude Sirdata CMP Scripts?

  • Dynamic and Geolocated Behavior: Sirdata CMP scripts dynamically adapt based on user location and preferences. Optimizing or caching these scripts can lead to incorrect or outdated behavior.

  • Regulatory Compliance: These scripts are essential for meeting privacy regulations. Any interference caused by caching or optimization may result in non-compliance, complaints, or loss of revenue.


By following these steps, SG Optimizer will exclude Sirdata CMP scripts from its caching and optimization processes, ensuring proper functionality and compliance.

PrécédentNitroPack WordPress PluginSuivantWP Super Cache WordPress Plugin

Dernière mise à jour il y a 5 mois

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