> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/tips-and-troubleshooting/video-gallery/business-hubs/video-how-to-connect-a-business-hub-for-a-google-ads-manager-account.md). # \[Video] How to connect a business hub for a Google Ads Manager account This video shows how to connect a Google Ads Manager business hub to centrally manage access to it and its assets from Cerby. *** ## Key concepts * With a Google Ads Manager business hub in Cerby, you can import the following user data to centrally and securely manage access to your Google Ads Manager account from Cerby: * Members or users * Native partners * Roles and permissions * Assets, campaigns, and accounts **IMPORTANT:** For a successful onboarding, make sure you meet the following prerequisites before getting started: * An active user account with an **Admin** role in the Google Ads Manager account. * An MCC ID. You can find the ID in the business information or settings by completing the following steps: 1. Log in to Google Ads Manager. 2. The ID is the 10-digit number displayed at the top-right corner of the page next to your profile picture. 3. Copy the ID and remove the dashes between the numbers to get only the numerical value of your ID. For example, if the MCC ID is **`733-123-4567`,** the number you need for the integration is **`7331234567`**. *** {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.cerby.com/tips-and-troubleshooting/video-gallery/business-hubs/video-how-to-connect-a-business-hub-for-a-google-ads-manager-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.