Hi all, We're looking for an update regarding Google's effort to not falsely identify ad text as containing phone numbers and marking the ad disapproved because of the PHONE_NUMBER_IN_AD_TEXT topic
This has previously been brought up by myself on this forum : https://groups.google.com/g/adwords-api/c/XTiXR6IXZlU/m/rQZAQTgBAQAJ Our clients are increasingly growing frustrated because ads that clearly have nothing close to resembling a phone number are being disapproved by Google's automated systems For example, this expanded text ad is disapproved because Google says it contains a phone number: type: EXPANDED_TEXT_AD expanded_text_ad { headline_part1: "Preowned Silverado 2500HD" headline_part2: "Priced As Low As $60,167" headline_part3: "XXX Ford" description: "We\'ve Got It On The Lot Today At XXX Ford." description2: "Call Our Team Today & Schedule A Test Drive!" path1: "Used" path2: "" } Clearly there is no phone number there. In the previous forum thread we went forward with the guidance to make sure we're adding ignorable policy topics to ads *on creation* in an effort to head this off. I'm not sure if that ever worked that well as this is an ongoing problem. Here is a request, request-id E1xHa8pD5WxhHpB_Ecuk2w, where we add a policy_validation_parameter with ignorable_policy_topics containing PHONE_NUMBER_IN_AD_TEXT in an effort to alert Google to the fact that there are no phone numbers in the Ad. Before mutation attempt, the ad had a status of: policy_topic_entries : [type: PROHIBITEDtopic: "PHONE_NUMBER_IN_AD_TEXT"] review_status : REVIEWED approval_status : DISAPPROVED Here is the attempt to get Google to re-review the Ad and realize there's no phone number: Request ------- MethodName: google.ads.googleads.v10.services.AdService/MutateAds Endpoint: googleads.googleapis.com:443 Headers: {developer-token=REDACTED, login-customer-id=ABC, x-goog-api-client=gl-java/11.0.13 gccl/17.0.1 gapic/17.0.1 gax/2.6.1 grpc/1.41.0} Body: customer_id: "XYZ" operations { update { type: EXPANDED_TEXT_AD expanded_text_ad { headline_part1: "Preowned Silverado 2500HD" headline_part2: "Priced As Low As $60,167" headline_part3: "XXX Ford" description: "We\'ve Got It On The Lot Today At XXX Ford." description2: "Call Our Team Today & Schedule A Test Drive!" path1: "Used" path2: "" } resource_name: removed id: removed final_urls: removed } update_mask { paths: "resource_name" paths: "id" paths: "final_urls" paths: "type" paths: "expanded_text_ad.headline_part1" paths: "expanded_text_ad.headline_part2" paths: "expanded_text_ad.headline_part3" paths: "expanded_text_ad.description" paths: "expanded_text_ad.description2" paths: "expanded_text_ad.path1" paths: "expanded_text_ad.path2" } policy_validation_parameter { ignorable_policy_topics: "CAPITALIZATION" ignorable_policy_topics: "PHONE_NUMBER_IN_AD_TEXT" } } Response -------- Headers: Metadata(content-disposition=attachment,content-type=application/grpc,request-id=E1xHa8pD5WxhHpB_Ecuk2w,date=Tue, 22 Feb 2022 21:59:52 GMT,alt-svc=h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43") Body: results { resource_name: removed } Failure message: null Status: Status{code=OK, description=null, cause=null}. The mutate succeeds and the ad is temporarily given a different status: review_status : REVIEW_IN_PROGRESS approval_status : UNKNOWN After a few minutes the ad is back to a dissaproved status policy_topic_entries : [type: PROHIBITEDtopic: "PHONE_NUMBER_IN_AD_TEXT"] review_status : REVIEWED approval_status : DISAPPROVED So a couple things here ... the ad very clearly does not have a phone number in it, and never has had a phone number in it. What is Google doing to correct this false trigger? This is precluding Ads from running which in turn results in less spend at Google which means less Google revenue. Is there something else we should be doing with regards to policy_validation_parameter or ignorable_policy_topics or exemption requests to get these Ads to pass the no-phone-number test? Our clients are getting increasingly agitated regarding this topic as it seems very easy to be able to detect if there actually is a phone number in the Ad and they're wondering why Google can't figure this out. Thanks Pete -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/c81c0d7c-ca60-4f45-88df-143a7f209675n%40googlegroups.com.
