Hey @sam8, yeah—that example you’re looking at is a recreation of the original report which has the same problem. I created it for that exact purpose, trying to isolate the problem—which it did.
Do you have any thoughts on how I could potentially progress resolution of this issue?
Gotcha. I’ve been looking for other instances of this coming up, and it does seem to be a persistent problem with GA4 specifically.
As far as I can tell, this has something to do with how GA4 enables data sampling when a data set exceeds a certain threshold. it goes from computing exact numbers to estimating.
It’s not something we can correct from the Looker Studio side, but I’ll see if there’s anything the GA4 team can do to address.
Thanks @sam8! Yeah, I assumed it had something to do with sampling but that’s a huge difference in numbers. Would be great if you were able to advocate for us with the GA4 team.