The short answer
Connect DuckDive to the agent you already run, then give that agent a written brief spec: which numbers to report daily, which only weekly, what counts as a real change, and when to say nothing. Your agent sets DuckDive up from one prompt. You click Continue with Google once, and there is no dashboard to open for the brief.
- Write the spec before the first brief, or you will get a wall of numbers every morning
- Compare with the same weekday last week, never with the day before
- Give the daily brief read-only access; allow actions only while setting up
Write the brief spec your agent follows
A chief of staff who reports every number is not doing the job. The same goes for an agent. If you just say "add marketing to my brief," you will get sessions, bounce rates and a top-ten list of pages, every day, in a different format each time. Within a week you stop reading it.
The fix is a spec: a short block of text your agent keeps with its standing instructions. It says what to read, what to compare it with, how long the answer may be, and what to keep to itself. Here is one you can paste and edit.
Ask your agentSave this as the marketing part of my morning brief. Use DuckDive. Weekdays: always give yesterday's sessions and conversions against the same weekday last week, in two lines. Numbers first, no adjectives. Mondays only: last 7 days against the 7 before for sessions, conversions, the top 3 channels and the top 3 landing pages by conversions, plus Search Console clicks and average position. Mention anything beyond those two lines only if it crosses my line: sessions 12%, conversions 25% or 10 conversions (whichever is bigger), Search Console clicks 15%. If nothing else crosses a line, end with "Otherwise a normal day." Check sync status first. If a source is not ready or its newest day is older than yesterday, tell me that instead of reporting it. Never explain a change you did not check.
Tools it calls get_sync_status get_ga4_overview get_ga4_channels get_ga4_landing_pages get_search_console_summary
Each line in that spec is doing a job. "Numbers first" stops the agent from opening with "Great news!" The two weekday lines are fixed, so a quiet morning still shows you the pair you care about; the thresholds only decide what gets added beneath them. The sync check stops it from reporting a zero when the data just hasn't landed yet. The last line matters most: an agent asked why something moved will happily guess. Make it say what it checked, or say it didn't check.
Where DuckDive fits: it is a remote server that speaks the Model Context Protocol, the open standard that lets apps like Claude and ChatGPT reach outside data. Your agent connects to https://api.duckdive.ai/mcp, signs in through Google, and gets tools that read your GA4 and Search Console numbers (and, should your company ever run them, Google Ads, Local Services Ads, Yext and Local Falcon).
DuckDive imports your history when a source is linked and keeps it. So the brief reads numbers DuckDive already holds, and you don't have to open Google Analytics to check what the agent said. You will still visit GA4 now and then for its own settings, such as marking which event counts as a signup.
Daily items versus weekly items
Most founder briefs fail because everything is daily. Some numbers are only worth reading once a week, because one day of them is noise. Here is how to split them, and the DuckDive tool behind each.
| Number | Daily brief | Monday brief |
|---|---|---|
| Sessions | Yes, vs same weekday | Yes, 7 days vs 7 before |
| Conversions (signups, demos) | Yes, with a count floor | Yes, with conversion rate |
| Channel mix | No, too noisy per day | Yes, top 3 by conversions |
| Landing pages | No, unless asked why | Yes, top 3 by conversions |
| Search Console clicks | Only past your threshold | Yes, with average position |
| Data health | Yes, silent unless broken | Yes, same rule |
The tools map cleanly. get_ga4_overview returns sessions and conversions per day with totals, so with a 14-day range the agent has yesterday and the same weekday last week in one call. get_ga4_channels and get_ga4_landing_pages give the Monday breakdowns. get_search_console_summary returns clicks, impressions, click-through rate and average position over time. get_sync_status tells the agent whether a source is current, still importing or broken, and how fresh its data is.
Why the same weekday, not the day before
Many B2B sites have a weekly shape, with quieter weekends. If yours does, Monday against Sunday looks like a surge every single week. Monday against last Monday cancels that rhythm out, so what's left is closer to real change. Don't take the shape on trust: the swing prompt in the thresholds section shows your own pattern in one answer.
Why yesterday is provisional
Google says GA4 data can take 24 to 48 hours to process, and reports may change during that window. Search Console also marks its newest data as preliminary. So a 7 a.m. brief about yesterday is a first read, not a final count. Tell the agent to mark it that way, or brief on the day before yesterday if you want settled numbers.
- Sessions
- GA4's count of visits to your site in the period. One person can start several.
- Conversions
- The word DuckDive's tools use. In GA4 these are now key events, which Google defines as events that measure an action particularly important to your business, such as a trial signup.
- Clicks
- Search Console's count of times someone clicked through to your site from Google Search results.
- Threshold
- Your line, per number, below which a change is not worth a sentence in the brief.
Handing the setup to the agent itself
You don't need to find a settings page. The agent does the setup and you click one button. Here is what happens, in order.
-
Make sure GA4 counts your signups
The brief can only report signups if GA4 records them. If your trial signup or demo request is an event but not yet a key event, mark it as a key event in GA4 first. Otherwise every "conversions" line will read zero. Google's same help page says the change counts only from the moment you make it, does not rewrite older data, and can take up to 24 hours to reach standard reports. So the first briefs after you mark it will show a short conversion history, and that is expected.
-
Paste the setup prompt
Paste this into the agent you already use. Add your address after "my website" if you like, in the form shown in the second prompt.
Paste into your agentSet up DuckDive for my website. Follow https://analytics.duckdive.ai/
agents.md
Paste into your agentSet up DuckDive for my website, example.com. Follow https://analytics.duckdive.ai/
agents.md -
Click Continue with Google, once
If DuckDive isn't connected yet, the agent registers the server and a DuckDive page opens. Choose Continue with Google. That one screen signs you in, creating the account if you don't have one, with no form. On the approval screen, keep Also allow actions ticked for now so the agent can do the setup. The agent never asks for or types your password.
-
Let it pick the site and link the sources
The agent calls
get_setup_status, which lists websites it found in your Google account. With one obvious match it adds it and tells you. With several, it asks you once. It then links the GA4 property and Search Console site that clearly match, and starts the history import. Google Ads and the other sources are optional; skip them if you don't run them. -
Give the import a moment, then hand over the spec
Let the history import finish first (a site with years of data needs longer), then paste your brief spec from the first section and tell your agent what time of day to run it. That last part is the agent's job, not DuckDive's: DuckDive answers the tool calls, while your agent's scheduler (a scheduled task, a cron job, a routine) decides when the brief runs and where it lands.
Which agent
Any agent that supports remote MCP servers with OAuth sign-in can connect. Claude works on any plan, though Claude's help center says Free accounts are limited to one custom connector (as of November 2026). In ChatGPT it needs Business or Enterprise. Each app labels this differently and moves it now and then, so check under Connectors, Apps or MCP. The step by step trace of an agent setting itself up shows every state it moves through, and there are client notes for connecting Claude and connecting ChatGPT.
No agent of your own yet? You can still ask Drake inside DuckDive.
Worked example: a Tuesday morning brief
Here is the daily line on an ordinary day. The founder of a fictional project tracking tool started with the one-line version of the spec shown below, before writing the full version: two fixed numbers, and search clicks only when they move more than 15%. The point to notice is what the agent reads and then leaves out.
Ask your agentEvery morning, tell me yesterday's sessions and conversions compared with the same weekday last week in two lines, and mention Search Console only if clicks moved more than 15%.
Tools it calls get_sync_status get_ga4_overview get_search_console_summary
(Scheduled run, Tuesday 7:00) Marketing section of the morning brief, using my one-line instruction.
get_sync_statuschecks that GA4 and Search Console are ready and how recent each one isget_ga4_overviewsessions and conversions per day for the last 14 daysget_search_console_summaryclicks per day for the last 14 days
Marketing: Monday had 3,412 sessions, up 7% on last Monday, and 41 trial signups, up from 37. Yesterday is provisional until GA4 finishes processing.
What the agent read (only the first two rows made the brief):
| Number | Last Mon | Mon | Change |
|---|---|---|---|
| Sessions | 3,198 | 3,412 | +7% |
| Trial signups | 37 | 41 | +11% |
| Search clicks | 958 | 1,026 | +7% |
Search clicks rose 7%, under the 15% line, so the brief says nothing about them. Both sources showed as ready.
Two lines, and you know the day was normal. Under the one-line instruction, sessions and signups always appear and search clicks need a 15% move to earn a sentence. Once the founder switched to the full spec, the same Tuesday would read the same two lines plus a closing "Otherwise a normal day.", which tells you the agent looked at everything else and found nothing worth your time.
Get your own two lines tomorrow morning
Once your site is linked, your agent can run this spec on your real GA4 and Search Console numbers from its next brief.
Free for 2 sites · No credit card
Worked example: the agent notices a signup slump
The brief earns its keep on the bad week. Say Thursday's brief flags signups below the line two days running. You reply, and the spec's last rule forces the agent to look before it talks.
Why did trial signups dip this week? Check channels and landing pages before you answer, and tell me what you would look at next.
get_ga4_overviewlast 14 days, split into this week and the week beforeget_ga4_channelssessions and conversions by medium, same two weeksget_ga4_landing_pagestop landing pages with conversions and conversion rateget_search_console_summarysearch clicks, to rule organic in or out
Trial signups fell from 214 to 168 (down 21%), but traffic didn't fall: sessions went from 10,310 to 10,420. Paid search (cpc) lost 43 of the 46 missing signups. "Before" is the previous 7 days; "now" is the last 7.
| Medium | Signups before | Signups now |
|---|---|---|
| organic | 69 | 71 |
| cpc | 71 | 28 |
| (none) | 54 | 52 |
| referral | 20 | 17 |
Paid sessions only slipped 3% (2,050 to 1,990), so the ads still bring people. They stopped signing up on one page:
| Landing page | Rate before | Rate now |
|---|---|---|
| /start/free-invoicing | 3.3% | 0.9% |
| /pricing | 3.8% | 3.9% |
| / | 1.4% | 1.3% |
Search clicks were up 2%, so organic is not the problem. What I'd look at next: open /start/free-invoicing and try the signup form yourself; ask the team whether that page or its form changed in the last 10 days; and check in GA4 that the trial signup key event still fires from that page. If you link Google Ads to this website in DuckDive, I can also show what each signup is costing you this week.
Notice what the agent did not claim. It cannot see your code, your deploys or your Google Ads account settings, so it hands you three checks rather than a verdict. That's the behavior you want from a chief of staff with partial information.
A Monday follow-up you might keep for the month-end update to your investors:
Ask your agentDraft the marketing paragraph of my monthly investor update from the last 30 days against the 30 before: sessions, trial signups, and the one channel that moved most. Plain numbers, no adjectives, under 80 words.
Tools it calls get_ga4_overview get_ga4_channels
If an investor instead asks to see your site's numbers in their own portfolio view, that's a separate setup on their side; how VC and accelerator teams ask founders for access covers what they'll request.
Read-only or actions: what a personal agent should be allowed
When you connect, the approval screen has one choice that matters: the Also allow actions box. Left unticked, your agent can only read. Ticked, and on an admin account, it can also add websites, link data sources, queue a data refresh and schedule a report.
| Question | Read-only | Actions allowed |
|---|---|---|
| Can it write the brief? | Yes, every data tool reads | Yes |
| Can it set itself up? | No, it sends you to the setup page | Yes, on an admin account |
| If a source looks stale | Reports it and stops there | Can queue a re-import of recent days |
| Can it delete data? | No | No, the connector can't delete data |
| Worst case on a misread | A wrong sentence in the brief | A wrong link, though it asks before moving a source |
| Better fit for | An unattended daily brief | Setup week, or adding sites often |
Our suggestion for a founder: allow actions while the agent sets things up, then disconnect under AI Connectors in DuckDive and connect again with the box unticked. Access stops the moment you disconnect, and the brief keeps working on the read-only connection. If a source goes stale, the agent tells you, and a connection that allows actions can queue a refresh (DuckDive allows one per website every 15 minutes).
Three facts settle most security worries for a founder. Sign-in hands your agent a DuckDive access token, so your Google password never lands in its config or its memory. It can see only the websites your own DuckDive account can see, and DuckDive never receives the chat, just a log of which tool ran. Once a tool returns last week's signups, though, that number sits with your AI provider under its terms, not ours; if the brief runs on a personal plan while the company pays for a team plan, check which set of data terms covers it. The whole threat model is laid out in our guide to connecting an AI agent to analytics safely.
Once a week, have the agent check its own plumbing:
Ask your agentCheck my DuckDive setup and tell me if any data source has stopped updating.
Tools it calls get_setup_status get_sync_status
get_setup_status shows your role, whether this connection may make changes, and each source's import status. get_sync_status shows how recent each source's data is. Together they answer "is my brief built on fresh numbers?" without you opening anything.
Thresholds that keep the brief quiet on normal days
Don't guess your lines. Ask the agent how much your numbers normally wobble, then set each line a bit above that. A line set below normal noise fires every week, and you learn to skip it.
One catch for conversions: GA4 counts a key event only from the day you mark it, so the 90 days before that read as zero and would make any swing look enormous. If you only just marked your signup event, wait until you have a few weeks of conversions before you run the swing prompt, and set the sessions and clicks lines first.
Ask your agentUsing the last 90 days of daily sessions, conversions and Search Console clicks, tell me how much a normal weekday moves against the same weekday the week before. Give me the typical swing and the biggest one, so I can set my brief thresholds.
Tools it calls get_ga4_overview get_search_console_summary
| Number | Normal | Line |
|---|---|---|
| Sessions | 6% | 12% |
| Trial signups | 8 | 25% or 10 |
| Search clicks | 7% | 15% |
Rules that keep a brief worth reading
- A count floor for small numbers. Going from 4 demo requests to 2 is "down 50%" and means nothing; require a minimum count as well as a percentage.
- Two days in a row for a dip. One bad Wednesday is weather. Flag a fall when it holds for a second weekday.
- Holidays get a note, not an alarm. Tell the agent which dates to expect quiet, such as a public holiday last week.
- A closing "Otherwise a normal day." Saying nothing about the rest looks like a broken brief. That closing line tells you the agent checked everything past the two fixed numbers.
- Freshness before numbers. A source that isn't ready gets reported as that, never as zero.
- Re-check the lines each quarter. As traffic grows, the same percentage means more people; run the swing prompt again.
Where this setup falls short
Honest limits, so you know what not to put in the spec:
- No revenue, pipeline or product usage. Your billing system, CRM and product database are not among DuckDive's six sources (GA4, Search Console, Google Ads, Local Services Ads, Yext, Local Falcon). For MRR or pipeline, give your agent a separate connector.
- No social or other ad platforms. Meta, LinkedIn and TikTok ads are not sources. Google Ads comes in as an account summary, not per campaign.
- No push alerts. Nothing pings you at 3 p.m. if signups stop. The brief only runs when your agent runs.
- Fixed date ranges. Tools take ranges from the last 7 days up to the last 12 months. The agent can't compare with the same week two years ago.
- GA4 detail is narrow. Date, channel and landing page only: no device, country or funnel reports.
- Not live. Numbers are as recent as the last import, which is why the spec checks sync status first.
If you want a dashboard you open by hand, GA4's own reports are free and fine. If a whole marketing team needs to answer leadership from the same numbers, the page for in-house marketing teams fits that better than a personal brief.
Founder questions about a personal agent and company data
Does DuckDive send the brief, or does my agent?
Your agent. DuckDive answers the tool calls your agent makes; it does not decide when the brief runs or where it lands. Set the schedule wherever your agent runs scheduled work. If your agent can't run on a timer, ask it each morning, or ask Drake inside DuckDive.
Will it work with the agent I already run?
Probably, as long as it can add a remote MCP server and finish a browser sign-in. The address to add is https://api.duckdive.ai/mcp, and no API key goes in your config. A founder running Claude on any plan, Claude Code in a terminal or Cursor beside the codebase is covered. A homemade harness is covered only if its MCP client handles OAuth. On the OpenAI side, the connector requires a ChatGPT Business or Enterprise workspace, so a personal Free or Plus login will not connect.
Do I have to open a dashboard or fill in a setup wizard?
No. Paste the setup prompt, click Continue with Google once, and the agent adds your site and links the sources. DuckDive has a web dashboard, but your brief never needs it.
Why don't the brief's conversions match GA4 this morning?
Two common reasons. Google says GA4 data can take 24 to 48 hours to process, so yesterday can still change. And the agent reads DuckDive's stored copy, which is as recent as its last import; ask the agent to check sync status. Also make sure your signup is marked as a key event in GA4.
Can the brief compare this week with last year?
Not cleanly yet. The widest window an agent can request is last12months, so the same week last year sits right on the edge of what it can see. For a young company a moving baseline is more useful anyway: have the brief set this week against the weekly average of the last 90 days, which shifts as you launch and grow. DuckDive keeps more history than an agent can reach today, so revisit the spec if longer ranges arrive.
My cofounder wants the same brief. How does that work?
Each person connects their own agent and writes their own spec. On a shared DuckDive account, admins can set things up and team members can only read, which suits a cofounder who just wants the numbers.
How do I switch it off?
Either switch works by itself: the AI Connectors screen inside DuckDive, or the connector list in your AI app. Pulling either one cuts the agent off right away. Then strip the brief spec out of its standing instructions, or it will keep trying tools that now refuse it.
What does it cost for one founder and one site?
Nothing, for a single site, and no card is asked for. A second product or site moves you onto paid pricing, shown in the pricing block further down this page.
Sources
- What is the Model Context Protocol (MCP)? (modelcontextprotocol.io, opened November 16, 2026): the open standard your agent uses to reach DuckDive.
- Data freshness (Google Analytics Help, opened November 16, 2026): why a 7 a.m. read of yesterday is provisional.
- Performance report (Search results): Overview and basic setup (Search Console Help, opened November 16, 2026): where the newest search data is marked preliminary.
- Conversions vs. key events in Google Analytics (Google Analytics Help, opened November 16, 2026): the definition behind the "conversions" line.
- Mark events as key events (Google Analytics Help, opened November 16, 2026): marking takes effect from that moment, leaves older data alone, and can take up to 24 hours to show.
- Get started with custom connectors using remote MCP (Claude Help Center, opened November 16, 2026): the one-connector limit on Free accounts.
- Set up DuckDive with your AI assistant (DuckDive, opened November 16, 2026): the file your agent follows when it sets itself up.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.
