Six sources, one place to ask
An AI agent can only reason about numbers it can reach. DuckDive links six marketing sources to each website you add, stores what it imports, and exposes the result through a single MCP server. This hub exists because the sources are not interchangeable. A Search Console click, a GA4 session and a Local Services Ads lead are three different things counted by three different systems, and an agent that treats them alike will give you confident nonsense.
Which source answers which kind of question
Google Analytics 4 describes what visitors did once they arrived: sessions, conversions, channels and landing pages. Search Console describes what happened before the visit, in Google's results: queries, pages, impressions, clicks and average position. Google Ads and Local Services Ads cover paid demand, the second being the pay-per-lead product for local service businesses.
The last two sit on the local side. Yext reports how each location's listing was found, viewed and acted on, along with reviews. Local Falcon reports where a location appears on a map grid for a tracked keyword. Neither is a website analytics source, so each page spells out what it can and cannot say about traffic.
Reading sources side by side
The useful questions rarely belong to one source. "Did the ad spend produce leads" needs Google Ads and GA4. "Why did this branch go quiet" may need the map grid, the listing actions and the organic clicks together. The guides show full workflows that join several sources.
A rule that saves trouble: ask the agent to name the source behind every figure it quotes, and treat a figure with no named source as unverified. The verification guide turns that rule into a checklist.
What to check before you ask
- Whether the source is linked to the right website, since one account can hold many.
- Whether the first import has finished, because partial history makes trends look flatter or steeper than they are.
- Whether the date window matches the source's own reporting delay.
- Whether the question needs a source you have not connected, in which case the honest answer is "this data is not here".
Access and permissions
Each source needs read access for the Google login you connect with, or the vendor's own login for Yext and Local Falcon. The access guide lists the exact roles to request from a site owner, and the safety guide explains what the agent can see once connected.
Limits worth knowing before you build a workflow
Each source carries a ceiling that no agent can lift. Search Console reports clicks and impressions for queries Google chooses to show, and it does not tell you who the visitors were. GA4 reports sessions on sites that have a working tag, so a site with broken tracking shows a flat line that is not the same as zero demand. Paid sources report what the platform counted, which may differ from what your sales team recorded. Local sources describe a listing or a grid, not a person.
These limits are not defects. They are the reason an honest agent answer sometimes reads "this data does not say". When your agent says that, it is working correctly, and your next step is to decide whether to connect another source or to accept the uncertainty.
Why stored history matters
DuckDive keeps what it imports, so a question about last quarter is answered from a copy that already exists, not a request that must reach Google, Yext or Local Falcon at the moment you ask. That matters most for sources where a vendor changes what it reports, because a saved record outlasts a product change. The stored versus live comparison explains the trade-off in detail, and the Local Services Ads history guide shows a case where saving early is the whole point.
Which source to connect first
For most websites, begin with Search Console and GA4: together they cover how people find a site and what they do on it. Add Google Ads if you buy clicks. Add Local Services Ads, Yext and Local Falcon if you serve customers at physical locations, and add them one site at a time so you can verify each against the vendor's own screen before moving on.
