FYI: Change to source_registration_time in Aggregatable Reports

[Akash Nadan]

Hi All,

We just want to flag that starting in Chrome release M129 and around September 20th, 2024 for Android, there was a change to “source_registration_time” behavior for Aggregatable Reports.

What was the change?

If the “aggregatable_source_registration_time” field is set to “exclude” (i.e. this is the default behavior) as part of your trigger registrations then it will be omitted from the “shared_info” object in the Aggregatable report. Previously, if “aggregatable_source_registration_time” was set to “exclude”, then the “source_registration_time” would be set to “0” in the “shared_info” object of the report.

Additional details can be found here.

What does this mean for you?

If you set “aggregatable_source_registration_time” to “exclude” or if you do not set this field in your trigger registrations, then you may want to check that your endpoint where you receive Aggregatable reports is set up to properly process Aggregatable reports that no longer contain “source_registration_time” in the “shared_info” object.

If you want “source_registration_time” to be included in the “shared_info” object of your Aggregatable reports, then you will need to make sure your trigger registrations set “aggregatable_source_registration_time” to “include”.

No Aggregation Service changes or updates are needed for this Aggregatable report change.

If you have any questions or comments, reply to this post or open an issue in the Privacy Sandbox Dev Support repository on GitHub.

Thanks,

Akash