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

# Google Analytics Integration

Track how users engage with your guideflows directly in Google Analytics 4. Guideflow supports two tracking methods, backend and frontend and most teams use both together for the most complete picture.<br>

* [**Backend tracking**](https://docs.guideflow.com/help/integrations/analytics-integrations/google-analytics-integration/ga4-backend-tracking.md): More reliable, not impacted by ad blockers. Best for critical events like conversions and lead creation.<br>
* [**Frontend tracking**](https://docs.guideflow.com/help/integrations/analytics-integrations/google-analytics-integration/ga4-frontend-tracking.md): Easier to set up, great for capturing demo interactions and engagement.

{% hint style="info" %}
Not sure which to use? For most teams, the best setup is backend for critical events and frontend for engagement.
{% endhint %}


---

# 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.guideflow.com/help/integrations/analytics-integrations/google-analytics-integration.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.
