Loading auth config...
Skip to main content
Lokker
A banner-style image representing privacy regulations and consent management, featuring icons such as locks for security, shields for protection, checkmarks for compliance, arrows for data flow, globes for global reach, and cookies/pixels for tracking technologies, symbolizing GDPR, CCPA, and consent management processes.

Common OneTrust Issues and Quick Fixes

Table of Contents​

Problem Description​

This guide covers the most common OneTrust issues you'll encounter and provides quick solutions to get your consent management working properly. These are the problems that come up most frequently and can usually be resolved quickly.

Quick Fix Index​

🚨 Critical Issues (Fix Immediately)​

⚠️ Important Issues (Fix Soon)​

🔧 Configuration Issues (Fix When Possible)​

Critical Issues​

Symptoms: OneTrust banner doesn't show up on the website Quick Fix: Check script loading and configuration

Steps:

  1. Verify Script Loading

    • Open browser DevTools → Console
    • Look for OneTrust script errors
    • Check Network tab for script loading

  2. Check Domain Configuration

    • Go to OneTrust Admin → Settings → Domains
    • Verify your domain is listed and active
    • Check for typos in domain names

  3. Verify Script Implementation

    • Ensure OneTrust script is in <head> section
    • Check for JavaScript errors before OneTrust loads
    • Verify script ID matches your OneTrust configuration

Common Causes:

  • OneTrust script not loaded
  • Domain not configured in OneTrust
  • JavaScript errors preventing execution
  • Script loading in wrong order

Symptoms: Tracking scripts run even when users haven't given consent Quick Fix: Enable automatic script blocking

Steps:

  1. Enable Automatic Blocking

    • Go to OneTrust Admin → Scripts → Script Management
    • Enable "Automatic Script Blocking"
    • Verify scripts are properly categorized

  2. Check Script Categories

    • Ensure each script has correct category assignment
    • Verify blocking rules are set for non-necessary scripts
    • Check that scripts respect consent preferences

  3. Test Script Blocking

    • Clear browser data and refresh
    • Verify no tracking scripts load initially
    • Accept consent and verify scripts now load

Common Causes:

  • Automatic blocking disabled
  • Scripts not properly categorized
  • Integration issues with other tools
  • Incorrect blocking rules

Changes Not Reflecting on Frontend​

Symptoms: OneTrust changes made but not visible on website Quick Fix: Publish changes and clear caches

Steps:

  1. Publish Changes

    • Go to OneTrust Admin → Look for "Publish" button
    • Click publish and confirm
    • Wait for confirmation message

  2. Check Environment

    • Verify you're in Production environment
    • Switch from Staging if need
    • Ensure changes are in correct environment

  3. Clear Caches

    • Hard refresh browser (Ctrl+F5)
    • Clear CDN cache if applicable
    • Check for application-level caching

Common Causes:

  • Changes not published
  • Wrong environment selected
  • Browser/CDN caching
  • Implementation issues

Important Issues​

Symptoms: Consent banner shows repeatedly on same page Quick Fix: Check for duplicate implementations

Steps:

  1. Check for Duplicate Scripts

    • Search HTML for multiple OneTrust script tags
    • Remove duplicate implementations
    • Ensure single script instance

  2. Verify Consent State

    • Check browser storage for consent data
    • Verify consent is being saved properly
    • Test in incognito mode

  3. Check Page Refresh Behavior

    • Verify banner doesn't reappear on refresh
    • Check for JavaScript errors on page load
    • Ensure proper consent state management

Common Causes:

  • Multiple OneTrust script instances
  • Consent state not persisting
  • Page refresh issues
  • Conflicting consent managers

Symptoms: User choices aren't rembered between sessions Quick Fix: Check storage configuration and browser settings

Steps:

  1. Verify Storage Settings

    • Check OneTrust storage configuration
    • Ensure cookies/local storage is enabled
    • Verify storage domain settings

  2. Check Browser Settings

    • Disable browser privacy extensions temporarily
    • Check if cookies are blocked
    • Test in incognito/private mode

  3. Verify Implementation

    • Check for JavaScript errors
    • Verify OneTrust events are firing
    • Test storage functionality

Common Causes:

  • Browser privacy settings
  • Storage configuration issues
  • JavaScript errors
  • Privacy extensions blocking storage

