🧪Troubleshooting

Use these tips to diagnose and debug wrapper integrations.

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: $$PREBID_GLOBAL$$.isLoaded === true

Enable Wrapper Console (via URL)

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

$$PREBID_GLOBAL$$Console=true

Example:

https://example.com/page?$$PREBID_GLOBAL$$Console=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:

$$PREBID_GLOBAL$$_debug=true

Example:

https://example.com/page?$$PREBID_GLOBAL$$_debug=true

This will log detailed wrapper events and operations to DevTools console.

Combine Query Flags

You can combine both flags:

https://example.com/page?$$PREBID_GLOBAL$$Console=true&$$PREBID_GLOBAL$$_debug=true

Note: $$PREBID_GLOBAL$$ here represents the macro placeholder used throughout this documentation. In public environments, use your assigned global variable name.

What to include in a bug report

• Page URL with query flags used

• Console output excerpts (errors/warnings) and network failures

• List of ad units on page and their attributes

• Device, OS, browser version, and UA