Delegated vs. Direct ads.txt Hosting

There are two ways to manage your ads.txt file. You can do it yourself (direct hosting) or have someone else do it for you (delegated hosting).

Most publishers host directly. They create ads.txt on their server, paste in the SSP lines they need, and update it when things change. It's straightforward.

But some publishers operate at a scale or in a structure where direct management doesn't make sense. Publisher networks managing hundreds of sites. CMS platforms generating ads.txt for thousands of publishers. Ad management companies running monetization for publishers who'd rather focus on content.

For these scenarios, the IAB Tech Lab introduced delegated hosting through the MANAGERDOMAIN variable. Here's how both approaches work, what breaks when they're misconfigured, and how to choose.

How Direct Hosting Works

Direct hosting is the default. Your ads.txt file lives at https://yourdomain.com/ads.txt and you control its contents.

text
greenvalley.com, 12345, DIRECT, f08c47fec0942fa0
pubmatic.com, 67890, DIRECT, 5d62403b186f2ace
openx.com, 11111, RESELLER, 69f78dc98cfe74e2

The DSP fetches this file, parses each line, and cross-references against sellers.json files. Verification is a single hop: your domain to the DSP.

Advantages of Direct Hosting

Full control. You decide which SSPs appear in your file, when entries are added, and when they're removed. No intermediary can change your file without your involvement.

Simpler verification chain. DSPs fetch one file from one domain. Fewer moving parts means fewer opportunities for verification to fail.

Faster updates. When you need to add a new SSP or remove a stale entry, you update the file and it's done. DSPs pick up the change on their next crawl (24-72 hours). No coordination with a third party required.

No dependency on external availability. Your ads.txt is only unavailable if your own server is down. With delegated hosting, you depend on both your server and the manager's server being accessible.

Disadvantages of Direct Hosting

Manual maintenance. Every SSP entry needs to be added, verified, and eventually removed when the partnership ends. For publishers with 20+ SSP relationships, this becomes a recurring operational task.

No centralized management across domains. If you operate five domains, you manage five separate ads.txt files. Keeping them consistent requires discipline.

Expertise required. You need to understand the ads.txt format, know which entries to include, and recognize when something needs updating. For publishers without dedicated ad ops, this can be a gap.

How Delegated Hosting Works

Delegated hosting uses the MANAGERDOMAIN variable to tell DSPs that a third party manages your ads.txt.

Your domain's ads.txt file looks like this:

text
MANAGERDOMAIN=admanager.com

The rest of your authorized sellers live in the manager's ads.txt file, which DSPs are directed to fetch.

The verification flow:

1. DSP fetches https://yourdomain.com/ads.txt
2. Sees MANAGERDOMAIN=admanager.com
3. Fetches https://admanager.com/ads.txt
4. Finds entries relevant to your domain in the manager's file
5. Cross-references those entries against sellers.json

Some implementations include both the MANAGERDOMAIN declaration and local entries:

text
MANAGERDOMAIN=admanager.com
greenvalley.com, 12345, DIRECT, f08c47fec0942fa0

In this case, DSPs consider both the local entries and the entries from the manager's file.

Advantages of Delegated Hosting

Centralized management. A single entity manages ads.txt for multiple domains from one place. Changes propagate to all managed domains without updating each file individually.

Professional management. If the managing entity specializes in ad operations, they may maintain the file more accurately than the publisher would on their own.

Reduced publisher burden. Publishers can focus on content while the manager handles supply chain configuration.

Disadvantages of Delegated Hosting

Added verification complexity. DSPs must fetch and process two files instead of one. If either file has issues (downtime, formatting errors, stale data), verification fails.

Dependency on the manager. If the manager's server is down or their ads.txt has errors, your verification breaks even though your own domain is fine.

Less control. The manager decides which entries appear. If they add or remove SSPs without your knowledge, your monetization changes without your consent.

DSP support varies. While major DSPs support MANAGERDOMAIN, not all DSPs handle delegated hosting correctly. Some may only check the publisher's local file and ignore the MANAGERDOMAIN declaration.

