Last Reviewed: 01 November 2024
Scope3 customers may have the ability to provide various types of data to the Scope3 Platform. Scope3 takes data privacy and security very seriously, and this document outlines how the platform uses contributed data of various types.
All contributed data must be accurate based on the Customer’s commercially reasonable efforts. Scope3 will compare data shared by counterparties and will use commercially reasonable efforts to reconcile differences. Scope3 will align contributed data to its published methodology to provide consistent data across the platform. Scope3 does not accept personal data or PII in any contributed data.
The Scope3 Emissions Model is an estimation of the carbon footprint of every ad impression based on a combination of data sets. The sources for the model are a combination of:
Scope3 combines these data sources daily to build a daily emissions model, or “snapshot,” which will be used to generate all reports and activation of the model for a particular date. Scope3 will aggregate volume data in the snapshot to prevent disclosure of sensitive information. For instance, if an SSP uploads traffic shaping data about the number of requests it sends to various monetization partners, Scope3 will use this data to calculate the emissions model for the SSP but will not show or share the number or percentage of requests that are sent to each partner.
Some data in the snapshot may be provided on behalf of another company. For instance, a traffic shaping vendor or carbon accounting vendor might provide data on behalf of a mutual customer. The mutual customer must explicitly approve third parties that are providing data on its behalf and may revoke this approval at any time.
Snapshots are retained indefinitely so that historical reporting and audits function properly. When contributed data are removed from the Scope3 platform, they will no longer be used to compute the model. Aggregated emissions numbers, as well as active supply paths, will continue to be incorporated into historical snapshots.
| Data | Detail | Schema / API | Use in Model | Exposed in API/UI |
|---|---|---|---|---|
| Upstream programmatic requests | Requests received and processed by an ad tech platform broken out by supplier, country, and integration method | Supply | Used to model paths between publishers and ad tech companies and the downstream emissions for suppliers | Valid supply paths will be visible in Inventory Explorer. Request data, including block ratio, are not exposed. |
| Downstream programmatic requests | Programmatic requests sent to bidders broken out by supplier and country | Traffic Shaping | Used to calculate downstream emissions | The aggregate emissions number (principal + downstream) is exposed. Per-bidder data is not exposed. |
| Sessions per property | Data transferred, ads seen, and time spent per session for each property | Property Metrics | Used to allocate corporate emissions | Aggregate corporate emissions per impression per property is exposed; session data is not exposed. |
| Sustainability Facts | Scope 1, 2, and 3 emissions by category | Sustainability Facts | Used to model corporate emissions and allocate between divisions and products | Optional |
| Ad stack | Monetization and ad serving partners by placement group | UI only | Used to model emissions by placement group | Aggregate impressions per placement group and monetization partner are exposed; placement groups are exposed; detailed ad stack and related metrics not exposed |
| Ad formats | File size, asset format, and configuration for proprietary ad formats | UI only | Used to model emissions by ad format | Aggregate emissions by ad format are exposed; details are not exposed |
| DOOH Screens | Screen names & identifiers, manufacturer & model, estimated power draw, average impression multiplier, physical dimensions, venue category, location | Backend upload | Used to model emissions from screens’ energy use | Individual screen emissions are exposed in API but not UI. Media owners can choose to expose emissions for a group of screens in UI. |
Scope3 customers may provide the Scope3 Platform with campaign delivery data from publishers, media owners, or ad tech platforms by uploading files, integrating through cloud storage buckets, or providing Scope3 with API access to these platforms.
Scope3 will treat all campaign delivery data as confidential information under the customer’s platform subscription agreement and will not share it with any other platform user unless explicitly specified by the customer (for instance, if a publisher wants to share delivery data with an advertiser) using the permissioning capabilities of the platform. Except with respect to campaign delivery data provided in connection with Green Media Products, customers may remove this data from the platform at any time, and all campaign delivery data will be removed at the end of the commercial relationship between Scope3 and the customer.
Campaign delivery data provided in connection with a Green Media Product may not be removed from the platform once it has been shared with the buyer of said Green Media Product, the "Buyer". After the termination of the commercial relationship between Scope3 and the customer, campaign delivery data previously shared may continue to be used by the Buyer for media reporting.
| Data | Detail | Schema / API | Exposed in API / UI |
|---|---|---|---|
| Media delivery data | Impressions and other metrics by campaign, line item, insertion order, country, seller, and placement | Media delivery | Available only to the principal; can optionally be shared with counterparties |
| Creative delivery data | Impressions and other metrics by creative group, vendor, ad format, and country | Creative delivery | Available only to the principal; can optionally be shared with counterparties |
Some Scope3 customers need to provide usage data to Scope3 for billing purposes. For instance, a customer with a revenue-sharing agreement would need to provide Scope3 with net revenue information at the end of each month. Usage data will be treated as confidential information under the customer’s platform subscription agreement. Usage data will not be removed from the platform upon termination of the commercial relationship as it is tied to invoices in the Scope3 accounting system and needs to be retained for audit purposes.
| Data | Detail | Schema / API | Exposed in API / UI |
|---|---|---|---|
| Usage | Impressions and/or net revenue by client | Customer usage | No |
Customers that use the Scope3 Platform may have the ability to create a Sustainability Profile that includes details about sustainability practices and proprietary ad formats.
Adding information to this Profile is not required and the customer retains full control over whether contributed information is made available to other users of the Scope3 Platform. The customer may remove this information from the platform at any time. At the end of the commercial relationship between Scope3 and the customer, Scope3 will remove the sustainability profile from the platform.