Core Concepts
How ConsentStack decides what to block, who sees a banner, and which consent rules apply to each visitor.
ConsentStack works out three things on every page load: where your visitor is, which consent rules apply there, and which scripts have to stay blocked until they choose. These pages explain the moving parts behind that.
If you are setting up for the first time, start with Getting Started. Come back here when you want to understand why the banner behaved the way it did.
Consent Models
Opt-in, opt-out, and notice-only are three different legal defaults, and the right one depends on where your visitor is sitting. This page covers how ConsentStack picks a model per visitor and what each one changes about the banner.
Categories & Regions
Every cookie and script is sorted into a category, and every visitor is matched to a region. Together those two decide what runs before consent. This page covers the category definitions, how regional rules are resolved, and what happens when a visitor's location is unclear.
Script Blocking
The part that does the actual work. ConsentStack detects third-party scripts and holds them until consent allows them, including tags injected by Google Tag Manager. This page explains the blocking mechanism and how to check it is working.
Banner & Preferences
What your visitors see and interact with: the banner itself, the preferences center, and the re-entry control that lets someone change their mind later.
Importing Consent
Switching from another CMP does not have to reset every visitor. ConsentStack can read the consent record your previous platform left behind and honor it, so returning visitors are not asked again. This page covers which platforms are supported and what carries over.