Sync data from Google Analytics to your warehouse destination via RudderStack.
Google Analytics is a popular analytics service that lets you track and report your website traffic across a variety of sources.
This document guides you in setting up Google Analytics as a source in RudderStack. Once configured, RudderStack automatically ingests your Google Analytics data and routes it to your specified data warehouse destination.
Go to Sources > New source > Cloud Extract and select Google Analytics from the list of sources.
Assign a name to your source and click Continue.
Next, configure the following dashboard settings:
Credentials: Choose from one of the following two authentication types:
Authenticate via Google (Oauth): Authenticate your Google Analytics account via Google (OAuth) by clicking
Sign in with Google and granting the required permissions.
Service Account Key Authentication: Enter the service account key in JSON format in the Service Account JSON Key field. Refer to the Google documentation for more information on obtaining the service account key.
The rest of the settings are as follows:
Replication Start Date: Choose the start date from which you want RudderStack to ingest the Google Analytics data. RudderStack will not replicate any data before this date.
View ID: Enter the ID of the Google Analytics View from where you want to fetch the data.
Custom Reports (Optional): Use this field to sync your custom reports from Google Analytics. You can sync multiple reports.
To add a custom report, click Add Report and enter the Report Name, Metrics, and Dimensions as shown:
You can also edit/delete an existing report:
Data request time increment in days (Optional): Enter the number of days after which RudderStack should request data from the Google Analytics API. It is recommended to set this value to 1 to avoid getting the sampled data. The minimum and maximum allowed values for this field are 1 and 364 respectively.
The following settings specify how RudderStack sends the data ingested from Google Analytics to the connected warehouse destination:
Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Google Analytics data into it.
Schedule Settings: RudderStack gives you three options to ingest the data from Google Analytics:
Basic: Runs the syncs at the specified time interval.
CRON: Runs the syncs based on the user-defined CRON expression.
Manual: You are required to run the syncs manually.
For more information on the schedule types, refer to the Common Settings guide.
Selecting the data to import
You can choose the predefined reports from which you want to ingest the data from Google Analytics by selecting them here:
The below table mentions the syncs supported by these resources from Google Analytics to your warehouse destination:
Full Refresh sync
For more information on the Full Refresh and Incremental sync modes, refer to the Common Settings guide.
To sync the data in incremental mode, you must include the ga:date dimension in your report. Otherwise, RudderStack will sync the data in full refresh mode.
Google Analytics is now configured as a source. RudderStack will start ingesting data from Google Analytics as per your specified schedule and frequency.
You can further connect this source to your data warehouse by clicking on Add Destination:
Use the Use Existing Destination option if you have an already-configured data warehouse destination in RudderStack. To configure a data warehouse destination from scratch, select the Create New Destination button.
Is it possible to have multiple Cloud Extract sources writing to the same schema?
Yes, it is.
RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.
How does RudderStack count the events for Cloud Extract sources?
RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.