Google Analytics Identification

Before the setting of the Sirdata Analytics Helper, the Google Analytics version(s) and property identifiers 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.

1) Identification of the Google Analytics Versions and Property Identifiants

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

Their form is the following: UA-XXXXXX-Y or G-XXXXXXX

Thanks to them, you can determine whether you use or want to deploy Google Universal Analytics 360 (UA) or Google Analytics 4 (GA4). The free version of Universal Analytics is no longer operational since July 1, 2023.

If you still have some doubts, the identification is very easy, and is based on the nomenclature of the Google Analytics property identifier :

if it starts with UA (ex: UA-XXXXXX-Y), it’s Universal Analytics
if it starts with G (ex: G-XXXXXXX), it’s GA4

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.

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

Whatever the version of your tag (UA or GA4), different integrations are possible :

via an asynchronous Google Analytics script (ga.js),
via a Universal Analytics script (analytics.js),
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) ga.js

If the form of your script is the one below, you are using Universal Analytics via ga.js :

<!-- Google Analytics →

<script type="text/javascript">

var _gaq = _gaq || [];

_gaq.push(['_setAccount', 'UA-XXXXXX-Y']);

_gaq.push(['_trackPageview']);

(function() {

var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;

<!-- End Google Analytics -->

This Google Universal Analytics integration has been outdated for several years and is not supported by either Google Consent Mode nor Sirdata Analytics Helper.

An update of your tags is mandatory before proceeding with the integration of Sirdata Analytics Helper. We suggest prioritizing an upgrade to GA4 using Google Tag Manager rather than the Global Site Tag script (gtag.js).

If you continue to use this integration, Sirdata Analytics Helper will not be able to work.

b) analytics.js

If your script looks like the below, you are using Universal Analytics via analytics.js :

<!-- Google Analytics -->

<script>

  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){

  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),

  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)

  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');


  ga('create', 'UA-XXXXXX-Y', 'auto');

  ga('send', 'pageview');

</script>

<!-- End Google Analytics -->

If you continue to use this integration for the free version of Universal Analytics, which has been disabled since July 1, 2023, Sirdata Analytics Helper will be ineffective. We suggest prioritizing an upgrade to GA4 using Google Tag Manager rather than the Global Site Tag script (gtag.js).

If you are using Universal Analytics 360, the scripts are not compatible with Google Consent Mode, but you can manually disable the use of cookies in the absence of consent or use a synchronous version of Sirdata Analytics Helper to block them.

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.

c) gtag.js

If your script looks like the below, you are using Universal Analytics via Global Site Tag :

<!-- 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', 'UA-XXXXXX-Y');
</script>

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

<!-- 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 indeed compatible with both types of property identifiers, and compatible with Google Consent Mode : this means Sirdata Analytics Helper will work perfectly.

d) via Google Tag Manager (GTM)

This is an integration compatible with both types of property identifiers.

If you use this type of tag you are using Universal Analytics via GTM :

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

These integrations are compatible with Google Consent Mode, so Sirdata Analytics Helper will work perfectly.

PreviousSirdata Analytics Helper NextMandatory prerequisite

Last updated 9 months ago