New Planning API to support media planning, carbon calculators, and ad server reporting. Also redesigned the API for supply graph reporting, deprecating the supply directness field.

The April emissions model incorporates hints from ads.txt files for channel and geo; connects sustainability data from the GitHub repository to the API; and models emissions at the publisher and ad tech platform level for ad server reporting use cases.

This release includes seller-specific emissions models and multiple improvements to supply graph accuracy (ad block and syndication detection, masked domain adjustments, sellers.json updates, EMX removal). The overall impact of these updates is a decline in modeled emissions for most properties.

This release models emissions by seller and buying method for more visibility into supply path; provides a flexible inventory field to accept either domain or app ID; splits out consumer device emissions; and sets up streaming video for wide release in the coming months.

The February 2023 dataset increases coverage for websites that do not sell programmatically or have multiple domain names, includes mobile apps for all customers, and improves accuracy for Google Open Bidding.

With this update we move away from our proprietary estimates of the carbon footprint of each component of the advertising supply chain and instead use open source methodology. We also switch to ads.txt and app-ads.txt as the primary source for mapping the programmatic supply chain. Finally, our overall boundary assumption is changing from "media production and distribution" to just "media distribution" to enable a more consistent comparison across media owners, publishers, and channels.

API version 1.1 adds support for device and network type to support the January 2023 Dataset. Version 1.1 also lays the groundwork to add new channels, likely in the February 2023 dataset release.

Changes allow Scope3 to easily collect data on a daily level instead of just by month and year and to dive more granularly into site and domain reporting. This lays the groundwork for supporting mobile apps and other channels.

Previously we have been suggesting future product and API proposals for feedback next to the live API documentation. This has caused confusion with our users, so we have decided to remove them from the primary docs site. We are exploring other mediums to ask for feedback on proposals.