How to Locate Google Ads Account ID

Learn how to locate your Google Ads Account ID

Overview

Follow this guide to learn how to locate your Google Ads Account ID.

Using an MMC:

Be sure to check if you are using an MCC as this will determine what Customer ID to use. Follow these steps to learn how to locate the Google Ads conversion account settings to determine this.

If you're using an MCC, first check your "Sub-account Settings" in your MCC. If the Google Ads conversion account says "client", then you must use the Customer ID of the child Google Ads Account. If it says "This manager" then you must use the Customer ID of the MCC Google Ads Account.

📘

Learn More: Manager Accounts (MCC) in Google Ads

Read this guide to learn more about Manager Accounts (MMC) in Google Ads and how to set up cross-account conversion tracking.


How to Find Your Account ID In The Google Ads Interface

Access Google Ads Account Settings:

  • Log into your Google Ads Accounts
  • Navigate to the upper-right hand corner of the homepage. Your Google Ads Account/Merchant ID will be located here.
    • Remove the dashes when entering for your Google Ads server-side destination.
    • (See Figure 1)

Step 1 screenshotFigure 1

How to Access Google Ads Account ID Using an MCC

Access Sub-Account Settings:

  • Begin on your Google Ads homepage and use the left-hand navigation menu to click on the "Accounts" tab.
  • An additional navigation menu will appear, locate and click on the "Sub-account settings" tab.
    • (See Figure 2)

Step 1 screenshot_Figure 2_

Locate Google Ads Conversion Account:

  • Once you have accessed the Sub-account settings in your Google Ads account, navigate to the chart located on the page.
  • Navigate to the column titled "Google Ads conversion account".
    • If the Google Ads conversion account says "client", then you must use the Customer ID of the child Google Ads Account.
    • If it says "This manager" then you must use the Customer ID of the MCC Google Ads Account.
      • (See Figure 3)

Step 2 screenshot

_Figure 3_