Privacy Signals Not Working​

Symptoms: GPC and DNT signals not being respected Quick Fix: Enable and configure privacy signal handling

Steps:

  1. Enable Privacy Signals

    • Go to OneTrust Admin → Settings → Privacy Signals
    • Enable GPC and DNT processing
    • Configure default behaviors

  2. Configure Category-Level Settings

    • Go to each cookie category
    • Enable "Respect GPC Signal" and "Respect DNT Signal"
    • Set appropriate actions for each category

  3. Test Signal Handling

    • Use GPC browser extensions
    • Enable DNT in browser settings
    • Verify signals are being processed

Common Causes:

  • Privacy signals not enabled
  • Category-level settings not configured
  • Script blocking rules not set
  • Integration issues

Configuration Issues​

GTM Integration Problems​

Symptoms: Google Tag Manager not respecting OneTrust consent Quick Fix: Configure GTM consent mode and OneTrust integration

Steps:

  1. Enable GTM Consent Mode

    • Go to GTM Admin → Container Settings
    • Enable "Consent Mode"
    • Set default consent to "denied"

  2. Create OneTrust Variables

    • Set up custom JavaScript variables for consent
    • Create consent triggers
    • Configure tag consent requirements

  3. Test Integration

    • Use GTM Preview mode
    • Verify tags only fire with consent
    • Check consent state changes

Common Causes:

  • GTM consent mode not enabled
  • Missing OneTrust integration variables
  • Tags not configured with consent triggers
  • Default consent too permissive

Performance Issues​

Symptoms: OneTrust causing slow page loads or performance problems Quick Fix: Optimize script loading and configuration

Steps:

  1. Optimize Script Loading

    • Load OneTrust script asynchronously
    • Minimize blocking operations
    • Use CDN for OneTrust resources

  2. Review Configuration

    • Check for unnecessary features enabled
    • Optimize cookie scanning
    • Review script blocking rules

  3. Monitor Performance

    • Use browser performance tools
    • Check for OneTrust-related delays
    • Optimize based on findings

Common Causes:

  • Synchronous script loading
  • Excessive cookie scanning
  • Complex blocking rules
  • Resource loading issues

Mobile Display Problems​

Symptoms: Consent banner not displaying properly on mobile devices Quick Fix: Check mobile-specific configuration and CSS

Steps:

  1. Verify Mobile Settings

    • Check OneTrust mobile configuration
    • Verify responsive design settings
    • Test on various mobile devices

  2. Check CSS Issues

    • Review mobile-specific CSS
    • Check for responsive breakpoints
    • Verify banner positioning

  3. Test Mobile Experience

    • Test on different screen sizes
    • Check touch interactions
    • Verify mobile consent flow

Common Causes:

  • Mobile configuration issues
  • CSS responsive problems
  • Touch interaction issues
  • Mobile-specific bugs

Prevention Best Practices​

1. Regular Testing​

  • Test consent flows monthly
  • Verify in multiple browsers
  • Check mobile experience regularly

2. Monitor for Issues​

  • Set up error monitoring
  • Track consent analytics
  • Monitor user feedback

3. Keep Updated​

  • Update OneTrust regularly
  • Monitor for new features
  • Stay current with best practices

4. Document Everything​

  • Keep configuration notes
  • Document custom implementations
  • Maintain troubleshooting guides

When to Escalate​

Escalate to OneTrust Support When:​

  • Configuration changes don't resolve issues
  • Problems affect multiple users/environments
  • Security or compliance concerns arise
  • Performance impact is significant

Escalate to Technical Team When:​

  • Integration issues persist
  • Custom code modifications need
  • Performance optimization required
  • Complex configuration changes need

Quick Reference​

Essential OneTrust Settings​

  • ✅ Automatic script blocking enabled
  • ✅ Privacy signals configured
  • ✅ Category-level settings configured
  • ✅ Scripts properly categorized
  • ✅ Changes published to production
  • ✅ Domain configuration correct

Common Error Messages​

  • "Script not found": Check script ID and domain
  • "Consent not saved": Verify storage settings
  • "Banner not showing": Check script loading
  • "Scripts still firing": Enable automatic blocking

Rember: Most OneTrust issues can be resolved quickly by following these steps. Start with the quick fixes, and if problems persist, use the detailed troubleshooting guides for your specific issue.