> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/marketing-growth/google-analytics/google-analytics.md).

# Google Analytics (Universal Analytics)

## **Why syncing my Google** Analytics **to** [**Whaly**](https://whaly.io)**?**

Syncing your Google Analytics can be useful for various cases:

* Consolidate your Google Analytics performance with your others data sources (Facebook Ads, LinkedIn Ads, etc.)
* Track the origin of your traffic (Referral, Paid search, ...)
* Measure the conversion rate of your website
* Monitor the performance of your website/app
* Provide an access on the Google Analytics performance to stakeholders (colleagues, partners, investors) without giving them access to the Google Analytics console
* ...

{% hint style="warning" %}
Our connector is only syncing the [Universal Analytics properties](https://support.google.com/analytics/answer/10220206) of Google Analytics.

For properties that are using [Google Analytics V4](https://support.google.com/analytics/answer/10089681), you should use the [Google Analytics V4 connector.](/connectors/source-catalog/marketing-growth/google-analytics/google-analytics-v4.md)
{% endhint %}

## Which Google Analytics data is synced by [Whaly](https://whaly.io)?

[Whaly](https://whaly.io) 🐳 is currently syncing the following data:

### Referential

* **Account**: An Analytics account is a way to name and organize how you track one or more properties (e.g. websites, mobile apps, point-of-sale devices) using Analytics.
* **Property**: A property is a website, mobile application, or device (e.g. a kiosk or point-of-sale device.)
* **Profile (Views in the UI)**: The view for an Analytics Account is the gateway to the reports: it determines which data from your property appears in the reports.

### Reports

* **Audience Overview**: Give you an overview of when your traffic is visiting your site, how many pages they read and how long they stay.
* **Ecommerce Overview**: Find out what is your ecommerce performance (revenue, etc.).
* **Ecommerce - Product**: Find out what is your ecommerce performance (revenue, etc.).
* **Load Performance**: Give you an overview of your site/app loading performance.
* **Page**: Give you an overview of how your website pages are performing.
* **Traffic origin**: Find out how your users are getting on your site/app.

{% embed url="<https://docs.google.com/presentation/d/1g2PNXa5fz9Uhy6opcqpRChYUvI5cwpWMS8isb4sWbFw/edit#slide=id.g244d368397_0_1>" %}

[You can find the relationship between all those objects here.](https://docs.google.com/presentation/d/1g2PNXa5fz9Uhy6opcqpRChYUvI5cwpWMS8isb4sWbFw/edit#slide=id.g244d368397_0_1)

## How to query Google Analytics data?

Whaly connector is syncing all Analytics Accounts, Properties & Apps and Views of the account selected in the authentication wizard.

In Google Analytics, Reports are attached to Views. When different Views are created on the same Properties & Apps, they're attached reports will contains duplicates.

Hence, when querying the synced reports, it's very important in order to get the proper values to always filter on the "Property/View" objects in order to avoid getting duplicates.&#x20;

{% hint style="success" %}
The field `label` of the View object is recommended to be the field to filter on to get the same results as in Google Analytics.
{% endhint %}

#### Example:

![](/files/gwmmIxOCvQNC0nQjsSsI)

Will be equivalent to browsing Google Analytics reports on the "1 Master View"

![](/files/WDA6wQdINps2d41CG7rn)


---

# 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.whaly.io/connectors/source-catalog/marketing-growth/google-analytics/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.