
Global Consent Gate by INformigados provides a customizable cookie banner and privacy choices panel. It is designed to assist a WordPress site with cookie/tracking consent requirements. It does not and cannot guarantee legal compliance. Legal obligations depend on your jurisdiction, sector, users, technologies, vendors, purposes and current law.
The default “Global Strict” configuration takes a conservative approach:
The built-in integrations accept only a Google Analytics 4 Measurement ID or a numeric Meta Pixel ID. No custom JavaScript, HTML snippets, arbitrary URLs or tag-manager containers can be entered. Both services are disabled by default. Preferences remains available through the consent API for integrations implemented separately by developers.
Blocking applies only to the built-in integrations. Remove duplicate trackers inserted by themes, tag managers or other plugins. Existing custom snippet fields from development builds are ignored and removed when settings are saved; they are not converted automatically.
The consent interface works without external services. Optional integrations connect visitors directly to the following services only when an administrator configures an ID and the visitor grants the corresponding category. Service requests expose the visitor’s IP address and browser/network metadata to the provider.
Loads gtag.js from www.googletagmanager.com after Analytics consent and configures your Measurement ID for page measurement. Google may collect page URLs, referrers, device/browser information, identifiers and usage events according to your Google property settings. Google Signals and advertising personalization are disabled in this plugin’s configuration. Consent Mode v2 signals do not load Google by themselves. Review your Google tag destinations and enhanced measurement settings separately.
Terms: https://marketingplatform.google.com/about/analytics/terms/us/
Privacy: https://policies.google.com/privacy
Loads fbevents.js from connect.facebook.net after Marketing consent and sends a PageView event for your Pixel ID. Meta may receive page URLs, referrers, browser/device information and cookie identifiers for advertising measurement. This plugin does not configure advanced matching. GPC blocks this integration when honoring GPC is enabled.
Terms: https://www.facebook.com/legal/technology_terms
Privacy: https://www.facebook.com/privacy/policy/
Global Consent Gate is not a Google-certified CMP or an IAB TCF implementation. Consent Mode signalling does not provide certification or guarantee compliance with advertising platform requirements.
The plugin uses localStorage key infoglco-choice-changed to notify other open tabs when choices change. This contains only a change timestamp.
The first-party cookie infoglco_consent stores a random consent identifier, policy version, timestamp and category choices so the site can remember the visitor’s decision.
Receipts are disabled by default. If server-side consent receipts are enabled, the plugin records:
The receipt system does not intentionally store the visitor’s raw IP address. WordPress/server infrastructure may independently log network data outside this plugin.
Configure receipt retention in Settings > Global Consent Gate. A daily cleanup task removes older receipts. You can export the latest 10,000 receipts or clear all receipts in the Records tab. Records are visitor-reported, not verified identity or tamper-proof evidence. An expired nonce on a cached page may prevent a receipt from being saved; the visitor choice still works.
Withdrawal reloads the page to stop supported integrations on subsequent loads. It does not erase third-party cookies or data already sent. Choose whether to retain or delete plugin data on uninstall in the Records tab.
The default user-facing language is English. All fixed plugin strings use the informigados-global-consent-gate text domain. A POT template is included in /languages/. Banner/category text is also editable directly in settings, allowing localized wording without modifying code.
The pre-directory build used shorter identifiers. Settings and receipt storage are migrated to the infoglco prefix. Visitors are asked for consent again because the cookie name changed. Update custom integrations to the API below and clear page/CDN caches after replacing the plugin.
JavaScript event:
window.addEventListener('infoglco:consent', function (event) { console.log(event.detail); });
JavaScript API:
window.INFOGLCOConsentGate.hasConsent('analytics')
window.INFOGLCOConsentGate.getConsent()
window.INFOGLCOConsentGate.open()
PHP helper (reads the request consent cookie):
infoglco_has_consent('analytics')
PHP honors the Sec-GPC request header when present. Browser-only GPC signals are available through the JavaScript API. Avoid using request cookies to personalize full-page cached responses without an appropriate cache strategy.