demo · v132
From bucket pick to encrypted report
Pick a named bucket on the trigger side and watch the field flow: trigger registration to histogram contribution to encrypted aggregatable report. The new named_budget field shows up at every stage so an ad-tech operator can debug overflows without breaking the encryption seal.
1 / trigger json
trigger registration
click "Synthesise report"
2 / histogram contribution
contribution
.
3 / encrypted payload
aggregatable report
.flattened report fields
attribution_destinationhttps://shop.example
source_registration_time—
named_budget v132—
aggregation_coordinator_originhttps://publickeyservice.msmt.gcp.privacysandboxservices.com
debug_cleartext_payload—
shared_info.apiattribution-reporting
scheduled_report_time—
why an operator cares
The named_budget field on the contribution and on the report means the bucket label travels with the data all the way to the encrypted payload. When an aggregation service operator decrypts and sees the budget tag, they know exactly which vertical owned the contribution — without that field they would have to reverse-engineer the bucket from the 128-bit aggregation key.