We have added a free sellers.json validator. Enter the domain of an SSP, exchange or ad network, or paste its file, and it checks the file against the IAB Tech Lab's Sellers.json 1.0 specification.

Every problem is listed with the sellers it applies to, what the value should be, and, where the IAB defines one, the error code buyers' crawlers report. So a code in somebody else's report can be looked up in one place.

[Read More]
 

If you earn money from advertising inside a mobile app or on connected TV, an app-ads.txt file is how you state publicly which companies are allowed to sell that advertising. It is the same idea as an ads.txt file, published by the app developer rather than by a website owner, and checked by the same buyers before they bid on your inventory.

The record format is identical to ads.txt, so most of it will already be familiar. The part that is genuinely different, and the part that quietly costs developers money, is where the file has to live. That is not something you choose. It is derived from your app store listing, and publishing one label too deep produces no error message anywhere at all.

[Read More]
 

You can now manage app-ads.txt files in ads.txt Guru, alongside the ads.txt files you already manage. Same editor, same validation, same collaboration groups, same delivery options.

It is included on the Publisher and Ad Network plans, and a domain's two files only count once against your domain allowance.

[Read More]
 

The problem: duplicate groups

If you run an ad network, the same seller accounts often need to appear differently depending on whose site they run on. On your own domain they are DIRECT. On the publisher domains you resell into, those same accounts must be RESELLER — with a MANAGERDOMAIN= line pointing back to you.

ads.txt Guru reuse groups already let you apply one set of records across many domains, but the relationship was fixed per record. So networks ended up maintaining two near-identical groups — one DIRECT, one RESELLER — and keeping them in sync by hand. Every account change had to be made twice, and the two drifted apart over time.

[Read More]
 

Why we built it

Agencies managing ads.txt for dozens of publishers have been telling us the same thing: setting up each new domain still required a few manual clicks in our UI. For an agency onboarding their tenth or fiftieth client, those clicks add up.

So we've added two new API endpoints that let you automate the bits that were previously UI-only.

[Read More]