This comprehensive FAQ addresses the most frequently asked questions about DigiConsent, covering installation, configuration, compliance, troubleshooting, and advanced usage. Whether you’re just getting started or looking to solve a specific issue, you’ll find clear, practical answers to help you use DigiConsent effectively.
Installation and Setup Questions
Do I need to deactivate my current cookie consent plugin before installing DigiConsent?
Yes, running two cookie consent plugins simultaneously creates conflicts and a confusing user experience. Before activating DigiConsent, deactivate and uninstall any existing cookie consent plugins. After DigiConsent is configured and tested, you can safely remove the old plugin completely.
Will DigiConsent work with my theme?
DigiConsent works with all properly coded WordPress themes. The only requirement is that your theme includes the wp_footer() function call in its footer template, which is a WordPress standard that all valid themes must meet. DigiConsent has been tested with popular themes from ThemeForest, Elegant Themes, and the WordPress.org repository.
Does DigiConsent work with page builders like Elementor or Divi?
Yes, DigiConsent is fully compatible with all major page builders including Elementor, Divi, Beaver Builder, WPBakery, Oxygen, and Bricks. The consent banner operates independently of page content and doesn’t interfere with page builder functionality.
I installed DigiConsent but don’t see the banner on my website. What’s wrong?
Several common causes: (1) You already have a consent cookie saved from testing—try viewing in incognito/private mode. (2) Your caching plugin hasn’t cleared the cache—clear all caches including WordPress, server, and CDN caches. (3) JavaScript errors from other plugins are preventing DigiConsent from loading—check your browser console for errors. (4) Your theme doesn’t include wp_footer()—verify this function exists in your theme’s footer.php file.
Configuration and Settings Questions
Which consent mode should I choose: opt-in, opt-out, or notice-only?
For most websites, choose opt-in mode. This is required if you have any visitors from the European Union and is the safest choice for compliance. Opt-in blocks all non-essential cookies until users explicitly consent. Only use opt-out if you’ve confirmed with legal counsel that it meets your obligations and you don’t serve EU visitors. Notice-only should only be used if you truly have no tracking cookies whatsoever—which is rare for modern websites.
What’s the difference between the four cookie categories?
Necessary: Essential cookies the website cannot function without (sessions, security, shopping cart). Users cannot disable these and consent isn’t required. Analytics: Cookies that track website usage to help you understand visitor behavior (Google Analytics, Hotjar). Require consent. Marketing: Cookies for advertising and tracking across websites (Facebook Pixel, Google Ads). Require consent. Functional: Cookies that enable enhanced features like live chat or social widgets. Require consent.
Should I put Google Analytics in the Necessary category so it always loads?
No, absolutely not. This violates GDPR and defeats the purpose of consent management. Google Analytics is not necessary for your website to function—it’s an analytics tool that requires consent. Placing optional tracking in the Necessary category is one of the most common compliance violations that regulators specifically look for during audits. Always put analytics tools in the Analytics category.
Can I change the consent mode after my site is already live?
Yes, you can change the consent mode at any time in Settings. However, understand the implications: switching from opt-out/notice-only to opt-in makes your site more privacy-protective (safe direction), but switching from opt-in to opt-out reduces privacy protection and may violate user expectations or regulations. If you must change modes, clear all caches and test thoroughly to ensure the new mode works correctly.
How do I add my Google Analytics tracking code?
Go to DigiConsent → Settings → Cookie Categories → Analytics tab. If you’re using Google Analytics 4 directly (not through Tag Manager), enter your GA4 Measurement ID (starts with G-XXXXXXXXXX) in the “Google Analytics 4” Quick Add field. DigiConsent will automatically generate the correct tracking code. If you’re using Google Tag Manager, enter your GTM container ID (GTM-XXXXXXX) in the GTM Quick Add field instead and manage GA4 inside GTM. Don’t use both fields—choose one approach.
What is Google Consent Mode v2 and should I enable it?
Google Consent Mode v2 is a framework that allows Google services (Analytics, Ads, Tag Manager) to adjust their behavior based on user consent. When enabled, Google can still collect some anonymized, aggregated data even when users reject cookies, using privacy-preserving measurement techniques. Enable it if you use any Google services—it provides better analytics coverage while respecting privacy. Set the default state to “Denied” for GDPR compliance.
Compliance and Legal Questions
Does DigiConsent make my website GDPR compliant?
DigiConsent handles the cookie consent aspect of GDPR compliance, but GDPR is much broader than just cookies. Full GDPR compliance also requires: a comprehensive privacy policy, data processing agreements with third parties, procedures for handling user rights requests (access, deletion, portability), data breach notification processes, and more. DigiConsent is an essential tool for compliance, but it’s one part of a larger compliance program.
Do I need a privacy policy in addition to DigiConsent?
Yes, absolutely. The consent banner provides brief information about cookie usage, but GDPR and other regulations require a detailed privacy policy that explains: what data you collect, why you collect it, how you use it, who you share it with, how long you keep it, and users’ rights regarding their data. DigiConsent includes a privacy policy link field—make sure you create a comprehensive privacy policy and link to it.
How long should I keep consent logs?
Most privacy experts recommend keeping consent logs for at least as long as you process data under that consent, plus 3-6 years afterward to cover potential legal challenges. Many organizations keep consent logs for 3-7 years total. However, balance this with data minimization principles—don’t keep logs indefinitely. Document your retention policy and configure DigiConsent to automatically delete logs older than your specified period.
Can I use a cookie wall (require consent to access my site)?
GDPR regulators generally consider cookie walls non-compliant because they don’t offer genuine choice—users must either accept or leave, which isn’t freely given consent. However, there’s ongoing debate about whether you can offer different service levels based on consent (free with ads vs. paid without tracking). The safest approach is to allow full site access regardless of consent choices, with degraded functionality only for optional features that depend on cookies.
What if a user says they never consented but I have no record of their consent?
This is why consent logs are crucial. If a user claims they never consented, check your consent logs for records matching their identifier, IP address, or timestamp they mention. If no record exists, either consent wasn’t obtained (compliance problem) or they’re mistaken/intentionally lying. The logs provide evidence. If you find you’re not properly logging consent, investigate immediately to fix the technical issue.
Technical and Troubleshooting Questions
Why are my analytics numbers lower after installing DigiConsent?
If you’re using opt-in mode, this is completely expected and normal. Google Analytics (and other tracking tools) now only track users who consent. Typically 15-40% of users reject or ignore cookie requests, so your analytics will show less traffic than actual site visits. This is the privacy compliance trade-off. The data you do collect is from users who explicitly consented, making it more ethically obtained even if less comprehensive.
How do I verify that scripts are actually being blocked until consent?
Open your website in incognito mode (to see it as a new visitor). Before accepting cookies, open browser developer tools (F12), go to the Network tab, and look for your tracking script requests (like Google Analytics, Facebook Pixel, etc.). In opt-in mode, these should NOT be loading. Now accept cookies and verify that the scripts load immediately. You can also check the Console tab for any JavaScript errors that might prevent proper blocking.
The banner appears but tracking scripts aren’t loading after I accept. What’s wrong?
Several possibilities: (1) Scripts are added to the wrong category—verify they’re in Analytics/Marketing/Functional, not Necessary. (2) JavaScript errors are preventing script execution—check the browser console for errors. (3) Caching issues—clear all caches. (4) Script code is malformed—verify you’ve included complete script tags with opening <script> and closing </script> tags. (5) Ad blockers or browser privacy features are blocking the scripts regardless of consent.
Can I customize the banner design to match my website?
Yes, extensively. Go to DigiConsent → Settings → Design tab to customize colors (background, text, buttons), typography (fonts, sizes, weights), borders, shadows, and more. The built-in design options allow you to create a consent banner that perfectly matches your brand while maintaining all functionality.
Does DigiConsent work with caching plugins?
Yes, DigiConsent is compatible with all major caching plugins including WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, and Autoptimize. However, you must clear your cache after making changes to DigiConsent settings. The consent banner must load on every page view to function correctly, so ensure your caching plugin doesn’t cache the banner in a way that prevents it from displaying.
How do I test the banner without clearing my browser cookies every time?
Use incognito/private browsing mode for testing. Each new incognito window is a fresh session without saved cookies, so you’ll see the banner as a new visitor would. Alternatively, use browser developer tools to manually delete the DigiConsent consent cookie between tests. Some browsers also offer “Clear Cookies and Site Data” options in developer tools for quick testing.
Feature and Functionality Questions
Can users change their consent preferences after accepting or rejecting?
Yes, users can change preferences at any time by clearing their cookies or using a consent management link you provide (recommended practice is adding a “Cookie Settings” link in your website footer that re-triggers the banner). When consent expires (default 365 days), users will see the banner again and can make new choices.
Can I have different consent banners on different pages?
DigiConsent uses a single global configuration across your entire website. You cannot have different banners on different pages through the standard interface. However, developers can use WordPress conditional tags and DigiConsent hooks to programmatically modify banner behavior on specific pages if needed. For most websites, consistent consent management across all pages is better for user experience and compliance.
Does DigiConsent support multiple languages?
DigiConsent is translation-ready and works with translation plugins like WPML and Polylang. You can translate all user-facing text including banner messages, category names, and button labels. The plugin includes a POT file for easy translation creation. If your site serves users in multiple languages, use a translation plugin to provide localized consent experiences.
Can I export my DigiConsent configuration to use on another website?
Yes, go to DigiConsent → Settings → Import/Export tab. Click “Export Settings” to download a JSON file containing your complete configuration including all settings, cookie categories, scripts, and design customization. On another WordPress site with DigiConsent installed, use the Import function to upload this file and instantly replicate your configuration. This is perfect for agencies managing multiple client sites or businesses with multiple domains.
What data does DigiConsent collect and store?
DigiConsent collects and stores: consent actions (accept, reject, customize), timestamp of consent, categories accepted, anonymized user identifier, IP address, user agent (browser information), and consent preferences. This data is stored in your WordPress database and is necessary for compliance documentation. DigiConsent does not send any data to external servers—everything stays on your WordPress installation.
Performance and Compatibility Questions
Will DigiConsent slow down my website?
DigiConsent is optimized for minimal performance impact. The JavaScript and CSS files total less than 25KB gzipped, and scripts load asynchronously without blocking page rendering. Database queries are optimized with proper indexing. In practice, DigiConsent adds less than 50ms to page load time on properly configured hosting. The consent banner loads after your content, so visitors see your page quickly.
Does DigiConsent work on WordPress Multisite?
Yes, DigiConsent fully supports WordPress Multisite. You can network-activate it for all sites or activate it on individual sites. Each site in the network maintains its own separate configuration, consent logs, and analytics. Settings are not shared across network sites, allowing each site administrator to customize consent management for their specific needs.
Is DigiConsent compatible with PHP 8.0 and PHP 8.1?
Yes, DigiConsent is fully compatible with PHP 8.0, 8.1, and 8.2. While the minimum requirement is PHP 7.4, we recommend using PHP 8.0 or higher for better performance and security. DigiConsent is actively tested with each new PHP version to ensure compatibility.
Comparison and Alternative Questions
How is DigiConsent different from other cookie consent plugins?
DigiConsent combines powerful features with ease of use: (1) True Script Blocking: Actually prevents scripts from executing until consent, not just showing a banner. (2) Quick Add Integrations: Automatic code generation for popular services like Google Analytics, Facebook Pixel, etc. (3) Comprehensive Analytics: Built-in analytics dashboard showing acceptance rates and trends. (4) Complete Customization: Extensive design options without requiring coding. (5) Google Consent Mode v2: Native integration with Google’s latest consent framework. (6) Consent Logs: Automatic compliance documentation.
Do I need DigiConsent Pro or is the free version sufficient?
The free version of DigiConsent includes all essential features for compliance: consent modes (opt-in/opt-out/notice-only), all four cookie categories, script management, Google Consent Mode v2, analytics dashboard, consent logs, and complete customization. This is sufficient for most websites. DigiConsent Pro adds advanced features like geolocation-based consent rules, advanced analytics including geographic distribution, priority support, and additional integrations. Most users find the free version meets their needs completely.
Getting Help and Support
Where can I get help if I’m having issues?
Several support options are available: (1) Documentation: This comprehensive guide and other documentation articles cover most scenarios. (2) WordPress.org Forums: Visit the DigiConsent support forum on WordPress.org for community help. (3) Knowledge Base: Check the DigiConsent website for additional articles and tutorials. (4) Pro Support: DigiConsent Pro users receive priority email support with faster response times.
How do I report a bug or request a feature?
For bugs, please report them on the WordPress.org support forum with detailed information: WordPress version, PHP version, steps to reproduce, expected vs. actual behavior, and any error messages. For feature requests, describe your use case and why the feature would be valuable. The development team actively monitors these forums and incorporates user feedback into development priorities.
Is there a way to test DigiConsent before installing it on my live site?
Yes, best practice is to test on a staging site first. Most managed WordPress hosts provide staging environments. Install DigiConsent on staging, configure it completely, test all functionality, and verify consent blocking works correctly before deploying to production. This prevents issues on your live site and gives you a safe environment to experiment with settings.
This FAQ covers the most common questions, but cookie consent management can involve unique situations. If your specific question isn’t answered here, consult the detailed documentation articles for deep dives into specific topics, check the WordPress.org support forums, or contact support if you’re a DigiConsent Pro user. The DigiConsent team is committed to helping you implement compliant, effective cookie consent management on your WordPress website.