> For the complete documentation index, see [llms.txt](https://docs.rhym.io/rhym-help-guide-and-faqs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhym.io/rhym-help-guide-and-faqs/integrations/google-analytics.md).

# Google Analytics

## Click on Add Integration in Editor Header

For every campaign, as you enter the editor. You can enable relevant integrations by clicking on **“Add Integration”** in the header. You will see all eligible integrations there.

<figure><img src="/files/4Q8QXS7F4CKGMztFKldA" alt=""><figcaption></figcaption></figure>

## Connect with GA

For Google Analytics & Facebook Pixel, you need to provide your ID for us to connect!

#### How to find a GA ID?

1. Login to your Google Analytics account & click on Admin Settings
2. Click on the Data Steam tab

   ![](/files/m9tnVwr1oQVgEeiO51ol)
3. Click on the relevant Data Stream or create a new one & copy the Measurement ID required for integration

   ![](/files/JFcSMYvZNKhoXYNuK6wu)


---

# 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://docs.rhym.io/rhym-help-guide-and-faqs/integrations/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.
