DIRECT lines inconsistent with public data
7 −23 ptsThe IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." 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 companies with different owner domains. 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 (7)
line 1 google.com, pub-2475780245225692, DIRECT, 8e1fd65b93cbeda7
→ observed: the same account is marked DIRECT by 5 different companies
line 331 Media.net, 8CUC8Q2L1, DIRECT
→ observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 5 different companies name in sellers.json: Match Group, LLC (via OB) domain in sellers.json: google.com
line 332 indexexchange.com, 184082, DIRECT
→ observed: the same account is marked DIRECT by 5 different companies
line 333 openx.com, 537150847, DIRECT, 6a698e2ec38604c6
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Match Group, LLC (via EB) domain in sellers.json: google.com
line 334 triplelift.com, 12212-EB, DIRECT, 6c33edb13117fd86
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Match Group (via EB Network) domain in sellers.json: google.com
line 335 pubmatic.com, 157164, DIRECT, 5d62403b186f2ace
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Match Media Group (via EB) domain in sellers.json: google.com
line 337 rubiconproject.com, 17694, DIRECT, 0bfd66d529a55807
→ observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 4 different companies name in sellers.json: Google domain in sellers.json: google.com