As an ad tech, you can use the Attribution Reporting API and the Private Aggregation API, two main aggregate entry points on the client side, to funnel reports to the Aggregation Service and receive a summary report in response.
| Use case | Entry point | Description |
|---|---|---|
| Bidding optimization | Attribution Reporting API (Chrome & Android) | Use aggregated reports to ingest conversion signals for bidding optimization purposes. |
| Cross-platform measurement | Attribution Reporting API (Chrome & Android) | Use the cross-web and app measurement capabilities to get visibility into performance across Chrome & Android. |
| Conversion reporting | Attribution Reporting API (Chrome & Android) | Create aggregated conversion reporting tailored to customers' campaign needs (includes CTCs and VTCs). |
| Campaign reach measurement | Shared Storage API & Private Aggregation API (Chrome) | Use cross-site ad view variables to measure campaign reach. |
| Demographic reporting | Shared Storage API & Private Aggregation API (Chrome) | Use cross-site ad view and demographic information to measure reach by demographics. |
| Conversion path analysis | Shared Storage API & Private Aggregation API (Chrome) | Store cross-site ad view and conversion variables to perform aggregated conversion path analysis. |
| Brand and conversion lift | Shared Storage API & Private Aggregation API (Chrome) | Reporting on test/control groups and polling information to measure brand lift and incrementality. |
| Auction debugging | Protected Audience API & Private Aggregation API (Chrome) | Use aggregated reports for debugging. |
| Distribution of bids | Protected Audience API & Private Aggregation API (Chrome) | Use aggregated reports to capture the distribution of bid values for auctions. |
Next steps
Ready to implement the Aggregation Service for your own use cases? To begin, follow our getting started guide to deploy through either Google Cloud or Amazon Web Services and start leveraging the power of aggregated data.