內容簡介
Global Consent Gate 是一款可自訂的 Cookie 機制與隱私選擇面板外掛，旨在協助 WordPress 網站滿足 Cookie 和追蹤同意的需求。雖然無法保證法律合規，但提供了靈活的選項以管理訪客的隱私選擇。
【主要功能】
• 可自訂的 Cookie 機制與隱私選擇面板
• 支援 Google Analytics 4 和 Meta Pixel 整合
• 訪客可隨時變更同意選擇
• 提供多種圖示與顏色自訂選項
• 無需前端 JavaScript 框架或外部服務
外掛標籤
開發者團隊
② 後台搜尋「Global Consent Gate – Cookies and Tracking」→ 直接安裝（推薦）
原文外掛簡介
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:
Necessary technologies can run immediately.
Preferences, Analytics and Marketing are off until the visitor grants that category.
Accept All and Reject Non-essential are equally prominent by default.
Visitors can reopen the panel and withdraw/change choices.
Choose a cookie, shield or sliders icon, text or both; customize its colors, size, spacing and side.
Settings are organized into General, Appearance, Text & links, Integrations, Records and About tabs.
Global Privacy Control (GPC) forces Marketing off when enabled.
Google Consent Mode v2 can be set to denied before supported tags and updated after the choice.
Optional pseudonymous consent receipts can be stored locally in WordPress.
No front-end JavaScript framework, jQuery dependency, remote CSS, remote fonts or external service is required by the plugin itself.
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.
External services
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.
Google Analytics 4
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
Meta Pixel
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.
Privacy
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:
random consent ID;
UTC timestamp;
action taken;
selected categories;
policy version;
selected legal profile;
one-way HMAC hash of the browser user-agent.
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.
Translation
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.
Developer integration
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.
