Price is Wrong in GA4 DebugView ?

Update time: March 28, 2026

If you’ve ever set up ecommerce tracking in GA4 and opened DebugView to validate it, you might have noticed something that looks very wrong. You send a price of 3.15 in your dataLayer, but DebugView shows 3150000.

At first glance, it looks like GA4 multiplied your price by one million. Your first thought is probably: “What did I break in my implementation?”

Don’t worry — your implementation is fine. This is a quirk of how GA4 displays certain values in DebugView, not a sign that your data is corrupted.

The problem: What You See in DebugView

For example, the  price  is 3.15:

Let’s say your dataLayer push looks perfectly correct:

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
})

You go to DebugView in GA4 to confirm the data is flowing, and this is what you see: price: 3150000

Picture Source：measure

Wait, what? That’s not 3.15. That’s over three million.

Your dataLayer is correct. Your GTM tag is correct. But DebugView is showing you a number that looks nothing like what you sent.

The reason: GA4’s internal scaling

Here’s what’s happening under the hood.

GA4 converts certain decimal-based values — like prices, revenue, and other monetary amounts — into scaled integer formats during internal processing. This improves storage efficiency and processing performance.

So when you send 3.15, GA4 stores it as 3150000 internally. If you’re thinking “that’s a weird way to store a price”, well, it’s actually quite common in systems that need to avoid floating-point precision issues.

Here’s the key insight:

DebugView sometimes exposes these raw internal values instead of the final formatted values that appear in standard GA4 reports. That’s what makes it look like something went wrong — but it’s just an internal representation that you’re not supposed to see directly.

The solution: do nothing (seriously)

In most cases, no action is required.

Although DebugView may display the processed internal value, the data stored and displayed in standard Ecommerce reports remains correct. Your revenue, item price, and purchase metrics in GA4 reports will still use the proper decimal values.

So if you’re looking at DebugView and see 3150000, but your standard ecommerce reports show 3.15, everything is working as intended. DebugView is just showing you the raw internal value that GA4 uses for processing, not the final value that ends up in your reports.

That said, if you’re using DebugView to verify raw parameter values — for example, if you’re passing custom monetary parameters that aren’t standard ecommerce fields — you might see similar scaling behavior. In those cases, the value in your standard reports depends on how you’ve configured the corresponding custom metric

Final Words

Seeing 3150000 when you sent 3.15 is the kind of thing that makes you doubt your entire tracking setup. I’ve been there. But once you know it’s just GA4’s internal scaling and not a bug in your implementation, it becomes one of those “huh, good to know” moments.

Have you run into other strange values in DebugView that turned out to be nothing? Drop a comment and share your experience.