On This Page
Hevo can replicate your Google Analytics data to your data warehouse using Google’s Reporting API. We recommend you to go through the Google Analytics Query Explorer before creating the Pipeline to ensure you configure it the way you require. You can also refer to the Common Queries section.
For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.
- An active Google Analytics account.
Configuring Google Analytics as a Source
Perform the following steps to configure Google Analytics as the Source in Hevo:
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Google Analytics as the Source.
In the Configure your Google Analytics Account page, click Add Account.
Select your linked Google account, and click Allow to provide Hevo
readaccess to your analytics data.
In the Configure your Google Analytics Source page, specify the following:
Pipeline Name: A unique name for your Pipeline, not exceeding 255 characters.
Account Name: All the Analytics accounts connected to the authorized Google Account would be suggested here; select the appropriate one.
Property Name: The website, application, or entity for which user analytics data is to be read. All the property names associated with the account selected above are suggested; select one according to your need.
View Name: Select the view on which reports must be generated. All the views associated with above account name and property name would be suggested here. Read Hierarchy of organizations, accounts, users, properties, and views to understand the Analytics account structure.
Metrics: Metrics are quantitative measurements that can be reported, based on the View Name you selected in Step 4 above. Select up to 10 Metrics you need in your report as Google’s API request can have a total of 10 metrics. Read Metric for more details.
Dimensions: Dimensions are attributes of your data. Select up to seven dimensions you need in your report as Google’s API request can have a total of 7 dimensions only. Read Dimension.
Note: Only the dimensions compatible with the metric selected above are available for selection. Read Source Considerations.
Segments: Segments can be used to get the subset of a data. They are used if the report data needs to be segregated on some basis. For example, you can use the Country segment to categorize the data on the basis a particular country.
Select up to four segments you need in your report as Google’s API request can have a total of four segments only. Your existing Pipelines won’t be affected by these Segments. Read Segments.
Historical Import Duration (in days): You can choose to import historical data. Hevo fetches data for last 90 days by default. Although, you can change this duration according to your need.
Specify the Advanced Options which let you limit results to metrics and dimensions with specific characteristics. To know more about this, visit our documentation on Google Analytics Filters.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency||Custom Frequency Range (Hrs)|
|1 Hr||15 Mins||24 Hrs||1-24|
Note: The custom frequency must be set in hours, as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.
Schema Mapping Considerations
During ingestion of the report data, the following additional columns are created in the Destination database along with
__hevo_id: Represents a unique ID of each unique event present in the Source data. Hevo derives this from the primary key columns of your Google Analytics data.
__hevo_report_date: Represents the date on which a report is fetched by Hevo.
Providing Access to your Google Analytics Account
Hevo needs permission to view your reports and other reporting entity details. You can read more about these permissions here.
Hevo is subject to the limits and quotas set on the Core Reporting API. Therefore, ingestion may be deferred due to these limits.
You can only select the dimensions that are compatible with the metric you select. Incompatible metrics are greyed out based on the selected dimensions.
Even for compatible metric/dimension combinations, an error may be displayed stating that the selected metrics and dimensions cannot be queried together, or that the selected metrics/dimensions are restricted. If the metric/dimension set belongs to Google Adwords, Google Analytics 360, or Google Adsense, this may be due to lack of permissions on the selected view.
For information on valid metric/dimension combinations, refer to Dimensions and Metrics Explorer.
For information on different types of errors, refer to Google Analytics Core Reporting API Changelog.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|
|Mar-07-2022||1.83||Updated sections, Configuring Google Analytics as a Source and Schema Mapping Considerations to add support for Segments.|
|Jan-03-2022||1.79||Added information about reverse historical load in the Data Replication section.|
|Oct-25-2021||NA||Added the Pipeline frequency information in the Data Replication section.|
|Mar-09-2021||1.58||Added section Schema Mapping Considerations.|