Loading auth config...
Skip to main content
Lokker
A visual representation of privacy and consent management, featuring icons of locks for security, shields for protection, checkmarks for compliance, cookies and pixels for tracking technologies, arrows indicating data flow, and globes symbolizing global regulations like GDPR and CCPA.

OneTrust Cookie Categorization Not Reflecting on Frontend

Table of Contents​

Problem Description​

You've updated cookie categorization in OneTrust, but the changes aren't visible on your website's frontend. The consent banner still shows old categories, and users can't see the updated cookie preferences.

Common Causes​

1. Changes Not Published​

The most common cause is that changes were made in OneTrust but never published to production.

2. Cache Issues​

Browser or CDN caching may be serving old versions of the consent banner.

3. Incorrect Environment​

Changes may have been made in the wrong OneTrust environment (e.g., staging instead of production).

Step-by-Step Debugging​

Step 1: Verify Publication Status​

  1. Navigate to OneTrust Admin Panel

    • Go to Admin → Data Governance → Cookie Compliance
    • Or use the direct URL: https://yourcompany.onetrust.com/app/admin/

  2. Check Publication Status

    • Look for the "Published" indicator in the top right
    • If it shows "Draft" or "Unpublished Changes", you need to publish

  3. Publish Changes

    • Click the "Publish" button
    • Confirm the publication
    • Wait for the confirmation message

Step 2: Verify Environment​

  1. Check Current Environment

    • In OneTrust admin, verify you're in the correct environment
    • Look for environment indicators (Production, Staging, Development)

  2. Switch to Production (if need)

    • Use the environment switcher in the top navigation
    • Ensure you're making changes in the right environment

Step 3: Clear Caches​

  1. Browser Cache

    • Hard refresh: Ctrl+F5 (Windows) or Cmd+Shift+R (Mac)
    • Clear browser cache and cookies for your domain

  2. CDN Cache (if applicable)

    • Contact your CDN provider to clear cache
    • Or use CDN purge tools if available

  3. Application Cache

    • Clear any application-level caching
    • Restart web servers if necessary

Step 4: Verify Implementation​

  1. Check OneTrust Script

    • Ensure the OneTrust script is loading from the correct environment
    • Verify the script URL in your HTML

  2. Inspect Network Requests

    • Open browser DevTools → Network tab
    • Look for OneTrust API calls
    • Verify they're hitting the correct endpoints

Prevention Best Practices​

1. Always Publish After Changes​

  • Make it a habit to publish immediately after making changes
  • Set up reminders or checklists for your team

2. Use Environment Management​

  • Keep staging and production environments separate
  • Test changes in staging before applying to production

3. Regular Audits​

  • Schedule monthly reviews of cookie categorization
  • Verify that published changes match intended configurations

Troubleshooting Checklist​

  • Changes have been published in OneTrust
  • Working in the correct environment (Production)
  • Browser cache has been cleared
  • CDN cache has been purged (if applicable)
  • OneTrust script is loading from correct environment
  • Network requests are hitting correct endpoints
  • No JavaScript errors in browser console

Still Having Issues?​

If the problem persists after following these steps:

  1. Check OneTrust Support

    • Contact OneTrust support with your issue ID
    • Provide screenshots of the problem

  2. Verify Implementation

    • Ensure OneTrust is properly integrated
    • Check for conflicting consent management tools

  3. Review Recent Changes

    • Look at what was changed and when
    • Verify the change was intended and correct