OWNERDOMAIN and MANAGERDOMAIN in ads.txt 1.1: syntax, when to add them, and sellers.json consistency
Key takeaways
- OWNERDOMAIN and MANAGERDOMAIN are variables added to the IAB Tech Lab ads.txt specification in version 1.1, released in 2022.
- OWNERDOMAIN declares the business domain of the entity that owns the site; the specification marks it as recommended and says it should equal the domain field of your entries in sellers.json.
- If OWNERDOMAIN is absent, the specification says consumers should assume the owner domain is the domain where the ads.txt file was found.
- MANAGERDOMAIN is optional and declares a primary or exclusive monetization partner, globally or for one country, using the format domain, optional two-letter country code.
- Google's AdSense help pages do not say whether AdSense reads OWNERDOMAIN or MANAGERDOMAIN; the variables are aimed at buyers and validators that compare ads.txt with sellers.json.

OWNERDOMAIN and MANAGERDOMAIN are two optional variables added in ads.txt 1.1. OWNERDOMAIN=example.com names the business that owns the site and should match the domain in your sellers.json entries. MANAGERDOMAIN=partner.com names an exclusive monetization partner, globally or per country. Neither one authorizes a seller, and Google’s AdSense help pages do not ask for either.
What problem do these variables solve?
Before version 1.1, an ads.txt line said that a seller account may sell a site’s inventory, and the DIRECT or RESELLER field described the relationship. Buyers had no standard way to check whether a DIRECT claim was true, or to tell owned inventory from resold inventory.
The IAB Tech Lab ads.txt 1.1 Implementation Guide lists the goals: “linking ads.txt/app-ads.txt directly to sellers.json”, identifying “primary, or exclusive representatives of a publisher’s inventory” through MANAGERDOMAIN, and connecting “the sellers.domain listed in sellers.json and the ads.txt file”. The two variables give buyers a domain to compare against the domain field in each ad system’s sellers.json.
The ads.txt 1.1 specification change log lists the version as “April 2022 public comment July 2022 final release”, while the implementation guide’s cover says “Released August 2022”.
What is the exact syntax?
Both are variable declarations in the VARIABLE=value form, like CONTACT and subdomain. The example from section 4.8 of the spec:
OWNERDOMAIN=mediacompany.com
MANAGERDOMAIN=yellowmediamanager.com, FR
MANAGERDOMAIN=bluemediamanager.com, US
greenadexchange.com, XF7342, DIRECT, 5jyxf8k54
| OWNERDOMAIN | MANAGERDOMAIN | |
|---|---|---|
| Status in the spec | “Recommended” | “Optional, use only when relevant” |
| Value | Root domain (Public Suffix List plus one label) | Root domain, then optional ISO 3166-1 alpha-2 country code |
| How many | One; “only the first should be used” if repeated | Several allowed, “but only one per country” |
| If absent | Owner assumed to be the domain where the file is found | No manager declared |
| Should match | domain of your PUBLISHER entries in sellers.json |
domain of the manager in sellers.json |
The spec says variables can appear anywhere, and recommends putting them “at the end of the file” for readability. The spec’s own example places them at the top; both work. The general line format is covered in ads.txt syntax.
What does OWNERDOMAIN declare?
The spec defines it as “the business domain of the business entity that owns the domain/site/app (e.g., example.com owns example1.com, example2.com, etc.).” Three rules from the spec:
- It “should be the same value as the sellers.domain in this Publisher’s entries in referenced sellers.json files.”
- It should be “Public Suffix List+1, not a full hostname or a URL.”
- It “is recommended that this field is included even if the OWNERDOMAIN is the same as the domain on which the ads.txt file is found.”
So a company called Example Media that owns recipes-site.com and travel-site.net would put OWNERDOMAIN=examplemedia.com in both sites’ ads.txt files. A solo publisher who owns only myblog.com and has no separate company domain would write OWNERDOMAIN=myblog.com.
How does OWNERDOMAIN connect to Google’s sellers.json?
The implementation guide states the publisher-side rule: “All accounts authorized in your ads.txt that are PUBLISHER in the corresponding sellers.json file should also have a sellers.domain in sellers.json that matches the OWNERDOMAIN in your ads.txt.”
For an AdSense publisher, that sellers.domain is the business domain you set in AdSense under Account, Settings, Account information, in the “Seller information visibility” section. Google’s sellers.json help page says the business domain appears only if you select “Transparent”, and that it “may be hidden in sellers.json until we have verified that you own the URL.”
| Your AdSense setting | Your Google sellers.json entry | Can a buyer match OWNERDOMAIN? |
|---|---|---|
| Transparent, business domain verified | Includes domain |
Yes, if the values are equal |
| Transparent, no domain | Name only | No domain to compare |
| Confidential | ID and seller type only | No |
If you are confidential in sellers.json, OWNERDOMAIN in your ads.txt cannot be cross-checked against your Google entry, though it still states ownership to anyone who reads the file. The full visibility setting is explained in sellers.json for AdSense.
What does MANAGERDOMAIN declare?
The spec describes MANAGERDOMAIN as “the business domain of a primary or exclusive monetization partner of the publishers inventory.” It “should only be used for a seller who is not the publisher but is the primary or exclusive programmatic seller for this site”, which “will typically only apply if the publisher is not selling their own inventory in the given market.”
Syntax details from the spec:
MANAGERDOMAIN=manager.comwith no country is the global default.MANAGERDOMAIN=manager.com, FRapplies to one country and overrides the default there.- One per country. The implementation guide recommends that consumers treat two managers for the same country “as if there is no MANAGERDOMAIN declared for that country.”
The implementation guide’s publisher advice is narrow: “only use MANAGERDOMAIN if a majority of your inventory is managed by a single entity.” It also warns that “if the same inventory is available through multiple sellers, and you still use MANAGERDOMAIN, buyers will likely treat the other non-manager accounts as RESELLER entries.”
Should an AdSense publisher add them?
| Your situation | OWNERDOMAIN | MANAGERDOMAIN |
|---|---|---|
| One site, AdSense only, you are the payee | Optional; recommended by the spec, e.g. OWNERDOMAIN=yoursite.com |
No |
| Several sites owned by one company | Yes, the company’s domain in every file | No |
| A sales house or partner sells most of your inventory | Yes | Yes, the partner’s domain |
| Different partner in one country only | Yes | One line with that country code |
| You resell other publishers’ inventory | Yes, in files you own; follow your partners’ guidance in theirs | Possibly, in the files you manage |
Google does not document whether AdSense uses either variable, and the AdSense “Ads.txt snippet” contains only the authorization line. Adding OWNERDOMAIN does not change your AdSense status, and its absence does not cause “Unauthorized”. The value is for other buyers and validators that implement ads.txt 1.1. If you are moving to a managed setup or to Ad Manager through a partner, the partner normally tells you which lines and variables to add; see AdSense vs Ad Manager.
What does a complete file look like for a typical AdSense site?
A publisher who owns myrecipes.com, sells through AdSense only, and has set myrecipes.com as the verified business domain in “Seller information visibility” could publish:
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
OWNERDOMAIN=myrecipes.com
The same publisher after selling the site to a media company whose sellers.json domain is bigmedia.com, with a sales house handling France only:
google.com, pub-1111111111111111, DIRECT, f08c47fec0942fa0
OWNERDOMAIN=bigmedia.com
MANAGERDOMAIN=saleshouse-example.com, FR
In the second case, the AdSense line must use the new owner’s publisher ID, and the sales house would add its own seller lines as instructed by its documentation.
Which mistakes should you avoid?
| Mistake | Why it is wrong | Correct form |
|---|---|---|
OWNERDOMAIN=https://www.example.com/ |
Must be a root domain, not a URL | OWNERDOMAIN=example.com |
OWNERDOMAIN=blog.example.com |
Hostname, not PSL+1 | OWNERDOMAIN=example.com |
| Two different OWNERDOMAIN lines | Only the first is used | Keep one |
| OWNERDOMAIN differs from your sellers.json domain | Buyers cannot match it | Use the same domain in both |
MANAGERDOMAIN=manager.com, France |
Country must be a two-letter ISO code | MANAGERDOMAIN=manager.com, FR |
| Two MANAGERDOMAIN lines for the same country | Treated as no manager for that country | One per country |
| MANAGERDOMAIN for a partner that sells a small share | Contradicts “primary or exclusive” | Leave it out |
How can you check your file?
Fetch the file and print the variable lines:
curl -sL https://example.com/ads.txt | grep -iE '^(ownerdomain|managerdomain)='
Then compare the OWNERDOMAIN value with the domain in your entry in Google’s sellers.json, using the grep -A4 method from the sellers.json guide. Be aware that tools differ: the IAB’s open-source reference crawler predates version 1.1 and does not store these variables, as described in validating ads.txt yourself. The wider set of related standards is mapped in IAB Tech Lab specs.
Frequently asked questions
Do I need OWNERDOMAIN for AdSense to show ads?
No. Google's AdSense help pages describe the authorization line google.com, pub-..., DIRECT, f08c47fec0942fa0 and do not mention OWNERDOMAIN. The IAB specification marks the variable as recommended, not required, and says that when it is absent, consumers should assume the owner is the domain where the file was found. Adding it is a transparency signal for buyers and validators, not an AdSense requirement.
What value should I put in OWNERDOMAIN?
The root domain of the business that owns the site, written like example.com, with no scheme, no www and no path. The specification says it should be the same value as the domain in your sellers.json entries. For AdSense, that is the business domain shown in Google's sellers.json when your seller information is transparent and the domain has been verified.
Should a small publisher add MANAGERDOMAIN?
Usually not. The specification says MANAGERDOMAIN should only be used for a seller that is not the publisher but is the primary or exclusive programmatic seller for the site. The implementation guide recommends it only when a single entity manages a majority of your inventory. If you sell through AdSense yourself, there is no manager to declare.
What happens if I declare two MANAGERDOMAIN lines for the same country?
The specification allows only one MANAGERDOMAIN per country. The IAB implementation guide says conflicting entries should not be used and will likely be ignored, and recommends that consumers treat two managers for the same country as if no manager were declared for that country. Keep one global line without a country code and, if needed, one line per specific country.
Sources
- Ads.txt Version 1.1 · IAB Tech Lab
- ads.txt 1.1 Implementation Guide · IAB Tech Lab
- Sellers.json · IAB Tech Lab
- Provide your seller information with sellers.json · Google AdSense Help
Related guides
- Google's sellers.json for AdSense publishers: seller information visibility and what buyers see
What Google's sellers.json says about your AdSense account, how the Seller information visibility setting works, and how to find your own entry in the file.
- ads.txt syntax for AdSense, line by line: pub ID, DIRECT, TAG ID, comments and variables
The AdSense ads.txt line field by field: google.com, your pub ID, DIRECT, f08c47fec0942fa0, plus comments, variables and the formatting errors that break parsing.
- AdSense vs Google Ad Manager: when a publisher outgrows AdSense, and what changes if you switch
AdSense or Google Ad Manager? What each product does, what Google says about eligibility, direct sales, tags and auctions, and signs you have outgrown AdSense.
- Validating ads.txt yourself: curl checks, the IAB Tech Lab open-source crawler and scripted audits
Check your ads.txt without third-party validators: curl tests that mimic a crawler, the IAB Tech Lab open-source crawler and its limits, and a short audit script.
- IAB Tech Lab and IAB Europe specifications: what an AdSense publisher needs to know
Which industry specs matter to an AdSense publisher: ads.txt 1.1, sellers.json, SupplyChain, OpenRTB, TCF and GPP, with current versions and what each asks of you.