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 4 Current »


While using our Google Ad Manager integration with features like check availability or the submit, an error message appears that is coming directly from the Google API. What does this mean and what are the best ways to handle this?


What does an error from the API mean?

When submitting data from ADvendio into external platforms, there are always to platforms involved. ADvendio as the system which sends data and the external platform (e.g. the AdServer) which 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 Google AdManager integration, what they mean and how to prevent them.

What are the most common error cases?

Also have a look here 7.8 Error Messages.

Also have a look here 7.8 Error Messages.

Error MessageReasonSolution
com.advendio.mediacloud.adServer.adswizz.restServices.utils.AdsWizzException: 400 - constraint.violated: The request entity had the following errors: (Errors: 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: Inventory Targeting

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.

  • No labels