The short answer
DuckDive is a Supermetrics alternative for AI agents only on one stretch of ground: Local Services Ads, Local Falcon map grids, and questions that span every Google site you run, read from history it imported earlier. Meta, LinkedIn, TikTok, HubSpot and Salesforce questions stay with Supermetrics, and so does anything that has to land in a Sheet or a warehouse. Most readers end up with both in the same agent.
- Send paid social, CRM and campaign changes to Supermetrics; send lead ads, map grids and cross-site Google questions to DuckDive
- A blended figure, such as cost per lead across Meta and Local Services Ads, needs both connectors in one prompt
- Supermetrics bills sources and accounts per source; DuckDive bills websites
Which connector answers which prompt
Start from the questions, not the logos. These are six prompts a Sheets-first marketer tends to try in the first days with an agent, and the connector that can actually return each one when both sit in the same chat.
| Prompt | DuckDive | Supermetrics |
|---|---|---|
| Meta Ads spend for last month | No, it has no Meta source | Yes, route it here |
| LSA leads, charged leads and spend, last 6 months against the 6 before | Yes, get_lsa_summary | No, no LSA connector found |
| Search Console clicks and position for every site | Yes, list_websites then a stored read per site | Yes, a live query per site, each billed as an account |
| Google Ads cost per conversion beside LSA cost per charged lead | Yes, two tools on one website | Partly, the Google Ads half |
| Create or change a campaign | No, never edits ad accounts | Yes, "Create or modify campaigns" per its MCP docs |
| One cost per lead across Meta and LSA | Partly, the LSA half | Partly, the Meta half |
Sources: Supermetrics MCP server docs, connector directory and knowledge base index, checked November 2026.
The plainest test is a question only paid social can answer.
Ask your agentPull Meta Ads spend for last month.
Tools it calls: none in DuckDive. This one goes to the Supermetrics MCP and its Meta Ads source.
DuckDive cannot answer this prompt. No DuckDive tool returns Meta spend, because Meta is not one of its sources. A well-behaved agent says so and hands the job to Supermetrics. If it offers a Google Ads figure from get_google_ads_summary as a stand-in, stop it there.
The reverse case: lead ads for a single remodeler. Neither Supermetrics' connector directory nor its knowledge base index listed a Local Services Ads source when we checked in November 2026, so this prompt only has one home.
Ask your agentFor Sunderby Kitchens, show Local Services Ads leads, charged leads and spend for the last 6 months against the 6 months before.
Tools it calls search get_lsa_summary
Google bills a charged lead once, and follow-up calls or messages with that customer are not charged again provided there is interaction within 15 days and the contact comes from the same phone number or email address, per its How leads work page; the Local Services Ads data source page explains what that does to the three numbers. Google is also moving LSA into Google Ads in waves from August 2026 into 2027 and says the old performance reports "won't transition to Google Ads" (transition notice), which the same data source page
Then a prompt both connectors can answer, run for a four-brand home improvement group before its Monday meeting.
Ask your agentShow Search Console clicks and average position for every one of my sites over the last 90 days.
Tools it calls list_websites get_search_console_summary
Show Search Console clicks and average position for every one of my sites over the last 90 days.
list_websitesreturns the group's four sites; each one has Search Console attachedget_search_console_summaryrun four times, once per site, last 90 days, from the stored copy
All four sites returned data. Sunderby Kitchens brings in the most clicks. Tarnbrook Cabinet Refacing ranks best on average but shows up for far fewer searches.
| Site | Clicks | Avg position |
|---|---|---|
| Sunderby Kitchens | 9,840 | 14.2 |
| Wexcombe Tile and Bath | 5,407 | 18.9 |
| Ferrowick Countertops | 3,115 | 21.7 |
| Tarnbrook Cabinet Refacing | 1,962 | 11.8 |
I kept the four positions separate. A plain average of them would weigh Tarnbrook, with the smallest footprint, the same as Sunderby, with more than five times its impressions.
Through Supermetrics the same prompt becomes four live queries, and four sites mean four accounts against your plan. What DuckDive returns for search, and what it leaves out, is on the Search Console data source page.
The last single-connector prompt puts Google's two ad products side by side for one site.
Ask your agentFor Sunderby Kitchens, put Google Ads cost per conversion next to LSA cost per charged lead over the last 90 days. Which one costs less per lead?
Tools it calls get_google_ads_summary get_lsa_summary
Treat the answer as directional. An Ads conversion is whatever action you told Google Ads to count, while a charged lead is a contact Google billed you for. Cousins, not twins.
Worked example: one cost per lead from two connectors
This is the prompt that pushes a Supermetrics user to add a second connector instead of swapping. Sunderby Kitchens promotes the same remodeling offer through Meta lead forms and through Local Services Ads. The owner wants a single figure for the quarter: what a lead costs across both. Meta sits behind Supermetrics, LSA behind DuckDive, and neither can finish the sum alone.
Ask your agentFor Sunderby Kitchens, get Meta Ads spend and Leads (form) for the last 90 days through Supermetrics, and Local Services Ads spend and charged leads for the last 90 days through DuckDive. Give me one blended cost per lead and label which connector supplied each number.
Tools it calls search get_sync_status get_lsa_summary in DuckDive, then a Facebook Ads query through the Supermetrics MCP
Give me one blended cost per lead across Meta and Local Services Ads for the last 90 days, and label which connector supplied each number.
searchDuckDive: finds the Sunderby Kitchens website and its idget_sync_statusDuckDive: reports the last day the stored LSA data coversget_lsa_summaryDuckDive: spend and charged leads, last 90 days, from the stored copySupermetrics MCPa live Facebook Ads query for the same 90 days, ending on that last stored day
Across both channels a lead cost $75.00 over the last 90 days. Local Services Ads was the cheaper half per lead; Meta brought slightly more leads for more money.
| Channel | Spend | Leads | Per lead |
|---|---|---|---|
| Meta, form | $8,460 | 104 | $81.35 |
| LSA, charged | $6,915 | 101 | $68.47 |
| Blended | $15,375 | 205 | $75.00 |
I stopped the Meta query on the last day DuckDive had LSA data for, so both rows cover the same 90 days. Meta's row counts form leads only, not Website Leads. Someone who filled in a Meta form and later rang through your LSA listing is in both rows, so 205 may overstate how many people you reached.
The routing shows in the tool calls: three DuckDive reads, then one Supermetrics query. If the list shows only one connector, the agent improvised half the figure, and you should ask where that half came from.
Four decisions behind a blended figure you can trust
- Line up the dates. DuckDive answers through its last import, while Supermetrics queries whatever dates it is sent. Have the agent read
get_sync_statusfirst and end the Meta query on the same day. - Choose one Meta lead metric. Supermetrics' note on Facebook Ads Results data warns that some metrics "have multiple values, like "Leads (form)" and "Website Leads"", and that matching Ads Manager means checking "your attribution setting is the same in Facebook". Name the metric in the prompt.
- Divide LSA spend by charged leads. Google's LSA reports help describes charged leads as the ones you were billed for. Dividing by every lead, billed or not, flatters the LSA half.
- Say out loud that people overlap. Two platforms each count their own leads, so the blended total is lead events, not unique customers. Your CRM is the place to deduplicate them.
None of these choices is stored anywhere unless you store it. Put the definitions in the agent's standing instructions, next to the routing rule in the setup steps below, so next quarter's figure is built the same way.
Supply the half of the figure Supermetrics cannot see
Link one site that runs Local Services Ads, free, and your agent can blend it with the Meta numbers it already pulls.
Free for 2 sites · No credit card
When the Sheet and the agent disagree
Sooner or later someone pastes the agent's figure next to the Supermetrics tab, and the two do not match. Usually neither is wrong. They were read from different places, for different dates, at different times.
A Supermetrics user's numbers can sit in three places: the Sheet or Looker Studio report as of its last refresh, a warehouse or Supermetrics Storage if you pay for one, and the ad or analytics platform itself. The Supermetrics MCP goes to the platform. Its product page says it "only presents data from successful, live API calls to the source marketing platform" (as published, checked November 2026). So Claude, asking through Supermetrics, never opens your Sheet; it calls the platform again with your login, and a failed query is reported rather than guessed. Storage is a separate product: the Storage docs say it "helps you store your data in one centralized place" and is "part of the Supermetrics Enterprise package", and they describe Looker Studio and Power BI reading from it, not the MCP.
DuckDive keeps its own copy. When a source is linked, it imports that source's history, and the MCP tools read the copy one website at a time, so a group-wide question is a quick loop over stored rows rather than a burst of requests to Google. The cost is that the copy is only as current as its last import. If a figure trails your tab, an admin can ask DuckDive to pull a recent stretch again, anywhere from a single day to a month back, and get_sync_status reports how current each source is. For quotas and the rest of the mechanics, see our stored-versus-live comparison.
| Question | DuckDive | Supermetrics MCP |
|---|---|---|
| Source of the numbers | A copy imported when each source was linked | A live call to the platform's API |
| Opens your Sheet or Looker report | No, reads its own copy | No, calls the source again |
| Newest possible figure | Partly, as of the last import | Yes, whatever the platform serves now |
| Stored history on your plan | Yes, kept per website | Partly, Storage sits in Enterprise |
Sources: Supermetrics MCP page and Supermetrics Storage docs, checked November 2026.
Here is what a mismatch looks like when you take it apart, using the Sunderby Kitchens search tab.
| Check | Sheet tab "GSC Sunderby" | Agent, through DuckDive |
|---|---|---|
| Clicks shown | 10,415 | 9,840 |
| Dates | July 1 to September 30, a calendar quarter | Last 90 days, up to the latest import |
| Freshness | Last scheduled refresh, with Search Console's reporting lag | As of the last import |
| Search Console property | Domain property, every subdomain | URL-prefix property for the www site |
Two of those rows explain most gaps. The dates differ because a tab built for a quarterly review holds calendar months, while DuckDive's windows roll back from today. The property differs because Google counts them differently: a Domain property "aggregates data for all subdomains, protocols, and subpaths", while a URL-prefix property is limited to addresses that begin with the exact prefix you typed, http or https included, per Google's Search Console property help. The remaining rows are timing. Supermetrics' Search Console notes list an "API delay: 2 days", and its refresh frequency doc ties freshness to your subscription and to each source's own cadence.
Before you call either number wrong
Ask the agent to restate the exact dates it used and which Search Console property it read, then rebuild the tab for the same span on the same property. A gap that survives both checks is worth a question to support; a gap that disappears was never a data problem.
Counting your roster in each plan's unit
Before either sales call, write down what you run and translate it into each vendor's billing words. Supermetrics' pricing page showed these tiers when we checked in November 2026:
- Starter: $59 a month billed monthly, or $44 a month billed yearly. One core destination, 2 data sources, 2 accounts per source, 1 user, 1,000 AI credits.
- Growth: $222 billed monthly, or $177 a month billed yearly. One core destination, 7 data sources, 7 accounts per source, 2 users, 4,000 AI credits.
- Enterprise: quote only, with custom sources and accounts and warehouse destinations such as Snowflake and BigQuery.
Three details move the count. The pricing page warns that "The definition of an "account" varies by data source." For search, Supermetrics' Search Console notes pin it down: "each Site is considered a separate account within the connection." And the pricing page says AI credits pay for Supermetrics' own AI features, because "Chatting with AI tools like Claude and ChatGPT doesn't use credits."
Destinations are the other line to read. Starter and Growth each include one core destination, and for many readers that slot already holds Sheets. Supermetrics' Claude guide says that to add AI chats you can add a destination, "upgrade your subscription", or "swap an existing destination to AI chats". The MCP page's FAQ says the MCP is "included in all Supermetrics plans that include Data API access". Ask which of those applies before assuming the agent rides on your Sheets seat.
| What the group runs | Supermetrics counts | DuckDive counts |
|---|---|---|
| 4 Search Console sites | 1 source, 4 accounts | Inside the 4 websites |
| 4 GA4 properties | 1 source, 4 accounts | Inside the 4 websites |
| 2 Google Ads accounts | 1 source, 2 accounts | Inside the 4 websites |
| 1 Local Services Ads account | No connector found | Inside Sunderby Kitchens |
| 1 Meta ad account | 1 source, 1 account | Not supported, stays in Supermetrics |
| Totals | 4 sources, up to 4 accounts each | 4 websites |
Set that against the published limits. Four sources with up to four accounts each is past Starter's 2 and 2, and inside Growth's 7 and 7. A fifth brand keeps you inside Growth and takes DuckDive from four websites to five. Do this count on your own roster before either vendor quotes you.
Source coverage, row by row
The overlap is narrower than the two logos suggest. Supermetrics stretches outward into paid social, CRM and ecommerce. DuckDive goes deeper into the local layer: lead ads and map grids. Both read GA4, Search Console and Yext. The DuckDive column names the tool your agent calls and the Sheets tab it does the work of.
| Source | DuckDive | Supermetrics |
|---|---|---|
| Google Analytics 4 | Yes, get_ga4_overview and two siblings do the work of a tab split by day, channel and landing page | Yes, connector with full field list |
| Search Console | Yes, get_search_console_summary, _keywords and _pages match a totals, queries and pages tab | Yes, many more dimensions, last 16 months |
| Google Ads | Partly, get_google_ads_summary is the account total row, not the campaign tabs | Yes, campaign-level data, plus creating or changing campaigns |
| Local Services Ads | Yes, get_lsa_summary replaces the tab people fill by hand from the LSA dashboard | No, no connector in its docs |
| Yext | Partly, get_yext_summary and get_yext_reviews give listing status and review counts, no review text | Yes, with a Yext app and API key |
| Local Falcon | Yes, get_local_rankings gives each keyword's map rank and top-3 share, a tab no Supermetrics connector fills | No, no connector in its docs |
| Meta, LinkedIn, TikTok ads | No | Yes |
| HubSpot, Salesforce, Shopify | No | Yes |
| Google Business Profile | No | Yes, listed as Google My Business |
Sources: Supermetrics MCP page, Search Console connector, Yext connection guide, connector directory, knowledge base index and MCP server docs, all checked November 2026.
Supermetrics' MCP page says it reaches "all marketing data sources available through the Supermetrics Data API", and its Search Console connector page lists the MCP and Claude as destinations, so search questions work through either one. We found no Local Services Ads or Local Falcon guide in the knowledge base index or the connector directory as of November 2026. If one appears, this table changes.
Hold the table up against your workbook. If most tabs are Meta and LinkedIn spend, Supermetrics carries the load and DuckDive adds little. If the tabs you update by hand are lead ad counts and map rank screenshots for service-area clients, those are exactly the rows Supermetrics leaves blank.
Ask your agentGo through my DuckDive websites one by one and tell me where Local Services Ads or Local Falcon is still unlinked, so I know which hand-filled tabs the agent can take over.
Tools it calls list_websites
Keeping Supermetrics for Sheets and warehouses
Most Supermetrics users should not switch. Every Sheets tab, Looker Studio report and warehouse transfer can stay exactly as it is. DuckDive goes in as a second connector in the same agent, and each question goes to the one built for it.
Supermetrics' Claude guide already tells you: "If you've connected more than one data tool, mention Supermetrics in your prompt by name". Do the same in reverse, and say "in DuckDive" when you want the stored, local or every-site answer.
Adding DuckDive takes five steps, none of them inside Supermetrics.
-
Reuse the Google login behind your Supermetrics connections
Supermetrics reached your GA4 and Search Console data through a Google login. Choose Continue with Google on the DuckDive sign-up page with that same account, and the properties it can already see are the ones you can link.
-
Work down the account list you already keep
The accounts in your Supermetrics Google connections are a ready-made checklist. Each domain on it becomes one DuckDive website, and the analytics property, search property, ad account and lead-ad account behind that domain attach to it where they exist. Yext listings and Local Falcon grids hook up on their own screen, only for the sites that use them. Attaching a source kicks off its history import, which usually wraps up within a few minutes.
-
Connect DuckDive in the agent that already has Supermetrics
Add a custom connector, sometimes called a remote MCP server, with the URL
https://api.duckdive.ai/mcp, then continue with Google. Any Claude plan works; ChatGPT requires a Business or Enterprise plan. Each app files this setting in a slightly different place and moves it now and then, so look in its settings under Connectors, Apps or MCP. For Claude, the one-click link is on our Claude setup page. Or hand the whole job to the agent and let it set DuckDive up:
Hand this to your agentSet up DuckDive for my website. Follow https://analytics.duckdive.ai/
agents.md -
Confirm every import finished
Before the first real question, have the agent check that nothing is still loading. Setup actions need an admin account; read access is enough for everything after.
Ask your agentIn DuckDive, list each of my sites with every linked source and how recent its data is, and flag anything still importing before I compare it with my Supermetrics sheet.
Tools it calls
list_websitesget_sync_status -
Write the routing rule and the blend rules down once
Put a short block in the standing instructions your agent reads at the start of each chat: paid social, CRM and campaign edits go to Supermetrics; Local Services Ads, Local Falcon and questions across all sites go to DuckDive; blended cost per lead uses Leads (form) and LSA charged leads over matching dates. You stop naming connectors in every prompt, and the agent stops guessing.
Weighing other connectors too? The Power My Analytics comparison counts billing units for another stored-data connector, the AgencyAnalytics comparison is about client reporting, and our roundup of marketing data MCP servers puts official, community and hosted options in one table.
Jobs Supermetrics does better
For plenty of teams, Supermetrics alone is the right answer, and adding a second connector is just one more thing to maintain.
Stay with Supermetrics alone if
- Paid social is most of the budget. Meta, LinkedIn, TikTok, Pinterest and Snapchat ads are on its MCP page. DuckDive reads none of them.
- Revenue lives in a CRM or store. HubSpot, Salesforce, Shopify and Klaviyo connect through Supermetrics. DuckDive has no CRM or ecommerce source.
- You want the agent to build or adjust campaigns. Supermetrics' MCP docs say it can "Create or modify campaigns", with new ones starting paused. DuckDive's tools read data and set up DuckDive itself; none of them touches an ad account.
- The warehouse is the product. Transfers to BigQuery, Snowflake and other destinations are core Supermetrics work. DuckDive does not load data into your warehouse.
- You need fine-grained Search Console or Ads cuts. Supermetrics' connectors offer a much longer field list for each source. DuckDive returns a fixed set: totals, top queries and top pages for search, and one account summary for Ads.
- Exact dates matter. DuckDive takes fixed windows only, so a launch week from the 3rd to the 9th is a job for a live query.
- Procurement asks for certificates. Supermetrics' MCP page lists SOC 2 Type II and ISO 27001.
What DuckDive does not do
Sheets, warehouses and agents: common doubts
Does the Supermetrics MCP read the data already in my Google Sheets?
No. Supermetrics says its MCP only presents data from successful, live API calls to the source platform. Your agent gets a fresh pull from the platform, not the numbers in your Sheet, so the two can differ by a refresh or a date window.
Is there a Supermetrics MCP for Claude?
Yes. Supermetrics documents a Claude connector you can find under Customize, then Connectors, and a general MCP server for other clients. Its MCP page says the MCP is included in plans that include Data API access, with a 14-day trial and no card, as checked in November 2026.
Can Supermetrics and DuckDive sit in the same agent?
Yes. Most MCP clients let you add more than one connector, and the model chooses between them from each tool's description. Name the connector in your prompt when a question could go either way, or write a standing routing rule once so the agent sends paid social to Supermetrics and local or multi-site Google questions to DuckDive.
Can one prompt use both connectors?
Yes, as long as both are connected in the same chat. The agent calls each in turn and combines the results, as in the blended cost per lead example above. Check the tool calls it lists: both connectors should appear, and the dates should match.
Can DuckDive feed my Google Sheets or BigQuery?
No. DuckDive is a data layer for AI agents, not a pipeline into spreadsheets or warehouses. Keep Supermetrics for Sheets, Looker Studio and warehouse transfers.
How far back can my agent ask in DuckDive?
A year is the longest an agent can ask about today. The agent picks from six preset spans, from one week up to one year, each ending at the most recent import. DuckDive pulls each source's past data at the moment you link it. Search Console itself keeps only 16 months, a limit Supermetrics also notes, so no connector can bring back older search data.
Which AI apps can connect to DuckDive?
Claude works on any Claude plan. Claude Code and Cursor connect too. ChatGPT connects only on Business or Enterprise, not on its Free or Plus tiers. Any other client that accepts a remote MCP server with OAuth can use https://api.duckdive.ai/mcp, and the login is a Google sign-in rather than a pasted key.
What does adding DuckDive cost next to my Supermetrics plan?
Your Supermetrics bill stays the same. A single DuckDive site is free and asks for no card; more sites are billed per website, as the pricing section shows. Start with a site that runs Local Services Ads or Local Falcon.
Sources
- Supermetrics MCP: connect AI to your marketing data (supermetrics.com), checked November 16, 2026.
- Supermetrics MCP server: Setup and connectivity (docs.supermetrics.com), checked November 16, 2026.
- Supermetrics for Claude (docs.supermetrics.com), checked November 16, 2026.
- About Facebook Ads Results data in Supermetrics (docs.supermetrics.com), checked November 16, 2026.
- Supermetrics Storage (docs.supermetrics.com), checked November 16, 2026.
- Good to know about Google Search Console (docs.supermetrics.com), checked November 16, 2026.
- About data source refresh frequency (docs.supermetrics.com), checked November 16, 2026.
- Google Search Console Connector & Integration (supermetrics.com), checked November 16, 2026.
- Yext connection guide (docs.supermetrics.com), checked November 16, 2026.
- Supermetrics Connectors & Integrations (supermetrics.com), checked November 16, 2026.
- Supermetrics knowledge base index (llms.txt) (docs.supermetrics.com), checked November 16, 2026.
- Supermetrics pricing (supermetrics.com), checked November 16, 2026.
- Add a website property to Search Console (support.google.com), checked November 16, 2026.
- How leads work (support.google.com), checked November 16, 2026.
- View reports on Local Services Ads (support.google.com), checked November 16, 2026.
- Local Services Ads transition to Performance Max campaigns with pay-per-lead goals (support.google.com), checked November 16, 2026.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional. Supermetrics is a trademark of its owner and is named here only to compare published features.
