> For the complete documentation index, see [llms.txt](https://docs.hbwrapper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hbwrapper.com/troubleshooting.md).

# Troubleshooting

Use these tips to diagnose and debug wrapper integrations. Most problems come down to a small mismatch between what's on the page and what's in the configuration — the checks below catch the common ones quickly.

The debugging tools work by adding a short flag to the end of the page's web address (a "query string"). This turns on an on-screen console or extra logging just for you, without affecting normal visitors.

> **A note on `pbjs` in this page:** `pbjs` is the wrapper's global variable name, set per site by the `globalVar` setting in `config.json`. It's `pbjs` by default and is used throughout these examples. **If your site uses a different `globalVar`, replace `pbjs` with that name** — including in the URL flags below (e.g. a site using `chp` would use `chpConsole=true`).

## Symptoms

* No ads rendering
* Long auctions or frequent timeouts
* Unexpected size or device behavior
* Ad refresh not happening as expected

## How to verify

* Check that `data-aaad='true'` is present on ad unit divs
* Check that `data-aa-adunit` uses the GAM Ad unit CODE and full path
* Confirm `Sizes` and device attributes match configuration
* Verify the wrapper is loaded: `pbjs.isLoaded === true`

## Enable Wrapper Console (via URL)

Append this query string to your page URL to show the wrapper console UI overlay:

```
pbjsConsole=true
```

Example:

```
https://example.com/page?pbjsConsole=true
```

This opens an on-page console with high-level status, ad unit states, and actions.

## Enable Verbose Debug Logging (via URL)

Append this query string to enable verbose logging in the browser console:

```
pbjs_debug=true
```

Example:

```
https://example.com/page?pbjsConsole=true&pbjs_debug=true
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hbwrapper.com/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.