The Gilt technology organization. We make work.

Importing Google Trends data

Igor Elbert analytics

Google Trends offers a trove of data for analysis. It’s not used nearly enough partially because good folks at Google did not provide an API to access the data. You can play with Trends in you browser, embed it into your webpages but it’s not that simple to get the raw data behind it to use it in your analysis.

There is a number of packages in Python, Perl, or R that pull the data for you but none of them did when I needed: compare hundreds of trends against each other.

You see, not contend with the lack of API Google returns trends on 1 to 100 scale so it’s hard to compare numbers for many different trends. You can plot several trends on the same graph but you will not be able to tell how they stand relative to another set of trends.

For example:


Above: “Game of Thrones” vs. “House of Cards”.
Below: “Orange is New Black” vs. “The Newsroom” 

Since each set is rescaled there is no way to tell how “House…” stands against “Orange…” 


I needed to get the trends for hundreds of fashion brands Gilt deals with and compare them against each other.

The logical solution seemed to use one search term as a baseline in every set and then rescale the results relative to a baseline term.

I borrowed heavily from GTrendsR package and came up with a script in R that pulls trends and rescales them relative to baseline.

It took some hacking: I took Google Trends export link that looks something like,+/m/0tlwzvq,+/m/0b6hm_f,+/m/0c5_m3,+/m/0f4w93&geo=US&date=2/2013+25m&cmpt=q&tz&tz&content=1&cid=TIMESERIES_GRAPH_0&export=5

and after looking at various export options found the one (export=3) that returns raw data in JSON-like string. For example:


// Data table response
 {"id":"query0","label":"Agent Provocateur","type":"number","pattern":""},
 {"id":"query1","label":"Kate Spade","type":"number","pattern":""}
 {"v":new Date(2015,3,18),"f":"Saturday, April 18, 2015"},
 {"v":new Date(2015,3,19),"f":"Sunday, April 19, 2015"},
 {"v":new Date(2015,3,20),"f":"Monday, April 20, 2015"},
 {"v":new Date(2015,3,21),"f":"Tuesday, April 21, 2015"},
 {"v":new Date(2015,3,22),"f":"Wednesday, April 22, 2015"},
 {"v":new Date(2015,3,23),"f":"Thursday, April 23, 2015"},
 {"v":new Date(2015,3,24),"f":"Friday, April 24, 2015"},

Which is turned into a valid JSON with 4 lines of R code and then parsed into R data structures with rjson package.

The result looks like:


And can now be analyzed, plotted, and joined with other data.


Because of the powers of SQL/MapReduce in our Teradata Aster database we can pull the trends and join with our relational data on the fly in SQL:

      ON (SELECT brand_name from dim_brands)
      PARTITION BY brand_name
      OUTPUTS('week DATE, term VARCHAR, trend INTEGER’)

Any comments on Google Trends, R style and overall approach are appreciated.

Happy trending!

Google Trends 1 Data 1 How-To 1