Advanced Analytica Advanced Analytica: IBOM
← All connectors
Google Analytics 4 (GA4) logo

Source connector

Google Analytics 4 (GA4)

Set up Google Analytics 4 (GA4) as a source and move its data into your chosen destination.

Version 2.11.10 certified generally available

Google Analytics 4 (GA4)

Find setup guidance and reference information for the Google Analytics 4 (GA4) source connector on this page.

Google Analytics 4 (GA4) is the latest Google Analytics version, introduced in 2020. Its data model focuses on events and user properties instead of page views and sessions. This model gives you more flexibility when customising reports. It also measures user behaviour more accurately across different devices and platforms.

This connector supports Google Analytics 4 (GA4) and Google Analytics 360 (GA360) properties.

Prerequisites

  • A Google Analytics account with access to the GA4 property and property ID you want to sync

Set up the connector

1. Set up Google Analytics 4

Create a service account

  1. Sign in as an administrator to the Google Account you use for Google Analytics.
  2. Go to the Service Accounts page in the Google Developers console.
  3. Select your project, or create one, then click Continue.
  4. Click + Create Service Account at the top of the page.
  5. Enter a service account name and, optionally, a description. Click Create and Continue.
  6. Choose the service account role. The recommended role is Viewer (Read & Analyze permissions). Click Continue.
  7. Select your new service account, then open the Keys tab. Click Add Key > Create New Key.
  8. Select JSON as the Key type. This generates and downloads the JSON key file used for authentication. Click Continue.

:::note When authenticating with a service account (Airbyte Open Source), grant the service account access to the GA4 property in Google Analytics. Creating the account and downloading its JSON key doesn’t automatically grant permission to read Analytics data.

  1. In Google Analytics, go to Admin → under Property, click Property access management.
  2. Click + → Add users, then add the service account email, for example, [email protected].
  3. Grant at least the Viewer role (read-only) for the target property. :::

Enable the Google Analytics APIs

Enable the required APIs before using the service account to access Google Analytics data:

  1. Go to the Google Analytics Reporting API dashboard. Select the project linked to your service account, then enable the API. You can also set quotas and check usage.
  2. Go to the Google Analytics API dashboard. Select the project linked to your service account, then enable the API.
  3. Go to the Google Analytics Data API dashboard. Select the project linked to your service account, then enable the API.

Airbyte Cloud

  1. Log into your Airbyte Cloud account.

  2. Click Sources, then click + New source.

  3. On the Set up the source page, select Google Analytics 4 (GA4) from the Source type dropdown.

  4. Enter a name for the Google Analytics 4 (GA4) connector.

  5. Select Authenticate via Google (Oauth) from the dropdown menu, then click Authenticate your Google Analytics 4 (GA4) account. In the pop-up window, sign in to your Google account and grant Airbyte access to your Google Analytics account.

  6. Enter the Property ID whose events are tracked. Use a numeric value, such as 123456789. If you’re unsure where to find it, refer to Google’s documentation. :::note A “Tracking Id”, such as “UA-123…-1”, in Property Settings identifies a Universal Analytics property. This connector can’t report Analytics data for that property. To create a new Google Analytics 4 property, follow these instructions. :::

  7. (Optional) In the Start Date field, use the datepicker or enter a date programmatically in the format YYYY-MM-DD. The connector replicates all data added from this date onwards. This setting doesn’t apply to custom Cohort reports.

  8. (Optional) In the Custom Reports field, describe any custom Google Analytics reports you want to sync. See the Custom Reports section below for guidance on defining these reports.

  9. (Optional) In the Data Request Interval (Days) field, set the interval for Google Analytics API data requests. Enter a value from 1 to 364 days. Larger values make syncing faster but increase the chance of sampling, which can make results inaccurate. Set this value to 1 unless faster syncing is essential and reduced accuracy is acceptable. This field doesn’t apply to custom Cohort reports. See the Data Sampling section below for more context.

  10. (Optional) Enable One Stream per Report to create one stream per report across all configured property IDs. Otherwise, the connector creates one stream for each report and property. This setting is recommended when syncing many properties. See the One Stream per Report section below — enabling it on an existing connection requires a full re-sync.

:::caution

Consider how you specify dimensions such as month or yearMonth. These dimensions organise the data according to your preferences. Your selected report date range also affects how data appears. A very specific range, such as one day, may produce duplicate entries for each day. This occurs when Data Request Interval (Days) is set to one day. To get more precise results and prevent duplicates, set Data Request Interval (Days) to 364.

