Manage Inventory

Add child sites to Ad Manager

Use site management to add sites
Only available in Google Ad Manager 360.

Add child sites for publishers with the Manage Inventory delegation type to manage and monetize their inventory.

Based on their Ad Exchange enable type, MCM Manage account child partners choose between two setups before ads serve:

  • A child partner without Ad Exchange enabled (or that has had Ad Exchange enabled before) can serve ads without extra setup.

  • A child partner that enrolled for self-signup Ad Exchange must include all domains that they would like to serve ads into the inventory list. These domains must be approved by the Trust and Safety (T&S) team.

Add a child site

Note: Before submitting your child publisher's site for approval, please make sure the site's content is high-quality, original, and attracts an audience.

The site should have unique content that's relevant to its visitors and provide a great user experience in line with Ad Manager policies. If your child publishers' sites repeatedly violate our policies, we may need to move beyond action at the individual page or site level, and take action at the account level.

The site also needs to be crawlable by robots.txt. If you have a disallow in robots.txt for all agents or just Google crawlers, the site review will fail. The site status doesn't specify failure to crawl the site.

To add a child site: 

  1.  Sign in to Google Ad Manager.
  2. Click Inventory and then Sites and then Child sites.
  3. Click New child site.
  4. In “Site URL”, enter your top-level domain without any prefixes, such as example.com.

    If this site has already been added in AdSense, you will be shown a warning that you’ve already added this site. This may disrupt ad serving and require retagging your website.

  5. In “Select child publisher,” enter the child publisher’s name.
    As you type, a list of child publishers appears.
  6. Select the child publisher from the list and then click Save and continue.
  7. You and your child publisher complete one of the following options:
    • The child publisher updates ads.txt
      1. The child publisher sets up an ads.txt file to verify site ownership.
      2. Click Copy and send the copied text to your child publisher.
        Note: In some cases, changes to the ads.txt file take a few days to process. If you get an error message that the ads.txt file isn't updated, please resubmit the site for approval.
    • The child publisher adds a GPT tag to their site
      1. Create a GPT tag using the same format required to tag all inventory delegated through Manage Inventory. Be sure to include both your and the child publisher’s network codes.
      2. Ask your child publisher to place the tag anywhere on the page. The tag can be 1×1 pixel, but it needs to be placed on the live site, not on a test page. The GPT tag must be called immediately upon page load, without requiring additional events to trigger the call.
    • The child publisher adds an HTML <meta> tag to their site

      The value added in the meta tag is the publisher ID and network code of the MCM parent publisher.

      Either one of the following tags is accepted as proof of ownership:

      • <meta name="google-ad-manager-publisher-id" content="{publisher-id}" />
      • <meta name="google-ad-manager-network-code" content="{network-code}" />
  1. To confirm completion, check the box next to “Ads.txt or GPT has been implemented.”

  2. Click Done.

Move sites to a child publisher

Multiple Customer Management parent publishers can move child publisher sites from Sites you own to Child sites for Privacy & messaging. Sites can also be moved between child publishers.

  1. Click Inventory and then Sites.
  2. Navigate to the site you want to move to Child sites and then click Move item.
  3. Select the child publisher associated with your site.
  4. Click Move site to confirm.

Add additional child publisher sites and subsites in Child sites.

When you move a site, all AdSense ads will stop showing on that site and related subsites.

Delete a child site

  1. Click Inventory and then Sites and then Child sites.
  2. In the row for the child site, click Delete.
  3. Click Continue to confirm you want to delete that site.

Check the status of a site in your sites list

Note: After you invite a child publisher to use MCM, make sure your child site is approved and marked "Ready." You should update the GPT tag at least 2 hours after your child publisher's site is approved.

  1. Click Inventory and then Sites and then Child sites.
  2. In the list of sites, find the child site and check its status.
    Tip: You can enter your own search term to quickly find child sites.
Status What it means
Needs review

The child site hasn't been checked yet. Click Review site to start the review process.

Needs attention

You need to fix some issues before the child site is ready to show ads.
Getting ready We're running some checks on the child site. This usually takes a few days, but in some cases can take up to 2 weeks.

Make sure you don't remove the site and resubmit it because this can delay the process. We’ll notify you when the site is ready to show ads.
Ready

The site is ready to show ads. Learn how to create new ad units.

Make sure you follow the Google Ad Manager Partner Guidelines at all times to continue showing ads. You'll find detailed information about policy violations in the Policy center.

Learn how to resolve policy violations in your Policy center

FAQ

Why can't I add my subdomain as a standalone child site?
If you get an error message for your site's URL, the site's platform isn't supported. For some common hosting platforms, such as WordPress.com, you can add the subdomain directly.
Some common hosting platforms include:
appspot.com
at.ua
azurewebsites.net
blog.hu
blog.jp
blox.pl
blogspot.com
cafe24.com
cocolog-nifty.com
com.nl
doorblog.jp
egloos.com
fc2.com
fc2web.com
firebaseapp.com
free.fr
github.io
hateblo.jp
hatenablog.com
hatenablog.jp
hatenadiary.com
hatenadiary.jp
herokuapp.com
infoteur.nl
jp.net
jpn.org
jugem.jp
ldblog.jp
livedoor.biz
livedoor.jp
main.jp
narod.ru
naturum.ne.jp
pixnet.net
sakura.ne.jp
blogs.sapo.pt
sblo.jp
seesaa.net
blog.shinobi.jp
blog.so-net.ne.jp
sourceforge.jp
sourceforge.net
ssl-lolipop.jp
blog.ss-blog.jp
squarespace.com
startpagina.nl
3dn.ru
ti-da.net
tripod.com
tumblr.com
typepad.com
ucoz.ru
ucoz.ua
uol.com.br
web.app
wordpress.com
wpblog.jp
wpengine.com
yolasite.com
xsrv.jp
000webhostapp.com

 

Do I need to add subdomains or subsites if I already have an approved child site for the top-level domain?
No. If the top-level domain has been approved through standard ads.txt verification or GPT verification, and you also want to serve ads on subdomains of the top-level domain, you don't have to add the individual subdomains.
Adding subdomains or subsites is only necessary if:
  • you're only authorized to monetize the subdomain, or 
  • you don't have ads.txt or GPT verification at the top-level domain. 
Are there any inconsistencies with child site approvals?
We heard a number of questions about inconsistencies around MCM site approvals.
For example, why can a child site be disapproved at first, and then approved later when submitted by a different parent? This can happen for various reasons, such as content changes in the child site. 
If a parent publisher has a child site that is currently disapproved, and they disagree with the reason provided, they should request another review in their Ad Manager account.

For mobile apps, can multiple Ad Manager app IDs be declared in the app?

When you set up a new app in Ad Manager, your app must be reviewed and approved before it can fully serve ads. Once the app is approved, the generated Ad Manager app ID is ready to be added in AndroidManifest.xml (Android) or Info.plist (iOS) files.

Only one Ad Manager app ID can be declared at a time. In an MCM context, this means that the app cannot have both the MCM parent and MCM child app IDs, or multiple MCM parent app IDs.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu