ORTB
OMID chapter navigation

Device attestation (1.6.0)

planned

Device attestation addresses the misrepresentation of device information in Connected TV (CTV) and mobile advertising: device manufacturers issue privacy-preserving attestations that let buyers independently verify that the inventory is genuine. Supported from OM SDK 1.6.0 on Fire TV and Apple devices, and reached from the verification client via the attest method.

What this page will cover

  • The device spoofing problem and what an attestation provides
  • The call contract of the attest method
  • Supported platforms and starting version
  • Finalisation status of the official guidance

Source material

SourceFile / pathcommitFetchedIntegration status
InteractiveAdvertisingBureau/OMSDK-Device-AttestationImplementation Guidance.md · attestation flow.jpga4556452026-09-22not integratedThe repository README self-describes as In Progress; the flow exists only as an image with no machine-readable source
InteractiveAdvertisingBureau/Open-Measurement-JSClientssrc/externs/omid-verification-client.js · CHANGELOG.mdb6f12bd2026-09-22integratedThe attest method signature and the 1.6.0 release notes are integrated into spec.json

Gaps to verify

  • The implementation guidance in the official OMSDK-Device-Attestation repository self-describes as In Progress, so its prose and flow diagram are not final; this site will not integrate details ahead of that and only records the capability's starting point (OM SDK 1.6.0, Fire TV and Apple devices) and the attest method contract.

Related chapters

This page is a chapter blueprint: it records what the chapter will cover, its source material and current blockers, while the body text has not been migrated yet. See meta.statusRule in data/omid-spec/chapters.json for the status definitions.