Device-level verification The tech works simply enough: First, a publisher integrates OM SDK 1.6. Then, when an ad creative is served to a user in the publisher's audience, code embedded in the creative triggers an attestation call to the measurement provider. The measurement provider then requests an attestation token directly from the manufacturer. The manufacturer provides the token using IETF's Privacy Pass Protocol. The protocol offers a safeguard against bad actors reverse-engineering the attestation, because the manufacturer must confirm that it provided the token.