gtrendsR 1.5.1

• Fix missing userType in the payload which was giving a 401 error (#414). Thanks to @philipwlewis for reporting and fix proposition.

gtrendsR 1.5.0

Bug fixes

• read.csv() now uses encoding = "UTF-8" to better deal with non-ascii characters (#394).

• Setting locale in queries via the hlargument 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).

New feature

• gtrends() as a new parameter compared_breakdown. When set to TRUE, then the relative hits across the keywords will be returned. Can only be used if one geo 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).

gtrendsR 1.4.8

• 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.

gtrendsR 1.4.7

• 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)

gtrendsR 1.4.6

• 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).

gtrendsR 1.4.5

• 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.

gtrendsR 1.4.4

• Dates are parsed correctly when time = "all" (#309). @JBleher

gtrendsR 1.4.3

gtrendsR 1.4.3

• 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 v1.4.2

gtrendsR 1.4.2

• 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)

gtrendsR v1.4.1

gtrendsR v1.4.1

• 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)).