# Debugger

The Consent Pro Debugger is an overlay that runs on your own site and reports what the runtime actually loaded — the banner it chose, whether the runtime is active, and which tracker categories are blocked before the visitor interacts.

## Open the debugger

Click **Preview** in the project header. Consent Pro opens your production domain in a new tab with a signed debugger token attached, and the overlay loads with the page.

Opening the preview is also what completes the **Preview banner on your website** step in **Initial setup** — seeing the banner in place is the one check Consent Pro cannot run for you.

The overlay starts collapsed as a **Consent Pro Debugger** pill. Click it to expand.

![The expanded Consent Pro Debugger overlay on a custom site](/web-app/debugger.png)

**info Access is token-based**
The token comes from your project, so the debugger loads on your production domain without leaving anything enabled for ordinary visitors. Open it through **Preview** rather than constructing the URL by hand.


## What it reports

**Banner Setup**

| Field       | Meaning                                            |
| ----------- | -------------------------------------------------- |
| Geolocation | The region the runtime resolved for this visit     |
| Banner Type | The banner that region maps to, such as **Opt In** |

**Initial Checks**

- **Consent Pro Runtime Active** — the runtime loaded and is running on the page.
- **Correct banner displayed** — the banner on the page matches the one the resolved region expects.

**Trackers before user interaction**

Each tracker category is listed with the number of trackers in it and whether it is **Allowed** or **Blocked** before the visitor has responded. Under an opt-in banner, every non-essential category should read **Blocked**.

## Simulating another region

**Geolocation** can be changed to another region to see which banner that region resolves to, without a VPN. The banner type updates to match the region mapping in your project.

Region mappings must be published before the debugger reflects them — see [Publishing Changes](/web-app/publishing).

## Reset the banner

**Reset Banner** clears the stored consent for the site so the banner appears again as it would for a first-time visitor. Use it after changing banner settings, since a stored consent otherwise suppresses the banner on later visits.