
### get total page view count for the month

Return 202305's each date's page count

```SQL
with data as (
SELECT event_date, event_name, count(*) as total
FROM `ga4_table.events_intraday_202305*`
group by 1, 2
having event_name = 'page_view'
order by 1
)
select event_date, total from data;
```

Total event count with event_name

```SQL
with data as (
SELECT event_name, count(*) as total
FROM `ga4_table.events_intraday_202306*`
group by 1
order by 1
)

select * from data;
```


GA4 Big Query Sample Query


## Table of Contents

1. [Introduction](#introduction)
2. [Prerequisites](#prerequisites)
3. [How to Use gtag to Add User Properties](#how-to-use-gtag-to-add-user-properties)
4. [Configure Custom Definitions for User Properties](#configure-custom-definitions-for-user-properties)
5. [What About the page_view Events for User Properties](#what-about-the-page_view-events-for-user-properties)
6. [GTAG Sample Code](#gtag-sample-code)
7. [Page Load Events Don't Contain the user_properties](#page-load-events-dont-contain-the-user_properties)
8. [Conclusion](#conclusion)

## Introduction

This blog shows how to add user properties to Google Analytics 4 (GA4). We'll demonstrate how to use `gtag` or Google Tag Manager to achieve this. For each approach, we'll also show how the actual user properties data appears in BigQuery for GA4.

## Prerequisites

This blog assumes your website is already set up with GA4 via Google Tag Manager, and the `gtag` and `dataLayer` global variables are available on your page.

- Website is set up with GA4.
- `https://www.googletagmanager.com/gtag/js` is loaded.

## How to Use gtag to Add User Properties

Here we'll start with how to use `gtag` to add user properties to GA4, and we'll verify the results in BigQuery as well.

The following is an example code snippet that fires a GA4 event with user properties. The first line of code sets the user_properties with the key `favorite_color`. We assume `favorite_color` is a user-specific attribute related to your site, so we set it to "blue". The next line sends the GA4 event `test_up_data1` to GA4.

```
gtag("set", "user_properties", {favorite_color: "blue"});
gtag("event", "test_up_data1", {other_data: "test up properties"});
```

When you run the above code from your browser console, you should see a GA4 event being sent from your browser as shown below. `ep` is event parameters, and `up` is user properties.
![send ga4 user_properties event](/images/send-user-properties/img1.png)

How does the above appear in BigQuery? You can see in the BigQuery table that the event we just fired from our browser has been received, and the user_properties contain `favorite_color` with the value present. Also, you'll notice the page_view and user_engagement events don't have that value. These two events are fired by GA4 and are automatically collected.
![send ga4 user_properties and big query](/images/send-user-properties/img2.png)

Now, if you run the same code again in the same browser, you'll notice the browser fires the event but without the user properties `favorite_color` field.

```
gtag("set", "user_properties", {favorite_color: "blue"});
gtag("event", "test_up_data1", {other_data: "test up properties"});
```

This is the BigQuery result after we made the second gtag request from the browser. Although we included the set with user properties, no user properties were added to the same event.
![big query with user properties](/images/send-user-properties/img3.png)

## Configure Custom Definitions for User Properties

It's not clear why using `gtag` with `set` for user properties has the above behavior, where only the first event sent to BigQuery contains the user_properties. It appears we need to configure the user property in GA4's `Custom definitions` section.

The following shows how to configure the user property in `Custom definitions`. As you can see below, we create a dimension named `favorite_color` with the Scope set to `User`.
![Config Custom Dimensions for User Properties](/images/send-user-properties/img4.png)

After setting the custom dimensions in the GA4 property, it might take some time for the results to take effect. We performed the following test. The `user_pseudo_id` is stored in the GA4 BigQuery table. You can see that when we load the page, the browser fires several events — `first_visit`, `scroll`, `session_start`, and `page_view` — and none of them have `favorite_color` in the user_properties table. After the page loads, we fired the same event `test_up_data1` a few times, and you can see they all have the `favorite_color` record.

Next, you can see that we fired `test_up_data` which contains `favorite_color`, and then we also fired another event `test_up_data2`. You'll notice this custom event also contains the user property `favorite_color`. So it appears that after we use `gtag` to `set` the user properties along with the configuration in the GA4 property, any custom event after the `set` will also include the same user properties. This makes sense as it's the user scope of events.
![User Properties at Big Query](/images/send-user-properties/img5.png)

### What About the page_view Events for User Properties

We also performed another test as shown below. You can see that we start a new session (since the `user_pseudo_id` changed). When we first load the page, the `page_view`'s user_properties is empty. But once we manually run the code above, you can see events with the `favorite_color` user property filled into the automatically collected events. Any other event will also include the same user properties. In addition, you can see that when we load the page again within the same session, the user properties still contain the same `favorite_color` value.
![User Properties at Big Query](/images/send-user-properties/img6.png)

## GTAG Sample Code

The following is the sample code from above. Once you click the button, the subsequent events including page_view will also include the user property `favorite_color`. Also, you need to add `favorite_color` to the custom dimensions in the GA4 property.

```
<button
  className="ga4"
>
test_up_data1
</button>

<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', '{Measurement ID}', {
      send_page_view: false
});

var buttonEle = document.querySelector(".ga4");
buttonEle.addEventListener('click', function(e) {
    gtag("set", "user_properties", {favorite_color: "blue"});
    gtag("event", "test_up_data1", {other_data: "test up properties"});
});
</script>
```

## Page Load Events Don't Contain the user_properties

There's one issue with the above code. If you start the page from a new session, the page view events don't contain the user_properties we set earlier. To solve this, we can use dataLayer along with user properties in the GA4 configuration.
![Big Query User Property - First Visit](/images/send-user-properties/img7.png)

Here, we define a dataLayer variable as favorite_color, then create a user property `favorite_color` in the GA4 configuration.
![GA4 Configuration - User Properties](/images/send-user-properties/img7.png)

Now, we just need to add the code to the page during page load. Make sure the code below is placed before the GTM scripts.

```
// place this code before gtm load scripts.
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
    favorite_color: "green"
})
```

## Conclusion

In summary, if you have GA4 fields that are user properties, the following looks like the correct implementation:

- Create a custom dimension in the GA4 property with the type set to User.
- Create a dataLayer variable for your property.
- Create a GA4 configuration and set the dataLayer variable as a user property.
- In your code, set the dataLayer value before the GTM script loads.

Now, page view and any subsequent events' user_properties should contain your new user property.


User-scoped custom dimensions in GA4. This blog shows how to set user properties in GA4 by using gtag or Google Tag Manager.

How to Set User Properties in GA4


## Table of Contents

1. [client_id](#client_id)
2. [language](#language)
3. [page_location](#page_location)
4. [page_referrer](#page_referrer)
5. [page_title](#page_title)
6. [user_id](#user_id)
7. [user_properties](#user_properties)

## Introduction

GA4 has several configuration fields that control how data is collected and sent. This post documents each field, how to set it via `gtag`, and what the corresponding query string key and BigQuery column are.

Reference: https://developers.google.com/analytics/devguides/collection/ga4/reference/config

## client_id

Stored as part of the first-party analytics cookie for 2 years, used to identify each user.

```
gtag('set', 'client_id', '123456');
gtag('event', 'test_gtag_set', { test_id: 'client_id'});
```

The `collect?v=2` request's query string key will be `cid`. The BigQuery column is `user_pseudo_id`, and the cookie `_ga` value will be updated to `GA.1.1.123456`. After updating this value, subsequent requests will always set the same value since the cookie is updated.

## language

By default, this uses the window object's `navigator.language` value.

```
gtag('set', 'language', 'en-ca');
gtag('event', 'test_gtag_set', { test_id: 'language'});
```

The `collect?v=2` request's query string key will be `ul`. The BigQuery column `device.language` will be updated to `en-ca`. The `navigator.language` value won't be updated.

## page_location

By default, this uses the window object's `document.location` value. It is not clear what condition would require updating this value.

```
gtag('set', 'page_location', '/test2');
gtag('event', 'test_gtag_set', { test_id: 'page_location'});
```

The `collect?v=2` request's query string key will be `dl`. The BigQuery column `event_params.page_location` will be updated to `/test2`.

## page_referrer

By default, this uses the window object's `document.referrer` value. If the user comes directly to the site, `document.referrer` should be empty and BigQuery will have no value.

```
gtag('set', 'page_referrer', 'https://technoapple.com');
gtag('event', 'test_gtag_set', { test_id: 'page_referrer'});
```

The `collect?v=2` request's query string key will be `dr`. The BigQuery column `event_params.page_referrer` will be updated to `https://technoapple.com`. Because `page_referrer` has a value, `event_params` will add 2 more values: `medium` with the value `referral` and `source` with the value `technoapple.com`.

## page_title

By default, this uses the window object's `document.title` value. It is not clear what condition would require updating this value.

```
gtag('set', 'page_title', 'my title');
gtag('event', 'test_gtag_set', { test_id: 'page_title'});
```

The `collect?v=2` request's query string key will be `dt`. The BigQuery column `event_params.page_title` will be updated to `my title`.

## user_id

The user's ID provided by the site.

```
gtag('set', 'user_id', '123');
gtag('event', 'test_gtag_set', { test_id: 'user_id'});
```

The `collect?v=2` request's query string key will be `uid`. The BigQuery column `user_id` will be updated to `123`. Once this value is set, subsequent gtag requests will always contain user_id as `123`.

## user_properties

Additional user preference information. You can set up to 25 additional user properties. The name maximum length is 24 characters and the value maximum length is 36 characters.

```
gtag('set', 'user_properties', {
  "data1": "1 data"
});
gtag('event', 'test_gtag_set', { test_id: 'user_properties'});
```

The `collect?v=2` request's query string key will be something starting with `up`, e.g. `up.data1`. The BigQuery column is `user_properties`, and it should contain the object `data1` with the value `1 data`.

```
gtag('config', 'G-NFY53GVWDK', {
   'user_properties': {
      "data_10": "10 data"
  }
});
gtag('event', 'test_gtag_set', { test_id: 'user_properties'});
```

## Conclusion

Understanding GA4 configuration fields is essential for properly tracking user behavior. Each field has a specific query string key in the `collect?v=2` request and a corresponding BigQuery column. By using `gtag('set', ...)`, you can customize how these fields are populated to suit your analytics needs.


A guide to GA4 configuration fields including client_id, language, page_location, page_referrer, page_title, user_id, and user_properties.

About GA4 Configuration Fields


## Table of Contents

1. [Introduction](#introduction)
2. [Setup Universal Analytics](#setup-universal-analytics)
3. [Setup Property](#setup-property)
4. [Add Basic Information](#add-basic-information)
5. [Setup Tracking Code](#setup-tracking-code)
6. [Add Tracking Code to Web Page](#add-tracking-code-to-web-page)
7. [Verify the Tracking Code](#verify-the-tracking-code)
8. [Conclusion](#conclusion)

## Introduction

This page shows an example of how to set up Universal Analytics for learning purposes. Please be aware that Google Universal Analytics will no longer process new data beginning July 1, 2023. You'll need to switch to a Google Analytics 4 Property.

## Setup Universal Analytics

If you're new to Google Analytics, you'll need to set up an account. Once you have a Google Analytics account, you can create a property as the screen shows below.

Again, this blog is for learning purposes only, so we choose the Universal Analytics property, but most likely you'll need to use the GA4 property.

### Setup Property

![Setup Property](/images/setup-analytics/img1.png)

### Add Basic Information

![Add Basic Information](/images/setup-analytics/img2.png)

### Setup Tracking Code

At this point, you should be getting the Google Tracking code snippet. You'll need to add this to your website so the site can start tracking activity.

![Setup Tracking Code](/images/setup-analytics/img3.png)

### Add Tracking Code to Web Page

As described in the Setup Tracking Code section, you'll need to copy the Google Tracking Code to any page on your site that needs tracking.

The following is sample code showing how to add a Google Tag Manager script to Next.js.

```
import Script from 'next/script'
export default function Nextra({ Component, pageProps }) {
  return (
    <>
      <Script
            strategy="afterInteractive"
            src='https://www.googletagmanager.com/gtag/js?id=UA-{Your Property ID}' />
      <Script
        strategy="afterInteractive"
        dangerouslySetInnerHTML={{
          __html: `
            window.dataLayer = window.dataLayer || [];
            function gtag(){dataLayer.push(arguments);}
            gtag('js', new Date());
            gtag('config', 'UA-{Your Property ID}');
          `,
        }}
      />
    </>
  )
}

```

### Verify the Tracking Code

After adding the above tracking code to your site, go back to Google Analytics and check if there are any records.

The above code sends a pageview to Google Analytics.

```
gtag('config', '{your tracking ID}');
```

## Conclusion

In this blog, we walked through setting up Universal Analytics with Google Tag Manager and adding the tracking code to a Next.js application. While Universal Analytics is being sunset, understanding the setup process is still useful for migration planning to GA4.


Most sites already use Universal Analytics. This blog shows how to set up both Universal Analytics and GA4 from Google Tag Manager.

How to Setup Universal Analytics and GA4 via Google Tag Manager


## Table of Contents

1. [Introduction](#introduction)
2. [Setup Universal Analytics](#setup-universal-analytics)
3. [Setup Property](#setup-property)
4. [Add Basic Information](#add-basic-information)
5. [Setup Tracking Code](#setup-tracking-code)
6. [Add Tracking Code to Web Page](#add-tracking-code-to-web-page)
7. [Verify the Tracking Code](#verify-the-tracking-code)
8. [Conclusion](#conclusion)

## Introduction

This page shows an example of how to set up Universal Analytics for learning purposes. Please be aware that Google Universal Analytics will no longer process new data beginning July 1, 2023. You'll need to switch to a Google Analytics 4 Property.

## Setup Universal Analytics

If you're new to Google Analytics, you'll need to set up an account. Once you have a Google Analytics account, you can create a property as the screen shows below.

Again, this blog is for learning purposes only, so we choose the Universal Analytics property, but most likely you'll need to use the GA4 property.

### Setup Property

![Setup Property](/images/setup-analytics/img1.png)

### Add Basic Information

![Add Basic Information](/images/setup-analytics/img2.png)

### Setup Tracking Code

At this point, you should be getting the Google Tracking code snippet. You'll need to add this to your website so the site can start tracking activity.

![Setup Tracking Code](/images/setup-analytics/img3.png)

### Add Tracking Code to Web Page

As described in the Setup Tracking Code section, you'll need to copy the Google Tracking Code to any page on your site that needs tracking.

The following is sample code showing how to add a Google Tag Manager script to Next.js.

```
import Script from 'next/script'
export default function Nextra({ Component, pageProps }) {
  return (
    <>
      <Script
            strategy="afterInteractive"
            src='https://www.googletagmanager.com/gtag/js?id=UA-{Your Property ID}' />
      <Script
        strategy="afterInteractive"
        dangerouslySetInnerHTML={{
          __html: `
            window.dataLayer = window.dataLayer || [];
            function gtag(){dataLayer.push(arguments);}
            gtag('js', new Date());
            gtag('config', 'UA-{Your Property ID}');
          `,
        }}
      />
    </>
  )
}

```

### Verify the Tracking Code

After adding the above tracking code to your site, go back to Google Analytics and check if there are any records.

The above code sends a pageview to Google Analytics.

```
gtag('config', '{your tracking ID}');
```

## Conclusion

In this blog, we walked through the simple steps to set up Google Universal Analytics on your website. While Universal Analytics is being sunset in favor of GA4, understanding the setup process remains useful for migration planning and maintaining legacy tracking configurations.


Simple steps to set up Google Universal Analytics on your website.

Google Analytics

GA4 Big Query Sample Query

How to Set User Properties in GA4

About GA4 Configuration Fields

How to Setup Universal Analytics and GA4 via Google Tag Manager

Setup Google Universal Analytics