> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/recommendations-and-merchandising/how-tos/how-to-configure-your-analytics-integration/how-to-configure-google-analytics-integration.md).

# How to configure Google Analytics integration

## How to configure Google Analytics integration

Connect **Google Analytics 4** with **AB Tasty Recommendations & Merchandising** to track recommendation performance and measure the business impact of your personalization efforts.

{% hint style="success" %}
The GA4 integration now supports automatic setup with no manual activation date and no Google OAuth flow. A BigQuery project is automatically created when needed, using an AB Tasty service account instead of a user Google login.
{% endhint %}

### Prerequisites

Before configuring Google Analytics integration, ensure you have:

* Active AB Tasty Recommendations & Merchandising account with deployed recommendations
* Google Analytics 4 property set up for your website
* Administrative access to your Google Analytics (and Biq Query if needed) account
* Understanding of your tracking requirements and business KPIs

### Access Google Analytics integration

Navigate to the integrations interface to set up your Google Analytics connection.

1. Log into your **AB Tasty R\&M dashboard**
2. Click **SETTINGS** in the left sidebar
3. Select the **Integrations** tab
4. Locate **Google Analytics 4** under *Analytics*
5. Click **CONNECT**

### Configure GA4 connection

Set up the integration between your Google Analytics property and AB Tasty platform.

Authorize access via service account\
Instead of signing into a Google account, you must add the AB Tasty service account to your GA4 Property:

```
reco-external-3854516562@prod-uc-serving-2407.iam.gserviceaccount.com
```

#### Configure data sharing settings

Two possibles flows to share data

**Case A – BigQuery already detected in your GA4 config**

* GA4 events are accessed through **BigQuery**
* If a BigQuery export already exists, AB Tasty automatically detects it.\
  You only need to grant the AB Tasty service account Viewer/Job User access to the existing GA4 BigQuery dataset.
* Once confirmed → integration is complete

**Case B – No BigQuery detected**

* A **BigQuery project is created automatically** when GA4 is connected
* The dataset is created in AB Tasty’s BigQuery project (`prod-bq-unicollect-211188`) using the service account.\
  No manual date is required — the activation/start date is automatically set to “today”.
* You receive a **confirmation screen** showing status

### Validate Google Analytics integration

You can confirm that the integration worked by checking:

#### In AB Tasty:

* The GA4 integration appears as **Connected and you have 2 new datasets :** `Purchase` and `Pageview`

#### In GA4:

* A BigQuery export is visible under\
  **Admin → Product Links → BigQuery Links**

#### In BigQuery:

* A dataset named `analytics_<property_id>` has been created
* New daily export tables begin appearing shortly after setup


---

# 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.abtasty.com/recommendations-and-merchandising/how-tos/how-to-configure-your-analytics-integration/how-to-configure-google-analytics-integration.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.