> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/integrations/metrics-tools/google-analytics.md).

# Google Analytics

Pull web analytics from Google Analytics into Smaply journey maps

Connect Google Analytics to surface web traffic, conversion, and user behaviour data on the journey moments where they matter, like landing-page bounce rate next to the awareness stage of an e-commerce journey.

#### Why connect Google Analytics

* Ground awareness, consideration, and conversion stages in actual web data
* Update once in GA; see it everywhere in your journey maps

{% hint style="info" icon="tag" %}
Service account auth (recommended for teams) is available on the Governance plan. OAuth is available on all plans with metrics integrations.
{% endhint %}

#### In this section

* [**Set up Google Analytics**](/integrations/metrics-tools/google-analytics/how-to-set-up-the-google-analytics-integration.md) - Connect at the account level using service account or OAuth.
* [**Use Google Analytics in a metric**](/integrations/metrics-tools/google-analytics/how-to-use-google-analytics-in-a-metric.md) - Add GA data to journey-map metric cards.


---

# 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://helpdesk.smaply.app/integrations/metrics-tools/google-analytics.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.