Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 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: 

When submitting Whenever data is submitted from ADvendio to external platforms, there are always two platforms are involved. ADvendio is sends the system which sends data and , while the external platform (e.g. the AdServersuch as the Ad Server) 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 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 own 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

Code Block
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 It seems that the item you are trying to submit does not have any defined zones.

Please define, specify which Zones zones should be used for the Itemitem.

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

Or via Alternatively you can use Inventory Targeting on the Campaign Item to determine which inventory to target in external systems4.3.4.5 How to configure which inventory to targeting in External Systems?

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

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

Our Gateway can not find which AdServer cannot determine the Ad Server it needs to connect 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 . 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

set to active? If inactive
  • is active, otherwise it will be ignored from our Gateway.

Common Issues and Solutions


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