Skip to Content
Compliance & frameworksCookieHub logic and behaviorHow regional framework rules work

How regional framework rules work

CookieHub uses a region-based configuration model to control how consent dialogs behave based on the geographic location of the user.

Each region in CookieHub can be configured with:

  • A policy framework (e.g., CookieHub, IAB GPP, IAB TCF 2.2)
  • A consent type (explicit/opt-in or implied/opt-out)
  • A customized interface (optional)

How regions are evaluated

When a user visits your website:

  1. Geo IP lookup is used to determine the visitor’s country or US state.
  2. CookieHub compares the result to the list of configured regions in your domain settings.
  3. The first matching region (based on your configuration order) is applied to determine:
    • Consent dialog layout
    • Consent type
    • Framework logic
    • Cookie blocking behavior

Region matching order

CookieHub checks for a match in the following order:

  1. Specific country or US state
  2. Predefined region group (e.g., Europe, US states)
  3. Global fallback (if no match is found)

This means more specific regions override more general ones.

Example: If you create a custom region for California and another region for US states, users in California will match the California region first—even if both apply.


What settings are applied?

For the matched region, CookieHub applies:

  • The selected framework (e.g., CookieHub, IAB GPP, IAB TCF)
  • The consent type (explicit or implied)
  • The customized layout and button settings (e.g., if “Deny all” is shown)
  • Whether the region uses a bar layout or an overlay dialog
  • Optional settings in the Preference Center (e.g., auto opt-out of categories)

All other regions are ignored for that user.


Global fallback behavior

If a user’s location does not match any defined region:

  • The “Default” region will be used automatically. This is a built-in fallback in CookieHub and always applies if no other region matches.
  • You can customize the Default region like any other region (framework, consent type, layout, etc.)

Summary

RuleBehavior
Location matches multiple regionsMost specific match wins
No matching regionGlobal fallback is used
Region sets framework + consent typeApplied automatically
Interface layout and behavior per regionFully customizable

Last updated on