At Criteo Engineering we are working on:
- Clarifying and documenting our understanding of the Prebid Addressability Framework (PAF) project requirements.
- Drafting specification and demonstrable prototypes that answer those
- Delivering an MVP of the necessary components
This repository is intended to share this work with the Prebid community, get feedback and reviews.
The minimum friction way to provide feedback is to use Github's Creating an issue from code feature.
It looks like this:
Specifications for a MVP, covering only a single id managed by several operators sharing a common registrable domain (e.g. operator1.prebid-a-f.com and operator2.prebid-a-f.com).
| Document | Description |
|---|---|
| signatures.md | General introduction on signatures and signature verification |
| audit-log-requirements.md | Functional requirements related to the Audit Log and the Transmissions. |
| audit-log-design.md | Design the technical solution for the Audit Log. |
| landscape.md | An overview of the different actors and their roles. |
| ad-server-implementation.md | Details PAF implementation in an Ad Server. |
| dsp-implementation.md | Data exchange specification, from the point of view of a DSP implementer. |
| operator-api.md | Operator API specification |
| operator-design.md | Design of the generation of PAF Data. |
| operator-design-alternative-swan.md | Summary of the SWAN solution for generating PAF Data. |
| operator-requirements.md | Requirements for the generation of the PAF Data. |
| website-design.md | Design of the website integration. |
| model | Data and messages model |
| json-schemas | Data and messages model in JSON schema format |
Please see Contributing.md