Microsoft Copilot
Connect Microsoft Copilot to Google Ads
Add the connector where your team already works, under your own Google sign-in, and ask your first question there.
- Your own Google sign-in
- Where your team already works
- It cannot delete
Setup
Three steps, once
Open the connector settings, paste the URL, and sign in with Google the first time you ask something.
Connect your Google Ads account
Sign up, then sign in with Google itself. You grant access to the accounts you can already open in the Google Ads interface, and nothing widens that.
Add the connector in Microsoft Copilot
Open the connector settings, add a connector of your own, and paste the URL. Whether your workplace lets you add one is your administrator's decision, not ours.
Connector URL https://mcp.adcopilot.cloud/mcpThe same URL for every client. Your own Google sign-in decides what it can reach.
Ask your first question
Start a conversation and ask about the account. Answers are read live, every call is written down, and it cannot delete.
The first turn
What Copilot answers first
You ask in plain words, the connector reads the account live, and the answer comes back with the request beside it.
An illustrative first turn: the assistant reads four connected products.
Google Ads
campaigns · spend
Google Analytics
key events
Search Console
verified sites
Tag Manager
tags · triggers
first read, before any change
Where you stand
- Account
- live, spending daily
- Tracking
- one tag quiet for 11 days
- Search terms
- 18% of spend unchosen
- Schedule
- always on, results are not
Start with the quiet tag.
Illustrative session
Asked in the Copilot chat your team already has open. Your Microsoft identity signs you in; the Google access is your own.
Questions
Policy, identity and limits
Whether your workplace allows it, whose sign-in is used, what it can change, and how to stop it.
That is your administrator's setting, not ours. If connectors of your own are switched off for your organisation, ask the person who owns that policy — we cannot lift it from our side, and we would not want to be able to.
Yours, signed in with Google itself. Your Microsoft identity signs you into the chat; the Google access is separate, granted by you, and withdrawn by you from your own Google account.
What you ask it to, inside limits that hold on our server: it cannot delete, it will not switch on the campaign it built, and it asks for your budget before it builds. Every call is written down, refusals included.
Remove the connector in your own settings, and withdraw the Google access from your Google account. Neither needs us, and both take effect at once.
Ask
Blocked by a policy?
Send the step you are on and what you are seeing, and we will answer.