Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Google Analytics Aggregated from the Previews page. See Manage Azure Databricks previews.
Get answers about the managed Google Analytics Aggregated connector in Lakeflow Connect, including how it differs from the Raw Data connector, its tables and custom reports, historical data, and authentication. For frequently asked questions (FAQs) that apply to all managed connectors, see Managed connector FAQs.
How is this connector different from the Google Analytics Raw Data connector?
The Google Analytics Aggregated connector ingests aggregated Google Analytics 4 (GA4) reports from the Google Analytics Data API, such as users, sessions, and events grouped by date and other dimensions. The Google Analytics Raw Data connector ingests event-level data that Google Analytics exports to BigQuery. Use the Raw Data connector to analyze individual events, and use the Google Analytics Aggregated connector to ingest the report metrics that Google Analytics calculates.
Which tables does the connector support?
The connector supports prebuilt report tables for user activity, core reports, user acquisition, traffic acquisition, engagement, monetization, demographics, tech, and audiences. It also supports a custom_report table that runs a report with the dimensions and metrics that you select. For the full list, see Supported source tables.
Can I ingest a report with my own dimensions and metrics?
Yes. Use the custom_report table, and set the property_id, dimensions, metrics, and cursor_dimension connector options. The cursor_dimension option sets the aggregation level of the report to day, GA4 week, month, or year. See Custom reports.
Can the connector ingest data from multiple GA4 properties in one pipeline?
Yes. For prebuilt report tables, list each property ID in the property_ids connector option. The connector ingests the table one time for each property and writes the property ID to the property_id column. For custom reports, add a custom_report object for each property.
How far back can the connector ingest data?
By default, the first sync ingests the previous 60 days of data. To start from a different date, set the start_date connector option. Each later sync ingests data after the last synced cursor value, minus the lookback window. See Connector options.
Why does the connector re-ingest recent data on every sync?
Google Analytics can update report metrics for recent dates after the data is first collected. On each sync, the connector requests the days in the lookback window again and updates the existing rows by primary key. To change the lookback window, set the lookback_window_in_days connector option. See Connector options.
Which authentication methods does the connector support?
The connector supports a service account (recommended) and OAuth 2.0 user-to-machine (U2M). A service account authenticates without an interactive sign-in, either as its own identity or by impersonating a Google Workspace user through domain-wide delegation. OAuth U2M authenticates as the Google user who signs in. For setup instructions, see Configure authentication to Google Analytics.