Google Analytics 4 DebugView FAQ Summary(2023) | Haran

Google Analytics 4 DebugView FAQ Summary(2023)

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:

Google Analytics 4  DebugView FAQ Summary(2023)

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:

Google Analytics 4  DebugView FAQ Summary(2023)

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?

Google Analytics 4  DebugView FAQ Summary(2023)

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.

If you don't understand, You can leave a comment below.
Like (0)
Post my comment
Cancel comment
Expression Texture Bold Strikethrough Center Italic Sign in

Hi, you need to fill in your nickname and email!

  • Nickname (required)
  • Email (required)
  • Website