Hi,
Thank you for reaching us out. I am Sherwin from Google Ads API support team. I
hope that you are doing well today.
Moving forward to your concern, the reason why you got that error message is
because, the expanded_text_ad is deprecated last June 30, 2022. You may check
this blog post for
Hi,
Thank you for reaching out to us.
Moving forward, Yes, the Google Ads API can be called either using gRPC or
REST. Both interfaces expose a resource-oriented design shared with other
Google Cloud APIs.
Since this is for Google Ads API, You need both OAuth 2.0 application
credentials and a
Reposting the last inquiry
(https://groups.google.com/g/adwords-api/c/l6F3J7HI33s) from the forum as
it wasn't routed to our support queue.
Regards,
Heidi
Google Ads API Team
On Wednesday, August 10, 2022 at 1:04:46 AM UTC+8 rohitl...@optmyzr.com
wrote:
> Is using *REST* Interface stable enoug
Hi Team,
I have also tried to make search request
https://googleads.googleapis.com/v10/customers/{customerId}/userLists:Search
Method: Post
body: {
"pageSize": 1,
"query": "SELECT user_list.id, user_list.description FROM user_list"
}
Response: 404 not found
Thanks,
Shan
On Thursday, Apr
Hello,
Thank you for reaching out to us.
So our team can also check on this, can you share to us the following details
below?
CID
login-customer-id
Complete API logs (request and response with request-id) for those 2 queries
Please send the requested details via the Reply privately to author o
