# Google Analytics Destination

> The **Google Analytics** export connector concerns what Google calls ' *Cost Data* ', i.e. the ability to import Impression, Clicks and Adspend metrics from the selected Data Sources in the Google Analytics Acquisition reports against the UTM dimensions.

### How often will the import happen?

> Once the connector is in place, Adloop will send daily data from the previous day. To ensure quality data, Adloop will also send data from D-3 on a daily basis (this may change as we indicate in our \[\[quality policy|Data-Quality]]).

## A. Requirements for using the Google Analytics connector (cost data)

> Only data from campaigns not managed by **Google** can be imported by this connector. Therefore, data from campaigns managed in Google Ads or Google Campaign Manager will not be imported.

### 1. Prepare the Matching between Data Sources and Google Analytics UTM

**Google Analytics** identifies the acquisition sources thanks to the **UTM** parameters (Source, Medium, Campaign etc.). The Platforms **Data Sources** have another form of nomenclature with specific **dimensions.**

> Matching consists in matching the dimensions of the Platforms **Data Sources** you want to import with the UTM values of **Google Analytics** . This way Google will know where to put the data.

For more information about Matching, see the \[\[dedicated section|Matching]].

### 2. Create a Dataset in Google Analytics

To create a Dataset, follow the procedure below:

**Admin > Data Import > Create**

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-ac1f0861ace3b098b411f04416c443c384a69d06%2Fimage-20220301-155724.png?alt=media)

Select **Cost Data** then **Continue**

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-1502f597f088fdc34e587001db2c27ee5812bfeb%2Fimage-20220301-155835.png?alt=media)

Give a name to the **Dataset** and select the **Views** it will impact (one or more)

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-a5e25e992584fdfa5d4ba115a820d81740af3c87%2Fimage-20220301-155930.png?alt=media)Indicate the Data that will be sent as shown in the screenshot below (in yellow, what must be added or selected) :

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-c55414129b6eb7c69ea5cd20cdaa574b01e33f19%2Fimage-20220301-160232.png?alt=media)

> Do not forget to select the **Overwrite** option. This is because Adloop sends data over several days to ensure that the indicators are completely reliable (see information on \[\[data quality|Data-Quality]]). If you leave the Summation option, the data will be added instead of replaced.

After validation the Google Analytics data set is created and you can **copy its ID** :

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-e25348eb96c556d79d95ef9dda639125ccf4ccb3%2Fimage-20220301-160327.png?alt=media)

## B. Creating the Export Destination and the Export in Adloop

### 1. Create the Export Destination

In the Export Destination, select the following connector:

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-637436948309ec93105c93323091c4974118ae23%2Fimage-20210630-170828.png?alt=media)Follow the configuration process:

* Name of the Destination
* Google Analytics account to send the data to

until you get to the screen where you are asked for the **Data Set ID** : (the ID retrieved from Google Analytics above)

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-7eae81fd74e64759b5f2116b4ec339bb24d00d63%2Fimage-20220301-160555.png?alt=media)

Validate everything and that's it, your Destination is ready.

### 2. Create the Export itself

No difficulties in this process.

Step 1: Select the Destination you just created![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-f268609fd3753908df2b8a471cdeb196cee8e2e2%2Fimage-20210707-092000.png?alt=media)

Step 2: Select the Data Sources you want to send to Google Analytics

> This is where you need to make sure you have configured consistent matching rules for the **Data Sources** you want to send, otherwise you will get an error like this:

![](https://3498010832-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3KEERJBEyYQ7ZxIIMK79%2Fuploads%2Fgit-blob-caf34723023590fa88088274c8f2a44994d1f43d%2Fimage-20210707-092033.png?alt=media)

Step 3: Name your export


---

# Agent Instructions: 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:

```
GET https://community.commandersact.com/adloop/v-exports-center/export-destinations/google-analytics-destination.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
