----------------- Hi, I'm using the GrowthBook experiment platform with a fact table–based data source (BigQuery). When I define N metrics on top of the fact table, GrowthBook is able to compute all metrics with a single underlying query, which is very efficient. However, when I view Experiment → Results and apply a segment, GrowthBook stops using the single fact-table query and instead executes *N separate queries*—one for each metric. This makes the query execution significantly less efficient and increases BigQuery cost. Is this expected behavior? And is there any way to preserve the single-query optimization when segmentation is applied?

@helpful-application-7107 can you advise?

Is there any update on this? @fresh-football-47124 @helpful-application-7107

@helpful-application-7107?

This issue was related to fact table optimizaiton. With enterprise plan this issue is not repeated. Thanks.

Hi there, sorry for the delay. Yes it is an enterprise only feature. Please let me know if you have further questions!