The short answer
Sign in with Google, link each site's GA4 property in DuckDive, and connect your agent to DuckDive's MCP server. Your agent can then read sessions, conversions, conversion rate, channel or source splits and top landing pages for any linked property, from history DuckDive already imported, with no exports and no Google Cloud project.
- Three GA4 tools cover totals, channels and landing pages; device, geography, events and revenue are not included
- What GA4 now calls key events, the tools call conversions, so your key event setup decides the answer
- Fix unwanted referrals in GA4 before you trust any source-level answer
What your agent gets from GA4, metric by metric
DuckDive sits between your agent and your Google data. You link a GA4 property to a website once; DuckDive imports its history and keeps it. Whether you ask about one property or twenty, the answer comes from that saved copy, so a twenty-site question is not twenty fresh trips to Google. The DuckDive home page covers the other five sources.
For GA4, the agent gets three data tools. Each reads one website over a fixed window.
get_ga4_overview: the daily line
Sessions and conversions for every day in the window, plus totals and a conversion rate for the whole period. This is the tool for "is it up or down", "which day did it break" and "what was the rate last quarter".
get_ga4_channels: where sessions came from
Sessions and conversions split by channel. It has one switch, group_by. Left on its default, medium, you get the channel view. Set to source, you get the individual referrers, such as a search engine or a partner's domain.
get_ga4_landing_pages: where sessions started
The top landing pages ranked by sessions, each with conversions and conversion rate. It returns 25 rows unless you ask for more, and up to 100 per call.
- Sessions
- Google defines it as the number of sessions that began on your website or app. A session ends after 30 minutes of inactivity by default (About Analytics sessions).
- Conversions
- The tools' word for the events you marked as key events in GA4. Google counts key events as the number of times users triggered one, so one session can add several.
- Conversion rate
- The rate the tools report beside sessions. Read the key events section below before you compare it with GA4's own session key event rate.
- Channel
- GA4's rule-based bucket for traffic, such as Organic Search or Referral. The default channel group rules mostly look at source and medium.
- Traffic source
- The site that referred the session, for example a search engine or another website's domain.
- Landing page
- Google's definition: the page path tied to the first page view in a session. It shows as (not set) when a session has no page_view event.
What is left out, and where to get it instead
The GA4 tools cover date, channel or source, and landing page. That answers most "how are we doing" questions, not every GA4 report. Know the edges, because an agent that guesses past its data is worse than one that says no.
| You want | DuckDive GA4 tools | Where to get it |
|---|---|---|
| Mobile vs desktop split | No, no device dimension | GA4 reports, or Google's own GA MCP server |
| Country or city | No, no geography | GA4 reports, or Google's own GA MCP server |
| Every event and its parameters | No, conversions only | GA4 Events report or Explorations |
| Audiences | No | GA4 Admin and audience reports |
| Ecommerce revenue and items | No, no revenue fields | GA4 monetization reports |
| A custom window, like one promo week | Partly, fixed windows of 7 days to 12 months | GA4 date picker |
| More than 100 landing pages | Partly, 100 rows per call | GA4 export or Explorations |
| The same question across many properties | Yes, reads stored history per site | Google's GA MCP server: partly, it fetches each property live on every question |
Sources: DuckDive's MCP tool definitions; Google Analytics MCP server guide, checked November 2026.
The fixed windows are last7days, last14days, last30days, last90days, last6months and last12months. If your question is "Black Friday week versus the week before", the agent cannot pin those dates. Ask about the last 7 days on the Monday after, or look it up in GA4 directly.
Conversions in the tools, key events in GA4
Google renamed the idea. Its help center now says events that measure actions important to your business are called key events, and keeps the word conversions for what Google Ads measures. DuckDive's tools still say conversions. When your agent reports conversions from GA4, it is reporting key events.
That makes your key event list the single biggest lever on every answer. Three facts from Google's key events help page (as of November 2026) matter here:
- You mark a key event in Admin under Events, by clicking the star next to it.
- Marking one is not retroactive. It counts from the time you mark it and does not change past data.
- A standard property can mark up to 30 events as key events.
The second point bites on stored history. If you starred generate_lead in March, any window that reaches back before March will show a jump that never happened. Ask your agent for the daily line first, and look for a step change on the day the key event was added.
Two kinds of rate
Google counts key events as occurrences, but its session key event rate counts sessions in which any key event happened. A form that fires twice per submit doubles conversions while that session rate stays put. If conversions come close to sessions, suspect double firing before you celebrate.
Ask your agentSanity check my GA4 setup: for every website I have in DuckDive, pull total sessions and conversions for the last 30 days and flag any property where conversions are more than half of sessions, or where conversions are zero.
Tools it calls list_websites get_ga4_overview
Worked example: channel mix across six properties
This is the question GA4 makes slow. Each property lives on its own, and the roll-up properties that combine several are a 360 feature (our guide on comparing GA4 properties without 360 covers the workarounds). Through DuckDive, the agent lists your websites, then reads the channel split for each one from stored history.
Ask your agentBreak down sessions and conversions by channel group for each of my six properties over the last 90 days, and tell me which property gets the largest share of its conversions from referrals.
Tools it calls list_websites get_ga4_channels
Which of my six properties leans hardest on referrals for its conversions, last 90 days?
list_websitesfinds the six websites and confirms each has GA4 linkedget_ga4_channelsrun once per website, last 90 days, default channel view (six calls, all from stored data)
Pebblecrest Tutoring stands out. 199 of its 486 conversions came from Referral, far above the other five. Marram Dune Holiday Lets is second, which fits a business listed on booking sites.
| Property | Conversions | From Referral |
|---|---|---|
| Pebblecrest Tutoring | 486 | 41% |
| Marram Dune Holiday Lets | 402 | 18% |
| Tamsin Row Alterations | 97 | 12% |
| Cindervale Guitar School | 233 | 9% |
| Sablewood Optics | 1,212 | 6% |
| Scorchmoor Hot Sauce | 611 | 4% |
That 41% deserves a second look before anyone credits a partner. The channel view cannot say which referrers sit behind it, so ask for Pebblecrest's traffic sources next.
There is no portfolio-wide tool. The agent made one call per property, each reading DuckDive's store instead of running a live report. Why that matters at 30 or 50 properties, quotas included, is laid out in stored history vs live API MCP servers.
Run that channel table on your own properties
Link your GA4 properties once, then ask which site depends most on one channel without opening six tabs.
Free for 2 sites · No credit card
Landing pages with sessions and conversion rate
This tool answers "where do people arrive, and does that page earn its traffic". It ranks by sessions, so busy pages that never convert sit near the top.
Ask your agentShow the top 25 landing pages for Sablewood Optics by sessions in the last 30 days and mark the ones with zero conversions.
Tools it calls list_websites get_ga4_landing_pages
| Landing page | Sessions | Rate |
|---|---|---|
| / | 9,120 | 2.3% |
| /frames/round | 3,480 | 2.8% |
| /blog/measure-your-pd | 2,960 | 0.0% |
| /lenses/blue-light | 1,740 | 1.8% |
| /try-on | 1,310 | 0.0% |
| (not set) | 420 | 0.7% |
Two zeros, two different stories. A how-to article that converts nobody is normal; people came to measure something, not to buy. A product page like /try-on with real traffic and no conversions at all is more often a tracking gap or a broken button. Open that page, complete the action yourself, and check that the key event fires.
The (not set) row is not a page. Google says it appears when a session has no page_view event. If that row grows, look for tags that send events without a page view.
Landing pages tell you what happened after the click. For what happened before it, the matching tools on our Search Console integration page show which queries and pages earn clicks in Google search.
Medium or source: choosing the right channel view
A channel is a bucket; the source is what is in it. Channels are fine until a number looks odd. Use this to pick:
Which view to ask for
- Mix over time. Use channels. "Is organic growing as a share of sessions" is a channel question.
- Comparing properties. Use channels. Source lists differ per site and do not line up in one table.
- A spike or drop inside one channel. Switch to source. One referrer or one search engine usually explains it.
- Crediting a partner or affiliate. Use source, and name the partner's domain in your question.
- Referral looks too good. Use source. Checkout pages, login pages and email domains hide in Referral.
- Big Unassigned share. Use source. GA4 files traffic as Unassigned when no channel rule matches, which often means messy campaign tags.
Ask your agentWhich traffic sources, not channel groups, sent Sablewood Optics' converting sessions in the last 14 days?
Tools it calls list_websites get_ga4_channels
Say "sources, not channel groups" plainly, as above, and the agent sets group_by to source. The tool does not join source to landing page, so the tools cannot say which pages a given referrer landed on; the agent can only line up the two lists and infer, as in the example below.
Worked example: a checkout provider listed as a referral
Back to the tutoring site. Its referral share looked like a partner program paying off. It was not. Google lists third-party payment processors as a textbook case for unwanted referrals.
Pebblecrest's referrals look too good to be true. Which referring sites got credit for its conversions in the last 30 days, and do any landing pages look wrong?
get_ga4_channelsPebblecrest, last 30 days, grouped by traffic sourceget_ga4_landing_pagesPebblecrest, last 30 days, top 25 by sessions
Most referral credit belongs to your own checkout. pay.tillwise.example, where parents pay for a lesson block, got credit for 58 of 168 conversions from only 72 sessions.
| Source | Conversions |
|---|---|
| 52 | |
| pay.tillwise.example | 58 |
| (direct) | 31 |
| newsletter | 12 |
| bing | 9 |
| maplehill-parents.example | 6 |
The landing pages agree. /booking/confirmed shows up as a landing page with 41 sessions and 37 conversions. Nobody lands on a confirmation page on purpose. Those are parents coming back from the payment page after a new session started.
The one real referrer is the parents' forum, with 6 conversions. Add the checkout domain to GA4's unwanted referrals list.
How to fix it, and what the fix will not do
Google's steps, as of November 2026: in Admin, open Data streams and pick the web stream. Then Configure tag settings, Show all, List unwanted referrals. Add the checkout domain and save. You need Editor access or higher on the property, and a web stream takes up to 50 unwanted referrals.
Expect some lag. Google explains that people who first arrived from that domain can keep being credited to it on later visits, because of last non-direct click attribution. Our reading is that the change does not rewrite sessions GA4 has already processed, and DuckDive keeps a copy of what GA4 reported, so Pebblecrest's earlier windows will still show the checkout domain. Write down the day you added it and compare only windows that begin after that day.
If the checkout runs on a domain you own and can tag, the better fix is cross-domain measurement, which carries the same user and session across both domains. Unwanted referrals is for domains you cannot tag.
One GA4 property per website
DuckDive files everything by website. Each website links to one GA4 property, and no property can serve two websites at once. Try to link a property already in use and DuckDive will not move it unless you say yes, so two websites never silently report the same traffic.
If one property tracks two domains through cross-domain measurement, that is one website in DuckDive. Here is the setup end to end.
-
Sign in with Google
Use Continue with Google on the DuckDive sign-up page. A single consent screen from Google handles sign-in, opens a DuckDive account for first-timers, and grants access to your Analytics and Search Console data.
-
Add each website
Add the site by its address, in the app or by asking your agent, which uses
add_website. Adding a site imports nothing yet. -
Link its GA4 property
list_available_sourceslists every GA4 property your connected Google logins can reach, with the likely match for that domain first. A clear, unused match can be linked straight away withconnect_website_sources. While you are there, attach the matching Search Console site, plus any ad accounts (Google Ads, Local Services Ads) that site actually spends on. -
Wait for the GA4 backfill
The moment a property is linked, DuckDive begins copying its past data. Expect minutes for most properties and longer for one with years of traffic. To check on it, ask your agent for
get_sync_status: it reports, per source, whether the copy is done, still running or broken, plus the date of the newest data it holds. -
Connect your agent and ask
Add DuckDive's MCP server,
https://api.duckdive.ai/mcp, to your agent and, once the DuckDive window appears, pick Continue with Google. You never paste an API key. Our guide to connecting Claude has a link that fills the connector in for you. Each app files this setting under its own menu, and the names move between releases; it is usually called Connectors, Apps or MCP.
If your agent should do steps 2 to 4 for you, keep "Also allow actions" ticked when you connect. Setup actions need an admin account. Team members can read but not change anything.
Ask your agentFor each site in DuckDive, which GA4 property feeds it? Then show me any GA4 properties my Google login can see that are not linked to a website yet, and which website each one probably belongs to.
Tools it calls list_websites list_available_sources
GA4 points people check before linking a property
DuckDive stores what GA4 reports; it does not clean it. Ten minutes in GA4 Admin first saves you from an agent repeating a tagging mistake across a year of history.
Before you link a GA4 property
- Right property. Make sure it is the live site's property, not a staging or test one with a similar name.
- Key events starred. Mark the events that mean a lead, a booking or a sale. Remember the change is not retroactive.
- No duplicate firing. Submit your main form once and confirm the key event counts once.
- Unwanted referrals listed. Add payment, booking and login domains that send people back to your site.
- Cross-domain set. If checkout runs on a second domain you own, tag both with the same stream.
- Campaign tags tidy. Check that utm medium values follow GA4's channel rules, so paid and email traffic do not land in Unassigned.
- Access in place. Your Google login must see the property. If it cannot, a property admin adds you as a user.
Running many properties
Make this checklist your standard, then run the sanity-check prompt above across every site monthly. The outlier is usually the property that broke. Teams reporting to executives can see how that fits their week on our page for in-house marketing teams.
When the GA4 tools are not the right fit
If your questions need device, country, event parameters, audiences or revenue, DuckDive's GA4 tools cannot answer them today.
For deep work on one property, Google's own Analytics MCP server is the stronger tool. Google's guide describes it as read-only and able to query reports and inspect property settings. It runs from your machine: you need Python 3.10 or newer, a Google Cloud project with the Analytics Admin and Data APIs enabled, and Application Default Credentials with at least Viewer on the property. The guide documents Claude Desktop, Claude Code and Cursor among its clients. For a few properties and a comfortable setup, it covers more of GA4 than DuckDive does.
DuckDive is the better fit when the pain is breadth rather than depth: many properties, no Cloud project, an agent that cannot launch a local server process, and GA4 next to Search Console, Google Ads and local data for the same site. The side-by-side is on Google's GA MCP server vs a hosted connector.
And if you already pay for GA4 360 and only need GA4 rolled up, a 360 roll-up property may do the job without any agent at all.
Questions before you link a GA4 property
Will my agent's GA4 numbers match what I see in Google Analytics?
They come from the same property, so they should line up for the same window. When they differ, check three things first: that you compared the same fixed window, that a key event was not added partway through it, and that you are comparing conversions with conversions rather than with GA4's session key event rate, which counts sessions instead of events.
Can I ask about a custom date range, like last November?
Not through the agent today. Each GA4 tool accepts one of six preset ranges, from a week up to a year, all counted back from today. A named past week, or this March against last March, still needs the GA4 date picker.
Does DuckDive change anything inside my GA4 property?
DuckDive only reads from GA4. Nothing the agent does through the connector can erase GA4 data or unlink your Google login. Fixes like starring key events or listing unwanted referrals are done by you in GA4 Admin. DuckDive's own actions, such as adding a website or linking a source, change your DuckDive account, not your GA4 settings.
What GA4 access does my Google login need?
Your Google login has to be able to see the property, or DuckDive will not list it when you link sources. If a property is missing from the list, ask someone with admin rights on that property to add your Google account as a user, then check again.
Can two websites in DuckDive share one GA4 property?
No. Each property is tied to a single DuckDive website, and you are asked before it is reassigned. If one property covers two domains through cross-domain measurement, add it as one website. If your sites share a property today, the agent will report their combined traffic.
How far back can my agent look in GA4?
On linking, DuckDive copies as much as 2 years of a property's past data and keeps it. The GA4 tools, though, look back 12 months at most, so a question that needs two full years side by side is beyond them for now.
Which agents can use the GA4 tools?
Claude, Cursor and Claude Code all work, as does any other MCP client able to reach a hosted server and log in with OAuth. In ChatGPT, custom connectors need a Business or Enterprise plan; Free and Plus cannot add one. No agent at all? You can ask Drake, the assistant built into DuckDive, inside the app.
Sources
- About Analytics sessions, Google Analytics Help Center, checked November 16, 2026.
- Default channel group, Google Analytics Help Center, checked November 16, 2026.
- Analytics dimensions and metrics, Google Analytics Help Center, checked November 16, 2026.
- What the value (not set) means in your reports, Google Analytics Help Center, checked November 16, 2026.
- Google Analytics MCP server guide, Google for Developers, checked November 16, 2026.
- Conversions vs. key events in Google Analytics, Google Analytics Help Center, checked November 16, 2026.
- Mark events as key events, Google Analytics Help Center, checked November 16, 2026.
- [GA4] Google Analytics account structure, Google Analytics Help Center, checked November 16, 2026.
- Identify unwanted referrals, Google Analytics Help Center, checked November 16, 2026.
- Set up cross-domain measurement, Google Analytics Help Center, checked November 16, 2026.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.
