Firebase Analytics新UI下移动端事件item_id、item_name等详情30天数据无法显示的问题咨询

I’ve run into similar head-scratchers with Firebase Analytics before, so let’s break down the most likely causes and fixes for your problem: where select_content event parameters like item_id and item_name show up clearly in the 30-minute real-time view, but vanish when you switch to the 30-day historical view.

Common Fixes to Try #

• Wait for Data Processing Completion
  Firebase handles real-time vs historical data differently. The 30-minute view pulls raw, near-instant events, but the 30-day view relies on aggregated datasets that take time to build. If you’re checking the 30-day view right after seeing the event in real-time, it might not have propagated into the historical tables yet. Give it 24-48 hours—this is the most common "fix" for this kind of discrepancy.

• Check Parameter Retention Settings
  Head over to your Firebase Console > Analytics > Events > Find the select_content event > Click "Manage Parameters". Make sure item_id, item_name, and content_type are set to Retain. If someone accidentally switched them to "Do not retain", those parameters won’t be included in historical aggregated data, even if recent real-time logs show them.

• Validate Parameter Values
  Double-check the dynamic values you’re logging. For example, name + ":" + heading might sometimes produce extremely long strings or contain edge-case characters that break aggregation (though Firebase is pretty forgiving, odd values can slip through). Try logging a static test value like new Parameter(ParameterName.ItemId, "test:static-heading") and see if that shows up in the 30-day view after processing. Also, ensure name, heading, and url are never null when this event fires—null values can cause parameters to be dropped from aggregated datasets entirely.

• Check for Accidental Filters in the Console
  It sounds silly, but I’ve done this more than once: when viewing the 30-day event details, make sure you haven’t applied a filter that’s hiding your parameters. Click the "Filter" button at the top of the event details page and confirm there are no active filters targeting item_id or item_name that might be excluding the data you want to see.

• Verify Firebase Service Status
  If this started happening out of nowhere, there might be a temporary issue with Firebase’s analytics processing. Check Firebase’s official status dashboard for any reported outages or delays affecting historical data aggregation. These issues usually resolve themselves quickly, but it’s worth confirming you’re not hitting a backend glitch.

Quick Code Check #

Your logging code looks solid at a glance, but just to be thorough, add some debug logs to confirm all parameters are being populated correctly when the event fires. For example:

Debug.WriteLine($"Logging select_content: item_id={name + ":" + heading}, item_name={url}");
CrossFirebaseAnalytics.Current.LogEvent(EventName.SelectContent, 
  new Parameter(ParameterName.ContentType, "abc"), 
  new Parameter(ParameterName.ItemId, name + ":" + heading), 
  new Parameter(ParameterName.ItemName, url));

This will help you rule out cases where dynamic values are missing or invalid at the time of logging.

内容的提问来源于stack exchange，提问作者Sagar S