Buyers want to know who is selling the impression they bid on. Three tools answer that question: ads.txt (or app-ads.txt), sellers.json and the SupplyChain object. When you join an MCM partner, getting them right is a required step, not a nice-to-have.

ads.txt and app-ads.txt

ads.txt is a plain text file at the root of your domain (example.com/ads.txt). app-ads.txt does the same job for apps and lives on your developer website. Each line names:

  1. the advertising system's domain;
  2. your publisher ID in that system;
  3. the relationship: DIRECT if you control the account, RESELLER if someone else sells on your behalf;
  4. optionally, a certification authority ID.

Google crawls these files regularly and says updates can take up to 48 hours to take effect.

What MCM changes

As part of joining MCM, a child publisher sets up ads.txt for every site it owns. Google's ads.txt guidance is to add the MCM parent as DIRECT, using the child's seller ID. Your partner will give you the exact line to paste.

Skipping this step is costly. Google states that if a site has an ads.txt file and the seller's publisher ID is not listed, Google stops buying ads on that site.

sellers.json

sellers.json is the other side of the coin. It is published by the ad system and lists the sellers it pays, so buyers can match a seller ID in ads.txt with a real business. In Ad Manager, publishers can choose how their seller information appears.

The SupplyChain object

The SupplyChain object travels with each bid request and lists every company involved in selling that impression. Google says it works together with ads.txt and sellers.json to give buyers transparency. For MCM Manage Inventory, Google marks the chain as complete with one node for the child and one for the parent, which requires parents to share their children's seller IDs.

A quick checklist

  • ads.txt exists at the root of every domain you monetize.
  • Your own Google line is present and correct.
  • Your MCM partner's line is present, marked DIRECT, with your child seller ID.
  • Old partners you no longer work with have been removed.
  • For apps, app-ads.txt is on the developer website listed in your store page.
  • You have re-checked the files after any site migration or CDN change.

Common mistakes

  • Putting ads.txt in a subfolder instead of the root.
  • Redirecting ads.txt to another domain without testing it.
  • Copying a partner's line with a typo in the seller ID.
  • Forgetting subdomains or secondary sites.

Where AdGlobeX fits

AdGlobeX Media's onboarding covers both web and app publishers, and correct ads.txt or app-ads.txt setup is part of joining any MCM parent. Getting it right on day one avoids weeks of lost demand.

About to join an MCM partner and want the supply chain right from day one? Begin with an account review application.