Weekly Marketing Report With Claude: Google Ads, GA4 and Search Console
Published November 14, 2026 · Written by Aanart

Claude can pull Google Ads, GA4 and Search Console reports through SourcetoMCP, write reviewed results to Google Sheets and update a Google Slides brief. Run it on demand first. For an automatic weekly run, a separate scheduler or runner must call the workflow with its own authorised access.
Pull a complete week from each source
Connect Google Ads, GA4, Search Console and the destination Sheets and Slides files. Use the marketing MCP setup guide for the three reporting sources. Record each account or property ID, the dates, currency, search type and time zone when known. Confirm which conversion action or event you are reporting.
Request two complete weeks for comparison and use each platform’s aggregate report for totals. If recent Search Console data is still incomplete, wait or label the week provisional. Put detail extracts in separate tabs when needed and keep row-limit warnings attached to them.
Fill the sample weekly marketing report workbook
Download the sample workbook and open a copy in Google Sheets. Replace the prefilled hypothetical source totals and dates with your own. Keep the prior and recent periods aligned and use one account currency. The review tab shows the changes and Google Ads cost per conversion.
| Source metric | Prior week | Recent week | Change |
|---|---|---|---|
| Ads spend (USD) | $900 | $1,000 | +11.1% |
| Ads primary conversions | 15 | 20 | +33.3% |
| Ads cost per conversion (USD) | $60 | $50 | −16.7% |
| GA4 sessions | 2,000 | 2,150 | +7.5% |
| GA4 key events | 80 | 86 | +7.5% |
| Search Console Web clicks | 820 | 760 | −7.3% |
| Search Console Web impressions | 25,000 | 24,000 | −4.0% |
Calculate cost per conversion from total spend divided by the matching conversion total. Leave the ratio unavailable when the denominator is zero or missing. GA4 sessions and Search Console clicks are separate measures. Keep separate rows for them and avoid treating the difference as missing traffic.
Prepare a three-slide brief
| Slide | What to show | Example decision |
|---|---|---|
| 1. Paid media | Spend, primary conversions and cost per conversion | Check which campaign contributed to the lower cost before shifting budget. |
| 2. Website and organic search | GA4 outcomes and Search Console visibility in separate panels | Inspect the queries behind the organic click decline and the landing pages behind the session gain. |
| 3. Decisions for next week | Owner, evidence, open issue and review date | Assign an analyst to check the highest-spend campaign and the largest query losses. |
Use an authorised Slides file and record its ID. To reuse a chart, embed a chart from Sheets in Slides as a linked chart, then refresh it after updating the Sheet. Check the slide labels and values against the source before sharing. See the Search Console to Sheets and Slides guide for the linked-chart workflow.
Run the workflow on demand
For [Ads customer], [GA4 property] and [Search Console property], compare [two complete weeks]. Return source totals and coverage warnings. Keep Ads primary conversions separate from GA4 key events. Prepare figures for [workbook ID] and a three-slide brief for [deck ID]. Show the exact tabs, ranges and slides you propose to update, then wait for approval. Do not change ad accounts.
On subsequent runs, update the specified ranges and existing slide objects. Use a week identifier so a retry replaces a report’s intended rows instead of adding a duplicate copy. Check counts and warnings before approving writes.
Schedule it with an external runner
SourcetoMCP provides the connected tools. A scheduled run needs a separate system to invoke an authorised client or workflow at the chosen time. Agree on the clock and date boundaries, where errors go and who can approve writes. A scheduled Claude message alone does not establish that the configured environment can call these tools.
Start with a scheduled read-only check or keep the write step manual. Log the run date, source IDs, result status and coverage. If a source fails, retain the prior output and identify which numbers are stale before presenting the brief as current.