Google Analytics

Google Analytics is an analytics service that helps you measure traffic and engagement across various platforms, like websites and apps.

ingestr supports Google Analytics as a source.

Bruin supports Google Analytics as a source for ingestr assets, and you can use it to ingest data from Google Analytics into your data warehouse.

To set up a Google Analytics connection, you need to add a configuration item in the .bruin.yml file and the asset file. You will need either service_account_file or service_account_json, and a property_id.

Follow the steps below to correctly set up Google Analytics as a data source and run ingestion.

Configuration

Step 1: Add a connection to .bruin.yml file

You can use either service_account_file to point to a JSON key file, or service_account_json to provide the JSON content directly:

    googleanalytics:
        - name: "googleanalytics"
          service_account_file: "/path/to/service/account.json"
          property_id: "1234"

Alternatively, you can use service_account_json to embed the credentials directly:

    googleanalytics:
        - name: "googleanalytics"
          service_account_json: |
            {
              "type": "service_account",
              "project_id": "your-project-id",
              ...
            }
          property_id: "1234"

• service_account_file: The path to the service account JSON file
• service_account_json: The content of the service account JSON as a string (use this when you don't have a file, e.g. when using secrets management)
• property_id: It is a unique number that identifies a particular property on Google Analytics. Follow this guide to know about property ID.

Find your GA4 property ID

1. Go to https://analytics.google.com/
2. Click Admin
3. Select the property
4. Select Property Settings

The numeric "PROPERTY ID" shown there (e.g. 123456789) is what you pass to the Data API as properties/GA_PROPERTY_ID. If you see a "Tracking ID" like UA-123...-1 instead, that's Universal Analytics and the Data API v1 won't work on it.

Step 2: Create an asset file for data ingestion

To ingest data from Google Analytics, you need to create an asset configuration file. This file defines the data flow from the source to the destination. Create a YAML file (e.g., gAnalytics_ingestion.yml) inside the assets folder and add the following content:

name: public.googleanalyticss
type: ingestr
connection: postgres

parameters:
  source_connection: googleanalytics
  source_table: 'custom:city,date:activeUsers,newUsers'

  destination: postgres

• name: The name of the asset.
• type: Specifies the asset’s type. Set this to ingestr to use the ingestr data pipeline. For Google Analytics, it will be always ingestr.
• connection: This is the destination connection, which defines where the data should be stored. For example: postgres indicates that the ingested data will be stored in a Postgres database.
• source_connection: The name of the Google Analytics connection defined in .bruin.yml.
• source_table: The name of the data table in Google Analytics to ingest data from.
• destination: The destination platform/type, for example postgres.

Available Source Tables

Table	PK	Inc Key	Inc Strategy	Details
realtime	ingested_at	-	merge	Retrieves real-time analytics data based on specified dimensions and metrics. Format: realtime:<dimensions>:<metrics>:<minutes_ranges>. Supports incremental loading by ingestion timestamp.
custom	datetime_dimension	datetime_dimension	merge	Retrieves custom reports based on specified dimensions and metrics. Format: custom:<dimensions>:<metrics>

Step 3: Run asset to ingest data

bruin run assets/gAnalytics_ingestion.yml

As a result of this command, Bruin will ingest data from the given Google Analytics table into your Postgres database.