Google Analytics 4 (Edge)

Configure Google Analytics 4 as a Source in your Pipeline

Perform the following steps to configure your Google Analytics 4 Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Google Analytics 4.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing Google Analytics 4 Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Google Analytics 4 Source.

   • In the Connect to your Google Analytics 4 account section, specify the following:

     • Google Account: Click the button to authorize Hevo. In the Google sign-in window that opens, select the Google account that has access to your Google Analytics 4 properties, review the requested permissions, and click Allow.

     • Account Selection: From the drop-down, select whether Hevo syncs data from all the accounts accessible to the authorized Google account, or only from specific accounts that you select.

       • Sync All Accounts: Hevo syncs data for all accounts accessible to your authorized Google Analytics 4 account, including any accounts added later.

       • Sync Specific Accounts: Hevo ingests data only for the accounts you select from the Properties to sync drop-down.

         

     • Historical Sync Duration: From the drop-down, select how far back Hevo fetches data on the first Pipeline run. Default: 6 Months. You cannot change this value after the Pipeline is created.

     • (Optional) Rollback Window (days): Specify the number of days for which Hevo re-fetches previously ingested report data to capture updated report data. Min: 2 days. Max: 90 days. Default: 30 days.

   • (Optional) In the Custom Reports section, define one or more custom reports. Each report you define is ingested into its own table in the Destination. To add a report, specify the following:

     

     • Report Name: A unique name for the report. This cannot be changed after the report is created.

     • Report Fields: Select the dimensions and metrics for the report from tabs grouped by category, such as Publisher, Platform/Device, User, Demographics, and Geography. Alternatively, you can pick a report template to automatically select the fields for a pre-built report.

       Note: A report can include a maximum of 9 dimensions and 10 metrics, and must include a date dimension that matches the selected Aggregation.

     • Aggregation: From the drop-down, select the time interval used to group the report data. Default value: Daily. You cannot change this value after the report is created. The Report Fields you select must include a matching date dimension: Date for Daily, Year week for Weekly, Year month for Monthly, and Year for Yearly.

     • (Optional) Filter Dimension: The Google Analytics 4 dimension used to filter the report data, for example, Country.

     • Filter Operator: The condition used to match the selected Filter Dimension.

     • Filter Type: Determines whether rows that match the filter condition are included in or excluded from the report.

     • (Optional) Filter Values: The value or values to match for the selected Filter Dimension. Enter comma-separated values if the Filter Operator is Exact match, or a single value if the Filter Operator is Contains.

   Note:

   • Click Save after configuring each report. Reports that are not saved before you click Test & Continue are not included in the Pipeline.

   • If you add a new custom report or edit an existing one after the Pipeline is created, resync the corresponding object to apply the changes and load the data using the updated configuration.

7. Click Test & Continue to test the connection to your Google Analytics 4 Source. Once the test is successful, you can proceed to set up your Destination.

   Note: If any custom report is configured incorrectly, such as with an unsupported field combination, an invalid aggregation, or a duplicate table name, clicking Test & Continue fails the Source configuration. Hevo lists all configuration issues in your custom reports. You can fix these issues by editing the reports before retrying.

{
  "auth": {
    "required": [
      "client_access"
    ],
    "properties": {
      "client_access": {
        "required": [
          "client_id",
          "client_secret"
        ],
        "properties": {
          "client_id": {
            "title": "Client ID"
          },
          "client_secret": {
            "title": "Client Secret"
          }
        }
      },
      "refresh_token": {
        "title": "Refresh Token"
      },
      "access_token": {
        "title": "Access Token"
      }
    },
    "anyOf": [
      {
        "required": [
          "refresh_token"
        ]
      },
      {
        "required": [
          "access_token"
        ]
      }
    ]
  }
}

{
  "name": "<source_name>",
  "connector_id": "google_analytics_hevo_edge",
  "type": "GOOGLE_ANALYTICS_HEVO_EDGE",
  "config": {
    "historical_sync_duration": "SIX_MONTHS"
  },
  "auth": {
    "client_access": {
      "client_id": "<client_id>",
      "client_secret": "<client_secret>"
    },
    "refresh_token": "<refresh_token>"
  }
}

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests historical data for the selected reports based on the historical sync duration specified when creating the Pipeline, and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For all prebuilt and custom reports, Hevo ingests only the incremental data using the date field in subsequent Pipeline runs. During each sync, Hevo also re-fetches data for the number of days specified in the Rollback Window (days) field to capture any revisions to previously ingested report data. This ensures that your Destination stays up to date.

If you add a new custom report to an existing Pipeline, Hevo ingests its historical data based on the historical sync duration specified when the Pipeline was created. Existing reports continue syncing only incremental data.

For all metadata objects fetched through the Google Analytics Admin API, Hevo ingests the entire data during each Pipeline run.

Before each Pipeline run, Hevo checks for any new custom dimensions or metrics in your Google Analytics 4 property. This ensures that they are available the next time you configure a custom report in Hevo.

The Google Analytics Data API enforces the following quotas per property:

• Standard properties are limited to 200,000 core tokens per day and 40,000 core tokens per hour, with a maximum of 10 concurrent requests per property.

• Analytics 360 properties are limited to 2,000,000 core tokens per day and 400,000 core tokens per hour, with a maximum of 50 concurrent requests per property.

If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

Schema and Primary Keys

Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

Click to view ERD

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Google Analytics Admin API - Metadata Objects

Google Analytics Data API - Prebuilt Reports

All prebuilt report objects are ingested using the Google Analytics Data API. Each object below corresponds to a fixed dimension/metric combination, aggregated by day and property.

Traffic Acquisition Reports

User Acquisition Reports

Demographic Reports

Technology & Device Reports

E-commerce Reports

Publisher Ads Reports

Page & Screen Reports

Events, Conversions & Audience Reports

In addition to the prebuilt reports listed above, you can define Custom Reports in the Source configuration. Each custom report you create is ingested into its own table, named after the report, containing the dimensions and metrics you select.