How regional framework rules work

CookieHub uses region-based configuration to control how the consent dialog behaves based on a user’s location. This ensures the correct legal framework and consent model is applied automatically.

What can you configure per region?

Each region can have:

• A policy framework (CookieHub, IAB GPP, or 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 site:

1. Geo IP lookup determines the visitor’s country or US state

2. CookieHub compares the result to your configured regions

   The first matching region applies and determines:

   • Consent dialog layout
   • Consent type
   • Framework logic
   • Cookie blocking behavior

Region matching order

CookieHub checks for matches in this order:

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

More specific regions override broader ones.

Example: If you have a region for California and another for all US states, California users match the California region first.

What settings are applied?

For the matched region, CookieHub applies:

• The selected framework (CookieHub, IAB GPP, or IAB TCF 2.2)
• Consent type (explicit or implied)
• Custom layout and button settings (e.g., “Deny all” option)
• Whether to use a bar or overlay layout
• Optional preference center settings (e.g., auto opt-out for categories)

All other regions are ignored for that user.

Global fallback behavior

If no region matches:

• The Default region is applied automatically
• The Default region can be customized like any other region (framework, consent type, layout)

Summary of rule behavior