Now that you have gotten the overview of Aggregation Service, it is time for you to deploy your very own instance of the Aggregation Service through Google Cloud or Amazon Web Services. If you would like to perform aggregation and generate summary reports locally before deploying to a public cloud, check out our local testing tool.
Steps
Fill out the Enrollment form.
Ensure that you have declared one of the following APIs within your ad tech server (e.g DSP, SSP, MMP). Depending on which measurement client API you are leveraging, do pick the corresponding
.well-known/
URL path. (Note: Only aggregate attribution reports from Attribution Reporting API can be passed to Aggregation Service. Don't pass event-level reports from Attribution Reporting API.)POST /.well-known/private-aggregation/report-shared-storage
POST /.well-known/private-aggregation/report-protected-audience
POST /.well-known/attribution-reporting/report-aggregate-attribution
Begin deployment: Pick either Google Cloud (GCP) or Amazon Web Services (AWS) as your cloud provider. You can follow the codelab instructions for a step-by-step guide on building your cloud environment and running your first job, or you can just consult the deployment steps for the instructions on building the cloud environment.
- Amazon Web Services (AWS): Codelab, Deployment steps
- Google Cloud (GCP): Codelab, Deployment steps
Ensure that once you have deployed your cloud service that you fill out the onboarding form, which will allow-list your Amazon Web Services account ID or Google Cloud service accounts. Make sure you have done this before you attempt to call any Aggregation Service APIs!