> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Google Analytics as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/google-analytics > **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links). ## On this page - [Prerequisites](#prerequisites) - [Adding a data source](#adding-a-data-source) - [Sync modes](#sync-modes) - [Configuration](#configuration) - [Supported tables](#supported-tables) - [Troubleshooting](#troubleshooting) ![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70) ![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d) Let AI connect your sources for you Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog. `npx @posthog/wizard warehouse` ![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png) ![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you The Google Analytics connector syncs daily report data from a Google Analytics 4 property – users, sessions, page views, devices, locations, traffic sources, and events – into PostHog. ## Prerequisites You need a Google account with read access to the GA4 property you want to sync, and the numeric property ID for that property. ## Adding a data source 1. In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section. 2. Click **\+ New source** and click **Link** next to this source. 3. Enter your credentials (see [Configuration](#configuration) below) and click **Next**. 4. Select the tables you want to sync, choose a sync method and frequency, then click **Import**. Once the syncs are complete, you can start querying this data in PostHog. When linking Google Analytics, you'll need: - **Google Analytics account** – connect a Google account that has read access to the property. PostHog requests the `analytics.readonly` scope when you authorize. - **Property ID** – the numeric GA4 property ID, found in Google Analytics under **Admin → Property settings → Property details** (for example, `123456789`). **Finding your Property ID** The Property ID is a numeric value like `123456789`. Don't confuse it with: - **Measurement ID** (`G-XXXXXXX`) – this is from your GA4 data stream or website tag and won't work here - **Universal Analytics ID** (`UA-XXXXXXX`) – this is from legacy Google Analytics (not GA4) and isn't supported Find the correct Property ID in Google Analytics under **Admin** > **Property settings** > **Property details**. ## Sync modes Each table can be synced in one of several modes, depending on what the source supports: - **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes. - **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured. - **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs. - **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected. See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them. ## Configuration | Option | Description | | --- | --- | | `Google Analytics account` **Type:** oauth **Required:** True | | | `Property ID` **Type:** text **Required:** True | The numeric GA4 property ID, found in Google Analytics under Admin → Property settings → Property details. This is not the 'G-XXXXXXX' Measurement ID from your website tag. | | `Custom reports (optional)` **Type:** textarea **Required:** False | Define your own report tables as a JSON array, on top of the built-in ones. Each report needs a name, GA4 dimensions, and GA4 metrics. PostHog always adds the date dimension and syncs each report daily. GA4 allows up to 9 dimensions (including date) and 10 metrics per report. | | `Days of history to sync initially (optional)` **Type:** number **Required:** False | How far back the first sync of each report goes. The default is 730 days. If a large property runs out of Google Analytics API quota, set a lower value, for example 90 or 365. | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `website_overview` | Daily totals for users, sessions, page views, session duration, and bounce rate. | Incremental, Full refresh | date | — | | `daily_active_users` | 1-day active users per day (DAU). | Incremental, Full refresh | date | — | | `weekly_active_users` | Rolling 7-day active users per day (WAU). | Incremental, Full refresh | date | — | | `four_weekly_active_users` | Rolling 28-day active users per day. | Incremental, Full refresh | date | — | | `devices` | Daily usage broken out by device category, operating system, and browser. | Incremental, Full refresh | date | — | | `locations` | Daily usage broken out by country, region, and city. | Incremental, Full refresh | date | — | | `pages` | Daily page performance broken out by host name and page path (including query string). | Incremental, Full refresh | date | — | | `traffic_sources` | Daily traffic broken out by session source and medium. | Incremental, Full refresh | date | — | | `user_acquisition` | Daily acquisition broken out by the source and medium that first acquired each user. | Incremental, Full refresh | date | — | | `landing_pages` | Daily performance of the first page in each session (landing page, including query string). | Incremental, Full refresh | date | — | | `campaigns` | Daily traffic broken out by session campaign, default channel group, source, and medium. | Incremental, Full refresh | date | — | | `key_events` | Daily key events and purchase revenue broken out by session source and medium. | Incremental, Full refresh | date | — | | `events` | Daily event counts broken out by event name. | Incremental, Full refresh | date | — | ## Troubleshooting If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.