Trust implications. You're trusting a third party with a file that directly affects your revenue. If the manager makes a mistake, you bear the consequence.

When to Use Each Approach

Use Direct Hosting When:

• You have a dedicated ad ops person or team. They can manage the file as part of their regular workflow.
• You operate one to five domains. The management overhead is manageable.
• You want maximum control over your supply chain. No intermediary decisions about which SSPs are in your file.
• You're using an ads.txt management tool. Tools like BeamFlow's ads.txt management can automate monitoring and alerts, giving you the benefits of centralized management without the delegation.

Use Delegated Hosting When:

• You operate a publisher network with dozens or hundreds of domains. Managing individual files at that scale isn't practical.
• You're a CMS or publishing platform. Your publishers expect you to handle monetization infrastructure.
• You don't have ad ops expertise in-house. You've hired a company specifically to manage your programmatic operations.
• Your ads.txt management is already part of a broader managed service agreement. The delegation is a natural extension of the relationship.

Delegated Hosting Pitfalls

If you choose delegated hosting, watch for these common issues:

Manager's ads.txt Is Down

If admanager.com/ads.txt returns a 404 or timeout, every publisher delegating to that manager loses verification. DSPs can't verify any of the managed entries.

Mitigation: Include critical SSP entries directly in your own ads.txt file alongside the MANAGERDOMAIN declaration. This provides fallback authorization even if the manager's file is temporarily unavailable.

Manager Adds Unauthorized SSPs

The manager adds SSPs that you haven't approved, potentially selling your inventory through partners you don't know or trust. Since you're not directly managing the file, you might not notice.

Mitigation: Regularly audit the manager's ads.txt to verify all entries are authorized. Set up monitoring to detect when new entries appear.

Manager Removes SSPs Without Notice

The opposite problem. The manager removes an SSP you rely on, and your demand from that SSP drops without warning.

Mitigation: Maintain your own record of which SSPs should be in your file. Compare against the manager's file on a regular schedule.

MANAGERDOMAIN Pointing to the Wrong Domain

The most basic error. The MANAGERDOMAIN value doesn't match where the manager actually hosts their ads.txt. Maybe the company changed domains. Maybe there was a typo. Either way, DSPs can't fetch the file.

Mitigation: Verify that https://[managerdomain]/ads.txt is accessible and returns valid content.

Hybrid Approach

Many publishers use a hybrid model: they host their own ads.txt with all SSP entries listed directly, but also use a management tool for monitoring, alerts, and version control.

This gives you the verification simplicity of direct hosting (single file, single domain, no intermediary) with the operational benefits of managed tooling (change detection, verification monitoring, health scoring).

The hybrid approach is what we recommend for most publishers. You maintain control. The tool maintains visibility.

Check your ads.txt hosting configuration to verify DSPs can access and verify your file correctly.

Frequently Asked Questions

Can I switch from delegated to direct hosting?

Yes. Remove the MANAGERDOMAIN line from your ads.txt and add all your SSP entries directly. DSPs will pick up the change on their next crawl. Make sure your local entries are complete before removing the delegation — you don't want a gap where neither the manager's file nor your local file has your entries.

Can I switch from direct to delegated hosting?

Yes. Add the MANAGERDOMAIN line and ensure the manager's ads.txt includes all your SSP entries. You can keep local entries as a backup during the transition. Once you confirm the manager's file is correct and DSPs are recognizing it, you can remove local entries if desired.

Does delegated hosting affect SEO?

No. ads.txt is a machine-readable file for programmatic advertising verification. It has no impact on search engine rankings or crawling.

Can I have multiple MANAGERDOMAINs?

No. The IAB specification allows only one MANAGERDOMAIN per ads.txt file. If you work with multiple management companies, you'll need to choose one as the primary manager or switch to direct hosting.

Is delegated hosting less secure?

It introduces an additional trust dependency. If the manager's infrastructure is compromised or their file is tampered with, your monetization is affected. Direct hosting limits this risk to your own infrastructure. For security-conscious publishers, direct hosting with monitoring tools is the safer choice.