> For the complete documentation index, see [llms.txt](https://helper.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helper.docs.sirdata.net/english/sirdata-analytics-helper-1/google-analytics-identification.md).

# Google Analytics Identification

Before the setting of the Sirdata Analytics Helper, the Google Analytics 4 property identifier(s) that you want to secure have to be identified

Indeed, depending on your current or planned integration of Google Analytics, some steps are necessary or, on the contrary, unnecessary.

Most of the time, and especially if you are already a Sirdata Consent Management Platform (CMP) customer, the process is extremely simple. Just follow the steps in this guide.

{% hint style="info" %}
Universal Analytics has been permanently shut down by Google (standard properties: July 1, 2023; UA 360 properties: July 1, 2024). This page only covers Google Analytics 4 (GA4). If you are still using legacy Universal Analytics scripts (ga.js, analytics.js) or identifiers in the form UA-XXXXXX-Y, a migration to GA4 is required before integrating Sirdata Analytics Helper.
{% endhint %}

## 1) Identification of the Google Analytics 4 Property Identifiers

In your Google Analytics account, or in your tags, the 1st thing you need to do is finding and writing aside your GA4 property identifier(s) : they will be useful for activating the Sirdata Analytics Helper service.

Their form is the following: G-XXXXXXX

{% hint style="warning" %}
Only the audience measurement is supported by the Sirdata Analytics Helper service : Google advertising services such as Google Ads, Campaign Manager 360, Display & Video 360, Search Ads 360 are not part of it.

If your identifier is in the format AW-XXXXXXX or DC-XXXXXXX, Sirdata Analytics Helper will be ineffective.
{% endhint %}

Once you have identified the services concerned, you can proceed to the next step : identification of the integration mode(s).

## 2) Identification of the integration

Different GA4 integrations are possible :

* via the Global Site Tag (gtag.js)
* or via the Tag Manager

For each property identifier which you want to activate Sirdata Analytics Helper for, it is necessary to determine the existing or planned integration, by analyzing the scripts or tags you use.

### a) gtag.js

If the form of your script is the below, you are using **GA4 via Global Site Tag** :

```html
<!-- Global Site Tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXX');
</script>
```

The Global Site Tag is compatible with Google Consent Mode : this means Sirdata Analytics Helper will work perfectly.

Therefore, you can go on with your installation of Sirdata Analytics Helper by following point II (“privacy”). If you use several property identifiers, before stepping to point II, make sure you noted the integration mode of each of them.

### b) via Google Tag Manager (GTM)

If you use this type of tag you are using **GA4 via GTM** :

<figure><img src="https://1307546236-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4kHDztybHWlVhU0ThHx4%2Fuploads%2FQkbE753sXWLutn7ZTwjL%2Fimage.png?alt=media&amp;token=66a24ae0-062f-487e-a50b-72e1a6f735a1" alt=""><figcaption><p>GA4 tag via Google Tag Manager</p></figcaption></figure>

This integration is compatible with Google Consent Mode, so Sirdata Analytics Helper will work perfectly.

Therefore, you can go on with your installation of Sirdata Analytics Helper by following point II (“privacy”). If you use several property identifiers, before stepping to point II, make sure you noted the integration mode of each of them.