:::

  1. Click Set up source and wait for the tests to finish.

Airbyte Open Source

  1. Go to the Airbyte Open Source dashboard.

  2. In the left navigation bar, click Sources. In the top-right corner, click + New source.

  3. Find and select Google Analytics 4 (GA4) from the available sources.

  4. Select Service Account Key Authentication from the dropdown list, then enter the Service Account JSON Key from Step 1.

  5. Enter the Property ID whose events are tracked. Use a numeric value, such as 123456789. If you’re unsure where to find it, refer to Google’s documentation. :::note A “Tracking Id”, such as “UA-123…-1”, in Property Settings identifies a Universal Analytics property. The Data API can’t report Analytics data for that property. To create a new Google Analytics 4 property, follow these instructions. :::

  6. (Optional) In the Start Date field, use the datepicker or enter a date programmatically in the format YYYY-MM-DD. The connector replicates all data added from this date onwards. This setting doesn’t apply to custom Cohort reports.

:::note If you don’t provide a start date, the default is two years before the initial sync. :::

:::caution Many analyses and data investigations need 24-48 hours to process information from your website or app. To improve data accuracy, the connector subtracts two days from the start date. For more details, refer to Google’s documentation. :::

  1. (Optional) Turn on Keep Empty Rows to return every row where all metrics equal 0.
  2. (Optional) In the Custom Reports field, describe any custom Google Analytics reports you want to sync. See the Custom Reports section below for guidance on defining these reports.
  3. (Optional) In the Data Request Interval (Days) field, set the interval for Google Analytics API data requests. Enter a value from 1 to 364 days. Larger values make syncing faster but increase the chance of sampling, which can make results inaccurate. Set this value to 1 unless faster syncing is essential and reduced accuracy is acceptable. This field doesn’t apply to custom Cohort reports. See the Data Sampling section below for more context.
  4. (Optional) In the Lookback window (Days) field, set how many days of past data each run refreshes. This keeps your data consistent when attribution changes after the event date and Google Analytics has processing latency. For example, a value of 5 re-fetches data from five days before the last bookmark date.
  5. (Optional) Enable One Stream per Report to create one stream per report across all configured property IDs. Otherwise, the connector creates one stream for each report and property. This setting is recommended when syncing many properties. See the One Stream per Report section below — enabling it on an existing connection requires a full re-sync.

:::caution

Consider how you specify dimensions such as month or yearMonth. These dimensions organise the data according to your preferences. Your selected report date range also affects how data appears. A very specific range, such as one day, may produce duplicate entries for each day. This occurs when Data Request Interval (Days) is set to one day. To get more precise results and prevent duplicates, set Data Request Interval (Days) to 364.

:::

  1. Click Set up source and wait for the tests to finish.

Supported sync modes

The Google Analytics 4 (GA4) source connector supports these sync modes:

Supported streams

This connector outputs these streams:

Preconfigured and custom report streams use the Google Analytics Data API properties.runReport method. Each stream represents a different combination of dimensions and metrics sent to the same API endpoint. Custom reports with specified pivots use the properties.runPivotReport method instead.

  • Preconfigured streams:
    • daily_active_users
    • devices
    • four_weekly_active_users
    • locations
    • pages
    • traffic_sources
    • website_overview
    • weekly_active_users
    • user_acquisition_first_user_medium_report
    • user_acquisition_first_user_source_report
    • user_acquisition_first_user_source_medium_report
    • user_acquisition_first_user_source_platform_report
    • user_acquisition_first_user_campaign_report
    • user_acquisition_first_user_google_ads_ad_network_type_report
    • user_acquisition_first_user_google_ads_ad_group_name_report
    • traffic_acquisition_session_source_medium_report
    • traffic_acquisition_session_medium_report
    • traffic_acquisition_session_source_report
    • traffic_acquisition_session_campaign_report
    • traffic_acquisition_session_default_channel_grouping_report
    • traffic_acquisition_session_source_platform_report
    • events_report
    • weekly_events_report
    • conversions_report
    • pages_title_and_screen_class_report
    • pages_path_report
    • pages_title_and_screen_name_report
    • content_group_report
    • ecommerce_purchases_item_name_report
    • ecommerce_purchases_item_id_report
    • ecommerce_purchases_item_category_report_combined
    • ecommerce_purchases_item_category_report
    • ecommerce_purchases_item_category_2_report
    • ecommerce_purchases_item_category_3_report
    • ecommerce_purchases_item_category_4_report
    • ecommerce_purchases_item_category_5_report
    • ecommerce_purchases_item_brand_report
    • publisher_ads_ad_unit_report
    • publisher_ads_page_path_report
    • publisher_ads_ad_format_report
    • publisher_ads_ad_source_report
    • demographic_country_report
    • demographic_region_report
    • demographic_city_report
    • demographic_language_report
    • demographic_age_report
    • demographic_gender_report
    • demographic_interest_report
    • tech_browser_report
    • tech_device_category_report
    • tech_device_model_report
    • tech_screen_resolution_report
    • tech_app_version_report
    • tech_platform_report
    • tech_platform_device_category_report
    • tech_operating_system_report
    • tech_os_with_version_report
  • Property metadata stream:
    • property_metadata
  • Custom stream(s)

