ConsentPress — Help & Documentation
Setup, Consent Mode, script blocking, shortcodes, and troubleshooting.
1) Quick start (5 minutes)
- Install & activate the plugin.
- Open ConsentPress → Pixels & GTM and add your GTM container ID (optional: Facebook/LinkedIn). For multi-domain/WPML, map per domain.
- Open ConsentPress → Cookie Settings: choose position, layout, font, button style, accent color, retention, and log privacy.
- Open ConsentPress → Cookie Definitions: click Scan Browser Cookies, auto-label, adjust categories/purpose, then Save Definitions.
- (Optional) Add the front-end cookie table to your policy page:
[cpc_cookie_table]
- Test in a private window: interact with the banner and verify entries in ConsentPress → Consent Logs.
2) Google Tag Manager & Consent Mode v2 (no GTM triggers required)
ConsentPress sends a Consent Mode default (denied) before GTM loads, then a consent update after the user chooses. GA4/Ads respect these signals automatically—no extra triggers needed.
Setup
- Enter your GTM ID in ConsentPress → Pixels & GTM.
- Ensure only ConsentPress injects GTM (avoid duplicates).
Signals sent
- Default (before GTM):
ad_storage
,analytics_storage
,ad_user_data
,ad_personalization
=denied
;functionality_storage
,security_storage
=granted
. - Update (after choice): values reflect granted/denied for each category.
Verify
Use GTM Preview/Tag Assistant → Consent tab to confirm default & update events match your selection.
3) Appearance (banner)
- Position: top / bottom / center modal / floating left / floating right
- Layout: full / centered / compact / minimal
- Typography: theme default / system / serif / sans; sizes: small / normal / large
- Buttons: filled / outline / subtle; radii: sharp / rounded / pill
- Overlay: none / dim / dim + lock scroll
- Labels & links: Accept, Decline, Manage, Save, Learn more; pick a target page
- Custom CSS (scoped to the banner)
A live preview updates as you edit settings.
4) Cookie definitions (hybrid)
- Click Scan Browser Cookies (front-end only).
- Auto-labeling uses a local registry and optional Open Cookie Database lookups.
- Edit: type, purpose, provider, duration, domain/path.
- Save Definitions writes
assets/data/cookie-definitions.json
(the banner & shortcode use this file).
5) Script Manager (autoblocking)
- Vendor templates: toggle enable/disable, default category per vendor (e.g., Marketing for Meta/LinkedIn; Analytics for Hotjar).
- Advanced rules (one per line): substring or
/regex/flags → category
. Example:connect.facebook.net → marketing /hotjar\.com/i → analytics
These rules prevent non-Google scripts from running until consent is granted. If you use GTM for Google tags, prefer Consent Mode; Script Manager is a fallback for everything else.
6) Shortcodes
Cookie definitions table
[cpc_cookie_table]
Add this to your privacy/cookie policy page to display a categorized table.
Consent gate wrapper
[cpc_consent_gate category="marketing"]
<iframe src="https://www.youtube.com/embed/..."></iframe>
[/cpc_consent_gate]
If consent isn’t granted for category
, a prompt is shown instead of the embed.
7) Consent logs & retention
- Logs: time, (anonymized) IP, (hashed) UA, domain, preferences
- Export CSV from the Logs page
- Retention: 1 / 3 / 6 / 13 months (daily WP-Cron cleanup)
- Storage: internal WP DB or external MySQL (auto-create when credentials are valid)
- Privacy mode: default = anonymize IP & hash UA; you can switch to full logging if you have a legal basis
8) Translations
Translation-ready (.pot
included) and ships with German, Dutch, Spanish, and French. Works with WPML/Polylang (per-domain pixel/GTM IDs supported).
9) Troubleshooting
Banner doesn’t show on first visit
- Check “Default Category Consent.” If you pre-grant categories, your site may treat consent as completed.
- Ensure your theme doesn’t hide the banner container with CSS.
Tag Assistant: “EEA consent missing”
- Confirm the plugin pushes default denied before GTM, and
gtag('consent','update', ...)
after choice. - Include all v2 keys:
ad_storage
,analytics_storage
,ad_user_data
,ad_personalization
,functionality_storage
,security_storage
.
Third-party cookie warnings
Those cookies are set by third-party domains. You cannot change them—block the vendor script until consent, or consider server-side/first-party alternatives.
JSON not updating
We append a version querystring. If needed, purge cache/CDN.
10) Advanced & Debug
- Debug Mode (Tools): verbose console logs; includes system cookies in scans.
- Optional cleanup: delete common first-party analytics/marketing cookies on revoke (toggle in Tools).
11) Uninstall
Deleting the plugin removes the internal table, options, and scheduled tasks. External DB tables are not modified.
12) FAQ
Do I need GTM templates or consent triggers? No. ConsentPress handles the Consent Mode defaults and updates. Use Script Manager for non-Google vendors.
Will it work after third-party cookies are gone? Yes. Consent applies to first-party cookies, localStorage, fingerprinting, and pings. Consent Mode + Script Manager keep you compliant.
How do I set per-domain GTM/Pixel IDs? In Pixels & GTM → domain mapping table.
13) Support
Docs & updates: https://consentpress.com
Email: support@consentpress.com
Include WP version, plugin version, a site link, and (if possible) a Tag Assistant recording.