...
...
...
...
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 indicate an issue during the integration process. What does an error from the API mean and what are the best ways to handle this?
...
Solution:
When submitting data from ADvendio to external platforms, there are always two platforms involved. ADvendio is the system which sends data and the external platform (e.g. the AdServer) receives data. While we try to focus our application on validating the item configuration within ADvendio so that we're not sending faulty data in our requests, there are still certain cases where an error is returned and shown in our interface as well as the result email:
...
This can have different reasons, for example, a problem with the authentication against the external system, a missing setting in ADvendio, or you are trying something which is generally not allowed (like changing the start date of an already running position). Following we are looking at the most common error messages returned from our Adswizz integration, what they mean and how to prevent 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:
Error Message: You'll see a list of different error messages, each with its own type and wording.
Reason: We provide explanations to help you understand what caused the error message. This will give you insights into why the issue occurred.
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); ) | There are no Zones defined for the Item you are trying to submit | Please define, which Zones should be used for the Item. You can do this by connecting Zones to the Ad Spec: 3.2.1 Create Ad Spec, Ad Price, and link to AdServer Or via Inventory Targeting on the Campaign Item: 4.3.4.5 How to configure which inventory to targeting in External Systems? Afterwards, try to submit the Item to AdsWizz again |
(No Ad Server Specified or it is inactive: null) | Our Gateway can not find which AdServer it needs to communicate with. The Item you're using is maybe not connected to an AdServer. | Check two things: For your campaign item, has the connected AdType an AdServer Login entered? If that is true, is the AdServer Login in ADvendio set to active? If inactive it will be ignored from our Gateway. |
For most common error cases have a look here at 7.8 Troubleshooting Error Messages: Resolving Common Issues and Solutions
...