Back to DigiConsent

Review Consent and Admin Hide – Advanced Pro Banner Control Features

DigiConsent Pro includes two powerful features for controlling consent banner display: Review Consent Prompts and Hide Banner for Administrators. These features give you precise control over when and to whom the consent banner appears, improving both user experience and development workflow. Review Consent ensures users periodically reconsider their privacy choices as your data practices evolve, while Admin Hide lets you test your site without the banner interfering with your work.

This guide covers both features in detail, explaining when and how to use them effectively while maintaining compliance and providing the best experience for both your visitors and your team.

Review Consent Prompts

The Review Consent feature periodically asks users to re-examine their cookie consent choices, even if their original consent hasn’t expired. This is valuable when you’ve updated your privacy policy, added new tracking services, or want to ensure users are making informed decisions with current information.

Why Review Consent Matters

Cookie consent shouldn’t be “set and forget.” Several scenarios warrant prompting users to review their choices:

  • Privacy Policy Updates: When you substantially update your privacy policy, users should be informed and given opportunity to reconsider
  • New Tracking Services: Adding new analytics or marketing tools means collecting new data—users deserve to know
  • Data Practice Changes: Changing how you use data (e.g., starting to share with new third parties) requires notification
  • Regulatory Compliance: Some privacy laws suggest periodic consent refresh, especially for sensitive data
  • Best Practice: Industry best practice recommends consent review every 6-12 months even without changes

How Review Consent Works

Unlike consent expiration (which deletes the consent cookie entirely), Review Consent:

  1. Tracks when user last reviewed their consent choices
  2. After configured review period (e.g., 6 months), shows banner again
  3. Pre-fills banner with user’s current choices (not blank)
  4. User can confirm existing choices or modify them
  5. Review timestamp updates whether user changes anything or not

Key Difference from Expiration:

  • Consent Expiration: Treats user as if they never consented (blank slate)
  • Review Consent: Maintains current consent while prompting reconsideration

Configuring Review Consent

  1. Navigate to DigiConsent Pro → Settings → Advanced → Consent Management
  2. Find Review Consent Period setting
  3. Set review period in months:
    • 0 months: Disabled (users never prompted to review)
    • 3 months: Quarterly review (frequent, may annoy users)
    • 6 months: Semi-annual review (recommended for most sites)
    • 12 months: Annual review (good for stable data practices)
    • 24 months: Biennial review (minimal prompting)
  4. Configure review banner messaging (optional):
    • Custom heading: “Please Review Your Privacy Choices”
    • Custom description: “We’ve updated our privacy practices. Please review your cookie preferences.”
    • Or use default messaging
  5. Save settings

Choosing the Right Review Period

6 Months (Recommended for Most Sites):

  • Good balance between staying current and not annoying users
  • Aligns with GDPR best practice recommendations
  • Appropriate for sites with occasional policy updates

3 Months (Frequent Updates):

  • Sites with rapidly changing data practices
  • E-commerce adding new marketing integrations frequently
  • High-compliance environments (healthcare, finance)
  • Warning: May frustrate users with too-frequent prompts

12 Months (Stable Sites):

  • Mature sites with stable tracking practices
  • Content sites without frequent marketing changes
  • Balance compliance with minimal user disruption

Disabled (0 Months):

  • Only for sites relying solely on consent expiration
  • Not recommended for GDPR compliance

Review Consent vs Consent Expiration

Both features can work together or separately. Understanding the relationship:

Example Configuration 1: Review Every 6 Months, Expire After 12 Months

  • Consent Expiry: 365 days
  • Review Period: 6 months
  • User journey:
    • Day 0: User accepts cookies
    • Day 180 (6 months): Review prompt (“Please review your choices”)
    • Day 365 (12 months): Consent expires entirely (if no review occurred)

Example Configuration 2: Review Only (No Expiration)

  • Consent Expiry: 3650 days (10 years, effectively never)
  • Review Period: 6 months
  • User journey:
    • Consent never expires
    • Banner appears every 6 months for review
    • Current choices pre-selected

