Repeated Event
Recently (March 24, 2023), many people will encounter repeated events when debugging in DebugView, such as:
This is actually a bug, and many users have encountered it, waiting for the official fix.
Further reading: Why are there many repeated events in GA4 DebugView?
Price Is Wrong
If you use DebugView to debug e-commerce tracking, you may notice that the price parameter is incorrect, the price you send is 3.15:
The DataLayer.push is right:
dataLayer.push({
event: "add_to_cart",
ecommerce: {
items: [
{
item_list_name: "Product details",
item_list_id: "Product details",
item_name: "CASEME 013 Series PU Leather Mobile Phone Shell with Wallet Stand for iPhone " +
"8/7/SE (2020)/SE (2022) 4.7 inch - Black",
item_id: "101115653A",
price: 3.15,
quantity: 1
}
]
},
gtm.uniqueEventId: 596
})
but it shows 3150000 in DebugView:
Picture Source：measure
Automatically multiplied by 100000, this is a bug in DebugView, but it will not affect the data in the e-commerce report.
Multiple Debug Devices
Some people have recently reported: Why are there so many Debug Devices in DebugView?
The reason is that you publish the debug_mode setting in GA4 tags to PROD.
For details, please see: Why are there so many Debug Devices in DebugView?
No debug data
If DebugView has no data during debugging, it may be caused by the following situations:
- Data delay, there will be a data delay of several seconds to tens of seconds, depending on the network.
- Developer traffic is excluded by data filters.
- Browser plug-ins: Browser plug-ins block Developer traffic, or affect the interface of DebugView.
UTM Parameters are Missing on the Second Page
Some people may notice when using DebugView, such as https://www.haranhuang.com?utm_source=admin of the landing page
- The first page_view event has the source parameter admin
- The second page_view event has no source parameter
Some people worry about whether the source parameter is lost.
In fact, no, UTM is at the session level. When it comes in, the UTM parameters are bound to the session ID, and subsequent events will be bound to the session ID, so it is opened by default.
The session ID is in Cookie _ga_<container-id>, if you are interested, you can read: In-depth Understanding Session in Google Analytics 4
