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

# Google Analytics 4

Connect Google Analytics 4 to enrich Pages with traffic, engagement, and selected conversion data.

Connect Google Analytics 4 (GA4) to bring website performance data into [Pages](/insights/onsite/pages.md). This lets you evaluate AI search visibility alongside traffic, engagement, and the business outcomes that matter to your team.

## How to Configure GA4

1. Open **Insights → Settings**.
2. Connect the GA4 property that corresponds to your site.
3. Optionally select one or more GA4 conversions, also called key events, to include in Insights.
4. Complete the connection.

Choose the events that best represent meaningful outcomes for your business, such as a completed signup or purchase.

{% hint style="info" %}
Selecting conversions is optional. You can still use GA4 traffic and engagement data in Pages without selecting a conversion.
{% endhint %}

## Use GA4 Data in Pages

After GA4 is connected, AirOps automatically syncs its data into matching URLs in Pages. GA4 enriches pages that AirOps already knows about from AI search citations or a sitemap; it does not create pages on its own.

Pages can include:

* Traffic and session data
* Engagement data
* Results for the conversions or key events selected during setup

Use this data with AI citation and Google Search Console metrics to prioritize content by business impact. For example, a page with meaningful conversion activity but declining citation visibility may be a higher-priority refresh than a page that receives little traffic and produces no selected conversions.

You can change which conversions or key events are included as your measurement goals evolve.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/insights/analytics/settings/google-analytics-4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.