- Various internal changes to better deal with missing data returned by queries (#418, #419).
- Fix missing
userType
in the payload which was giving a 401 error (#413). Thanks to @philipwlewis for reporting and fix proposition.
-
read.csv()
now usesencoding = "UTF-8"
to better deal with non-ascii characters (#394). -
Setting locale in queries via the
hl
argument now returns data (@marcf-91). For example,gtrends(keyword = "Macron", geo = "FR", hl = "fr")
. -
It was difficult to maintain an up-to-date database of all country codes supported by Google because they do not provide such a list.
gtrends()
now only checks the syntax structure of the entered code to make sure it matches the iso format (#390).
gtrends()
as a new parametercompared_breakdown
. When set toTRUE
, then the relative hits across the keywords will be returned. Can only be used if onegeo
is used conjointly with more than one keyword. For example:head(gtrends(keyword = c("nhl", "nba"), geo = "CA", compared_breakdown = TRUE)$interest_by_region)
(#404).
-
Skip internet-based tests on CRAN that were found to randomly fail on Debian machine and locally under Ubuntu-latest (#384).
-
Explicitly verify if internet is available before launching the unit tests (#379).
-
Added support for NULL proxy domain, and additional curl options (#339) @alfirrell.
-
Handling related topics with only "Top" or "Rising" sections, as well as those with both @alfirrell.
-
Switch Travis CI to R 4.0.0, use bionic as base.
-
Fixes subsetting in
extract_related_topics
and data processing for Namibia. (#353) @joachim-gassen -
Add more country codes. (#166)
-
Fixes CRAN error on r-devel. (#365)
- Fix an issue when there was no "rising" data returned for the related topics. Some tests were failing due to this issue and causing errors on CRAN (#347).
-
Queries returning hourly data giving without keyword no longer crashes (#323, #336). @JBleher
-
Added the possibility to use search operators like "+" and "-". @JBleher
-
Added unit test using the tinytest package (#316).
-
Fixes issues with Google Trends API changes.
- Dates are parsed correctly when
time = "all"
(#309). @JBleher
-
Added more options to specify time interval of the search (#289). @JBleher
-
Fixed dangling time zone parameters (#290). @JBleher
-
Fixed also issues with different results when requests were issued from different time zones and different locale settings.
-
Download multiple time ranges for direct comparison.
-
Now also an option to only download interest over time is added.
-
Showing the returned status code when it is failing (i.e. not 200) (#304).
-
Bug fix keyword encoding when there are multiple keywords with '&'. (#300, #301) @ThiesDS
-
gtrendsR can now be used behind a proxy, see
setHandleParameters()
(#245) @VictorYammouni -
Fixes breaking changes introduced by Google Trends (#273, #274)
-
Now able to search with "&" character (#267).
gtrends("A&W", geo = "CA")
-
gtrendsR now depends on R >= 3.2.0 (#264)
-
Fixes error when mixing topic and search terms in query (#284) @mamut86
-
It is now possible to use DMA (
gtrends(keyword="obama",geo="US-AL-630")
) (#238). -
Added missing country codes (#213).
-
Can now mix both country and sub country codes (
plot(gtrends("pizza", geo = c("CA", "GB-ENG")))
) (#218). -
New parameter
low_search_volume
allowing low search volume regions (#229). -
Fixing breaking changes that were introduced by Google Trends (#252) @kevinmager65.
-
Can now search without keywords (
gtrends(geo = c("CA"), category = 20)
).
- Due to recent changes to Google Trends API,
gtrendsR
has been almost re-written form scratch. One big visible change is that signing into a Google account is no longer required to download data from Google Trends.
-
Added missing all DMAs within the US (#146).
-
gtrendsR now correctly use the
hl
(local) parameter to retrieve data (@antaldaniel). -
Better support for queries using non-ascii keywords (
gtrends("österreich")
).
-
Added some missing country codes (#94).
data("countries")
. -
Now able to specify for which Google products the request is performed using the
gprop
parameter (#112). Possible values arefroogle
for Google shopping,new
for Google news,youtube
for YouTube videos andimages
for Google images. -
Now able to query using Google categories
?gtrends
(#89). -
Returned data is now tidy (#110). The
trend
object now containskeyword
,hits
andlocation
header (head(sport_trend$trend)
). -
Fixing a bug where overriding
countries
variable was breaking package's functionalities (#109). -
Correct default fallback for querying for google.user and google.password in gconnect (#121)
-
Fixing login issue due to backend changes made by Google (#103). Thanks to @MrLoh for initial implementation and suggestions.
-
Fixing crash occurring when monthly data was returned (#81).
-
gtrends()
will throw a warning if data is returned monthly (#80). -
gtrends()
is now correctly detecting when quota limit is reached (#90).
-
A ggplot2 object can now be returned for further customization.
plot(gtrends("NHL")) + ggtitle("NHL trend") + theme(legend.position="none")
-
Support for hourly and daily data (#67). For example, it is now possible to have hourly data for the last seven days with
gtrends("nhl", geo = "CA", res = "7d")
. Use?gtrends
for more information about the time resolution supported by the package. -
Support for categories (#46). Ex.:
gtrends("NHL", geo = "US", cat = "0-20")
will search only in the sport category. -
Some countries (ex: Hong Kong) were missing from the list (#69).
-
Various typos and documentation work.
-
Added support for sub-countries (#25). Ex.:
gtrends("NHL", geo = "CA-QC")
will return trends data for Québec province in Canada. The list of supported sub-countries can be obtained viadata(countries)
. -
Data parsing should work for any data returned by Google Trends (i.e. countries independent).
-
Better support for queries using keywords in different languages (#50, #57). Ex.:
gtrends("蘋果", geo = "TW")
-
Now able to specify up to five countries (#53) via
gtrends("NHL", geo = c("CA", "US"))
-
Fixing issue #51 allowing UK-based queries via
geo = "GB"
- Fixing issue #34 where connection verification was not done properly.
- Now able to use more latin character in query. For example:
gtrends("montréal")
. - Can now deal with data returned other than in English language.
- First version of gtrendsR