Hello Pete,
Could you do me a huge favor? Could you in the forum choose 'Reply to author'
and send me the request ID of one of the requests where you are seeing this? I
don't want to accidentally track down a similar ad when taking a look at this.
Thanks,
Nadine Wang
Google Ads API Team
ref:_0
included in your mutate Ad
> request, and still flagging with policy PHONE_NUMBER_IN_AD_TEXT error. In
> my view, I suspect probably the ad description part where numbers are
> included is causing policy errors. However, as you mentioned, this time you
> encountered it again despite putti
Jinky,
The complete request, response and request-id is literally in the initial
post.
request-id E1xHa8pD5WxhHpB_Ecuk2w
Request
---
MethodName: google.ads.googleads.v10.services.AdService/MutateAds
Endpoint: googleads.googleapis.com:443
Headers: {developer-token=REDACTED, login-customer-id
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/adword
Hi Xavier,
Thank you for reaching out to us.
It appears that this "descriptions {text: "$12,000 - $16,000 - Part-Time -
Resumes requested, please apply on Get.It."}" is the cause of the error you've
encountered. With that, kindly confirm to the Product Team if this is the value
that causes the
Hi guys, I'm trying to create an Ad using the API but I'm getting this:
*Request:*
Method: /google.ads.googleads.v9.services.AdGroupAdService/MutateAdGroupAds
Host: googleads.googleapis.com
Headers: {
"developer-token": "REDACTED",
"login-customer-id": "X",
"x-goog-api-client": "gl-p