The property_metadata stream uses full refresh and the Admin API properties.get method. It emits one record for each configured property ID. Each record includes a property_id field for joining it with report streams.

The property_metadata stream requires Google Analytics Admin API (analyticsadmin.googleapis.com) for the GCP project linked to the credentials. Service account users must enable it in their own project. Without it, this stream fails with a 403 SERVICE_DISABLED error, but report streams continue working.

Connector features

Custom reports

Custom Google Analytics reports let you query specific data for your needs. You can define these components:

  • Name: The custom report’s name.
  • Dimensions: An array of data categories, such as city or user type.
  • Metrics: An array of quantitative measurements, such as active users or page views.
  • CohortSpec: (Optional) An object containing cohort analysis settings, such as cohort size and date range. Find more information about this object in the GA4 documentation.
  • Pivots: (Optional) An array of data pivot tables, such as page views by city. Find more information about pivots in the GA4 documentation.

Find the full list of API-supported dimensions and metrics in here. Use the GA4 Dimensions & Metrics Explorer to check whether dimensions and metrics are compatible with your GA4 property.

This basic User Engagement report tracks sessions and bounce rate by city:

[
  {
    "name": "User Engagement Report",
    "dimensions": ["city"],
    "metrics": ["sessions", "bounceRate"]
  }
]

Add a cohort with a seven-day range and pivot on the city dimension for more detail. The report then shows engagement trends across the top 50 cities for the specified date range.

[
  {
    "name": "User Engagement Report",
    "dimensions": ["city"],
    "metrics": ["sessions", "bounceRate"],
    "cohortSpec": {
      "cohorts": [
        {
          "name": "Last 7 Days",
          "dateRange": {
            "startDate": "2023-07-27",
            "endDate": "2023-08-03"
          }
        }
      ],
      "cohortReportSettings": {
        "accumulate": true
      }
    },
    "pivots": [
      {
        "fieldNames": ["city"],
        "limit": 50,
        "metricAggregations": ["TOTAL"]
      }
    ]
  }
]

One stream per report

By default, the connector creates a stream for every report and Property ID combination. With 57 built-in reports and 70 properties, this creates about 3,990 streams. This volume slows catalogue loading, complicates stream management and increases the chance of setup errors.

Enable One Stream per Report to create one stream per report across every configured property. Each record includes a property_id field. The stream’s primary key includes property_id, keeping rows from different properties distinct in the destination. Each property also has its own incremental cursor, so properties sync independently.

Consolidated streams use the name <report_name>Consolidated. For example, the devices report becomes devicesConsolidated. The connector doesn’t create per-property streams such as devices and devicesProperty5729978930 while this setting is enabled. The distinct name ensures the consolidated stream starts clean. It doesn’t inherit the destination table or incremental cursor from the single-property stream it replaces.

The stream schema combines the field definitions from every configured property. This is important when you use custom metrics, which GA4 defines separately for each property. The schema includes a custom metric even when it exists for only some properties, preventing its data from being dropped. If properties type the same metric differently, the connector uses the type from the property listed first in Property IDs.

:::caution

Enabling or disabling this setting changes stream names. Data is written to new destination tables, and incremental state resets. Avoid changing this setting casually on an established connection.

