From f4da6f3d5a61bf379bcd093cc2c381bf18d7ac14 Mon Sep 17 00:00:00 2001 From: stevelamoree Date: Wed, 18 Sep 2024 17:09:57 -0700 Subject: [PATCH] Apply changes for b/348972742 Bug 348972742 title is "Incorrect reference to aggregate report account limit in batching strategy doc." In second paragraph of "Batch by advertiser" section, changed second sentence from "...hitting the aggregatable report report account limit for each batch" to read "...hitting the shared ID limit for each batch." --- docs/batching-strategies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/batching-strategies.md b/docs/batching-strategies.md index d6f1ed0d..2a1bced0 100644 --- a/docs/batching-strategies.md +++ b/docs/batching-strategies.md @@ -123,7 +123,7 @@ report accounting. Private Aggregation does not have an attribution_destination field, which is the advertiser. It is recommended to batch by advertiser, meaning to include reports belonging to a single advertiser in -the same batch, to avoid hitting the aggregatable report account limit for each batch. Advertiser is +the same batch, to avoid hitting the shared ID limit for each batch. Advertiser is a field considered in sharedID generation, so reports with the same advertiser could also have the same sharedID, which would require them to be in the same batch to avoid errors.