Challenge
When using our Trade Desk integration, such as checking availability or submitting, you may encounter an error message directly from the TTD API. What does this error indicate and what are the most effective methods for managing it?
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 AdServer) 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 TTD 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 TTD error messages, the reasons behind them, and the necessary steps to troubleshoot and overcome integration challenges you may encounter:
Error Message: You will 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 toward finding a solution and getting past the error.
Currently, we have not received any reports of TTD error messages. However, if you experience any problems, please get in touch with us.
Error Message | Reason | Solution |
|---|---|---|
Id: SYNTAX, Code: $.RTBAttributes.MaxBidCPM.Amount: Error deserializing the request as JSON: The value {null} is not valid for this property. & $.RTBAttributes.BaseBidCPM.Amount: Error deserializing the request as JSON: The value {null} is not valid for this property. | No values in “Base bid” and “Max Bid” fields | Add values accordingly to both fields |
When Pacing mode is Off, (all flights of) the Paused campaign must have one of DailyBudget or DailyBudgetInImpressions set. | Nor Pacing mode or DailyBudget/Impressions has been added | Select a Pacing Mode or add a Daily Budget/Impressions to the Buying item |
$.AdvertiserId: The property ‘AdvertiserId’ may not be set to Paused null. & $.CampaignFlights[0].EndDateExclusiveUTC: Specified date must be valid and occur in the future | Advertiser not properly mapped. End date in the past | Set up an Advertiser correctly to a valid Connection ID. Check end dates of Buying order/Items to be in the future |
To resolve common issues and find solutions for error messages, check out section 7.8 Troubleshooting Error Messages: Resolving Common Issues and Solutions.