MANAGERDOMAIN Demystified

Over the past year working with publishers, a question kept coming up again and again — and has never been cleanly answered: can a publisher have more than one MANAGERDOMAIN?

The real money problem nobody is talking about

Here’s the scenario playing out across the industry right now.

A publisher works with two yield management companies — both excellent partners, each handling roughly half of their inventory.

Both partners, quite reasonably, ask to be declared as MANAGERDOMAIN in the publisher’s ads.txt.

The publisher obliges.

And quietly, without anyone realizing it, revenue starts leaking.

Here’s why: DSPs performing supply path optimization (SPO) often filter for DIRECT paths as the shortest, cleanest route to supply.

If your yield manager is listed as RESELLER, which they often are when the MANAGERDOMAIN field is occupied by someone else, they become invisible to a meaningful chunk of programmatic budget.

The publisher doesn’t get an alert.

There’s no error message.

The money simply doesn’t show up.

This is the actual impact of the MANAGERDOMAIN problem: not a compliance issue, not a technical footnote — a direct hit to publisher revenue that most monetization teams have no idea is happening.

What the IAB spec actually says

Each ads.txt file can have one MANAGERDOMAIN entry per country represented, or a single entry for global representation.

The manager is expected to exclusively represent the majority of the supply of the underlying publisher for the specified geography.

Being unable to get a clear answer from the industry, I reached out directly to the IAB Tech Lab with three questions:

1. Can a publisher declare two MANAGERDOMAIN entries for the same country or globally if they genuinely split management between two companies?

2. What happens if no single manager controls 80%+ of supply — does the field simply not apply?

3. How are DSPs actually using this field today, and is there any enforcement standard?

The official answer, as of publishing: one MANAGERDOMAIN per country, not one total.

Technically, multiple entries are allowed — but only if each one represents a different geography.

Which, frankly, is not how the industry works.

What it takes to qualify as a MANAGERDOMAIN

According to the IAB Tech Lab specification, a MANAGERDOMAIN must be a vendor that manages the majority of the inventory — defined as at least 80%.

So publishers need to ask themselves two questions:

• Do I use a third-party company that manages the majority of my inventory?

• Do I have my own seats that I am monetizing directly?

If the answer to the first question is yes and the second is no, then that vendor can legitimately be listed as MANAGERDOMAIN.

This is where the real problem sits.

The spec requires the manager to control at least 80% of supply.

A publisher working with two different yield management companies — which is extremely common in the real world, technically cannot declare both as MANAGERDOMAIN.

They can only declare the one who controls the majority.

The other simply lives in the ads.txt as a RESELLER, which defeats the entire purpose of the field.

The conflict with real-world publisher setups

Any ad-tech provider worth considering will tell a publisher that “in order to maximise your revenue, you need to declare us as MANAGERDOMAIN.”

And they’re not wrong to ask.

Advertisers generally prefer the shortest path to a publisher’s traffic, and MANAGERDOMAIN flags a vendor as the entity with the closest possible relationship to that publisher, and moreover, It signals the vendor as a premium, direct supply partner.

So the immediate practical question becomes: if a publisher works with two ad-tech partners, each handling 50% of the traffic, can both be declared as MANAGERDOMAIN? According to the spec: no.

According to real-world commercial pressure: both will ask to be defined that way.

The enforcement problem

MANAGERDOMAIN is “optional” and “should” be provided when a manager is used.

A site that should provide it can simply choose not to, and still claim full spec compliance.

Similarly, a DSP can claim to support the ads.txt spec while ignoring these variables entirely. MANAGERDOMAIN is not truly enforceable — it is, in practice, an SPO hint and nothing more.

Two paths the industry should take

In my humble opinion, there are two directions the industry can and should take on this:

1. Allow publishers to declare more than one MANAGERDOMAIN.

Given that these are vendors a publisher genuinely works with and routes significant traffic to, there is no good reason why the playing field should not be levelled for all qualifying partners.

2. DSPs should recognise that most publishers are, de facto, their own manager.

The majority of publishers I have worked with control their own traffic and choose which vendors to send it to based on performance.

Unless stated otherwise, the actual manager domain is often the publisher’s own monetization team — which is not necessarily the same as the OWNERDOMAIN.

DSPs leaning too heavily on MANAGERDOMAIN as an SPO signal are making an assumption that simply does not hold in most real-world setups.

I would choose option one.

Option two makes advertisers dependent on the accuracy of DIRECT and RESELLER entries in ads.txt — and the level of abuse in those entries is a whole other conversation.

You would not believe what some vendors try to pass off on DIRECT ads.txt lines. 😉

What should publishers do right now?

Don’t wait for the spec to catch up. Here’s a quick audit you can do today:

1. Open your ads.txt file and find every vendor listed as MANAGERDOMAIN.

2. Cross-reference with your yield management partners — are all of them represented correctly?

3. Ask each partner how DSPs in their network are interpreting MANAGERDOMAIN and RESELLER entries today.

4. If a key partner is stuck as RESELLER, have a direct conversation about how to restructure the relationship or the entry to protect your revenue.

The ambiguity in the spec is real and it is not going away overnight. But publishers who understand the mechanics are in a far better position to protect their revenue than those who leave their ads.txt on autopilot.