> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/track/connecting-google-analytics.md).

# Connecting and using Google Analytics 4

Connect your GA4 property to a client, understand the metric tiles, toggle chart lines, and use the source filter, granularity, and comparison controls.

The Google Analytics 4 (GA4) integration brings on-site traffic, engagement, and conversion data into Rankability so you can see what happens after users click through from search results.

## Connecting GA4 to a client

1. Navigate to a client and open **Track**.
2. Expand the **GA4 sessions** tile in the executive summary strip, or scroll to the GA4 Performance card.
3. Click **Connect Google Analytics**.
4. Sign in with the Google account that has access to the GA4 property.
5. Select the property that matches your client’s website.

Once connected, Rankability fetches your GA4 data and displays it immediately. Data refreshes each time you load the Track page.

## Understanding the GA4 Performance card

The card displays five metric tiles across the top:

* **Sessions** – Total sessions for the selected period. Toggleable – click to show or hide the chart line.
* **Organic search** – Sessions from traditional search engines (Google, Bing, Yahoo, DuckDuckGo, and others). Toggleable.
* **AI referral** – Sessions from AI platforms (ChatGPT, Gemini, Perplexity, Claude, and others). Toggleable.
* **Conversions** – GA4 conversion events. Toggleable.
* **Engagement rate** – The percentage of sessions that were engaged (display only, not charted).

Click any toggleable tile to add or remove its line from the trend chart below. Active tiles show a colored left border; inactive tiles appear dimmed.

## Controls

* **Source filter** – Filter all data by specific traffic sources. Choose individual engines and AI platforms, or use the preset buttons for All, Organic only, or AI only.
* **Date range** – Choose 7, 14, 28, or 90 days.
* **Granularity (D / W / M)** – Switch between daily, weekly, and monthly chart views.
* **Compare** – Overlay the previous period’s data as dashed lines on the chart.
* **Annotate** – Add notes to specific dates (see [Using GA4 annotations](/track/using-ga4-annotations.md)).

## Traffic sources breakdown

Below the chart, the card shows a detailed traffic sources table split into two sections: **Organic search** and **AI referral**. Each row shows the source name, its share of total sessions, and the session count. This helps you understand exactly where your traffic comes from.

## Related articles

* [Understanding organic search vs AI referral traffic](/track/organic-vs-ai-referral-traffic.md) — What these categories mean and why they matter.
* [Using GA4 annotations](/track/using-ga4-annotations.md) — Mark events on the GA4 chart timeline.
* [Reading per-keyword GA4 data](/track/per-keyword-ga4-data.md) — See GA4 metrics for individual tracked keywords.
* [Connecting and using Google Search Console](/track/connecting-google-search-console.md) — Set up GSC alongside GA4 for a complete picture.


---

# 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, and the optional `goal` query parameter:

```
GET https://help.rankability.com/track/connecting-google-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.