Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Current »

Challenge

While using our Adswizz integration with features like check availability or submit an error message appears that is coming directly from the Adswizz API and indicates an issue during the integration process. What does an error from the API mean and what are the best ways to handle this?

Solution: 

Whenever data is submitted from ADvendio to external platforms, two platforms are involved. ADvendio sends the data, while the external platform (such as the Ad Server) receives it. There can be various reasons for encountering errors, such as authentication issues with the external system, missing settings in ADvendio, or attempting to perform unauthorized actions, like altering the start date of a position that is already active.

We will discuss the most frequent error messages that occur during our Adswizz integration, their meaning, and how to avoid them.

What are the most common error cases?

With the below information, you'll be equipped with a clear understanding of Adswizz error messages, the reasons behind them, and the necessary steps to troubleshoot and overcome integration challenges you may encounter:

  1. Error Message: You'll see a list of different error messages, each with its type and wording.

  2. Reason: We provide explanations to help you understand what caused the error message. This will give you insights into why the issue occurred.

  3. Solution: For each error message, we offer troubleshooting steps to resolve the problem. These steps guide you towards finding a solution and getting past the error.

AdSwizz Error Message

Reason

Solution

com.advendio.mediacloud.adServer.adswizz.restServices.utils.AdsWizzException: 400 - constraint.violated: The request entity had the following errors: (Errors: constraint.ad.targeting.zones.empty: Zones may not be empty (zoneIds); )

It seems that the item you are trying to submit does not have any defined zones.

Please specify which zones should be used for the item.

You can achieve this by connecting Zones to the Ad Spec: 3.2.1 Create Ad Spec, Ad Price, and link to AdServer

Alternatively you can use Inventory Targeting on the Campaign Item to determine which inventory to target in external systems: 4.3.4.5 How to configure which inventory to targeting in External Systems?

Once you have completed these steps, please attempt to submit the item to AdsWizz again.

(No Ad Server Specified or it is inactive: null)

Our Gateway cannot determine the Ad Server it needs to connect to. It is possible that the item you are using is not linked to any AdServer.

Ensure the following:

  • that the AdType connected to your campaign item has an Ad Server Login entered

  • that the AdServer Login in ADvendio is active, otherwise it will be ignored from our Gateway.

Delivery Report Error: No Response from Adswizz API

There is the possibility you encounter the following error message, when using our delivery report features for Adswizz.

Adswizz API does not respond to our Delivery Report, please try the report again to a later time and check if your configuration in ADvendio is correct.

This means that there has been a problem in the communication with the Adswizz API. In certain cases, requests for reporting data are not answered in by Adswizz and thus no data could be imported into ADvendio. Our implementation strives to retry communication until we receive results, but in certain cases, we will need to cancel and show the message in the result email.

55133391-05ec-4563-bbd3-5ff0f632aede.png

This will mean the following for you:

  • In this specific case, we will cancel our delivery import and not update any of the ADvendio Items, we need to proceed like this in order to make sure there are no number mismatches on individual Campaign Items. This means the numbers from the last delivery import will still be present

  • The next scheduled run of the delivery import (e.g. for Monthly imports it’s planned once a day, so it could be the same time next day) will continue as usual. In most cases we expect that this run should finish again successfully.

  • If you need data to import urgently, you can use our delivery report center, and schedule a new import for the next full hour.

Common Issues and Solutions


For most common error cases have a look here at 7.8 Troubleshooting Error Messages: Resolving Common Issues and Solutions.


  • No labels