DIRECT lines inconsistent with public data
6 −4 ptsThe ads.txt specification defines DIRECT as an account the publisher directly controls. For these lines, either the ad system's own sellers.json lists the account as INTERMEDIARY, or the same account is marked DIRECT in the files of 3 or more unrelated companies. Either way, the public data does not support the DIRECT label. Buyers that use DIRECT labels in supply-path decisions may treat these lines differently.
Evidence (6)
line 6 pubmatic.com, 159349, DIRECT, 5d62403b186f2ace
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Ookla, LLC (via EB) domain in sellers.json: google.com
line 59 sharethrough.com, zBDOrtmh, DIRECT, d53b998a7bd4ecd2
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Ookla - OB domain in sellers.json: google.com
line 109 media.net, 8CUS8BS1R, DIRECT
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Ookla, LLC (via OB) domain in sellers.json: google.com
line 131 video.unrulymedia.com, 2070966140, DIRECT
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Google - Ookla, LLC domain in sellers.json: google.com
line 200 triplelift.com, 12458-EB, DIRECT, 6c33edb13117fd86
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Ookla, LLC (via Google EB) (via EB Network) domain in sellers.json: google.com
line 204 onetag.com, 7e0bf488ee44332-OB, DIRECT
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Ookla-OB domain in sellers.json: google.com