Announcement: Chrome 112: New features in the Attribution Reporting API

[Maud Nalpas]

Hi API testers,

New features for the Attribution Reporting API have landed in Chrome 112, to address tester feedback we've received:

1. Support for multiple destinations.
2. Filter-based deduplication keys for aggregatable reports. (potentially breaking change)

Both of these features are available in Chrome 112—which is Beta at the time of this writing, and soon Stable.

Change #1: Support for multiple destinations

• Documentation
  • See Handbook > destination.
• What should you do?
  • If you use only one value as a destination, no change is required. This change is non-breaking and backwards-compatible.
  • If this is useful for your use case, consider using the new feature to list several sites as destinations.

Change #2: Filter-based deduplication keys for aggregatable reports (potentially breaking)
This change has already been announced. Review details here.

Questions/Feedback
If you experience any issue or have any implementation questions on these new features, please file an issue in our developer support repository.