UTM Parser
Decode tagged links and check the campaign naming holds together.
Write a valid ads.txt so your ad inventory is not spoofed.
exchange domain | your publisher ID | DIRECT or RESELLER | TAG ID. The TAG ID is optional but recommended.
Add a network
Your generated code appears here.
The ads.txt Generator writes authorised digital seller records in the exact comma-separated format the IAB specification requires, with the common networks preset so you need only your publisher ID. A single malformed line is skipped silently by buyers, so the validation here is the point of the tool.
Add each ad partner with your publisher ID and the generator writes the ads.txt records in the exact comma-separated format the IAB specification requires. Common networks are preset, so AdSense, Ad Manager, Amazon and the rest need only your ID.
ads.txt exists to stop domain spoofing, where someone sells fake inventory claiming to be your site. Publishing the file at yourdomain.com/ads.txt declares which sellers are authorised, and buyers check it before bidding. The format is unforgiving: each record is exactly the exchange domain, your publisher account ID, the relationship (DIRECT if you have a contract with them, RESELLER if they resell on your behalf), and optionally the TAG certification ID — comma separated, one per line. A single malformed line is skipped silently, which is why an invalid file usually shows up as revenue that quietly does not arrive.
AdSense, Ad Manager, Amazon, Criteo, Index Exchange, Magnite, PubMatic, OpenX and more, with the right domains.
The relationship field is explained rather than guessed at, since getting it wrong stops a partner bidding.
Malformed records are skipped silently by buyers, so they are caught here instead.
The same records in the app variant, with a note on where that file actually has to live.
The same seller and ID listed twice is flagged rather than shipped.
Pick from the presets or add any exchange by its canonical domain.
The account ID that network knows you by — for AdSense, your pub- number.
DIRECT when you contract with them; RESELLER when they sell on your behalf.
Save as ads.txt at yourdomain.com/ads.txt, served as plain text over https.
At the root of your domain, exactly at yourdomain.com/ads.txt, served as plain text. It cannot be in a subdirectory, and crawlers do not look anywhere else. For subdomains that sell their own inventory, each needs its own file.
DIRECT means you have a direct contract with that seller for your inventory. RESELLER means you have authorised them to resell it on your behalf. Getting this wrong is a common cause of a partner being unable to bid, so check the relationship with each network rather than guessing.
Only if you have a mobile app selling ads. It follows the same format and lives at the root of the developer website listed in your app store entry — not on the app itself, which is where people usually go wrong.
It is skipped, silently, with no error anywhere. The rest of the file still works, so the symptom is not a broken site — it is one partner unable to bid on your inventory and revenue that quietly does not arrive.
What people who use the ads.txt Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the ads.txt Generator. It takes half a minute and no account.
Write the first reviewDecode tagged links and check the campaign naming holds together.
Pull the related phrases a piece of content actually uses.
Paste a page and get every meta tag audited in one report.
Compare two pages and find the passages they share.
Build nginx rewrite and return rules from a redirect map.
See the anchor text profile of a page, grouped and ranked.
Turn one image into every favicon size, plus the markup.
Turn a list of questions into valid FAQPage JSON-LD.