> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/your-data-sources/ga4.md).

# Google Analytics 4

Google Analytics 4 (GA4) brings your **website traffic** into Kula Intelligence — how many people visit, where they come from, which pages perform, and whether visits turn into bookings.

## What we read — and what we don't

* **We read:** aggregated reports — totals and trends — from the GA4 Data API.
* **We don't:** track individual visitors, and we never change your GA4 setup. GA4 only gives us **aggregated** numbers, not personal data.

## This connector is set up differently

There's **no key to paste**. Instead you grant a Google **service-account email** read access to your GA4 property, and tell us your property ID.

## What you'll need

* **Viewer** access on your GA4 property for the service-account email Kula shows you.
* Your GA4 **property ID**.

## How to connect

1. In Kula, open **Connectors → Google Analytics 4** and copy the **service-account email** shown there.
2. In **GA4 → Admin → Property access management**, add that email as a **Viewer**.
3. Back in Kula, enter your **property ID**, click **Test**, then **Connect**.

## Good to know

* GA4 keeps about **14 months** of history, so that's as far back as the import can reach.
* GA4 re-processes the most recent couple of days, so very recent numbers can shift slightly. Kula re-checks a short recent window each day to stay accurate.

## If it stops working

The usual cause is the service-account's Viewer access being removed, or a changed property ID. Re-grant Viewer access (or re-enter the property ID) and re-test. See [Keeping your connectors healthy](/your-data-sources/operating.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kula.digital/your-data-sources/ga4.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.