Challenge
While using our Trade Desk integration, 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:
When data is sent from ADvendio to external platforms, two platforms are involved in the process. ADvendio sends the data, while the external platform, which could be an AdServer, receives it. There are various reasons why errors may occur, including authentication issues with the external system, missing settings in ADvendio, or attempting to perform unauthorized actions. For example, trying to change the start date of an active position. We will focus on the most common error messages that occur during our TTD integration, their meanings, and how to avoid them.
What are the most common error cases?
The following information will provide you with a comprehensive understanding of TTD error messages, the underlying causes, and the necessary actions to address integration issues that 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.
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. | 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, if ‘Pace to daily limit’ is selected remember to add a Daily Budget 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 |
| ‘Pace to daily limit’ is selected and no Daily Budget was assigned to the Buying item | Add a Daily Budget to the Buying item |
To resolve common issues and find solutions for error messages, check out section 7.8 Troubleshooting Error Messages: Resolving Common Issues and Solutions.