Firebase技术问题：BigQuery是否会遗漏未携带货币参数的购买事件数据？

Hi there! Let's dig into your Android-side mystery since you've already nailed down the iOS problem (great catch on the string-type revenue parameter!). Here's how to tackle this:

First, Does BigQuery Skip Purchase Events Without a Currency Parameter? #

Short answer: Probably not, but there are a few caveats to verify:

• GA4's BigQuery integration typically captures all events sent to GA4, even those missing required parameters. If an Android purchase event doesn't include the currency parameter, it won't disappear from BigQuery—instead, you won't see a currency entry in the event_params array for that event row.
• Double-check GA4's event filtering rules: Head to your GA4 property > Data Streams > Select your Android stream > Event Settings > Look for any filters that might discard events missing the currency parameter. If such a filter exists, those events won't make it to BigQuery at all.
• Verify your BigQuery export scope: Ensure you're exporting the full date range and all user/device segments. Partial exports or filtered views can sometimes make it seem like events are missing when they're just not in the subset you're querying.

Step-by-Step Troubleshooting for Android's Unset Currency Parameter #

Since you don't see string-type revenue or missing currency records in BigQuery, let's trace the issue back to the source:

1. Audit Your Android Event Code #

• Double-check that when logging the purchase event, you're explicitly setting the currency parameter using the official Firebase Analytics constant. For example:

  FirebaseAnalytics.getInstance(context).logEvent(FirebaseAnalytics.Event.PURCHASE) {
      param(FirebaseAnalytics.Param.CURRENCY, "USD")
      param(FirebaseAnalytics.Param.REVENUE, 29.99)
  }
  

  If you're using a custom parameter name instead of the official currency param, GA4 won't recognize it as the default currency field, leading to "未设置" in Data Studio.
• Add debug logs in your Android app to print the exact parameters and their types when sending the purchase event. This will confirm if currency is being set at all, and if its value is a valid ISO 4217 code.

2. Use Firebase DebugView to Validate Events #

• Connect your Android device to Firebase DebugView, trigger a purchase, and inspect the event in real time. Look for the currency parameter in the event details:
  • If it's missing entirely, the issue is definitely in your client code.
  • If it's present but has an invalid value (like an empty string), that's why Data Studio shows "未设置".

3. Check GA4 Real-Time Reports #

• In your GA4 property, go to Realtime > Trigger a purchase from an Android device. Look for the purchase event in the real-time feed and check the currency value. If it shows "未设置" here too, the problem is upstream (client-side or GA4 processing), not BigQuery. If it shows correctly here but not in BigQuery, wait a few hours—BigQuery exports can have delays up to 24 hours.

4. Verify GA4 Parameter Configuration #

• Head to GA4 > Custom Definitions > Custom Parameters. Ensure that currency is set as an Event Parameter with the correct data type (string). If it's not registered here, GA4 might not map it properly to BigQuery.

5. Check for Edge Cases #

• Are there any user segments or device types where the Android purchase event is sent without currency? For example, maybe users in a specific region or on older Android versions aren't triggering the parameter correctly. Narrow down your BigQuery queries to filter by device.mobile_brand_name or geo.country to see if the issue is isolated.

Final Notes #

Start with DebugView and client code audits—those are usually the fastest ways to spot missing or misconfigured parameters. If everything checks out client-side, circle back to GA4's event filters and BigQuery export settings to rule out data pipeline issues.

内容的提问来源于stack exchange，提问作者Ezequiel Tucuman