The short answer
DuckDive links one Google Ads account to each of your websites and gives Claude, ChatGPT, Cursor or any MCP agent five account totals through get_google_ads_summary: spend, clicks, impressions, conversions and cost per conversion. Your agent reads them beside the same site's GA4 and Search Console data. Campaign, keyword and search term work stays in Google Ads.
- Screen every account in one conversation, then open Google Ads only where it is needed.
- Ads clicks and GA4 paid sessions rarely match exactly; a gap that suddenly widens is the signal.
- For campaign-level work in one account, Google's own Ads MCP server fits better.
What account-level Ads data answers, and what it does not
People searching for a Google Ads MCP usually want one of two things: to run campaigns from a chat window, or a straight answer to "how did paid do this month, on every site we look after?" without opening a dozen accounts. This page is for the second group.
DuckDive stores each website's Ads totals next to that site's GA4 traffic, Search Console clicks and Local Services Ads leads. Your agent reads all of it through one connection, so "did paid get pricier while organic held?" comes from one site's full picture, not two exports pasted together. It reports; it does not edit ads. Know the boundary before you sign up:
| Question | DuckDive | Where else to answer it |
|---|---|---|
| What did this site spend, and what did a conversion cost? | Yes, account totals for a fixed window | Google Ads overview, one account at a time |
| How does paid compare with the site's GA4 and organic numbers? | Yes, same website, same conversation | Two reports and a spreadsheet |
| Which campaign or ad group moved? | No, account totals only | Campaigns view, or Google's Ads MCP |
| Which keywords and search terms took the budget? | No | Search terms report in Google Ads |
| Pause a campaign, change a bid or budget | No, nothing is edited in Ads | The Google Ads interface |
Local Services Ads has its own page, Local Services Ads data for AI agents. To set both channels' cost per lead in one ledger, use the ad spend versus leads guide.
When Google's Ads MCP server is the better tool
Google's Ads API team publishes its own server in the googleads/google-ads-mcp repository on GitHub. For some jobs it beats DuckDive outright. Its read tools are search, which builds Google Ads Query Language (GAQL) queries, get_resource_metadata and list_accessible_customers. Its write tools create assets and manage labels in two steps: a validate call returns a checksum, and nothing commits until a second call repeats it after you approve.
Google's Google Ads MCP server developer integration guide (last updated November 13, 2026) lists the setup: a Google Cloud project with the Ads API enabled, Python 3.10 or later, and gcloud or OAuth credentials. New projects start on test access, so production accounts need a higher access level. It also says developer tokens were sunset on September 9, 2026, and that the server cannot create, change, pause or enable campaigns, ads, budgets or bids.
| Question | DuckDive | Google's Ads MCP server |
|---|---|---|
| Who runs the server | DuckDive hosts it; you add one URL | You: local process, or your own Cloud Run |
| What you set up first | Continue with Google | Cloud project, API access level, OAuth client or gcloud |
| What it can read | Partly, five account totals | Yes, any field GAQL exposes |
| Changes inside Ads | No | Partly, assets and labels after you confirm |
| Other sources in the same answer | Yes, GA4, Search Console, LSA, Yext, Local Falcon | No, Google Ads only |
| Client accounts under a manager (MCC) | One Ads account linked to each website | Yes, via the optional login_customer_id, one account per query |
| History | Imported when linked, then stored | Live query to the Ads API each time |
| Better fit when | Reading paid results beside each site's analytics and search data | Campaign, keyword and search term analysis, in any account you can reach |
Sources: googleads/google-ads-mcp on GitHub and Google's developer integration guide, checked November 2026.
Manager accounts are not the dividing line. The repository's README says that when your access runs through a manager account, you pass the manager's customer ID in the optional login_customer_id parameter on each call, or set GOOGLE_ADS_LOGIN_CUSTOMER_ID as a default. So an agency can reach every client with Google's server too, one account per query.
The real split is depth against pairing. If your week goes on rebuilding ad groups and auditing search terms, Google's server reads fields DuckDive never stores. If it goes on asking whether paid got pricier while a site's organic clicks and GA4 conversions held, DuckDive already has those three sources filed under the same website. The wider field is in marketing data MCP servers compared, and the live versus stored trade-off in stored history versus live API servers.
DuckDive is also wrong if you need Microsoft Advertising or Meta. Its six sources are GA4, Search Console, Google Ads, Local Services Ads, Yext and Local Falcon.
Five numbers per account, defined
get_google_ads_summary returns five figures for the website you name, over one of six fixed windows, from a week to a year. No custom dates. Each figure keeps Google's definition, quirks included.
- Spend
- What the account was charged in the window. Google Ads labels this column Cost.
- Clicks
- Google's Click: Definition page counts any click on your ad, including its headline or phone number. Invalid clicks, such as accidental or automated ones, are filtered out and not charged.
- Impressions
- Per Impressions: Definition, one is counted each time your ad is shown on a search result page or another site on the Google Network.
- Conversions
- Google's Understand your conversion tracking data page says this column counts primary conversion actions only, and that it is calculated by the time of the click, not the time of the conversion.
- Cost per conversion
- The same page says it is calculated by dividing your total cost by the number in your Conversions column, so anything that moves conversions moves this too.
Click-through rate, cost per click and click-to-conversion rate are not in the output. Your agent divides them out; ask it to show each step so a wrong denominator stands out. The guide to checking your agent's numbers has a routine for that.
Ask your agentPull Duskline Electrical's Google Ads totals for the last 30 days, then work out click-through rate, average cost per click and the click-to-conversion rate from them. Show each division so I can paste it into Monday's client notes.
Tools it calls search get_google_ads_summary
Two settings move the conversions column. Google advises setting only bottom-of-funnel actions as primary, so the count is not inflated. It also recommends counting "One" per click for leads, so a refreshed thank-you page is not counted twice. If cost per conversion suddenly halves, check both before you celebrate.
Worked example: spend rising faster than conversions across sites
Run this screen monthly across every account. Spend creeping up is normal; spend creeping up while conversions stay flat is a leak. The baseline is the prior pace: subtract the last 30 days from the 90-day totals, which leaves the 60 days before, then halve that to get a month.
Ask your agentFor each website with Google Ads linked, compare cost per conversion over the last 30 days with its average over the last 90 days.
Tools it calls list_websites get_google_ads_summary
Which client sites are spending faster than they convert, last 30 days against the pace before that?
list_websitesfinds the six client websites with a Google Ads account linkedget_google_ads_summarylast 90 days, once per siteget_google_ads_summarylast 30 days, once per site
Two sites are paying noticeably more per conversion than their prior pace. Duskline Electrical spent 30% more while conversions dipped 5%, so each one now costs $82.11 against $60.00. Halyard Marine Supply jumped further, from $25.00 to $42.86, for a different reason.
| Site | Spend vs pace | Conv. vs pace | Cost per conv., 30 days |
|---|---|---|---|
| Duskline Electrical | +30% | -5% | $82.11prior $60.00 |
| Halyard Marine Supply | +20% | -30% | $42.86prior $25.00 |
| Brindlestone Fencing | +20% | +12.5% | $80.00prior $75.00 |
| Tumbleweir Pools | -30% | -37.5% | $84.00prior $75.00 |
| Saltmarsh Physio | -2% | -2% | $30.00prior $30.00 |
Duskline is a spending story: budget went up and the extra clicks did not convert. Halyard is a conversions story. Its spend rose by a fifth, yet conversions fell by almost a third, which is more than a modest budget rise explains. Before anyone touches Halyard's bids, check whether a primary conversion action was switched off or its enquiry form stopped sending.
Brindlestone is running ahead too, but conversions nearly kept up: watch, don't act. Tumbleweir lost conversions faster than it cut spend, possibly just the end of pool season. Copperwick Candles has an account linked but no spend, so I left it out.
For Duskline, open change history and the campaigns view next; for Halyard, start with conversion goals. These totals show that something changed, not which campaign.
Recent days undercount
Google files each conversion under its click date, and says reporting can lag 24 to 48 hours, so the newest days in any window are short. Leads that convert days after the click widen that. Rerun a borderline result a week later before cutting a budget.
Run the spend screen on your own accounts
Link each site's Ads account, and your agent can flag the ones spending ahead of their conversions whenever you ask.
Free for 2 sites · No credit card
Paid clicks against GA4 paid sessions
Clients who open both reports often ask why Ads shows more clicks than Analytics shows paid visits. Ads counts clicks on an ad. GA4 counts sessions on your site and files them under a channel; its Default channel group page puts Google Ads traffic into Paid Search when the source platform is Google Ads and the campaign or network is search.
GA4 has to recognize the click first. Google's About auto-tagging page explains how: auto-tagging adds a GCLID parameter to the landing URL, which is stored in a Google Analytics cookie on your domain. With redirects, it says, make sure the GCLID reaches the final landing page. If it does not, the visit happens but GA4 cannot tie it to the ad.
Google's older article on the difference between Google Ads clicks and Analytics sessions, written for Universal Analytics, lists the usual causes:
- Several clicks, one visit. Two quick clicks make one session.
- One click, later visits. A bookmark return can start new sessions with the original ad's details.
- Leaving before the page loads. The click counts; the tag never runs.
- Invalid clicks. Ads drops them; Analytics keeps them as sessions.
So sessions per click is a baseline for each site, not a target. A ratio that holds for months, then drops in one, means something broke between ad and page. Google's article on technical problems with clicks and sessions names a common culprit, a redirect to a mobile site, and says Google has seen many cases where that redirect drops the gclid parameter. The GA4 side, channel by channel, is covered in connecting Google Analytics 4 to your agent.
Ask your agentFor Kettlewood Movers, compare Google Ads clicks with GA4 paid search sessions over the last 30 days; is anything lost between the click and the landing?
Tools it calls search get_google_ads_summary get_ga4_channels get_search_console_summary get_ga4_landing_pages
Worked example: a redirect that lost the paid click
Here is that question for a mover whose site was rebuilt a month ago. Nobody linked the rebuild to paid search, because the Ads account looked healthy.
Kettlewood's Ads clicks are steady but GA4 paid traffic fell. Is something lost between the click and the landing?
searchfinds the Kettlewood Movers website and its idget_google_ads_summaryclicks and conversions, last 30 and last 90 daysget_ga4_channelssessions by medium, last 30 and last 90 daysget_search_console_summaryGoogle organic clicks, last 30 and last 90 daysget_ga4_landing_pagestop landing pages, last 30 and last 90 days
Yes. About 690 paid visits in the last 30 days look to have been filed by GA4 as organic search instead of paid. Clicks held steady, but paid sessions per click fell from 87% to 55%, and organic sessions rose by almost exactly the number that went missing. Prior pace is the 60 days before, scaled to 30.
| Measure | Prior pace | Last 30 |
|---|---|---|
| Google Ads clicks | 2,080 | 2,140 |
| GA4 cpc sessions | 1,805 | 1,170 |
| Sessions per click | 87% | 55% |
| GA4 organic sessions | 3,240 | 3,930 |
| Search Console clicks | 3,060 | 3,020 |
| Google Ads conversions | 96 | 71 |
Search Console clicks barely moved, so the extra organic sessions are not new search demand. Landing pages show the timing: /get-a-quote had 2,960 sessions over 90 days and none in the last 30, while /quote/ appears only in the last 30, with 1,610. That is a URL change. If ads still point at /get-a-quote and the redirect drops the query string, the GCLID never reaches GA4. The google.com referrer usually survives, so those paid visits land as google / organic (or as direct if the referrer is also lost).
Ads conversions fell 26% on flat clicks, which fits if they rely on recognizing the click on the page. I can't see the redirect, so treat this as the lead, not proof.
The fix happens on the website and in Ads, not in DuckDive:
Trace the click from ad to page
- Click one of your own ads. Google's auto-tagging page suggests this test. Once the page loads, look for gclid= in the address bar.
- Point ads at the live URL. Set final URLs to the page that loads, so no redirect sits in the path.
- Keep query strings on redirects. Check the CMS plugin, server or CDN rule; some strip everything after the question mark.
- Check the GA4 tag on the new template. Rebuilt pages can ship without it, or with it stuck behind a consent banner.
- Re-run on the last 7 days. Once fixed, sessions per click should climb back.
Manager accounts and which Ads account belongs to which website
Agencies rarely log in to client accounts one by one. Google's About Google Ads manager accounts page describes a manager account (MCC) as one that lets you view and manage many accounts from one sign-in, and notes that up to 20 Ads accounts can be tied to one email address; beyond that, Google recommends a manager account.
Google's own server walks that hierarchy query by query, with the manager's ID in login_customer_id. DuckDive files things the other way round: the website comes first, and it gets exactly one Google Ads account, the one paying for that domain's clicks, picked from the accounts your connected Google login has access to. You can make the pick, or let your agent propose it. Once an account belongs to a website it says so, and DuckDive asks before reassigning it.
Account names rarely match domains, so let the agent propose matches and approve them yourself:
Ask your agentList every Google Ads account my Google login can reach, show which DuckDive website each one is linked to, and suggest a website for any that are still unlinked. Don't link anything yet.
Tools it calls list_available_sources list_websites
Then check from the other side, so no client misses next month's paid review:
Ask your agentWhich of my websites have no Google Ads account linked, and which have one linked but no spend in the last 90 days?
Tools it calls list_websites get_google_ads_summary
A linked account with no spend is usually a paused client, a test account or a wrong pick at setup. A missing account means your login has no access yet; the guide to Google access for every site covers who invites whom. For the wider review routine, see QBR prep for full-service agencies.
Linking an Ads account to its website, step by step
-
Sign in with the Google login that reaches your Ads accounts
Select Continue with Google. With no DuckDive account yet, that creates one, no form. Agencies: use the login you use for client accounts.
-
Create a website for every domain your ads land on
If one Ads account sends clicks to two domains, it can still belong to only one of them, so choose the domain most of its final URLs use.
-
Link the site's sources, Ads included
Link each site's GA4 property and Search Console site. Link its Google Ads account too, if it runs one. Each link starts importing that source's history, which usually takes a few minutes.
-
Give your AI app the DuckDive connector
The per-app walkthroughs for Claude and ChatGPT cover the connector menus; if you are an admin and want the agent to create the websites and pick the Ads accounts for you, hand it this line:
Give your agent this lineSet up DuckDive for my website. Follow https://analytics.duckdive.ai/
agents.md -
Prove the spend matches before you trust a screen
Once
get_sync_statusshowsgoogle_adsas ready, ask for one site's spend over the last 7 days and set it against the Cost column in Google Ads for the same days. A small gap on the newest day is fine. A zero where Ads shows money almost always means the wrong account was picked in step 3, so fix that link before running the cost per conversion screen.
Handing off to the Google Ads interface for campaign work
A good screen ends with a short list of accounts and a reason to open each. DuckDive stops there. When your agent flags a site, check these in Google Ads, in this order:
- Change history. Filter to the weeks the totals turned; bid strategy, budget and new campaign changes all show here.
- Campaigns, sorted by cost. Account totals hide one campaign doubling while the rest hold.
- Search terms. Broader matching can buy clicks on queries that never convert.
- Conversion goals. Was a primary action added, removed or switched between Every and One?
- Final URLs. After a site change, ads should land without a redirect.
Then tell the agent what you found, such as which campaign took the extra budget and when you paused it. It cannot see that context otherwise.
Spend data, permissions and history
DuckDive reads the data you link. None of its tools edit a campaign, bid, budget or ad, and the connector can't delete data, connect or disconnect your Google account, or email anyone but you. Its actions are setup tasks, such as adding a website or refreshing data, for an Agency Admin or Client Admin who kept "Also allow actions" ticked. Team members only read.
Your AI app gets a DuckDive access token, never your Google password, and sees only websites your account can see. DuckDive does not receive your chat; what the AI provider does with tool results is governed by its own policies. Disconnect any time under AI Connectors, and access stops at once.
Linking an account pulls in its history, and your agent then reads that stored copy rather than hitting the Ads API for every site in every question. The longest window it can ask for is 12 months.
Month-end needs one extra step. Because Google keeps adding conversions to past click dates, ask the agent (admin only) to refresh google_ads for the closing month's last days before you send a client the numbers; it allows one refresh per site per quarter-hour.
What Ads managers ask before connecting
Is DuckDive Google's official Google Ads MCP server?
No. Google's Ads API team publishes its own server, googleads/google-ads-mcp, which you host yourself. DuckDive is a separate hosted connector that reads account totals and sets them beside the same website's GA4 and Search Console data. It is not made by or affiliated with Google.
Can my agent see campaign or search term data, or change bids?
No to both. get_google_ads_summary returns five account totals per website, with no campaign, ad group, keyword or search term rows. None of DuckDive's tools edit anything in Google Ads. Use the Ads interface, or Google's own server, for that work.
Do I need a developer token or a Google Cloud project?
No. You continue with Google, add one MCP address to your AI app and sign in. There is no API key and nothing to host. Google's own Ads MCP server is the one that needs a Cloud project with the Ads API enabled.
We manage clients through a manager account. How does that work?
Use the Google login that already opens your client accounts. Each client website then gets the one Ads account that pays for its clicks, chosen from the accounts that login has access to. If a client's account is not among the choices, that login has not been granted access to it.
Why are my Google Ads clicks higher than GA4 paid sessions?
Ads counts every click, including repeat clicks in one visit, while GA4 counts sessions and only files them as paid search when it recognizes the click. Some gap is normal. A sudden drop in sessions per click usually means a redirect or a missing tag.
Can I try it with one Ads account first?
Yes. One website is free, and no credit card is asked for. Link that site's Google Ads account with its GA4 property and Search Console site, then run this page's questions on your own numbers.
Sources
- googleads/google-ads-mcp, GitHub, checked November 16, 2026.
- Google Ads MCP server: Developer integration guide, Google for Developers, checked November 16, 2026.
- Click: Definition, Google Ads Help Center, checked November 16, 2026.
- Impressions: Definition, Google Ads Help Center, checked November 16, 2026.
- Understand your conversion tracking data, Google Ads Help Center, checked November 16, 2026.
- Default channel group, Analytics Help, checked November 16, 2026.
- About auto-tagging, Google Ads Help Center, checked November 16, 2026.
- [UA] The difference between Google Ads Clicks, and Sessions, Users, Entrances, Pageviews, and Unique Pageviews in Analytics [Legacy], Analytics Help, checked November 16, 2026.
- [UA] Do I have a technical problem with Clicks and Sessions? [Legacy], Analytics Help, checked November 16, 2026.
- Manager Accounts (MCC): About Google Ads manager accounts, Google Ads Help Center, checked November 16, 2026.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.
