...
...
...
...
...
...
...
...
Challenge
While using our Equativ integration with features like check availability or submit an error message appears that is coming directly from the Equativ API. 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 that sends data and the external platform (e.g. the AdServer) receives data.
...
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). We are looking at the most common error messages returned from our Equativ 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 Equativ error messages, the reasons behind them, and the necessary steps to troubleshoot and overcome integration challenges you may encounter:
...
Error Message | Reason | Solution |
|---|---|---|
(No AdServer 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. |
...