Recommended Approach: Use both—12 month expiration with 6 month review. This prompts periodic review while ensuring consent eventually expires completely.

Triggering Manual Review

When you make significant privacy policy changes, you may want to force immediate review for all users:

  1. Navigate to DigiConsent Pro → Settings → Advanced
  2. Find Force Consent Review option
  3. Enable option and save
  4. All users will see banner on next visit, regardless of review period
  5. Their previous choices are pre-selected
  6. After reviewing, normal review schedule resumes

When to Force Review:

  • Major privacy policy update
  • Added significant new tracking service (e.g., first time adding Facebook Pixel)
  • Changed data retention policies substantially
  • Started sharing data with new third parties
  • Regulatory requirement for re-consent

Review Consent Messaging Best Practices

When prompting review, clarity matters:

Clear Messaging:

  • “Time to review your cookie preferences”
  • “Please review your privacy choices—we’ve updated our practices”
  • “Your current choices are selected below. Confirm or modify as needed.”

What Changed:

  • If you changed something, explain briefly: “We’ve added new analytics tools to improve our site”
  • Link to “What’s New” section of privacy policy
  • Be transparent about why you’re asking for review

Respect Choices:

  • Don’t reset choices to defaults (keep their current selections)
  • Don’t make accept button more prominent during review (same as original banner)
  • Honor their choice if they confirm without changes

Hide Banner for Administrators

The Hide Banner for Administrators feature prevents the consent banner from appearing for logged-in administrators. This improves development and content management workflow without affecting how visitors experience your site.

Why Hide Banner for Admins

While working on your WordPress site, the consent banner can be distracting or interfere with tasks:

  • Content Editing: Banner obscures content you’re trying to edit in preview
  • Design Work: Banner interferes with viewing layout and design changes
  • Development/Debugging: Banner adds extra elements to inspect/debug
  • Screenshot Creation: Marketing materials shouldn’t include consent banner
  • Training: Training staff on admin features; banner isn’t relevant
  • Productivity: Seeing banner on every page gets tiresome for daily admin work

Important: This feature only hides the banner for logged-in administrators. Regular visitors still see the banner normally. This ensures you can work comfortably while maintaining compliance for actual users.

Enabling Admin Hide

  1. Navigate to DigiConsent Pro → Settings → Advanced → Banner Display
  2. Find Hide Banner for Administrators setting
  3. Enable the checkbox
  4. Save settings
  5. Consent banner will no longer appear when you’re logged in as administrator

Who is Considered an Administrator:

By default, this feature hides the banner for users with the “manage_options” capability, which includes:

  • Administrator role (full access)
  • Custom roles with manage_options capability

Who Still Sees the Banner:

  • All non-logged-in visitors
  • Logged-in users with lower roles (Editor, Author, Contributor, Subscriber)
  • Logged-in administrators when viewing in private/incognito mode (not logged in)

Testing After Enabling Admin Hide

After enabling admin hide, you should still test that regular visitors see the banner correctly:

Method 1: Private/Incognito Window

  1. Open private/incognito browser window
  2. Visit your site (you’re not logged in in this window)
  3. Verify banner appears correctly
  4. Test accept/reject functionality
  5. Confirm banner respects choices

Method 2: Different Browser

  1. Use different browser where you’re not logged in
  2. Visit your site
  3. Verify banner appears and functions

Method 3: Logged Out View

  1. Log out of WordPress
  2. Visit site as regular visitor
  3. Test banner functionality
  4. Log back in when done

Extending to Other User Roles

By default, only Administrators are excluded. If you want to hide banner for other roles (e.g., Editors who also work on the site daily), you can customize using WordPress filters.

Example: Hide for Editors Too

add_filter('digiconsent_should_show_banner', function($should_show) {
    // Hide for administrators and editors
    if (current_user_can('manage_options') || current_user_can('edit_pages')) {
        return false;
    }
    return $should_show;
});

