Hi.
Is it possible to get device_id when exporting googleAnalytics4 data to Bigquery or RedShift?
The device_id refers to information that can identify a user or device.
Solved! Go to Solution.
Device-based reporting identifiers are a collection of identifiers that serve the purpose of tracking users across multiple devices and sessions. This set includes identifiers such as device_id, user_pseudo_id, and advertising_id. Client IDs, on the other hand, are distinct identifiers given to each user or device interacting with your website or application. These identifiers facilitate the tracking of a user or device across different sessions and devices.
In the context of BigQuery, both device_id and user_pseudo_id are part of the data exported from Google Analytics 4. The user_pseudo_id is a unique identifier, created by Google Analytics 4, to track a user across various devices and sessions. Similarly, the device_id is a unique identifier, but it's assigned to a device by the operating system.
By activating device-based reporting identifiers, client IDs for websites become interconnected. This implies that if a user accesses your website from one device and later from another device, Google Analytics 4 can trace the user's activity across both devices.
Importantly, the user_pseudo_id is considered more privacy-conscious compared to the device_id. This is because the user_pseudo_id isn't connected to a specific device, hence it's unable to track a user's physical location.
I see.
I like the fact that user_pseudo_id can be exported from Google Analytics4 and is very privacy friendly.
Basically, I understood that by using user_pseudo_id, I can use BigQuery to analyze the logs.
Thanks for your answer.
Yes, it is possible to get device_id when exporting Google Analytics 4 data to BigQuery or Redshift.
However, this requires the activation of the Enhanced Measurement feature within your Google Analytics 4 property. Once Enhanced Measurement is activated, the device_id will be incorporated into the data exported to BigQuery or Redshift.
Here's a guide on how to activate Enhanced Measurement in Google Analytics 4:
After activating Enhanced Measurement, the device_id will be part of the data exported to BigQuery or Redshift. The device_id is a unique identifier assigned to each device that accesses your website or app, allowing you to track user activity across various sessions and devices.
Here's an illustration of how the device_id column might appear in a BigQuery table exported from Google Analytics 4:
device_id: 1234567890abcdef
The device_id is a 16-character hexadecimal string. It's crucial to remember that the device_id may not always be accessible. If a user has chosen to opt out of tracking or if the device lacks a unique identifier, the device_id will not be included in the data.
Thank you!
It is easy to understand. I will try it.
Please tell me additional information
If we enable device-based reporting identifiers, are the client IDs linked for websites?
Also, in BigQuery, is it something called user_pseudo_id?
Device-based reporting identifiers are a collection of identifiers that serve the purpose of tracking users across multiple devices and sessions. This set includes identifiers such as device_id, user_pseudo_id, and advertising_id. Client IDs, on the other hand, are distinct identifiers given to each user or device interacting with your website or application. These identifiers facilitate the tracking of a user or device across different sessions and devices.
In the context of BigQuery, both device_id and user_pseudo_id are part of the data exported from Google Analytics 4. The user_pseudo_id is a unique identifier, created by Google Analytics 4, to track a user across various devices and sessions. Similarly, the device_id is a unique identifier, but it's assigned to a device by the operating system.
By activating device-based reporting identifiers, client IDs for websites become interconnected. This implies that if a user accesses your website from one device and later from another device, Google Analytics 4 can trace the user's activity across both devices.
Importantly, the user_pseudo_id is considered more privacy-conscious compared to the device_id. This is because the user_pseudo_id isn't connected to a specific device, hence it's unable to track a user's physical location.
I see.
I like the fact that user_pseudo_id can be exported from Google Analytics4 and is very privacy friendly.
Basically, I understood that by using user_pseudo_id, I can use BigQuery to analyze the logs.
Thanks for your answer.