Manage Inventory

Update your tags to MCM

The instructions are only applicable if you are presently using Google Publisher Tag on the inventory you are representing. This tag change won't affect your current ad serving.

Once Multiple Customer Management is enabled, the existing Google Publisher Tag should be updated to add the child network code to the ad unit definition on the page in order to use inventory management. The ad unit remains configured in the parent's Ad Manager network. Use the tag generator or manually update the JavaScript.

GPT code sample

  <script async src=""></script>
    window.googletag = window.googletag || {cmd: []};
    googletag.cmd.push(function() {
         .defineSlot('/1234567,1234/Travel', [300, 250], 'div-gpt-ad-1568729559138-0');

The highlighted parameter, 1234, represents the network code for the child publisher. 1234567 represents the parent network code.

In the code on the page, you must add the highlighted parameter to the .defineSlot() function. This will allow the child publisher network to be recognized and help creatives serve correctly when “Manage Inventory” is enabled. No changes to the line items or targeting are necessary.

After you invite a child publisher to use MCM, make sure your child site is approved and marked "Ready." Allow about 4 to 5 hours after child site approval before updating the GPT tag with the child's network code.

Video tag sample,1234/topleveladunit&[placeholder]&vpmute=0&vpa=click&

App tag sample

For MCM Manage Inventory, update the app ad unit code with the parent and child network similar to the display GPT tag. In addition, you should also claim the child publisher's app. The following segment must be placed within the code block: /1234567,1234/parent_ad_unit.

1234567 represents the parent network code, while parent_ad_unit represents the name of the ad unit in the MCM MI parent network.

Refer to the corresponding SDK documentation (Android, iOS) for specific methods to set the ad unit ID within your app.

Note: Parent publishers wishing to use SDK Bidding should consider the added complexity. To receive bid requests, SDK Bidders may need placement information, secure signals, or both. For placement sharing and secure signals, Google supports having a single configuration per network. The configuration is based on the App ID. If the child app uses their Google Ad Manager App ID, the GMA SDK won’t send secure signals with the ad request. If the bidder requires secure signals, the bidder will be filtered in the parent’s auction and won’t get a bid request. Bidders that don’t require signals will be eligible for bid requests.

Create a child publisher report

You can view reporting data broken down by child publisher.
  1. Sign in to Google Ad Manager.
  2. Click Reporting and then Reports.
  3. Click New report.
    The "Historical" report type is selected by default.
  4. Enter a meaningful name for the report.
  5. Select dimensions and metrics:
    • Required: "Child network code" dimension
    • Optional: All other dimensions and metrics
  6. Click Run.

Learn more about Ad Manager reporting.

Was this helpful?

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