1. Property identity
For web inventory, review the domain, publisher and placement. For app and CTV inventory, review the bundle or channel identifier, public store or listing where available, publisher or developer and the environment represented.
Evidence before labels
Programmatic Inventory Quality and Supply Transparency
AdSelect reviews inventory identity, source relationship, transparency information, technical samples and the quality documentation available for each opportunity. Evidence is described with its scope and period rather than turned into a universal “clean” claim.
Four review layers
Quality starts with knowing what the inventory is
A third-party result can be useful, but it does not replace property identity, supply-path transparency, technically consistent requests and evidence from the live test.
2. Supply-path transparency
Review ads.txt or app-ads.txt, sellers.json and SupplyChain information where applicable. The seller relationship stated by the partner should be consistent with the public files and traffic being represented.
3. Technical consistency
Review sanitized OpenRTB requests or VAST examples for the identity, environment, format, placement and supply-path fields expected for the opportunity. Missing or contradictory fields are resolved before traffic expands.
4. Evidence and live test
Record available third-party documentation with its source and period, then review live delivery, quality signals, discrepancies, errors and any escalations during a controlled test.
Third-party documentation
Name the evidence without overstating it
Depending on the source, available documentation may include assessments or reports associated with Pixalate, DoubleVerify or HUMAN. AdSelect records the source, inventory covered, measurement period and result made available for review.
Transparency checklist
What partners should prepare
Publisher or supply partner
- • Legal or operating entity and commercial role
- • Domains, bundle IDs, store links or channel identifiers
- • Format, placement, device and geography details
- • ads.txt or app-ads.txt and seller relationship
- • Expected scale and representative technical samples
- • Available quality documents with dates and scope
Demand partner
- • Required formats, environments and markets
- • Integration and request-field requirements
- • Brand-suitability and inventory restrictions
- • Required transparency and measurement evidence
- • Test limits and acceptance checks
- • Reporting, discrepancy and escalation contacts
During the test
Quality review continues after connectivity
Pre-test documents establish the expected source. Live test evidence shows whether traffic, measurement and delivery match that expectation.
- 01
Sample
Compare representative requests or tags with the documented source and format.
- 02
Monitor
Review delivery, errors, source consistency and available quality signals.
- 03
Investigate
Escalate mismatches with timestamps, IDs, logs and the evidence needed to reproduce them.
- 04
Decide
Continue, adjust, pause or expand only after both parties review the findings.
What this page does not claim
- • AdSelect does not claim that every source is certified by a named provider.
- • A historical assessment is not represented as a permanent result.
- • Source-level evidence is not extended to unrelated apps, domains or sellers.
- • Quality review does not guarantee fill, revenue or campaign performance.
What partners can expect
- • Questions tied to the source and integration being evaluated.
- • A request for verifiable identity and supply-path information.
- • Clear test boundaries, reporting definitions and escalation contacts.
- • A joint review before the opportunity is expanded.
Have source-level quality evidence to review?
Share the property identity, supply path, format, markets, expected scale and the document source, scope and period.
Schedule a Quality Discussion