sorry, 1 request per second, 60/minute
On Wednesday, March 23, 2022 at 1:15:09 PM UTC+1 Matthew Cloy wrote:
> Hi Peter,
>
> Well my question remains - the current ratelimit is too small to use this
> API in a scalable 3rd party product.
> Are search-volumes going away as a feature one can lever
Hi Peter,
Well my question remains - the current ratelimit is too small to use this
API in a scalable 3rd party product.
Are search-volumes going away as a feature one can leverage to build a
product with more than a handful of users?
(We use search volumes as part of our product in evaluatin
To improve matter, I have just tried batching the requests across our
searches, but can only supply 20 keywords at a time, any more and the API
errors out with "The input has an invalid value".
We are using the API: KeywordPlanIdeas.GenerateKeywordIdeas
Is this the correct API to retrieve searc
We also seem unable to get the search volumes without also retrieving a
list of suggestions for the input keyword - which is different, perhaps
related?
On Tuesday, March 22, 2022 at 11:46:26 AM UTC+1 Matthew Cloy wrote:
> Hi,
>
> We are seeing a HUGE difference in the number of QPS we can perf
Hi,
We are seeing a HUGE difference in the number of QPS we can perform reading
search volumes using Ads API vs our old Adwords API implementation.
We are not interested in managing ads campaigns or actually pushing ads out
/ campaigns etc.. just fetching the google search volumes (and CPC,