Changing it on an existing connection requires a schema refresh. Your connection’s stream list reflects its latest schema discovery. Per-property streams continue appearing and syncing no data until you refresh the schema. Follow these steps in order:

  1. Enable the source setting and save your changes.
  2. Run Refresh source schema on each connection that uses this source. The per-property streams, including devices and devicesProperty5729978930, are reported as removed. The <report_name>Consolidated streams then appear.
  3. Enable your chosen consolidated streams and apply the changes.
  4. Run a sync. The consolidated streams are new, so this fully backfills every property.
  5. After confirming the backfill, you may drop the old per-property destination tables. Airbyte leaves these tables in place. Keep them if you might revert — see below.

Between steps 1 and 3, the connection still lists old stream names that no longer exist in the source. Syncs during this period return no records for those streams.

Reverting is supported and loses no data. Disable the setting and refresh the schema to restore per-property streams under their original names. Each stream resumes from the cursor it held before you enabled the setting. The next sync re-fetches the period when the setting was enabled, leaving no gap.

Step 5 is the only exception. Deleting a destination table doesn’t reset the stream’s cursor. If you drop the old tables and later revert, streams resume from their old cursors. The recreated tables will then omit everything before those cursors. Clear these streams when reverting to run a full backfill.

:::

:::caution

Adding a Property ID after enabling this setting. New properties join existing consolidated streams as new partitions. A new partition starts from the stream’s current cursor, not from your Start Date. The connector doesn’t backfill the new property’s historical data or raise an error. After adding the Property ID, clear the affected streams to backfill this data.

This behaviour doesn’t apply when the setting is off. A new Property ID then creates new streams that backfill independently.

:::

Both settings make the same number of API requests. This setting reduces catalogue size and destination table count, not sync duration.

Data sampling and request intervals

Google Analytics 4 uses data sampling to estimate analytics data above Google’s predefined compute thresholds. Set Data Request Interval to control the interval used for Google Analytics API data requests. This can reduce the chance of sampling in your results.

Set the interval to one day to process less data per request. This reduces the chance of sampling and can produce more accurate results. Larger intervals, up to 364 days, can speed up syncing. Choose a smaller value for accuracy unless faster syncing is essential and potential inaccuracies are acceptable. This field doesn’t apply to custom Cohort reports.

For more information about data sampling, refer to Google Analytics documentation.

Performance

The Google Analytics connector is subject to Google Analytics Data API quotas. For a detailed quota breakdown, refer to Google’s documentation.

Data type map

Integration TypeAirbyte Type
stringstring
numbernumber
arrayarray
objectobject

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Changelog

