Unable to aggregate ratio metrics in the request. Please select another metric.
此错误表示您已要求 Looker Studio 对已汇总的比率指标执行某些操作，但 Looker Studio 无法执行这些操作。例如，您已将基于计算字段的过滤条件应用于包含比率指标的图表。
解决方法是在图表中选择非比率字段（例如，使用展示次数而非点击率），或移除或更改过滤条件。
深入了解
比率指标显示两个或更多个值的相对大小。例如，Google Ads 指标“点击率”(CTR) 是指广告获得的点击次数除以广告展示次数所得的比值。在 Google Analytics 中，感兴趣的会话占比是指在您的网站或移动应用中感兴趣的会话所占的百分比，而跳出率则与感兴趣的会话占比相反。“跳出率”是指非感兴趣的会话所占的百分比。
在 Looker Studio 中，如果您以需要产品重新计算比率的方式过滤包含比率指标的图表，则会收到之前的错误。
以下 3 点有助于您了解此问题：
来自 Google Analytics、Google Ads、YouTube 和 Google Marketing Platform 产品等数据集的数据在到达 Looker Studio 时已经汇总。例如，当 Looker Studio 请求 Google Ads 指标（例如点击率）时，系统会将数据处理为适当的汇总类型。
鉴于上述原因，计算字段函数会在汇总后应用于数据。您无法（通常也不需要）返回原始数据，查看该指标的每个唯一实例。例如，如果您尝试在 Google Ads 数据源中使用公式 SUM( Impressions ) 创建计算字段，则会收到以下错误：
Re-aggregating metrics is not supported。
这是因为“展示次数”已汇总（并且其汇总类型“自动”无法更改）。
为了保持一致性，Looker Studio 中的所有计算字段函数都可以与所有数据源类型搭配使用，即使底层系统不原生支持该函数也是如此。例如，您可以使用 CONCAT 函数联接任何数据源中的多个值，即使底层系统没有自己的 CONCAT 函数也是如此。Looker Studio 会请求数据并自行执行串联操作，而不是将 CONCAT 函数“推送”到底层系统。
汇总失败示例
那么，这一切与 Unable to aggregate ratio metrics 错误有何关系？下面的示例深入探讨了 CONCAT 示例，以帮助您了解相关内容。
假设您在 Google Ads 数据源中使用以下公式创建了一个名为“广告系列：点击类型”的计算字段：
CONCAT(Campaign, " : ", Click Type)
Looker Studio 会分别针对广告系列和点击类型发出查询，然后执行串联操作。结果会分组，因此不会出现重复记录。
该过滤条件会要求 Looker Studio 包含 Campaign : Click Type 返回的每个记录（如果该记录包含字符串 Headline）。该字段是两个维度的串联；为了满足此请求，Looker Studio 必须重新提取这些维度，然后应用过滤条件。问题在于表格中存在比率指标 CTR。Google Ads 比率指标会在 Looker Studio 请求之前计算出来。Looker Studio 无法访问原始数据，也无法针对在串联字段中仅包含字符串 Headline 的记录重新计算新比率。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-03。"],[],[],null,["# What does the "Unable to aggregate ratio metrics" error mean?\n\nAt a glance\n-----------\n\nHave you seen this error message?\n\n`Unable to aggregate ratio metrics in the request. Please select another metric.`\n\nThis error means that you've asked Looker Studio to do something with an already [aggregated](/looker/docs/studio/aggregation) ratio metric that it can't do. For example, you've applied a filter based on a calculated field to a chart that contains a ratio metric.\n\nThe solution is to select a non-ratio field in the chart (for example, use **Impressions** instead of **CTR**), or remove or change the filter.\n\nIn depth\n--------\n\nRatio metrics show the relative sizes of two or more values. For example, the Google Ads metric, **Clickthrough rate** ([CTR](https://support.google.com/google-ads/answer/2615875)), is the number of clicks that your ad receives divided by the number of times your ad is shown. In Google Analytics, [**Engagement rate**](https://support.google.com/analytics/answer/12195621) is the percentage of engaged sessions on your website or mobile app, while [**Bounce rate**](https://support.google.com/analytics/answer/12195621) is the opposite of the engagement rate. The bounce rate is the percentage of sessions that were not engaged.\n\nIn Looker Studio, you get the prior error when you filter a chart that includes ratio metrics in a way that requires the product to recalculate the ratios.\n\n### Here are 3 things to help you understand this issue:\n\n1. Data from data sets such as Google Analytics, Google Ads, YouTube, and Google Marketing Platforms products is already aggregated by the time it gets to Looker Studio. For example, when Looker Studio requests a Google Ads metric such as **CTR** (click-through rate), the data is already processed into the appropriate aggregation type.\n\n2. Because of the previous point, calculated field functions are applied to your data post-aggregation. It's not possible (nor would it generally make sense) to go back into the raw data and look at every unique instance of that metric. For example, if you try to create a calculated field with the formula `SUM( `\u003cvar translate=\"no\"\u003eImpressions\u003c/var\u003e` )` in a Google Ads data source, you'll get the following error:\n\n `Re-aggregating metrics is not supported`.\n\n That's because **Impressions** is already aggregated (and its aggregation type, **Auto**, can't be changed).\n | **Note:** This isn't necessarily the case with data sources such as Google Sheets, MySQL, or BigQuery, where you are able to send non-aggregated data to Looker Studio. For example, if you had raw impression data in a Sheet, you could use functions like the SUM function to add it all up and the AVG function to generate the average.\n3. For consistency, all calculated field functions in Looker Studio are available for use with all data source types, even if the underlying system doesn't natively support that function. For example, you can use the CONCAT function to join multiple values in any data source, even if the underlying system doesn't have a CONCAT function of its own. Instead of \"pushing down\" the CONCAT function to the underlying system, Looker Studio requests the data and performs the concatenation itself.\n\nAggregation failure example\n---------------------------\n\nSo what does all that have to do with the `Unable to aggregate ratio metrics` error? This example goes a little deeper with the CONCAT example to help you find out.\n\nSuppose you create a calculated field called **Campaign : Click Type** in a Google Ads data source, using the following formula:\n\n`CONCAT(Campaign, \" : \", Click Type)`\n\nLooker Studio issues queries for **Campaign** and **Click Type** individually, and then performs the concatenation. The results are grouped, so there is no duplication of records.\n\nYou can now use that concatenated field in your charts, and the metrics you include are aggregated properly. For example, we could use **Campaign : Click Type** as the dimension and **CTR** as the ratio metric in a table:\n\nBut now, suppose you apply a filter to show only those records where the value of **Click Type** is `Headline`:\n\nThis will break the chart:\n\nWhy it breaks\n-------------\n\nThe filter asks Looker Studio to include each record returned by the **Campaign : Click Type** if it contains the string `Headline`. That field is a concatenation of two dimensions; to fulfill this request, Looker Studio has to refetch those dimensions, and then apply the filter. The problem is the presence in the table of the ratio metric, **CTR** . Google Ads ratio metrics are computed before Looker Studio requests them. Looker Studio has no way to access the raw data and recompute the new ratios for the records that contain only the string `Headline` in the concatenated field.\n\nThe solution\n------------\n\nThe solution in cases like this depends on the data you are trying to show. In this example, you could either replace the **CTR** metric with a non-ratio metric, such as **Impressions** . Or, instead of filtering on the concatenated **Campaign : Click Type** field, put the filter on the standard **Click Type** field, which would achieve the same result.\n\nThe chart now works:\n\nRelated resources\n-----------------\n\n- [Google Analytics Dimensions \\& Metrics Explorer](https://developers.google.com/analytics/devguides/reporting/core/dimsmets)\n- [Google Ads Glossary](/google-ads/topic/3121777)"]]
