This guide will walk you through the steps required to properly set up googleAnalyticsR in terms of installation and authentication.
It assumes you have R installed on your machine and access rights to one or more Google Analytics accounts. In this case it will only take a few lines of R code to make a first test call to the GA API following the examples below.
The rest of this guide will give you an overview of the available set up options and cover some good practices to follow under different scenarios of use.
If you wish to try out the library before installation, an RStudio Cloud project is available that has the library pre-installed.
Once you are logged in, issue the following two R commands in the R console bottom-left:
1: Yes to say you wish to keep your OAuth access credentials.
The library should then launch a browser window and ask you to login to Google - log in with an email that has access to your Google Analytics - it will take you to a screen with an OOB token. Copy-paste that token back into RStudio:
(The OOB token is only needed on RStudio Cloud - if you have googleAnalyticsR installed locally on your desktop it will authenticate automatically via
You should then be authenticated and ready to use the functions in the package. Try
ga_account_list() as a way to check you are authenticated correctly:
The latest stable version of
googleAnalyticsR is available on CRAN.
install.packages("googleAnalyticsR", dependencies = TRUE)
You may prefer to use the latest development version on GitHub which you can install via the below.
Check out the NEWS to see whats currently available in each version.
If you know docker, then a public image is available at
gcr.io/gcer-public/googleanalyticsr:masteris the latest GitHub version
gcr.io/gcer-public/googleanalyticsr:CRANwill be the last CRAN version
googleAnalyticsR requires the packages described in the
Imports field of the
DESCRIPTION file to be installed first, which it will do via
install.packages("googleAnalyticsR", dependencies = TRUE)
The depedencies are roughly split into the following roles:
gargleare used for authentication with Google APIs
httrwork with API responses
purrrare used to make outputs easy to use (clean data.frames rather than nested lists)
If you install
httpuv then the authentication flows will occur behind the scenes - this is normally installed by default but if you do not include it you will need to use the more manual OOB method to generate authentication tokens.
Once you have installed the package you can make a first call to the GA API to test the connection.
## setup library(googleAnalyticsR) ## This should send you to your browser to authenticate your email. # Authenticate with an email that has access to the # Google Analytics View you want to use. ga_auth() ## get your accounts account_list <- ga_account_list() ## account_list will have a column called "viewId" account_list$viewId ## View account_list and pick the viewId you want to extract data from. ga_id <- 123456 ## simple query to test connection, get 10 rows google_analytics(ga_id, date_range = c("2017-01-01", "2017-03-01"), metrics = "sessions", dimensions = "date", max = 10)
ga_auth_setup() to configure your own GCP project and set up auto-authentication options.
Recommended long term defaults are:
ga_auth(email="firstname.lastname@example.org")to create an authentication token cache, and repeat the
ga_auth(email="email@example.com")call to default to that email in future API calls
GARGLE_EMAILin the same
.Renvironfile to your email to auto-authenticate on package load e.g.
To access the GA API authentication is required.
The example in the previous section used the simplest among the three available ways to authenticate to the API. If you are planning to make systematic use of the API however, it’s worth to know all the available options in order to choose the most suitable.
Note that no matter which method you use, the authentication is actually done via the
googleAuthR package. In its documentation pages you can read more about advanced use cases.
To authenticate you need a client project (that authentication is performed through) and the user email to authenticate with (that gives access to that user’s Google Analytics accounts)
As of version
googleAnalyticsR>=0.6.0.9000 authentication is done via the
gargle package. This creates a global cache that is accessed via the email you authenticate with.
If you use
ga_auth() the first time then it will ask you to create email credentials. You can then authenticate in the browser via your email. The next time you wish to authenticate,
ga_auth() will give you an option to use those credentials again:
library(googleAnalyticsR) ga_auth() #>The googleAnalyticsR package is requesting access to your Google account. #> Select a pre-authorised account or enter '0' to obtain a new token. Press #>Esc/Ctrl + C to abort. #> 1: firstname.lastname@example.org #> 2: email@example.com
If you want to skip the menu, supply the email you wish to authenticate with:
To auto-authenticate on package load, add an environment argument
GARGLE_EMAIL via an
.Renviron file or otherwise.
The fast authentication way of the previous section worked via the default Google Cloud Project for googleAnalyticsR which is shared with all googleAnalyticsR users. Even though it is a shared project other package users are not able to see and access your GA data.
However since Google has changed verification processes, the consent screen for the default googleAnalyticsR library may warn of ‘danger’, which you will need to trust and accept if you want to continue using the default project. It is preferred to use your own and get your own verificataion process.
You can not use the default project for scheduled scripts on servers - only interactivly. The default library is only intended for users to get to know the library looking for data as quickly as possible.
With the amount of API calls possible with this library via batching and walking, its more likely the default shared Google API project will hit the 50,000 calls per day quota.
However, using the default project means you will not need to go through the process outlined below to create your own Google Cloud Platform credentials and you can directly authenticate using the
ga_auth() function and your browser as soon as the library is downloaded.
A new setup function is available in versions >0.7.2 - use this to launch a wizard that will help you walk through some of the more advanced authentication setups detailed below. You will need to create your own Google Cloud Project and download a client Id file to get started.
library(googleAnalyticsR) ga_auth_setup() #ℹ ==Welcome to googleAnalyticsR v0.7.1.9000 setup== #This wizard will scan your system for setup options and help you with any that are missing. #Hit 0 or ESC to cancel. # #1: Setup your own client ID and secret #2: Setup auto-authentication (OAuth2 email) #3: Create and download JSON service account key #4: Setup auto-authentication (JSON service account key) #5: Add a service account email or another email to your GA account
To mitigate all the above, use your own Google Developer Console client ID, so it is not shared across all users of this library.
The easiest way to set this up is to create your own Google Cloud Platform project and then in R use the
ga_auth_setup() function and select option 1.
The setup function goes through the steps below.
This file is found in the Google Cloud Platform under
APIs & Services > Credentials > Create credentials > OAuth client ID > Desktop. For Shiny authentication, choose
Web application instead of
In the below examples the client ID file is downloaded to
# In your .Renviron GAR_CLIENT_JSON=~/dev/auth/gcp_client.json
You can also set your clientID before the library is available via
ga_auth()or other data fetching calls.
If set via environment argument, restart R and then load the library:
If setting in the script via
googleAuthR::gar_set_client() then it will look like this:
If you want to use with Shiny, then you need to download web based JSON client secrets. In that case, you then set the webapp clientId/secrets (which could be the same GCP project as the “Other” credentials.)
Note: With either the default or your own GCP projects using the
ga_auth()function, you can specify the email you will use by passing that to the
ga_auth(email="firstname.lastname@example.org). This will skip the interactive menu choice for authentication. This can be useful when authenticating within an Rmarkdown document in which case it is recommended to specify your email (an Rmarkdown document can change the working directory during knitting).
You can alternatively authenticate by downloading a JSON file attached to a Google Cloud service account. More details on how to do that are on the
A service authentication file then needs to be created that has edit access to the GA account. It is recommended to make a dedicated service account if you don’t need it for anything else.
The easiest way is to use
ga_auth_setup() and select option 3 to create the file for you using your own details for authorization, then option 5 to add it to the GA account you need.
In your R script you can then authorize via:
…or if you have set the environment arg
GA_AUTH_FILE to the service key filepath, simply loading the library to enact auto-authenticataion.
This is helpful for Docker contaienrs where you don’t want to usually include any authentication files, but can specify them via environment arguments when launching the container.
If you want to set it up yourself, the setup wizard goes through these steps:
You should now be able to use the JSON auth file to authenticate with Google Analytics API via:
library(googleAnalyticsR) ga_auth(json_file = "your_auth_file.json") # test authentication al <- ga_account_list()
Note: A service account is a special type of account that belongs to an application rather than an individual user. If you should use this option, chances are you are already familiar with how they work. If however you wish to find out more about when and how to use service accounts, follow the link to the Google Cloud documentation page on Understanding Service Accounts
This section covers some other aspects of authentication under various scenarios of use. This information is useful especially if you work systematically with Google Analytics and possibly other Google products too.
To save authenticating and setting your GCP client each R session, you can specify the files/email in an
.Renviron file that will be looked for each time you load
GAR_CLIENT_JSONtakes care of the GCP project client.id to authenticate under
GARGLE_EMAILlets you specify an email address that has already authenticated to skip the interactive menu. Make sure you authenticate with the right scopes and GCP project first in an interactive session.
GA_AUTH_FILEis an optional argument if you have a service JSON key
You can set environment arguments via
Sys.setenv() or using an
.Renviron file saved in your home directory, but the recommended way is to use
ga_auth_setup() and select option 2 (for OAuth2 email) or 4 (for JSON service account keys)
# In your .Renviron GAR_CLIENT_JSON=~/dev/auth/gcp_client.json GARGLE_EMAILemail@example.com GA_AUTH_FILE=/Users/me/dev/auth/keys/googleanalyticsr-auth-key.json
Restart your R session to enact the arguments created in
.Renviron - when you load the library they will be loaded in.
If you are using more than one API for authentication (such as Search Console), then authenticate using
googleAuthR::gar_auth() instead, to ensure you authenticate with the correct scopes. See the multiple authentication section on the
googleAuthR website for details.
If you have set up a personal project then you can use the
options() function as shown in the previous section
Using gargle means that you get a menu option to choose which email to authenticate with each time you issue
ga_auth(). This makes working with multiple GA accounts a lot easier to work with.
library(googleAnalyticsR) ga_auth(email="firstname.lastname@example.org") client_one <- google_analytics(ga_id_one, date_range = my_date_range, metrics = "sessions", dimensions = c("date", "medium")) ga_auth(email="email@example.com") client_one <- google_analytics(ga_id_two, date_range = my_date_range, metrics = "sessions", dimensions = c("date", "medium"))
Once the set up is complete you are ready to start using the package to access your GA data. To give you some ideas the v4 API page of this site provides several examples of key functionalities provided by the package.