API Error for Destination not working. How to resolve?

[Oskar Wallén]

Hi, 

We've just recently started experiencing something new in the API and we are wondering how we can resolve this. 

Some customer's  URLs seems to be flagged. From the timestamp in my example it looks like it was about a year ago, I have removed the URL for privacy purposes.

All insights are helpful on how we can resolve this. 

Example json response: 

{"error":{"code":400,"message":"Request contains an invalid argument.","status":"INVALID_ARGUMENT","details":[{"@type":"type.googleapis.com\/google.ads.googleads.v12.errors.GoogleAdsFailure","errors":[{"errorCode":{"policyFindingError":"POLICY_FINDING"},"message":"The resource has been disapproved since the policy summary includes policy topics of type PROHIBITED.","location":{"fieldPathElements":[{"fieldName":"operations","index":0},{"fieldName":"create"},{"fieldName":"ad"}]},"details":{"policyFindingDetails":{"policyTopicEntries":[{"type":"PROHIBITED","evidences":[{"destinationNotWorking":{"dnsErrorType":"HOSTNAME_NOT_FOUND","device":"DESKTOP","expandedUrl":"###","lastCheckedDateTime":"2022-08-06 16:09:58"}},{"destinationNotWorking":{"dnsErrorType":"HOSTNAME_NOT_FOUND","device":"IOS","expandedUrl":"###"}}],"topic":"DESTINATION_NOT_WORKING"}]}}},{"errorCode":{"policyFindingError":"POLICY_FINDING"},"message":"The resource has been disapproved since the policy summary includes policy topics of type PROHIBITED.","location":{"fieldPathElements":[{"fieldName":"operations","index":1},{"fieldName":"create"},{"fieldName":"ad"}]},"details":{"policyFindingDetails":{"policyTopicEntries":[{"type":"PROHIBITED","evidences":[{"destinationNotWorking":{"dnsErrorType":"HOSTNAME_NOT_FOUND","device":"DESKTOP","expandedUrl":"###","lastCheckedDateTime":"2022-08-06 16:09:58"}},{"destinationNotWorking":{"dnsErrorType":"HOSTNAME_NOT_FOUND","device":"IOS","expandedUrl":"###"}}],"topic":"DESTINATION_NOT_WORKING"}]}}}],"requestId":"ISKv0C2T567sgNfKQyAemQ"}]}}

[Google Ads API Forum Advisor]

Hi Oskar,

 

Thank you for reaching out to the Google Ads API Support Team.

 

Upon checking, a POLICY_FINDING error indicates that the ad you created has triggered policy violations. You may refer to this guide <https://developers.google.com/google-ads/api/docs/policy-exemption/overview?hl=en#handle_ad_policy_violations> for an example on how to automatically handle ad policy violations. You can check this Ads help center on Google Ads policies for more information: https://support.google.com/adspolicy/answer/6008942. For the error DESTINATION_NOT_WORKING, you may check this Ads help article <https://support.google.com/adspolicy/answer/6368661?sjid=7350203794489560122-AP#673> for some options in order to resolve it.

 

As an aside, I've observed that you're still sending your requests to version 12 of the API which is already deprecated. I would advise updating to the latest version of the API as issuing your requests to a deprecated (or sunset) version of the API may incur risks of losing access to it. You can check the below links for more information as well as how to do so:

• Deprecation and sunset dates - https://developers.google.com/google-ads/api/docs/sunset-dates
• Upgrade to the latest version - https://developers.google.com/google-ads/api/docs/upgrade

 

In the event that you'd need further assistance regarding the Google Ads API or have any clarifications, just let us know.

 

This message is in relation to case "ref:_00D1U1174p._5004Q2n8KFW:ref"

Thanks,
 

Google Ads API Team

[Oskar Wallén]

Hi 

Thank you for your timely response. 

As for the error at hand I wonder how we can trigger a scan of the website through the API.

As you can the timestamp suggests that website was scanned "2022-08-06 16:09:58". This particular policy violation can't be resolved automatically.  

This is a long time ago and the website is working? 

Yes we know we are using v12 and will be upgrading well before sunset as suggested in the link you provided. 

Kind regards

[Google Ads API Forum Advisor]

Hi Oskar,

Thank you for getting back to us. 

Please note that in Google Ads API perspective, the timestamp you mentioned which pertains to the last_checked_date_time field will only return the time the URL was last checked as per this reference (https://developers.google.com/google-ads/api/reference/rpc/v12/PolicyTopicEvidence.DestinationNotWorking). Since the API only mirrors the UI, with regards to triggering a scan to the website, would you be able to share with us the UI screenshot for this feature? This is so we could provide more appropriate guidance in performing this via API. 

Additionally, with regards to resolving the policy violation, I would recommend reaching out Google Ads product support team (https://support.google.com/google-ads/gethelp) for more appropriate insights on this issue.