After completing the initial setup of DigiConsent, it’s time to dive deeper into the comprehensive configuration options available. This guide covers all essential settings in detail, helping you create a cookie consent system that perfectly balances compliance, user experience, and your website’s specific needs.
Understanding the Settings Interface
The DigiConsent Settings page is accessed by clicking DigiConsent → Settings in your WordPress admin menu. The settings are organized into tabs for easy navigation:
- General: Core banner settings, consent behavior, and text customization
- Cookie Categories: Management of Necessary, Analytics, Marketing, and Functional categories
- Design: Visual customization including colors, fonts, and styling
- Import/Export: Configuration backup and transfer tools
This guide focuses on the General tab and Cookie Categories tab, which contain the most critical configuration options for getting DigiConsent operational.
General Settings Deep Dive
The General tab contains the foundation of your consent configuration. Each setting here affects how your banner appears and behaves.
Banner Layout Options
The banner layout determines the visual presentation and positioning of your consent banner. DigiConsent provides four distinct layouts, each with specific use cases:
Bottom Banner
Displays as a horizontal bar at the bottom of the viewport. This layout spans the full width of the screen and pushes content up slightly when visible. It’s the most familiar format for users and works excellently on both desktop and mobile devices.
When to use: This is the default choice for most websites. It’s non-intrusive while still being clearly visible, and users recognize this format from countless other websites. Recommended for e-commerce sites, blogs, and business websites where you want to maintain visibility of page content.
Top Banner
Displays as a horizontal bar at the top of the viewport. Similar to the bottom banner but anchored to the top of the screen. This layout can push page content down, which may affect the initial view of your website.
When to use: Choose this when you want maximum immediate visibility but don’t have important content at the top of your pages. Works well for sites with hero images or full-screen sections where pushing content down doesn’t negatively impact the user experience.
Side Banner
Displays as a vertical panel on either the left or right side of the screen. This modern layout doesn’t affect the vertical flow of content and can be less disruptive to reading or browsing.
When to use: Ideal for content-heavy sites where you don’t want to interrupt the vertical reading flow. Works particularly well on desktop but may be less practical on narrow mobile screens. When selecting this option, you’ll also choose left or right positioning.
Fullscreen
Displays as an overlay that covers the entire viewport until the user makes a decision. This is the most attention-grabbing layout, preventing any interaction with the website until consent is addressed.
When to use: Use this when consent is absolutely critical and you need to ensure every visitor sees and interacts with the banner. Common in highly regulated industries or when your legal team requires explicit, impossible-to-miss consent requests. However, be aware this can negatively impact user experience if overused.
Banner Position (Side Banner Only)
When you select the Side Banner layout, an additional setting appears allowing you to choose left or right positioning. The banner will slide in from the selected side and remain anchored there.
Left vs. Right considerations:
- In left-to-right languages, users scan from left to right, so left positioning is slightly more visible
- Right positioning keeps the banner out of the way of navigation menus typically on the left
- Consider your website’s layout—avoid overlapping important UI elements
- Test both options to see which feels more natural with your design
Consent Behavior Configuration
The Consent Behavior setting is arguably the most important configuration choice in DigiConsent, as it determines your compliance approach and directly affects your legal obligations.
Opt-in (Block cookies until consent)
In opt-in mode, DigiConsent prevents all non-essential tracking scripts from executing until users explicitly provide consent by clicking Accept or customizing their preferences. Scripts added to cookie categories (except Necessary) will not load until consent is granted.
Technical behavior: When the page loads, DigiConsent blocks script execution by wrapping them in special script tags with type text/plain and a data attribute. Only after consent is received do these scripts get converted to executable JavaScript and run.
Compliance implications: This mode satisfies the strictest interpretations of GDPR, ePrivacy Directive, and similar regulations. It ensures you have explicit, informed consent before any personal data collection occurs. This is legally required for European Union visitors.
Business implications: You’ll collect less data overall because some users will reject tracking. Your analytics will be incomplete, showing only users who consented. This is the trade-off for legal compliance and user trust.
Opt-out (Allow cookies, user can reject)
In opt-out mode, all tracking scripts load immediately when the page loads, but users can reject them after the fact. The banner still appears, but scripts execute before any user interaction.
Technical behavior: Scripts execute normally without blocking. If a user later rejects cookies, the consent banner notes their preference, but scripts that already ran cannot be “unrun.” On subsequent visits, rejected scripts will be blocked.
Compliance implications: This mode may not satisfy GDPR requirements for EU visitors, as it collects data before consent is obtained. However, it may be acceptable in jurisdictions with less strict requirements, such as most of the United States (excluding California and some other states).
Business implications: You collect maximum data because tracking happens by default. Most users won’t reject cookies, so your analytics will be nearly complete. This maximizes your ability to track and optimize but may create compliance risks.
Notice-only (Informational)
In notice-only mode, the banner simply informs users that cookies are being used, without offering any choice or requiring any action. All scripts load normally.
Technical behavior: Scripts execute exactly as they would without DigiConsent installed. The banner is purely informational.
Compliance implications: This mode does not satisfy GDPR or most modern privacy regulations that require explicit consent for non-essential cookies. Use this only if you’re certain your jurisdiction doesn’t require consent, or if you’ve removed all tracking cookies from your site.
Business implications: Full data collection with no restrictions. However, limited legal protection and potential regulatory risk if your jurisdiction changes its requirements.
Text Customization Fields
DigiConsent provides three text fields for customizing your banner message. Effective text is crucial for both compliance (informed consent requires clear information) and conversion (clear benefits increase acceptance rates).
Pre-Heading Text
This small text appears above your main heading. It’s optional but helps create a friendly, approachable tone. Keep it very brief—1-3 words maximum.
Best practices:
- Keep it conversational and friendly
- Use it to acknowledge the interruption: “Before you continue…”
- Or create a welcoming tone: “Hi there!” or “Welcome!”
- Don’t use legal language or jargon
Heading Text
This is your banner title—the most prominent text in the consent banner. It should immediately communicate what the banner is about.
Best practices:
- Be clear and direct: “We use cookies” or “Cookie preferences”
- Keep it short: 3-7 words maximum
- Avoid overly cute or clever language that might confuse users
- Make it scannable—users should understand instantly
Description Text
This is your opportunity to explain what cookies do, why you use them, and what value they provide. This field accepts multiple sentences and is crucial for informed consent.
Best practices:
- Explain specific uses: “We use cookies to remember your shopping cart, understand which content you enjoy, and show relevant advertisements”
- Focus on user benefits, not your data needs: Instead of “We use cookies to track you,” say “We use cookies to personalize your experience”
- Be honest—don’t hide what you’re doing
- Keep it concise: 2-4 sentences is ideal
- Use plain language: Avoid terms like “optimize engagement metrics” when you mean “understand what you like”
- Consider your audience’s privacy awareness level
Privacy Policy Integration
Linking to your privacy policy is essential for GDPR compliance and building trust. The privacy policy should provide comprehensive details that the banner can’t accommodate.
Privacy Policy Page
Use the dropdown to select the WordPress page containing your privacy policy. DigiConsent will automatically generate a link to this page within the banner.
What your privacy policy should include:
- Complete list of cookies used with descriptions
- Purpose of each type of data collection
- Third parties who receive data (Google, Facebook, etc.)
- Data retention periods
- User rights (access, deletion, portability)
- Contact information for privacy questions
- Legal basis for processing (legitimate interest, consent, etc.)
Privacy Policy Link Text
Customize the text of the privacy policy link. The default “Privacy Policy” is standard and recognized by users. Only change this if your organization uses different terminology, such as “Privacy Statement” or “Data Protection Policy.”
Consent Expiration
This setting determines how long (in days) user consent remains valid before the banner appears again to request fresh consent. The default is 365 days (one year).
Balancing compliance and user experience:
- Shorter periods (90-180 days): More conservative, ensures consent stays current, good if your cookie usage changes frequently. However, can frustrate users who must repeatedly consent.
- 365 days (default): Balances compliance with user convenience. Aligned with GDPR guidance suggesting yearly consent refresh. Recommended for most websites.
- Longer periods (730+ days): Minimizes user interruption but may not satisfy strict compliance interpretations. Generally not recommended unless your cookie usage is extremely stable.
When consent expires: When the expiration period ends, the consent cookie is deleted, and the user will see the banner again on their next visit, as if they were a new visitor. Their previous choice is not remembered.
Google Consent Mode v2 Configuration
Google Consent Mode v2 is an advanced feature that integrates DigiConsent with Google’s consent framework. This section appears in the General Settings tab.
What is Google Consent Mode?
Google Consent Mode allows Google services (Analytics, Ads, Tag Manager) to adjust their behavior based on user consent. When users don’t consent, Google can still collect some anonymized, aggregated data without using cookies, allowing you to maintain some analytics capability while respecting user choices.
Enable GCM Toggle
Toggle this to ON if you use any Google services (Google Analytics, Google Ads, Google Tag Manager). When enabled, DigiConsent will automatically communicate consent status to Google’s services.
Benefits of enabling GCM:
- Better analytics coverage even when users reject cookies
- Improved conversion tracking for Google Ads
- Compliant data collection through Google’s consent-aware mode
- Automatic configuration—DigiConsent handles the technical implementation
Default Consent State
When GCM is enabled, you’ll see an option to set the default consent state before user interaction:
Denied (Recommended)
Sets all consent types to “denied” by default. This aligns with opt-in consent behavior and GDPR requirements. Google services will use consent-aware measurement until users accept cookies, at which point DigiConsent updates the consent state to “granted.”
Granted
Sets consent to “granted” by default. This aligns with opt-out consent behavior. Google services operate normally from the start. If users reject cookies, DigiConsent updates the state to “denied.”
Recommendation: Use “Denied” for GDPR compliance. This ensures Google services respect user privacy before consent is obtained.
Button Settings Configuration
The Button Settings section allows you to customize which buttons appear in your consent banner and what text they display. Each button serves a specific purpose in your consent flow.
Show Accept Button
This toggle controls whether the Accept button appears. The Accept button allows users to accept all cookies with one click. This should remain ON in virtually all scenarios—it’s the primary positive action users can take.
Accept Button Text
Customize the text shown on the Accept button. Default is “Ok For Me.” Consider these alternatives:
- “Accept All” (clear and explicit)
- “Accept Cookies” (specific about what’s being accepted)
- “I Agree” (simple and common)
- “Got It” (casual and friendly)
Best practices: Use clear, action-oriented language that tells users exactly what happens when they click. Avoid ambiguous terms.
Show Reject Button
This toggle controls whether the Reject button appears. The Reject button allows users to reject all optional cookies with one click. For GDPR compliance, you must provide an easy way to reject cookies—keep this ON.
Reject Button Text
Customize the text shown on the Reject button. Default is “No Thanks.” Consider these alternatives:
- “Reject All” (matches “Accept All” pattern)
- “Decline” (formal and clear)
- “No Thanks” (polite and friendly)
- “Essential Only” (explains what happens)
Compliance note: GDPR requires that rejecting cookies is as easy as accepting them. The reject button should be equally prominent and easy to click.
Show Settings Button
This toggle controls whether the Settings button appears. The Settings button opens a detailed modal where users can view descriptions of each cookie category and accept/reject them individually. Keep this ON to provide granular control.
Settings Button Text
Customize the text shown on the Settings button. Default is “Let Me Choose.” Consider these alternatives:
- “Customize” (short and clear)
- “Cookie Settings” (explicit about function)
- “Manage Preferences” (professional)
- “See Details” (informational focus)
Why this matters: Some privacy-conscious users want granular control—they might accept analytics but reject marketing cookies. The Settings button enables this level of choice.
Saving and Testing Your Configuration
After making configuration changes, always follow this process:
- Scroll to the bottom of the Settings page
- Click Save Settings
- Wait for the success confirmation message
- Clear all website caches (WordPress cache, server cache, CDN cache)
- Open a private/incognito browser window
- Visit your website to see the changes
- Test all functionality (Accept, Reject, Settings buttons)
- Verify text changes appear correctly
- Test on mobile devices
Important: Changes only apply to new visitors or visitors whose consent has expired. Users with existing consent cookies won’t see changes until their consent expires or they clear their cookies.
Common Configuration Scenarios
Here are recommended configurations for common website types:
E-commerce Website (EU Audience)
- Consent Behavior: Opt-in
- Layout: Bottom Banner
- GCM: Enabled, Denied by default
- Buttons: All three enabled
- Expiration: 365 days
- Description focus: Explain how cookies improve shopping experience
US Business Website (Non-EU)
- Consent Behavior: Opt-out (if legally acceptable) or Opt-in (safer)
- Layout: Bottom Banner or Side Banner
- GCM: Enabled, Granted by default (if using opt-out)
- Buttons: All three enabled
- Expiration: 365 days
Content/Blog Website
- Consent Behavior: Opt-in
- Layout: Bottom Banner (doesn’t interrupt reading)
- GCM: Enabled if using Google services
- Buttons: All three enabled
- Expiration: 365 days
- Description focus: Explain how analytics helps create better content
By carefully configuring these essential settings, you create a consent management system that balances legal compliance, user experience, and your business needs. The configuration process may seem detailed, but each setting plays an important role in how your consent system functions and protects both your users and your organization.