Updated: December 19, 2025
If you’ve set up the BigQuery export from GA4 or Firebase and noticed that data is missing — or the numbers don’t match what you see in GA4 — you’re not alone. I’ve seen more and more reports about this since 2024, especially with streaming exports.
If my guess was correct, you have come to the right place. But I’ll be honest with you from the start: the answer here isn’t satisfying.
The Problem: Missing Data in BigQuery
Here’s the scenario: you’ve linked your GA4 property to BigQuery, the export is running, but when you query the data, significant chunks are missing. You check your row limits, your billing is set up, the expected events are supposed to be exported — but the numbers still don’t add up.
Sound familiar?
I’ve seen community posts, bug reports on Google’s Issue Tracker, and discussions across forums all pointing to the same frustration. Multiple projects, multiple users, same pattern. It feels like a widespread bug.
What Google Said
So I dug into the Issue Tracker responses. Here’s what Google’s Product Engineer Team had to say:
Unfortunately, we can’t fix the issue at this time and apologize for any inconvenience.
Product Engineer Team Comments: Issues like this are often specific and not part of a wider bug. Each case needs individual troubleshooting, so we recommend checking row limits, missing billing details, and ensuring expected events are exported.
If you have any further questions or need assistance with any other matter, please don’t hesitate to create a new issue on the Issue Tracker. I will now proceed to close this issue.
Let me translate that for you: “We can’t find a pattern. We can’t reproduce it. We’re closing the ticket.”
Long story short — Google’s official position is that this is an isolated case, the cause couldn’t be identified, and therefore it can’t be fixed. Whether you believe it’s actually isolated or not, that’s where things stand as of now.
What You Can Try
Given that Google has essentially closed the door on a formal fix, here’s what I’d suggest:
- Check the basics first — verify your row limits aren’t being hit, confirm your billing details are correct, and make sure the events you’re expecting are actually being sent (check the DebugView in GA4 first).
- Try relinking to a new BigQuery project — I’ve seen some cases where creating a fresh BigQuery project and relinking the GA4 export to it resolved the discrepancies. It’s not guaranteed, but it’s worth a shot if you’re stuck.
- Compare with GA4 directly — if the data is in GA4 but not in BigQuery, at least you know your tracking is working. The issue is on the export side, not collection.
I will not cover all possible scenarios here because, honestly, I just couldn’t come up with them. There are still many unknowns with this issue.
Final Words
This is one of those situations where you’d expect better from Google, especially for a paid product like BigQuery. Unfortunately, the official response has been to close the issue without a fix, leaving users to troubleshoot on their own.