Setting up Google Analytics 4
Step-by-step guide on setting up Google Analytics 4 as a destination in RudderStack.
Last updated
Was this helpful?
Step-by-step guide on setting up Google Analytics 4 as a destination in RudderStack.
Last updated
Was this helpful?
Before configuring Google Analytics 4 as a destination in RudderStack, verify if the source platform is supported by Google Analytics 4 by referring to the table below:
Connection Mode
Web
Mobile
Server
Device Mode
Supported
-
-
Cloud Mode
Supported
Supported
Supported
To know more about the difference between cloud mode and device mode in RudderStack, read the guide.
Once you have confirmed that the source platform supports sending events to Google Analytics 4, follow these steps:
From your , add the source. Then, from the list of destinations, select Google Analytics 4.
Assign a name to your destination and click on Next.
To successfully configure Google Analytics 4 as a destination, configure the following settings:
API Secret: This field is required only for the cloud mode setup where you can enter the API Secret generated through the Google Analytics dashboard. It can be created in the Google Analytics dashboard under Admin > Data Streams > Choose your stream > Measurement Protocol > Create.
Client Type: Select the client type as gtag
or Firebase
from the dropdown:
gtag
- Supported for the cloud and device mode both. If you select gtag
, enter the below:
Measurement Id: Enter the Measurement Id which is the identifier for a data stream. It can be found in the Google Analytics dashboard under Admin > Data Streams > Choose your stream > Measurement ID.
Firebase
- Supported only for the cloud mode. If you select Firebase
, enter the below:
Firebase App Id: Enter the Firebase App ID which is the identifier for Firebase app. It can be found in the Firebase dashboard under Project Settings > General.
All the settings mentioned below are applicable only for the device mode.
Block a Page View Event: Enable this setting to disable sending page_view
events on load. However, you can explicitly send a page_view
event by calling the page()
API.
Extend Page View Property: Enable this setting to send the following properties along with any other custom property to the page
call of the RudderStack SDK:
url
search
Send userId to GA: This setting exhibits the following behavior:
Finally, click on Next to enable Google Analytics 4 as a destination in Rudderstack.
Go to the Admin section in the left sidebar.
Select the relevant account and property.
Click on Data Streams and select the stream to get the Measurement Id as shown:
Go to the Admin section in the left sidebar.
Select the relevant account and property.
Click on Data Streams and select the stream.
Click on Measurement Protocol API secrets to get the API Secret as shown:
Go to the Admin section in the left sidebar.
Select the relevant account and property.
Refer to the section for more information on how to obtain the API Secret, Measurement Id and Firebase App ID.
Google Analytics 4 has a limit on the number of unique properties per event name. The default page_view
event supports the properties mentioned in the guide.
If enabled, the user ID is set to the identified visitors and sent as explained in the guide.
If disabled, userId
is not sent and Rudderstack only sends the user traits set as user_properties
to Google Analytics. The user properties are set on the gtag
client as explained in the guide.
This option is applicable only if you're sending events to Google Analytics 4 via the web device mode. Refer to the guide for more information on this feature.
Use device mode to send events: Enable this setting to send events via the .
Login to dashboard.
Login to dashboard.
Login to dashboard.
Click on Data Streams and select the stream to get the Firebase App Id as shown:
For queries on any of the sections covered in this guide, you can or start a conversation in our community.