The differences between GA3 and GA4 and frequently asked questions are as follows.
Q1. When can I use GA4 data?
As the platform changes to GP One, data from the changed platform will be collected into GA4.
Starting on April 24, 2023 in the UK, GA4 data from each country will be available from the point of change to the GP One platform.
Before transferring to GP One, LG.com 5.0 data is collected into GA3 and can be checked in the GA3 account.
Q2. Is GA3 data transferred to GA4?
no. GA3 and GA4 have different data collection systems and different sites, making it difficult to aggregate the same data. Therefore, you must check the data in each account.
(GA3: LGE Performance, GA4: LGE All)
+
GA3 data can be stored and used in the Console until July 2024, and GA4 data can only be viewed up to 25 months in the Console, so it can only be viewed for up to 25 months. (Google policy)
Since RAW data is stored in Bigquery, if it is outside the Console viewing period, you can access the data directly by receiving data or receiving access rights through Bigquery. (Link insertion required: Go to the permission application guide page)
Q3. How can I compare GA4 and GA3 data?
We will also be adding GA3 tagging to GP One for key indicator (ATC, WTB, E-Commerce) data in the United Kingdom (UK) and Australia (AU). We plan to accumulate data for approximately 3 to 6 months, and provide an official guide to KPI data based on that data.
However, as the site changes, data differences that occur due to changes in journey and click elements, etc. must be taken into account. (There is no data correction due to different sites)
Check if there are any metrics that change in GA4
Users: No changes regarding users
Sessions: In the case of sessions 1) When midnight passes, a new session is created after midnight, but disappears in GA4. 2) In GA3, a new session is created when a New Campaign Parameter (UTM) is introduced, but in GA4, existing sessions are maintained.
> Conclusion: Some sessions are expected to decrease (Reference: Google GA4 session description page [GA4] About Analytics sessions - Analytics Help)
Hits: No changes regarding hits.
GA3 Event vs. GA4 Event
1) Event in GA3: Event Category-Event Action-Event label, there are 3
└ GA3 Event: Refer to LGE GA360 Event & Cusotm Dimension-v_3.1 file event list
2) Event in GA4: There is only Event Name and Event Parameter, and Event Parameter is dependent on Event Name.
└ GA4 Event: Refer to GP1_GA4_event_guide_v1.0 and GP1_GA4_Event&Custom Dimension file event list
GA4 Custom Dimension/Metric
GA3: CD-200, CM-200
GA4: CD-125, CM-125
Q4. How can I check the structure of GA4?
Events, goals, etc. set based on UK data from mid-June will be added to the current Confluence page.
You can easily check for updates by setting “Receive update notification” in the required information section. (You can receive email notifications by setting up Confluence for each individual.)
Q5. How has the Ecommerce event data seen in GA3 changed in GA4?
Ecommerce event data
Ecommerce event data has changed as shown in the table below, so please refer to the contents and check GA4 data.
+
In addition to the GA3 → GA4 renewal, the site structure has also changed with the renewal of LG.COM 5.0 to GP1, making it difficult to compare all GA event contents 1:1.
Instead, we will provide you with an on-screen guide explaining GA4's event rules and how to set up events to be collected within the GP1 site. Please refer to the changes from LG.COM GA3.
GA4 event organization criteria
GA4 events are divided into ecommerce and non-ecommerce events.
1) GA4 e-commerce event
- Values used as event category/action/label in GA3 are replaced with event name in GA4.
- Values used as event labels in GA3 can be used as event parameters attached to GA4 event names.
2) GA4 non-ecommerce event
- The RULE for non-ecommerce events is as follows, and exceptions may occur in some cases. If you are curious about the details, please refer to the GA4 training materials and GA4 event page documents.
3) GA4 event guide w. images
Please check the link above for a guide to the GA4 event screen based on the GP1 site screen.
* This information is based on the UK site as of July 17, 2023.
Q6. How are events collected when the add to cart button and checkout button are clicked?
As the site has been reorganized, there have also been changes to the event data collection method/structure.
If you want to see the add to cart button or checkout button click data, you can check the collected data according to the rules below.
|
Promotion&PBP page add to cart |
OBS - IN STOCK |
Parameter delivery_date_selected |
|
| 수집 이벤트: e-commerce | 수집 이벤트: non e-commerce | ||
| Selected date | add_to_cart | product_add_to_cart_click | delivery date (Y) |
| Unselected date | product_add_to_cart_click | delivery date (N) | |
|
PBP page checkout |
OBS - IN STOCK |
Parameter delivery_date_selected |
|
| 수집 이벤트: e-commerce | 수집 이벤트: non e-commerce | ||
| Selected date | add_to_cart | product_checkout_click | delivery date (Y) |
| Unselected date | product_checkout_click | delivery date (N) | |
* Need to distinguish between the begin_checkout event that occurs on the checkout page and the product_chekcout_click that occurs on the PBP page
* Checkout button non-e-commerce event name changed to product_checkout_click as of July 1, 23 (June 6 to June 30, 23: product_move_to_checkout)
Q7. The data collected in GA is different from the actual information. Is this resolved by modifying GA tagging?
LGE GA is not a form of data collection where all information is defined in GA.
In some cases, defined data is sent to GA through another route, so if GA data is different from actual data, it is necessary to check not only at GA but also at the place where the data is defined.
[UA]
q1) CD68 page purpose value is not classified by actual page type. (ex. Page purpose of A URL - PDP value is being collected, but the actual page type is a category page)
a1) CD68 is categorizing information for each page, and the content defined through CMS is transmitted to GA.
Therefore, the value can be modified by the DO team (CNX Manager Lee Do-young) and the LG.COM operator in each region, and when the modification is completed and reflected on the real server, normal data collection is possible in GA.
Q8. Is it necessary to apply for GA4 Access again?
Yes, I need it again. GA3 will be maintained for as long as the application period, and GA4 will be set in a different account, so please request permission by selecting the country where the new GA4 will be rolled out.
GA permission request) https://lge-ga-support.atlassian.net/servicedesk/customer/portals
Q9. How will the property options be set?
Most of the settings will be similar to GA3(UA), and we will share the settings after each country. Additionally, you may be curious about the use of Google Signal and Consent Mode, and we plan to discuss this with the Google tech team to ensure that there are as few differences as possible between Console and Bigquery and that it is easy to use for marketing purposes.
+ Additional update on June 30, 2023
Check attribute settings for each country: GA4 tagging: Policy and Process
2. Use of Consent Mode: We plan to operate the setting by applying it to some of the Rollout countries with GP1 on July 25, 2023. Discussions for those countries are ongoing.
Q10. Are there any changes to GA tagging methods for website analytics?
no. There is no difference in the basic analytics tagging method. The method of collecting data from the LG.com 5.0 site with GA3 and the method of collecting data from GP1 with GA4 are the same. Check tagging policy
However, there has been a change in the source of product-related information. Please check item 3 below for this information.
Additionally, there are UX changes to ATC and Checkout, so there may be changes in increase or decrease due to those changes.
As a data collection method through GTM Snippet, if the LG.com site takes a common header and creates a page, all page views are collected.
The contents of DataLayer, Attributes, and Global variables negotiated when building the site are not much different from the already inserted items, and the defined rules (e.g. name, connection link, etc. within the a tag of the ATC button component) are applied to the conditions defined on the page (e.g. : When an event action (button click) occurs, data is retrieved. This is a tagging method to appropriately respond to changes in site components, and was also applied in LG.com 5.0.
In PDP, product-related information (BU, product category information) was received from CMS by creating standardData/_dl (standardData: data worked for product categories in CMS, _dl: basic page information). However, after the platform was changed to GP1, data is received as an item called ga4_dataset by sending it from PIM to the information API.
*StandardData and _dl information are organized in ga4_dataset, which is the name for LGE of Global variables.
Q11. GA4 vs. GA3 How big is the data gap?
As a result of comparing GP1 data in GA3 and GA4 as of one month (30 days) after the launch of UK GP1, users increased by 6.7%, sessions increased by 2.7%, sessions per users -3.8%, and number of purchases increased by 0.9% in GA4 compared to GA3. It is confirmed with .
GP1 The overall traffic to the same site is slightly higher in GA4 than in GA3, but there is no significant difference.
In the case of users, there is currently an issue with login user aggregation due to an issue at the time of delivery of login information from Adobe to GA. (As of July 13, 23)
This issue is under review, and may currently affect users - aggregated after removing duplicate users when checked on an overall period basis. (Visit classification restrictions based on user login Y/N)
*This is data for one month after the launch of UK GP1, and the trend may change.
Check data: UK GA3, GA4 console
Data period: 6/6~7/5 (30 days) Check data
*6/6 excludes traffic from 00:00 to 6:00, which is the pre-opening time based on UK local time.