Expand to review
VersionDatePull RequestSubject
2.11.102026-11-0390580Update dependencies
2.11.92026-10-2976413Surface expired/revoked OAuth refresh tokens as a config_error with a re-authentication message instead of a generic “Something went wrong” error
2.11.82026-10-2789937Update dependencies
2.11.72026-10-2089236Update dependencies
2.11.62026-10-1388637Update dependencies
2.11.52026-10-0687874Update dependencies
2.11.42026-09-2986645Update dependencies
2.11.32026-09-2286919Promoted release candidate to GA
2.11.3-rc.12026-09-1583188Reports with more than 100,000 rows per slice are now fully paginated instead of being silently truncated. Report rows are now returned in a deterministic order (sorted by every configured dimension), so pages cannot overlap or skip rows while paginating.
2.11.22026-09-1584599Update dependencies
2.11.12026-09-0985797Stop inferring the credentials auth_type from empty client_id / credentials_json values
2.11.02026-09-0985761Promoted release candidate to GA
2.11.0-rc.12026-08-1183783Add an opt-in One Stream per Report mode that combines all configured property IDs into one stream per report named <report_name>Consolidated, with schemas merged across properties. Off by default; existing connections are unchanged
2.10.22026-08-1183343Preserve nested name fields when resolving dynamic streams
2.10.12026-08-1183952Update dependencies
2.10.02026-07-3083273Add the property_metadata stream with GA4 property metadata from the Admin API
2.9.452026-07-2882938Update dependencies
2.9.442026-07-2182436Update dependencies
2.9.432026-07-1481845Update dependencies
2.9.422026-06-3081086Update dependencies
2.9.412026-06-2380482Update dependencies
2.9.402026-06-1679881Update dependencies
2.9.392026-06-0979340Update dependencies
2.9.382026-06-0277618Infer auth_type from credentials when missing to fix OAuth connection failures
2.9.372026-06-0277243Update dependencies
2.9.362026-05-2777877Update the connector runtime to the latest CDK version and reduce intermittent stream read hangs
2.9.352026-05-19PR-pendingRestore default_concurrency to 4 after c=6 rollout showed heartbeat timeout outliers
2.9.342026-05-1878161Promoted release candidate to GA
2.9.34-rc.22026-05-01PR-pendingPhase 1 step 3: bump default_concurrency 5 to 6 (tier-aware api_budget stays live)
2.9.34-rc.12026-04-2977550Phase 1 step 2: bump default_concurrency 4 to 5 and activate the tier-aware api_budget (Standard 10 req/s, Analytics 360 50 req/s on opt-in via subscription_tier)
2.9.33-rc.12026-04-2376956Add concurrency_level (default 4, max 16) and subscription_tier spec field (Standard or Analytics 360) for the Path B concurrency tuning rollout (RC); existing and tier-aware api_budget kept commented during tuning
2.9.312026-04-2076185Surface the GA4 API error message on 400 and 403 responses, and stop retrying permission errors
2.9.302026-04-1476190Add access_token to extract_output and complete_oauth_output_specification to fix OAuth secretId 422 regression
2.9.322026-04-2176600Update dependencies
2.9.312026-04-0976185Improve error messages for HTTP 400/403 responses; use predicate-based 403 handling to distinguish permission errors (config_error) from other 403s (retry)
2.9.302026-04-0976190Add access_token to extract_output and complete_oauth_output_specification to fix OAuth secretId 422 regression
2.9.292026-04-0175580Add oauth_connector_input_specification with granular scopes
2.9.282026-03-3175678Update dependencies
2.9.272026-03-2474568Update dependencies
2.9.262026-02-2573632fix(source-google-analytics-data-api): use GA4 today keyword for timezone-correct end dates (AI-Triage PR)
2.9.252026-02-2473750Update dependencies
2.9.242026-02-1773404Update dependencies
2.9.232026-02-1073067Update dependencies
2.9.222026-02-0372590Update dependencies
2.9.212026-01-2071924Update dependencies
2.9.202026-01-1471432Update dependencies
2.9.192025-12-1870693Update dependencies
2.9.182025-11-2569892Update dependencies
2.9.172025-11-1869414Update dependencies
2.9.162025-11-1269279Flag authentication issues as config_error
2.9.152025-10-2969011Update dependencies
2.9.142025-10-2168302Update dependencies
2.9.132025-10-14tbdPromoting release candidate 2.9.13-rc.1 to a main version.
2.9.13-rc.12025-10-0867148Add dimensionFilter into the body of requests for custom reports and custom DimensionFilterConfigTransformation component
2.9.122025-10-0767262Update dependencies
2.9.112025-09-3066306Update dependencies
2.9.102025-09-1066008Update to CDK v7
2.9.92025-09-0965895Update dependencies
2.9.82025-08-2365311Update dependencies
2.9.72025-08-0964631Update dependencies
2.9.62025-08-0264254Update dependencies
2.9.52025-07-2663820Update dependencies
2.9.42025-07-1963528Update dependencies
2.9.32025-07-1663339Promoting release candidate 2.9.3-rc.2 to a main version.
2.9.3-rc.22025-07-1563297Enable progressive rollout
2.9.3-rc.12025-07-1563297Fix bug where concurrent partitions are not merged back together properly so sequential state can’t progress to the latest record
2.9.22025-07-1263129Update dependencies
2.9.12025-07-0561135Update dependencies
2.9.02025-07-0362507Promoting release candidate 2.9.0-rc.1 to a main version.
2.9.0-rc.12025-06-3061550Unwrap to manifest-only
2.8.22025-06-1761678Bump Memory on CHECK to 1600Mi
2.8.12025-06-1261555Fixes time data parsing issue
2.8.02025-06-1161533Promoting release candidate 2.8.0-rc.2 to a main version.
2.8.0-rc.22025-06-1161491Fixed cohort check, record extractor and discovery
2.8.0-rc.12025-05-2060342Migrate to low-code
2.7.72025-05-1760708Update dependencies
2.7.62025-05-1059870Update dependencies
2.7.52025-05-0359225Update dependencies
2.7.42025-04-2658808Update dependencies
2.7.32025-04-1257703Update dependencies
2.7.22025-04-0557063Update dependencies
2.7.12025-03-2950048Update dependencies
2.7.02025-02-1248381add end date optional parameter
2.6.22024-12-1448649Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
2.6.12024-10-2947899Update dependencies
2.6.02024-10-2847013Migrate to CDK v5
2.5.132024-10-2847061Update dependencies
2.5.122024-10-1246819Update dependencies
2.5.112024-10-0546475Update dependencies
2.5.102024-09-2846158Update dependencies
2.5.92024-09-2145773Update dependencies
2.5.82024-09-1445503Update dependencies
2.5.72024-09-0745289Update dependencies
2.5.62024-08-3144980Update dependencies
2.5.52024-08-2444645Update dependencies
2.5.42024-08-1744337Update dependencies
2.5.32024-08-1343929Increase streams max_time to backoff
2.5.22024-08-1243909Update dependencies
2.5.12024-08-1043289Update dependencies
2.5.02024-08-0742841Upgrade to CDK 3
2.4.142024-07-2742746Update dependencies
2.4.132024-07-2042347Update dependencies
2.4.122024-07-1341801Update dependencies
2.4.112024-07-1041561Update dependencies
2.4.102024-07-0941295Update dependencies
2.4.92024-07-0640935Update dependencies
2.4.82024-06-2540429Update dependencies
2.4.72024-06-2240140Update dependencies
2.4.62024-06-2139916Added ability to skip missing stream in the CATALOG
2.4.52024-06-0638884Make lookback window configurable.
2.4.42024-06-0639209[autopull] Upgrade base image to v1.2.2
2.4.32024-06-0338865Enforce unique property IDs
2.4.22024-03-2036302Don’t extract state from the latest record if stream doesn’t have a cursor_field
2.4.12024-02-0935073Manage dependencies with Poetry.
2.4.02024-02-0734951Replace the spec parameter from previous version to convert all conversions:* fields
2.3.02024-02-0634907Add new parameter to spec to convert conversions:purchase field to float
2.2.22024-02-0134708Add rounding integer values that may be float
2.2.12024-01-1834352Add incorrect custom reports config handling
2.2.02024-01-1034176Add a report option keepEmptyRows
2.1.12024-01-0834018prepare for airbyte-lib
2.1.02023-12-2833802Add CohortSpec to custom report in specification
2.0.32023-11-0332149Fixed bug with missing metadata when the credentials are not valid
2.0.22023-11-0232094Added handling for JSONDecodeError while checking for api qouta limits
2.0.12023-10-1831543Base image migration: remove Dockerfile and use the python-connector-base image
2.0.02023-09-2930930Use distinct stream naming in case there are multiple properties in the config.
1.6.02023-09-1930460Migrated custom reports from string to array; add FilterExpressions support
1.5.12023-09-2030608Revert : auto replacement name to underscore
1.5.02023-09-1830421Add yearWeek, yearMonth, year dimensions cursor
1.4.12023-09-1730506Fix None type error when metrics or dimensions response does not have name
1.4.02023-09-1530417Change start date to optional; add suggested streams and update errors handling
1.3.12023-09-1430424Fixed duplicated stream issue
1.3.02023-09-1330152Ability to add multiple property ids
1.2.02023-09-1130290Add new preconfigured reports
1.1.32023-08-0429103Update input field descriptions
1.1.22023-07-0327909Limit the page size of custom report streams
1.1.12023-06-2627718Limit the page size when calling check()
1.1.02023-06-2627738License Update: Elv2
1.0.02023-06-2226283Added primary_key and lookback window
0.2.72023-06-2127531Fix formatting
0.2.62023-06-0927207Improve api rate limit messages
0.2.52023-06-0827175Improve Error Messages
0.2.42023-06-0126887Remove authSpecification from connector spec in favour of advancedAuth
0.2.32023-05-1626126Fix pagination
0.2.22023-05-1225987Categorized Config Errors Accurately
0.2.12023-05-1126008Added handling for 429 - potentiallyThresholdedRequestsPerHour error
0.2.02023-04-1325179Implement support for custom Cohort and Pivot reports
0.1.32023-03-1023872Fix parse + cursor for custom reports
0.1.22023-03-0723822Improve rate limits customer faced error messages and retry logic for 429
0.1.12023-01-1021169Slicer updated, unit tests added
0.1.02023-01-0820889Improved config validation, SAT
0.0.32022-08-1515229Source Google Analytics Data Api: code refactoring
0.0.22022-07-2715087fix documentationUrl
0.0.12022-05-0912701Introduce Google Analytics Data API source
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.