Add this code to your theme’s functions.php or custom plugin.

Admin Hide Best Practices

  • Enable for productivity: If you work on your site frequently, enable admin hide to reduce distraction
  • Regular testing: Monthly, test in private window to ensure visitors see banner correctly
  • Before major changes: Before updating consent settings, test as visitor to see what they experience
  • Team training: Ensure team knows banner is hidden for them but shows for visitors
  • Client sites: Particularly useful for agency/developer workflow on client sites

When NOT to Use Admin Hide

  • Testing consent functionality: Disable admin hide when testing how consent works
  • Debugging consent issues: If users report banner problems, disable admin hide to see what they see
  • Compliance audits: During compliance review, experience site as visitor (disable or test in private window)
  • Stakeholder demonstrations: When showing site to stakeholders, they should see real visitor experience

Temporary Admin Hide Override

If admin hide is enabled but you need to temporarily see the banner (for testing), you don’t need to disable the setting. Instead:

Quick Override Methods:

  • Use private/incognito window (fastest)
  • Temporarily log out
  • Add URL parameter override (if DigiConsent supports it): ?digiconsent_preview=1
  • Disable admin hide, test, re-enable

Combining Both Features

Review Consent and Admin Hide work well together, addressing different needs:

Typical Configuration:

  • Review Consent: Enabled, 6-month period
  • Admin Hide: Enabled
  • Consent Expiry: 12 months

How They Interact:

  • Administrators never see banner while logged in (admin hide)
  • Regular visitors see banner initially
  • After 6 months, visitors see review prompt
  • After 12 months (if no review), consent expires and banner shows again
  • Administrators testing in private window see all visitor experiences

Common Scenarios and Solutions

Scenario 1: Privacy Policy Major Update

Situation: You’ve substantially revised your privacy policy and added new tracking services.

Solution:

  1. Update privacy policy page
  2. Add new tracking scripts to DigiConsent categories
  3. Update banner description to mention changes
  4. Navigate to Force Consent Review setting
  5. Enable to trigger immediate review for all users
  6. Save and test in private window

Scenario 2: Banner Not Showing (Admin Hide Confusion)

Situation: You enabled admin hide and forgot, now think banner is broken because you don’t see it.

Solution:

  1. Check DigiConsent Pro → Advanced → Hide Banner for Administrators
  2. If enabled, that’s why you don’t see it
  3. Test in private window to confirm it shows for visitors
  4. Leave admin hide enabled (working as intended)

Scenario 3: Too Many Review Prompts

Situation: Users complain about seeing consent banner too frequently.

Solution:

  1. Check review period setting
  2. If set to 3 months, consider increasing to 6 or 12 months
  3. Verify you haven’t accidentally enabled “Force Consent Review” permanently
  4. Check consent expiry isn’t too short (should be 12+ months typically)

Configuration Checklist

Review Consent Setup:

  • ✅ Review period configured (recommend 6-12 months)
  • ✅ Review messaging customized (optional but recommended)
  • ✅ Relationship to consent expiry understood (review < expiry)
  • ✅ Force review mechanism understood for policy changes
  • ✅ Tested in private window to see visitor experience

Admin Hide Setup:

  • ✅ Admin hide enabled for productivity
  • ✅ Tested in private window (banner shows for visitors)
  • ✅ Team aware banner is hidden for admins but shows for users
  • ✅ Testing procedure established (use private windows)
  • ✅ Know how to temporarily override for debugging

Review Consent and Admin Hide are sophisticated features that improve both user privacy communication and administrative workflow. Review Consent ensures users stay informed about your data practices with periodic reminders to reconsider their choices, promoting transparency and ongoing consent validity. Admin Hide improves your productivity by removing the banner distraction while you work, without affecting the visitor experience. Together, these features demonstrate DigiConsent Pro’s attention to both compliance best practices and practical usability for website administrators.

Similar Articles

Back to DigiConsent