Challenge
When While 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 When data is submitted sent from ADvendio to external platforms, two platforms are involved in the process. ADvendio sends the data, while the external platform (such as the AdServer) , which could be an AdServer, receives it. There can be are various reasons for encountering why errors may occur, such as including authentication issues with the external system, missing settings in ADvendio, or attempting to perform unauthorized actions, like altering . For example, trying to change the start date of a position that is already activean active position. We will discuss focus on the most frequent common error messages that occur during our TTD integration, their meaningmeanings, and how to avoid them.
What are the most common error cases?
With the below information, you'll be equipped with a clear The following information will provide you with a comprehensive understanding of TTD error messages, the reasons behind themunderlying causes, and the necessary steps actions to troubleshoot and overcome integration challenges 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.
| Info |
|---|
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 the “Base bid” 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 is assigned to the Buying item | Add a Daily Budget to the Buying item |
Web Service Exception: Missing Query ID for TOTAL interval, please check the Additional Delivery Report settings in your thetradedesk connection Error processing result lines: Empty response from service | No AdditionalDeliveryReportSettings or Query ID is present for one or all the options needed (Daily, Monthly, and Total) to generate the report | Case #1: Go to AdditionalDeliveryReportSettings in your connection and create the missing one(s) (Daily, Monthly or Total) Case #2: Go to the AdditionalDeliveryReportSettings and check on each one of them that QueryID has the Template ID value from The Trade Desk report template. |
| Info |
|---|
To resolve common issues and find solutions for error messages, check out section 7.8 Troubleshooting Error Messages: Resolving Common Issues and Solutions. |