过滤 ID 指南
目前,借助汇总服务,您现在可以利用过滤 ID 以不同的节奏处理某些衡量结果。现在,您可以在汇总服务中创建作业时传递过滤 ID,如下所示:
POST createJob
Body: {
"job_parameters": {
"output_domain_blob_prefix": "domain/domain.avro",
"output_domain_bucket_name": "<data_bucket>",
"filtering_ids": [1, 3] // IDs to keep in the query
}
}
如需使用此过滤实现,建议您从衡量客户端 API(Attribution Reporting API 或 Private Aggregation API)开始,并传入过滤 ID。这些数据将传递给您部署的汇总服务,以便最终摘要报告返回预期的过滤结果。
如果您担心这会对预算产生什么影响,请放心,汇总报告账号预算只会用于过滤在 job_parameters
中为报告指定的 ID。这样,您就可以为同一报告指定不同的过滤 ID 来重新运行作业,而不会遇到预算耗尽错误。
以下流程展示了如何在 Private Aggregation API、Shared Storage API 中使用此功能,以及如何通过公共云中的 Aggregation Service 使用此功能。

此流程展示了如何使用 Attribution Reporting API 过滤 ID,并将其传递到公共云中的汇总服务。

如需进一步了解,请参阅 Attribution Reporting API 说明文档和 Private Aggregation API 说明文档,以及初始提案。
如需了解详情,请继续阅读 Attribution Reporting API 或 Private Aggregation API 部分。如需详细了解 createJob
和 getJob
端点,请参阅 Aggregation Service API 文档。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2024-12-05。
[null,null,["最后更新时间 (UTC):2024-12-05。"],[[["The Aggregation Service now allows processing certain measurements at different cadences using filtering IDs."],["Filtering IDs are specified during job creation to control which data is included in the aggregated reports."],["Budgets are only consumed for filtering IDs specified in the job parameters, enabling flexible report generation without budget exhaustion."],["This functionality is integrated with the Attribution Reporting API and Private Aggregation API for flexible data processing."],["Detailed documentation and explainers are available for further information on implementation and usage."]]],["The Aggregation Service now supports processing measurements at different cadences using filtering IDs. These IDs, passed during job creation, specify which data to include. Filtering IDs are initiated via the Attribution Reporting or Private Aggregation APIs. Budget is only consumed for specified filtering IDs, allowing job reruns with different IDs. This process is facilitated through the Private Aggregation and Shared Storage APIs, as well as with the Attribution Reporting API, flowing through to the Aggregation Service.\n"]]