DIRECT lines inconsistent with public data
6 −11 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 7 pubmatic.com, 157859, DIRECT, 5d62403b186f2ace #Pubmatic
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Streema, Inc. (via EB) domain in sellers.json: google.com
line 15 triplelift.com, 6075-EB, DIRECT, 6c33edb13117fd86 #Triplelift
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Streema (via EB Network) domain in sellers.json: google.com
line 20 rubiconproject.com, 20204, DIRECT, 0bfd66d529a55807 #Rubicon
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Google domain in sellers.json: google.com
line 24 lijit.com, 265404-eb, DIRECT, fafdf38b16bf6b2b #SOVRN
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: pubteck.com (via Google EB) domain in sellers.json: google.com
line 164 toponad.com, 16385e313a271a, DIRECT, 1d49fe424a1a456d #Mintegral
→ observed: the same account is marked DIRECT by 98 different companies
line 185 vidoomy.com, 7646534, DIRECT #Mintegral
→ observed: the same account is marked DIRECT by 77 different companies