Activity
Newest
Oldest
Ilya Zub
planned
We stopped implementing Google Trends API because now we improve the engines we already support. We will re-evaluate this feature request in the future.
J
Jeff Schneider
Ilya Zub: clarify please; you killed this?
Ilya Zub
Jeff Schneider: We haven't worked on Google Trends API since April. We'll update the status once someone from our engineering team will continue to work on this feature.
J
Jeff Schneider
We're doing some planning on our end and really need a delivery date on this feature.
Ilya Zub
Jeff Schneider: What data do you want to be extracted from Google Trends? This information will help us to reduce the scope.
J
Jeff Schneider
Ilya Zub: Yes. Use this query as an example: https://trends.google.com/trends/explore?geo=US&q=demandbase,6sense Then, download the .CSV and look at it. The data is a time-series over some duration for one ore more terms. We want the contents of the CSV but as a standard API call (http/json). Our filter criteria will always be: "United States", "Past 12 Months", "All Categories", "Web Search".
Ilya Zub
Jeff Schneider: Thank you! So you want only the
multiTimeline.csv
?J
Jeff Schneider
Ilya Zub: Yes, just convert the .csv to as a standard api format. That's it.
I
Itai Dagan
Hi Elizabeth Oster :)
there is an ETA on this feature?
thanks!
Elizabeth Oster
Itai Dagan: Not yet, we have a working version of the API at this point so we're in the review process.
Milos Djurdjevic
in progress
J
JS
Hi Elizabeth, any ETA on this feature?
Elizabeth Oster
JS: I've bumped the priority of this in our backlog. We still have other features that we are working on at the moment. But we should begin development on this soon.
J
JS
any idea when will this be implemented?
J
JS
make sure you support all dates: now%201-H, now%204-H, now%201-d, etc in adition to date ranges
related queries: both rising and top
and average for each keyword
it should support up to 5 keywords
Julien Khaleghy
planned