Skip to main content
All CollectionsAd Serving
Testing and debugging a VAST campaign
Testing and debugging a VAST campaign
Konstantin Manzuk avatar
Written by Konstantin Manzuk
Updated over a week ago

First of all, please check if VAST tag URL matches with all the points from notes section from this article

To test a VAST campaign, choose a "Test mode" in "Prioritize your campaign" in campaign settings and put your device advertising ID/IDFA into a "Test device IDs" field and save the campaign.

You can check if the campaign is in the ad waterfall by going through Appodeal SDK logs in your app. To enable logging, follow the instructions in this article. If the campaign is loaded and shown, then everything is configured right.

If it is loaded, but not shown, please contact Appodeal support.

If it is not even loaded, please follow the next steps: 

  1. Configure Charles as a man-in-the-middle HTTPS proxy, following the instructions in these articles:

2. Make sure that there are requests to the VAST URL domain in the Charles after SDK initialization. If it is there, right-click on the one and choose “Enable SSL proxying” option, then restart Charles.

3. Open the request and pay attention to the URL for the following details: there should be no non-parsed macros and whitespaces, the URL should be displayed in its entirety.

4. Click on “Response": you will see a server response, and if everything is fine, it should look like this:

5. If response is empty or contains some errors or messages, please contact an ad provider support.

Did this answer your question?