Consider migration from origin to site enrollment for Aggregation service: Feedback requested about aggregation-service HOT 4 OPEN

Note that adtechs will still be able to determine which origins are processed and consume budget based on valid origins included in their reports for each batch. Specifying the site or a list of origins in createJob is more for usability/validation and does not change this functionality.

from aggregation-service.

Thank you very much for this feature.

from aggregation-service.

Thank you very much for this feature.

You're welcome!

from aggregation-service.

As a quick update, we have now launched site enrollment for Aggregation Service.

As part of this launch, we have updated our aggregation service onboarding form to use the site (ex: https://adtech.com) instead of origin (ex: https://analytics.adtech.com/ ) for enrollment. This creates consistency with the enrollment for the client API and streamlines onboarding by allowing adtechs to enroll multiple origins of the same domain as one site.

Adtechs should ensure the site used for new aggregation service enrollments is the same site used for the client API enrollment. They should also ensure they are using the correct URL format for their reporting origin (ie, ensure the https:// prefix is included in the origin) to avoid errors.

There is no action needed for prior enrollments. AWS accounts/GCP projects already mapped to previously enrolled origins will be updated to map to the applicable site.

Note that this change does not include batching of multiple origins for the same site in a single job; the createJob API still supports only one origin per job. However, we are actively working on this proposal as mentioned in my earlier post and will update our status page once we have more information on this and other features.

We welcome any feedback on this feature.

Thank you!

from aggregation-service.