The short answer
Connect each new client's GA4, Search Console and Google Ads to DuckDive, then have your agent run the same intake checks for every engagement: whether key events are honest, whether the site credits itself, where visits land and leak, which search positions are close to paying, and what a paid conversion really costs. Failed checks become the memo and the 90-day plan.
- Test the key events before you quote any rate
- Keep each client as its own website in DuckDive and name the client in every prompt
- On the last day, disconnect your agent and give back the client's Google access
The new-client marketing audit, as a first-week checklist
Clients rarely call a consultant when things are fine. Your first deliverable sets how far they trust you for the next three months.
The trap is a growth idea built on untested numbers. If your memo's conversion rate came from a broken key event, someone on the client side will notice. So the order is fixed: measurement first, then attention, then money.
Run these in order, days one to four
- Data is in. Every linked source has finished importing before you read a number.
- Key events behave. Daily conversions move with sessions, never near one per visit or jumping overnight.
- No self-referrals. The client's own domains, portals and form hosts never appear as a source of converting visits.
- Channel mix explained. You can say which medium carries conversions and why direct is the size it is.
- Landing pages checked both ways. Flag busy pages that convert nobody, and rates too high to be real.
- Search positions banded. Know how much demand sits in positions 4 to 10, where small gains move clicks.
- Ads cost tested. Google Ads' cost per conversion, held against what GA4 credits to paid search.
- Access logged. Every Google login and role the client gave you, written down for the hand-back.
- Key event
- A GA4 event flagged as important, such as a form submission. DuckDive's tools report key events under the older word, conversions.
- Self-referral
- A visit credited to a domain that is really the client's own: an old domain, a booking portal or a form host.
- Average position
- Search Console's topmost position for each query, averaged across every query the site appeared for.
- Landing-page leak
- Our term for a busy page that turns almost no visits into a key event.
Day one: can the key events be trusted?
Two inherited setups cause most of the trouble in a new client's GA4.
The event that fires when a page loads
Someone wanted to count enquiries from a page view. Google's help on creating key events says you cannot simply mark page_view as a key event, because every pageview would then count as one. Its fix is a new event, such as thank_you, copied from page_view and limited to the confirmation page.
The inherited version often points at the form page instead, so it fires whenever the contact page loads. The giveaway is a landing page converting near 100%.
Ask your agentWhich landing pages for Calloway & Finch show a conversion rate above 50%, which often means a key event fires on page load?
Tools it calls search get_ga4_landing_pages
The site that refers visitors to itself
Google's help on unwanted referrals notes that GA4 already skips referrers that match the current page's domain or any of its subdomains. So when the client's name turns up as a source, look for a second domain they own, such as a portal or last year's brand domain. Visitors pass through it and come back, and the conversion gets credited there.
Ask your agentAudit day one for Calloway & Finch Architects: list the traffic sources sending converting sessions over the last 90 days and flag any named like the client's own domain, which usually means self-referrals.
Tools it calls search get_ga4_channels
A third check catches a key event someone edited last month: a step in the daily line while sessions carry on as before.
Ask your agentBefore I trust any Stillwater Bookkeeping number: show daily sessions and conversions for the last 90 days and point out any day where conversions jump or fall by half while sessions stay level.
Tools it calls search get_ga4_overview
Get the inbox count
On the kickoff call, ask how many enquiries reached the client's inbox or CRM in the last 90 days. It is the only honest test of the key event. If GA4 reports several times more, that is your first finding.
Worked example: a new client whose conversions look too good
Calloway & Finch, a fictional architecture practice, hired a fractional CMO because "the website converts brilliantly but the phone is quiet". Here is the day-one pull, from GA4 history DuckDive imported at linking.
Calloway & Finch says GA4 shows hundreds of enquiries but the partners see a handful a month. What is GA4 counting over the last 90 days?
searchfinds the Calloway & Finch website and its idget_ga4_overviewsessions, conversions and conversion rate, last 90 daysget_ga4_channelsthe same window, grouped by traffic sourceget_ga4_landing_pagestop landing pages by sessions, same window
GA4 counted 742 conversions from 5,940 sessions, a 12.5% rate. For a practice that wins work through long conversations, one enquiry in every eight visits is not believable. Two setup problems explain most of it.
| Source | Conversions | Rate |
|---|---|---|
| 268 | 7.9% | |
| (direct) | 301 | 17.8% |
| callowayfinch- | 151 | 80.3% |
| archdirectory. | 14 | 3.5% |
| All other sources | 8 | 3.2% |
Self-referral. The practice's own client portal is the third-biggest source of conversions from just 188 sessions. The new-project enquiry form is embedded on the portal domain and sends people back to /thanks once they submit, so each return opens a fresh session and the portal, not the search or link that found the visitor, takes the credit.
| Landing page | Conversions | Rate |
|---|---|---|
| / | 61 | 2.0% |
| /contact | 521 | 97.6% |
| /thanks | 149 | 87.1% |
| /projects/quay-house | 3 | 0.5% |
Key event on page load. Nearly every session starting on /contact converts, even people who only glance at the address. A second enquiry event built on that page's URL looks to be starred beside the real one on /thanks, where the sessions are mostly portal visitors. The same page-load event explains (direct) at 17.8%: the partners' email signatures and printed letterheads point straight at /contact, so those visits arrive as direct and count as an enquiry the moment the page opens.
Ask the partners how many enquiry emails arrived in these 90 days. That figure, not 742, is the baseline for the engagement.
Day two's message is short. Unflag the event built on the contact page, so the thank-you event alone counts enquiries, and give the portal domain cross-domain measurement or a place on the unwanted referrals list. Google's referral help shows, in its worked example, that a session from before the exclusion stays credited to the referrer, so the fix only cleans data from that day on.
Treat the 742 as history you cannot clean. Put the fix date in the memo, and compare only windows that open after it, or the partners will read a slow week as a collapse.
Test your newest client's key events before the kickoff call
Link their GA4 and Search Console, then ask which sources and landing pages are taking credit for enquiries that never happened.
Free for 2 sites · No credit card
Days two to four: where attention and money go
Channel mix
Ask for sessions and conversions by medium over 90 days, then by source if a bucket looks odd. A big direct share after the self-referral fix is a question for the client: offline campaigns, QR codes, or email links without campaign tags?
Landing-page leaks
Read the conversion rate down the top landing pages by sessions. Heavy traffic with a near-zero rate is worth more than a new campaign. If that page also ranks, our guide to pages that rank but don't convert covers the follow-up.
Search position bands
Search Console's help builds average position from the topmost spot a link held for each query and warns the metric can mislead, so one site-wide average is weak evidence. DuckDive returns up to 100 top queries by clicks, each with its own position, so you can band them instead: 1 to 3 is defended ground, 4 to 10 is page one but underused, 11 to 20 is a content project.
Ask your agentGroup Stillwater Bookkeeping's top 100 search queries from the last 90 days into positions 1 to 3, 4 to 10 and 11 to 20, and tell me which band holds the most clicks and which queries sit just outside the top three.
Tools it calls get_search_console_keywords get_search_console_summary
Ads efficiency
For Ads, DuckDive sees the account as a whole: what was spent, the clicks and impressions it earned, the conversions Ads recorded and the cost of each. Set that beside what GA4 credits to paid search. They never match exactly, since attribution differs, but a gap of two or three times usually has a setup cause.
Check the counting option first. Google advises you to count every conversion for purchases and one per ad click for leads. A lead form counting every conversion flatters cost per lead.
Ask your agentFor Stillwater Bookkeeping, put Google Ads spend, conversions and cost per conversion for the last 90 days next to the conversions GA4 credits to cpc over the same window, and tell me how far apart the two counts are.
Tools it calls get_google_ads_summary get_ga4_channels
Worked example: a findings memo for a yoga studio group
By day four you want one page the owner reads in five minutes, with no more than three problems. Delphine Yoga Collective is a fictional group of studios sharing one website, its key events already checked.
Write a one-page findings memo for Delphine Yoga Collective from the last 6 months of data: three problems, the evidence for each, and the first fix.
searchfinds the Delphine Yoga Collective websiteget_ga4_overviewdaily sessions and conversions, last 6 monthsget_ga4_channelsthe same window by mediumget_ga4_landing_pageswhere the six months of visits first arrived, and how each page convertedget_search_console_summaryclicks, impressions and average position over timeget_google_ads_summarythe Ads account's own signup count against its spend
Delphine Yoga Collective: six-month findings. 31,400 sessions and 1,120 conversions (intro-offer signups), a 3.6% rate. Organic search brings 520 of those conversions, direct 391 and paid search 142.
| Problem and first fix | Evidence |
|---|---|
| 1. Paid search looks three times cheaper in Google Ads than in GA4 First fix: check whether the signup conversion action counts every conversion instead of one per click. | Ads: 468 conversions on 9,840 dollars, 21.03 each. GA4 credits cpc with 142, about 69.30 each. |
| 2. The class schedule gets traffic and almost no signups First fix: put the intro offer and its button at the top of /schedule. | /schedule: 9,240 sessions, 0.6%. /intro-offer: 2,180 sessions, 9.8%. |
| 3. Search visibility grew while clicks shrank First fix: pull top pages and queries to find which studio pages slipped. | Months 4 to 6 against 1 to 3: impressions 212,000 to 236,000 (+11%), clicks 8,420 to 6,910 (-18%), average position 7.4 to 9.1. |
Not checked: class revenue, the booking system and social ads. They are outside the data I can read.
Before sending, read the draft as a sceptical owner would:
- Every number names its source and window, so nobody can say you mixed a month with a quarter.
- Each problem gets one first fix small enough to start next week.
- The "not checked" line protects you if the real issue lives in the booking system.
Turning the findings into a 90-day plan
The memo says what is wrong; the plan says in what order, and how you will know. Two rules keep it honest.
- Measurement fixes go first. Each change to a key event or conversion setting restarts the clock on clean data, so make them in week one and note the date.
- Check-ins follow the available windows. The agent can look back a week, two weeks, a month, a quarter, half a year or a full year, each counted back from the day you ask. A fix on day 5 gives a clean 30-day read from about day 35, so book the check-in then.
| Weeks | Work | Number to watch |
|---|---|---|
| 1 to 2 | Switch the Ads signup action to one per click | Ads conversions against GA4 cpc conversions |
| 3 to 6 | Rebuild /schedule around the intro offer | /schedule rate, from 0.6% |
| 5 to 10 | Refresh the studio pages that slipped in search | Clicks and average position |
| 11 to 13 | Report back and agree what continues | All three against the memo |
Each check-in is one saved prompt, worded like the baseline so the comparison stays fair.
Ask your agentDay 50 check-in for Delphine Yoga Collective. Using the last 30 days, give me Google Ads conversions beside GA4 cpc conversions, the /schedule conversion rate, and Search Console clicks, each next to the figure from my memo.
Tools it calls get_search_console_summary get_ga4_landing_pages get_google_ads_summary get_ga4_channels
Paste the memo's figures in with it; the agent only knows your memo if you give it back.
Running several clients without mixing them up
With five live engagements, one wrong noun in a prompt and you quote the yoga studio's numbers to the architects. DuckDive's unit is the website: each has its own sources and stored history, and every data tool reads one website at a time. Linking Stillwater's GA4 property to Delphine by mistake is hard to do, because a property can sit under only one website and DuckDive asks before moving it.
Accounts can hold several clients, with websites filed under each. When your agent adds a site to such an account, DuckDive makes it ask which client the site belongs to. Habits do the rest:
- One chat per client. Earlier answers cannot leak into a new memo.
- Full client names in prompts. "Stillwater" and a future "Stillwell" are one typo apart.
- A monthly roster check. Clear out finished work.
Ask your agentList every website in my DuckDive account with the data sources linked to each. I want to spot anything left over from engagements that already ended.
Tools it calls list_websites
If you are growing into a team on retainers, see our page for full-service agencies preparing quarterly reviews.
Kickoff-call setup and last-day hand-back
Setup fits inside the kickoff call. DuckDive connects your agent to the client's Google data through one sign-in and stores the imported history, so every audit question reads data already on hand instead of a fresh pull from Google.
-
Get added to the client's Google accounts
Ask the client to add your work Google account as a user on their GA4 property, Search Console site and, if they advertise, Google Ads account.
-
Log in as the user your client invited
Choose Continue with Google on DuckDive and pick the work address the client just added, not a personal Gmail. DuckDive shows every property that address can open, so if one login serves several clients, expect to see all of them and pick carefully.
-
Connect your agent and let it do the setup
Add DuckDive to your assistant, keep "Also allow actions" ticked if you want it to set things up, and paste the prompt below. Setup actions need an admin account. Our guide to connecting Claude has the exact clicks; ChatGPT needs a Business or Enterprise plan.
Paste this during the kickoff callSet up DuckDive for my website. Follow https://analytics.duckdive.ai/
agents.md -
Link the client's site to its sources
The agent adds the website, then links its GA4 property and Search Console site. Link the Google Ads account too, if the client runs ads. Linking starts the history import.
-
Wait for the import, then run day one
Most client histories finish importing within minutes; an old, busy property can take longer, so check sync status before day one and never quote a half-imported window.
-
Hand everything back on the last day
Open AI Connectors in DuckDive and disconnect your assistant (deleting it from the AI app's connector list also works); its access ends at once. Then give back the client's Google access, product by product, using our removal checklist.
Where this audit runs out of road
The intake audit above fits DuckDive well. Some consulting questions do not, and those are better answered in the client's own tools.
| Audit job | Agent reading DuckDive | Working in GA4 and Ads directly |
|---|---|---|
| Same checks across three to eight clients | Yes, one prompt per check, stored data | Partly, one property and login at a time |
| Drafting the memo from the numbers | Yes, the agent writes from what it read | Partly, you copy figures by hand |
| An exact date range, like the month before you started | No, fixed windows only | Yes, any range in the date picker |
| Debugging which event fired and why | No, conversion totals only | Yes, GA4's event reports |
| Fixing key events or the referral list | No, it reads, it does not edit | Yes, in GA4 Admin |
| Campaign, ad group or search term detail | No, account summary only | Yes, in Google Ads |
One client a quarter, audited in an afternoon? GA4 and Google Ads alone will do, and paid social, CRM pipelines and call tracking sit outside DuckDive's sources anyway. It earns its place when engagements overlap and you rerun the same checks on day 50 and day 90 without five sets of Google logins. If the client has an in-house team who will keep asking after you leave, point them to the page on in-house teams answering executives with AI; the DuckDive overview lists all six sources.
Questions consultants ask before a pilot
Does my client need their own DuckDive account?
No. You sign in with the Google account the client added as a user, and DuckDive lists what that login can reach. The client only grants Google access, which they control and can withdraw.
Can the agent fix the broken key event or referral list for me?
No. DuckDive reads data; you change key events, referral lists and Ads conversion settings yourself in GA4 Admin or Google Ads. DuckDive's only actions are setup steps, such as adding a website, linking sources, refreshing data and scheduling an email report, and only for admins.
Can I look at the exact month before my engagement started?
Not through the agent today; the tools read fixed recent windows, such as the last 30 or 90 days. For an exact calendar month, use the date picker in GA4 or Search Console and say so in the memo.
Where does my client's data go when I ask a question?
Two services touch it, and most client agreements want both named. DuckDive keeps the imported Google history plus a record of each tool call (which tool, which website, what time), but the chat itself never reaches it, and your AI app holds a DuckDive token rather than any Google password. The numbers your assistant reads then sit with that AI company under its terms, which is the clause to show the client's lawyer before you sign the NDA.
What happens to a client's data when the engagement ends?
Disconnect the agent under AI Connectors, which stops access immediately, and have the client remove your Google user. DuckDive's privacy policy keeps analytics data while your account is active or as needed to run the service, and removes personal data within 30 days of account deletion. For one website's stored data, ask DuckDive.
What does it cost to run four or five clients?
Your first site is free with no credit card, so you can run the full audit on one client before paying anything. Each extra client adds its own site fee, and the plans further down this page carry today's numbers.
Sources
- Create or modify key events, Google Analytics Help, checked November 16, 2026.
- Identify unwanted referrals, Google Analytics Help, checked November 16, 2026.
- What are impressions, position, and clicks?, Search Console Help, checked November 16, 2026.
- About conversion counting options, Google Ads Help, checked November 16, 2026.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.
