The event fields contain information that uniquely identifies an event. Most of these values are automatically collected by Google Analytics, including many of the values in the event_params field.
Field Name | Data Type | Description | Example Values |
---|---|---|---|
event_date | STRING | The date when the event was logged – see Working with dates and times for more info | 20230715 |
event_timestamp | INTEGER | The time (in microseconds, UTC) when the event was logged – see Working with dates and times for more info | 1690660217183263 |
event_name | STRING | The name of the event – see Querying events for more info | page_view click purchase |
event_params | RECORD | Event parameter keys and values associated with the event – see Event parameters for more info | See table below |
event_previous_timestamp | INTEGER | The time (in microseconds, UTC) when the event was previously logged. | 1690660217183263 |
event_value_in_usd | FLOAT | The event’s ‘value’ parameter (converted to USD) | 25.00 |
event_bundle_sequence_id | INTEGER | The sequential ID of the bundle in which these events were uploaded | 65 |
event_server_timestamp_offset | INTEGER | Timestamp offset between collection time and upload time (in micros) | 1012891 |
event_params
Listed below are some of the common keys you may find in the event_params field. However, it’s important to note that this list is not exhaustive, and your site or app’s specific implementation may introduce additional keys to capture relevant data.
Event Key | Data Type | Description | Example Values |
---|---|---|---|
page_location | STRING | URL of the web page where the event was collected | https://mysite.com/ https://mysite.com/account/ |
page_title | STRING | The title attribute of the web page where the event was collected | Home Mysite – Account |
page_referrer | STRING | The URL of the page the user was on prior to this event | https://www.google.com/ |
firebase_screen | STRING | The name of the app screen where the event was collected | home account |
firebase_screen_class | STRING | The name of the app class where the event was collected | MainActivity AuthenticationActivity |
ga_session_id | INTEGER | A unique identifier for the given users’ session | 1690585146 |
ga_session_number | INTEGER | A counter of the given users’ sessions on the site or app | 1, 2, 3, etc. |
session_engaged | STRING | An indicator of whether the given user’s session is classed as engaged or not | 1 or 0 |
engagement_time_msec | INTEGER | A measure of how long the user has been active on the site | 10876 |
link_url | STRING | The URL of the link clicked | https://www.facebook.com/mypage |
link_domain | STRING | The domain of the link clicked | facebook.com |
outbound | STRING | An indicator of whether the link directs to an external site or not | true or false |
Sample event fields query
Select the event fields you need from the below query.
For more information on how to extract specific values from the event_params field check out the tutorial Extract GA4 event parameters in BigQuery.
SELECT
event_date,
event_timestamp,
event_name,
event_params,
event_previous_timestamp,
event_value_in_usd,
event_bundle_sequence_id,
event_server_timestamp_offset
FROM `<project>.<dataset>.<table>`
Important Note: Make sure you replace the placeholders within the WHERE clause with the specific values for the table you are working with. For example, if you want to extract data for January 31st 2021 from the e-commerce sample dataset, use the following values:
- <project> should be replaced with bigquery-public-data
- <dataset> should be replaced with ga4_obfuscated_sample_ecommerce
- <table> should be replaced with events_20210131
Ensure that you substitute these placeholders with your actual project, dataset, and table names when executing the queries.
For details and examples of other fields & dimensions see: