Troubleshooting

Here are some pointers that can be useful when troubleshooting why no ad is displayed.

1. Is the container active?

Open ADK Panel and check Include inactive. Verify that the container is in the list and not marked as inactive.

• If the container is not represented in the list, go to step 2.
• If it is inactive, verify that the ADK breakpoints are correctly configured and that you are on the right screen size, and try again.
• Otherwise, continue to step 4.

2. Is the container div in the HTML document?

Open the browser dev tools and verify that the container div is present in the document. For example, if you have configured a container called my-container, your HTML should contain a corresponding element:

<div data-adk-container="my-container"></div>

If the container div is not present, add it and try again.

3. Is the container attached?

Verify that the container div has a data-adk-instance attribute. If it does not, it means that the container is not attached. You can verify that this is the case by running the command adk.container.attach() in the browser's Javascript console. The attribute will then be added to the div. The solution is to find a suitable location in the integration code to add the attach call. You can learn more about attaching containers in the Publisher integration section.

4. Is lazy loading delaying the request?

If lazy loading is enabled, ADK waits to request content until the container is near the viewport. Scroll closer to the container, or temporarily disable lazy loading to check whether this is the cause.

5. Is there consent to read and write cookies?

If a TCFv2 CMP is available when ADK loads, ADK will wait for consent before reading/writing cookies and making ad requests. Try disabling the TCF check by setting __ADK_TCFAPI__ = false before loading ADK. If that solves the problem, verify that your CMP configuration includes Advisible AB (vendor ID 900). Try clearing the consent cookie and reload the page.

6. Is an ad requested and delivered?

Open the network tab in the browser dev tools. Filter on advisible.com and verify that a request is made to the query endpoint. If the result is an empty array (i.e., []), it means that no ad was delivered. Test ads should generally be used instead of live ads when testing an integration.

7. Is the ad template loaded?

If the template is an HTML file, verify in your ADK config that the URL is linked to the adapter with addTemplate(). Open the network tab in the browser dev tools and use the filter to verify that the HTML file is loaded. If the ad is rendered using a Javascript function, you can debug it by adding console logs.