In the Explore tab of Pulse Results, you can use user dimensions to drill down and explore results. However, the user properties you can segment on are only derived from exposure events, not custom events. Any overrides that are used to force a user into the test will be ignored from pulse results. If you only have override userIds in the results, nothing will show up in the pulse filters. If you're having trouble finding a specific user property, it might be due to these reasons.
It's also important to note that the availability of User Dimensions can vary depending on the gate/experiment you’re querying on. Some entities have User Dimensions available, some don’t based on whether there are exposures or not.
Regarding the issue of error ranges for Daily Topline Impact
and Daily Projected Launch Impact
not populating, this was due to a bug that occurred during our internal migration of infrastructure and data. We have fixed this bug and it affected certain metric types. All new custom queries should not have a problem. For some metrics, the topline impact could have a 0 as the CI, because all users can have the value of 1 if the metric is an indicator. However, we'll do an audit to make sure the calculation is consistent with our scorecard.