Skip to main content

Consent Overrides

Overrides let you customize consent behavior for specific scenarios without modifying your main site configuration.

When to use overrides​

  • A/B testing: Test different default states for consent categories
  • Partner requirements: Enable specific vendors for contractual obligations
  • Regional compliance: Adjust defaults for specific jurisdictions
  • Emergency changes: Quickly disable a problematic vendor

Override types​

Category overrides​

Force a consent category to a specific state:

OverrideEffect
Force enabledCategory is always consented, regardless of user choice
Force disabledCategory is always rejected, regardless of user choice
Default enabledPre-checked in the preferences dialog
Default disabledUnchecked by default (standard GDPR behavior)

Vendor overrides​

Target specific vendors within a category:

{
  "vendor": "google-analytics",
  "category": "analytics",
  "override": "force-enabled",
  "reason": "First-party analytics exemption"
}

Creating an override​

  1. Navigate to Overrides in the sidebar
  2. Click New Override
  3. Configure the override:
    • Name: Descriptive identifier
    • Type: Category or Vendor
    • Target: Which category/vendor to affect
    • Action: Force enabled, force disabled, or default state
    • Conditions: Optional region or device filters
  4. Click Save

Override conditions​

Apply overrides conditionally based on:

  • Region: EU, California, specific countries
  • Device type: Desktop, mobile, tablet
  • URL pattern: Specific pages or paths
  • Date range: Temporary overrides with auto-expiry

Override priority​

When multiple overrides apply, priority is determined by:

  1. Most specific condition wins (URL > region > device > global)
  2. Later-created overrides win over earlier ones with same specificity
  3. Vendor overrides take precedence over category overrides

Audit trail​

All override changes are logged:

  • Who made the change
  • What was changed
  • When it was changed
  • Previous value

View the audit trail in Overrides → History.

Best practices​

  • Document reasons: Always add a reason for compliance audits
  • Use expiry dates: Set auto-expiry for temporary overrides
  • Review regularly: Audit overrides quarterly
  • Test first: Use staging site keys before applying to production

Next steps​