How to Connect Google Ad Manager to Microsoft Copilot (No Code)

If you run inventory in Google Ad Manager, you already know the reporting grind. You build a query in the native reporting UI, wait for it to run, then export the result to a spreadsheet. It is slow, and by the time the numbers are ready the question you actually had has often moved on.

Your ad server data also sits in its own silo. Ad Exchange yield, direct-sold performance, and AdSense backfill live in separate reports, so comparing programmatic revenue against direct ad server revenue usually means stitching CSV exports together by hand.

Worst of all, there is no simple way to just ask a plain-language question like “how did viewability trend last month?” and get an answer back. You have to know exactly which report to open and which fields to pull before you see a single number. The fix is connecting Google Ad Manager to Microsoft Copilot with Windsor.ai.

Start for free: connect Google Ad Manager in a couple of clicks at onboard.windsor.ai. Windsor.ai has a free forever plan and no credit card is required.

Before you start

You only need three things to follow this guide:

• A Google Ad Manager account with real reporting data you can authorize.
• A Windsor.ai account. It is free forever with no credit card required, so you can create one in under a minute.
• Access to Microsoft Copilot Studio, where you will add Windsor MCP as a tool.

Connect Google Ad Manager to Copilot with Windsor.ai

The whole setup is no-code and takes a few minutes. Copilot only reads and analyzes your Google Ad Manager data, so nothing you do here changes anything inside Google Ad Manager.

1. Connect the data source in Windsor.ai. Go to onboard.windsor.ai/app/google_ad_manager, sign in, and authorize Google Ad Manager. Pick the account or accounts you want to report on, then click Next.
2. Add Windsor MCP as a tool in Copilot Studio. In Microsoft Copilot Studio, create a new agent, click + Add tool, then + New tool, then Model Context Protocol. Fill in the tool details:
   • Server Name: Windsor MCP
   • Server URL: https://mcp.windsor.ai
   • Authentication: API Key
   • Header name: Authorization

   Click Create, then Add and configure.

3. Create a new connection. Under “Not connected”, choose Create new connection, then enter your Windsor API key with the Bearer prefix, for example: Bearer YOUR_WINDSOR_API_KEY. Use your own key here in place of the placeholder.
4. Start querying. Open a new chat. Copilot asks you to connect to Windsor MCP through the Connections manager. Click Connect, then Submit. Return to the chat, click Retry, and then ask about your data.

The Google Ad Manager metrics that matter

Once connected, Copilot can read and analyze the core publisher fields from your ad server and Ad Exchange. These are the ones most publishers watch:

Metric	What it tells you
Ad Server All Revenue	Total revenue booked through your ad server. This is your headline publisher earnings figure.
Ad server impressions	How many impressions your ad server delivered. It is the volume base for every yield and fill calculation.
Ad server clicks	Clicks recorded by your ad server, paired with impressions to read engagement on served inventory.
Ad server viewable impressions rate	The share of served impressions that were actually viewable. It is a core quality signal for buyers.
Ad server average viewable seconds	How long a viewable impression stayed on screen on average, useful for premium and video inventory.
Ad Exchange revenue	Revenue earned through Ad Exchange, so you can compare programmatic yield against direct ad server revenue.
Ad Exchange CTR	Click-through rate on Ad Exchange inventory, a demand-quality read on your programmatic demand.
AdSense impressions	Impressions filled through AdSense, useful when AdSense backfills unsold inventory.

What to ask Copilot: prompt ideas

Copy and paste any of these into your Copilot chat once the connection is live. Every prompt is read-only reporting, so Copilot answers from your numbers without touching anything in Google Ad Manager.

Summarize my ad server revenue, impressions, and viewability rate for the last 30 days, and show how Ad Exchange revenue compares to direct ad server revenue.

Show my ad server viewable impressions rate and average viewable seconds by week for the last quarter, and flag any weeks where viewability dropped.

Compare Ad Exchange revenue and Ad Exchange CTR against my ad server clicks and Ad Server All Revenue for the last 30 days, and tell me which demand source is delivering better yield.

Bonus: analyze Google Ad Manager alongside your full stack

Windsor.ai connects hundreds of sources, so Copilot can read and blend Google Ad Manager with the rest of your data for a single source of truth. A few realistic, read-only blends:

• Yield across every demand source. Blend Ad Server All Revenue, Ad Exchange revenue, and AdSense impressions in one view to compare direct, programmatic, and backfill earnings side by side, no CSV merging required.
• Revenue against audience. Combine Ad Server All Revenue with Google Analytics 4 traffic to see revenue per thousand pageviews and how audience volume moves your earnings, all in one blended report.
• Cost of the audience you monetize. If you also buy traffic, blend Ad Server All Revenue with your Google Ads or Meta Ads spend for a cross-channel, ROAS-style read on what it costs to acquire the audience that generates your ad revenue.

Conclusion

Once Google Ad Manager is connected to Microsoft Copilot through Windsor.ai, your ad server reporting stops being a spreadsheet chore and becomes a conversation. Ask about revenue, fill, viewability, or how Ad Exchange stacks up against direct ad server yield, and get an answer in seconds, all read-only and always from your current numbers.

Ready to try it? Connect Google Ad Manager and start asking Copilot questions at onboard.windsor.ai. Start for free, free forever, no credit card.