Hello Team,
Can you confirm that this is an API limitation and is possible from the
Google Ads Platform? I can attach exclusion audience to a VIDEO type
campaign, and value rules to a PERFORMANCE_MAX campaign from the UI. Does
it mean that it is non functional from the platform as well?
Essentially I know there are tools like super metric that allow you to
authenticate with Oauth providing an adwords scope. From this point without
providing any additional value they are able to list my accessible ad
accounts and pull data from these accounts.
however when I try to do the same
Hi Team,
I am using the keyword_view table from the API but noticed that the
"ad_group_criterion_status" is not updating daily (I paused a keyword the
2nd of May and its still showing as Enabled in the report). Is there a
specific refresh rate for this metric/table?
--
--
Hello,
Thank you for getting back to me. I appreciate your assistance on this
matter. Looking forward to your response once you have more information.
On Fri, May 10, 2024 at 8:05 PM Google Ads API Forum Advisor
wrote:
> Hello,
>
> I'm checking with the team on the status of this fix. I know
Hi,
Thank you for reaching out to the Google Ads API support team.
To create keywords for campaigns with a resource name, you may use this
endpoint "Method: customers.campaignCriteria.mutate ". Also, to create keywords
for ad group with resource name, you may use this end point "Method:
Hi Nasser,
As mentioned earlier, the value rule set is attached to a campaign that does
not support value rules. Currently, campaign level value rule sets can only be
created for Search, or Display campaigns. The Performance Max is not supported
in this value rule. Having that said, we would
Hi,
As requested earlier, in order to investigate why the
query_resource_consumption is returning zero, provide us with the complete API
logs (request and response logs with request-id and request header) generated
at your end.
If you are using a client library and haven't enabled the logging
Hello,
I'm checking with the team on the status of this fix. I know it was planned for
v16_1 but it's not clear whether it actually made that release. I'll let you
know when I find out.
Also, for additive minor releases like v16_1, the API version remains v16 for
actual requests and other
Hi,
I would like to know how to identify expensive queries right now.
I manage tens of thousands of accounts, and each account runs multiple
queries every day.
If there are any expensive queries, errors may occur frequently after June
17th.
To avoid this, I would like to know in advance
