In Old version of Google Analytics Goal is present, But in New GA-4 We can see Event in Place of Goal.
An event in the context of website or app analytics refers to a specific interaction or occurrence that you can measure and track. Google Analytics, a popular web analytics tool, automatically collects certain events by default. However, you also have the ability to set up custom events on your website or app to collect additional data that is specific to your business goals and user interactions.
Types of events
1. Automatically Collected Events
Default Events Automatically Collected by Google Analytics During Website or App Setup.
———-
| Event | Automatically triggered… | Parameters |
| ad_click | when a user clicks an ad | ad_event_id |
| (app) | Publisher events coming from AdMob via the Google Mobile Ads SDK or Ad Manager via the Ad Manager integration | |
| This event is not exported to BigQuery. | ||
| ad_exposure | when at least one ad served by the Mobile Ads SDK is on screen | firebase_screen, firebase_screen_id, firebase_screen_class, exposure_time |
| (app) | This event does not appear in reports and is not exported to BigQuery. | |
| ad_impression | when a user sees an ad impression | ad_event_id, value |
| (app) | Publisher events coming from AdMob via the Google Mobile Ads SDK or Ad Manager via the Ad Manager integration | |
| This event is not exported to BigQuery. | ||
| ad_query | when an ad request is made by the Mobile Ads SDK | ad_event_id |
| (app) | This event does not appear in reports and is not exported to BigQuery. | |
| ad_reward | when a reward is granted by a rewarded ad served by the Mobile Ads SDK | ad_unit_code, reward_type, reward_value |
| (app) | ||
| adunit_exposure | when an ad unit served by the Mobile Ads SDK is on screen | firebase_screen, firebase_screen_id, firebase_screen_class, exposure_time |
| (app) | This event does not appear in reports and is not exported to BigQuery. | |
| app_clear_data | when the user resets/clears the app data, removing all settings and sign-in data | |
| (app) | Android only | |
| app_exception | when the app crashes or throws an exception | fatal, timestamp, engagement_time_msec |
| (app) | The event is sent when you integr | |
| app_remove | when an application package is removed (uninstalled) from an Android device | |
| (app) | Android only | |
| This event is different from the D | ||
| app_store_refund | when an in-app purchase is refunded by Google Play | product_id, value, currency, quantity |
| (app) | Android only | |
| This event is not exported to BigQuery. | ||
| app_store_ | when a paid subscription is cancelled in Google Play | product_id, price, value, currency, cancellation_reason |
| subscription_cancel | Android only | |
| (app) | Requires an initial subscription that was made on or after July 1, 2019. | |
| This event is not exported to BigQuery. | ||
| app_store_ | when a free-trial subscription is converted to a paid subscription | product_id, price, value, currency, quantity |
| subscription_convert | This event is set as a default conversion. | |
| (app) | Requires an initial subscription that was made on or after July 1, 2019. An initial free-trial subscription is logged as an in_app_purchase with the subscription parameter set to true. | |
| This event is not exported to BigQuery. | ||
| app_store_ | when a paid subscription is renewed | product_id, price, value, currency, quantity, renewal_count |
| subscription_renew | This event is set as a default conversion. | |
| (app) | Requires an initial subscription that was made on or after July 1, 2019. | |
| This event is not exported to BigQuery. | ||
| app_update | when the app is updated to a new version and launched again | previous_app_version |
| (app) | The previous app version id is passed as a parameter. | |
| This event is conceptually differe | ||
| click | each time a user clicks a link that leads away from the current domain | link_classes, link_domain, link_id, link_url, outbound (boolean) |
| (web) | By default, outbound click events | |
| The parameters populate the following dimensions: | ||
| Link classes (from link_classes) | ||
| Link domain (from link_domain) | ||
| Link ID (from link_id) | ||
| Link URL (from link_url) | ||
| Outbound (from outbound) | ||
| Collected by default via enhance | ||
| dynamic_link_app_open | when a user re-opens the app via a dynamic link | source, medium, campaign, link_id, accept_time |
| (app) | ||
| dynamic_link_ | when the app is updated to a new version and is opened via a dynamic link | source, medium, campaign, link_id, accept_time |
| app_update | Android only | |
| (app) | ||
| dynamic_link_ | when a user opens the app for the first time via a dynamic link | source, medium, campaign, link_id, accept_time |
| first_open | ||
| (app) | ||
| error | logged in place of an event that can’t be logged because it is invalid in some way | firebase_error, firebase_error_value |
| (app) | _err (firebase_error), _ev (firebase_error_value), and _el (firebase_error_length) parameters have additional information. | |
| This event does not appear in reports and is not exported to BigQuery. | ||
| file_download | when a user clicks a link leading to a file (with a common file extension) of the following types: | file_extension, file_name link_classes, link_id, link_text, link_url |
| (web) | document | |
| text | ||
| executable | ||
| presentation | ||
| compressed file | ||
| video | ||
| audio | ||
| This event is collected by default via enhanced measurement. See the file extensions that trigger the event | ||
| firebase_campaign | when the app is launched with campaign parameters | source, medium, campaign, term, content, gclid, aclid, cp1, anid, click_timestamp, campaign_info_source |
| (app) | This event does not appear in reports and is not exported to BigQuery. | |
| firebase_in_app_ | when a user takes action on a Firebase In-App Message | message_name, message_device_time, message_id |
| message_action | ||
| (app) | ||
| firebase_in_app_ | when a user dismisses a Firebase In-App Message | message_name, message_device_time, message_id |
| message_dismiss | ||
| (app) | ||
| firebase_in_app_ | when a user sees a Firebase In-App Message | message_name, message_device_time, message_id |
| message_impression | ||
| (app) | ||
| first_open | the first time a user launches an app after installing or re-installing it | previous_gmp_app_id, updated_with_analytics, previous_first_open_count, system_app, system_app_update, deferred_analytics_collection, reset_analytics_cause, engagement_time_msec |
| (app) | This event is not triggered when a user downloads the app onto a device, but instead when he or she first uses it. To see raw download numbers, look in Google Play Developer Console or in iTunesConnect. | |
| Supports measuring first_open conversions for users who accept Apple’s iOS 14 app-tracking prompt. | ||
| first_visit | the first time a user visits a website or launches an Android instant app with Analytics enabled | |
| (app, web) | ||
| form_start | the first time a user interacts with a form in a session | form_id, form_name, form_destination |
| (web) | Note: You can only use the para | |
| Collected by default via enhance | ||
| form_submit | when the user submits a form | form_id, form_name, form_destination, form_submit_text |
| (web) | Note: You can only use the para | |
| Collected by default via enhance | ||
| in_app_purchase | when a user completes an in-app purchase, including an initial subscription, that is processed by the Apple App Store or Google Play Store | product_id, price, value, currency, quantity, subscription, free_trial, introductory_price |
| (app) | The product ID, product name, currency, and quantity are passed as parameters. | |
| This event is triggered only by ver | ||
| Android: | ||
| To see in-app purchase data for | ||
| Note that Analytics doesn’t automatically measure paid-app purchase revenue. Also, your reported revenue in Google Analytics may differ from the values you see in the Google Play Developer Console. | ||
| Analytics ignores events that are | ||
| iOS: | ||
| Note that Analytics doesn’t automatically measure paid-app purchase revenue and refunds. | ||
| Analytics ignores events that are flagged as invalid or sandbox. | ||
| notification_dismiss | when a user dismisses a notification sent by Firebase Cloud Messaging (FCM) | message_name, message_time, message_device_time, message_id, topic, label, message_channel |
| (app) | Android only | |
| notification_foreground | when a notification sent by FCM is received while the app is in the foreground | message_name, message_time, message_device_time, message_id, topic, label, message_channel, message_type |
| (app) | ||
| notification_open | when a user opens a notification sent by FCM | message_name, message_time, message_device_time, message_id, topic, label, message_channel |
| (app) | ||
| notification_receive | when a notification sent by FCM is received by a device when the app is in the background | message_name, message_time, message_device_time, message_id, topic, label, message_channel, message_type |
| (app) | Android only | |
| os_update | when the device operating system is updated to a new version. The previous operating system version id is passed as a parameter | previous_os_version |
| (app) | ||
| page_view | each time the page loads or the browser history state is changed by the active site | page_location (page URL), page_referrer (previous page URL), engagement_time_msec |
| (web) | Collected by default via enhance | |
| screen_view | when a screen transition occurs and any of the following criteria are met: | firebase_screen, firebase_screen_class, firebase_screen_id, firebase_previous_screen, firebase_previous_class, firebase_previous_id, engagement_time_msec |
| (app) | No screen was previously set | |
| The new screen name differs from the previous screen name | ||
| The new screen-class name differs from the previous screen-class name | ||
| The new screen id differs from the previous screen id | ||
| scroll | the first time a user reaches the bottom of each page (i.e., when a 90% vertical depth becomes visible) | engagement_time_msec |
| (web) | Collected by default via enhance | |
| session_start | when a user engages the app or website | |
| (app, web) | A session ID and session number | |
| user_engagement | when the app is in the foreground or webpage is in focus for at least one second. Learn more | engagement_time_msec |
| (app, web) | ||
| video_complete | when the video ends | video_current_time, video_duration, video_percent, video_provider, video_title, video_url, visible (boolean) |
| (web) | For embedded YouTube videos t | |
| Collected by default via enhance | ||
| video_progress | when the video progresses past 10%, 25%, 50%, and 75% duration time | video_current_time, video_duration, video_percent, video_provider, video_title, video_url, visible (boolean) |
| (web) | For embedded YouTube videos t | |
| Collected by default via enhance | ||
| video_start | when the video starts playing | video_current_time, video_duration, video_percent, video_provider, video_title, video_url, visible (boolean) |
| (web) | For embedded YouTube videos t | |
| Collected by default via enhance | ||
| view_search_results | each time a user performs a site search, indicated by the presence of a URL query parameter | search_term, optionally ‘q_<additional key=””>’ (where <additional key=””> matches an additional query parameter you specify to be collected under advanced settings) |
| (web) | Collected by default via enhance | Note: This event only sends the unique_search_term parameter when it has a value of 1 (i.e. when the string is unique to that session). |
Source URL: https://support.google.com/analytics/answer/9234069?sjid=15202470368136962457-AP
2. Enhanced event measurement
Enhanced measurement in Google Analytics allows you to track user interactions with your content by enabling specific options (events) directly within the Google Analytics interface. This feature eliminates the need for manual code changes on your website or app. Once you enable these options for a web data stream, your Google Analytics tag will immediately start sending events, capturing valuable user engagement data.
3. Recommended events
Predefined events are events that you can implement on your website or app, which come with predefined names and parameters. These events allow you to leverage existing and future reporting capabilities in your analytics tool.
For All Type of Properties
——-
| Event | Trigger when |
| ad_impression | a user sees an ad impression, for app only |
| earn_virtual_currency | a user earns virtual currency (coins, gems, tokens, etc.) |
| join_group | a user joins a group to measure the popularity of each group |
| login | a user logs in |
| purchase | a user completes a purchase |
| refund | a user receives a refund |
| search | a user searches your content |
| select_content | a user selects content |
| share | a user shares content |
| sign_up | a user signs up to measure the popularity of each sign-up method |
| spend_virtual_currency | a user spends virtual currency (coins, gems, tokens, etc.) |
| tutorial_begin | a user begins a tutorial |
| tutorial_complete | a user completes a tutorial |
Source URL: https://support.google.com/analytics/answer/9267735
For Online Type Sales
This type are useful for retail, education, ecommerce, real estate, and travel
| Event | Trigger when |
| add_payment_info | a user submits their payment information |
| add_shipping_info | a user submits their shipping information |
| add_to_cart | a user adds items to cart |
| add_to_wishlist | a user adds items to a wishlist |
| begin_checkout | a user begins checkout |
| generate_lead | a user submits a form or a request for information |
| purchase | a user completes a purchase |
| refund | a user receives a refund |
| remove_from_cart | a user removes items from a cart |
| select_item | a user selects an item from a list |
| select_promotion | a user selects a promotion |
| view_cart | a user views their cart |
| view_item | a user views an item |
| view_item_list | a user sees a list of items/offerings |
| view_promotion | a user sees a promotion |
Source URL: https://support.google.com/analytics/answer/9267735
For Games Type
————
| Event | Trigger when |
| earn_virtual_currency | a user earns virtual currency (coins, gems, tokens, etc.) |
| join_group | a user joins a group to measure the popularity of each group |
| level_end | a user completes a level in the game |
| level_start | a user starts a new level in the game |
| level_up | a user levels-up in the game |
| post_score | a user posts their score |
| select_content | a user selects content |
| spend_virtual_currency | a user spends virtual currency (coins, gems, tokens, etc.) |
| tutorial_begin | a user begins a tutorial |
| tutorial_complete | a user completes a tutorial |
| unlock_achievement | a user unlocks an achievement |
Source URL: https://support.google.com/analytics/answer/9267735
4. Custom Events
Custom events refer to events that you define based on your specific needs and requirements. They are created when no other predefined events adequately capture the interactions or occurrences you want to track. Unlike predefined events, custom events do not appear in most standard reports by default.
We can set Custom Event with help of below methods.
Methods to Set up a custom event
Set up your custom event using one of the following options:
- The Google tag (website)
- Google Tag Manager (website)
- Firebase (apps)
