Have Your Agent Build a Weekly Marketing Report

One prompt, and your weekly report is ready in minutes instead of hours: numbers from every connected channel, compared to the previous week, in compact overviews.

Each marketing source, taken on its own, tells an incomplete story. GA4 says conversions have collapsed. Google Ads says everything is quiet. Search Console says clicks are rising. Every number is correct, and yet each one alone is misleading. The value of a good report isn't in gathering the numbers, but in cross-checking them: only when the sources sit side by side do you see whether a movement is a real problem or a measurement error. By the end of this tutorial you have a reusable prompt that delivers this report every week, plus the two follow-up prompts that turn numbers into a decision.

What you need

The report is adaptive: it takes in the channels whose source is connected and leaves the rest honestly empty. You connect your accounts once in the portal, which the tutorial Connect Marketing Accounts to Your Agent shows you (for ChatGPT there's the ChatGPT counterpart).

• Required: at least one web source. Either GA4 (sessions, users, conversions, traffic sources) or Search Console (organic clicks, impressions, position). Either one is enough to start.
• Optional: Google Ads (cost, clicks, conversions, CPA). Without Ads the "Paid search" section stays empty; in step 2, skip the Ads part of the cross-check.
• Optional: Microsoft Clarity (on-page behavior). A bonus for interpretation, not a must for the report.
• The agent can add further connected sources (for example your Google Business Profile): just include them as their own line in the prompt, such as "5) Google Business Profile: views, calls, directions".

1. Build the report template once

The first prompt does the work you'd otherwise do by hand across three tools. Write it cleanly once, then each week you just copy it. Replace [workspace] with the name of your account from the portal.

Build me a weekly report for [workspace].
Time frame: the last completed week (Mon to Sun), compared to the previous week.

1) Web (GA4): sessions, active users, conversions and top traffic sources, each with change vs. the previous week
2) Paid search (Google Ads): cost, clicks, conversions and CPA per campaign
3) Organic search (Search Console): clicks, impressions, avg. position and the most important queries
4) Bottom line: the three most important movements in three sentences

Format: one compact overview per source with Δ vs. the previous week.
Leave sources that aren't connected honestly empty and don't guess numbers.

What you get back:

Web (GA4):        Sessions 890 (−23%) · Users 720 (−21%) · Conversions 22 (−46%)
Paid search:      Cost €480 (−6%) · Clicks 190 (−7%) · Conversions 14 · CPA €34 (±0%)
Organic search:   Clicks 34 (+10%) · Impressions 3,900 (+8%) · Avg. position 18.4
Bottom line: web traffic and conversions down, paid search stable, organic slightly up.

✓ Checkpoint: You have a compact overview per connected source with a Δ comparison to the previous week, and unconnected sources are empty instead of showing made-up numbers.

Doesn't work? If you get an error about a source, the workspace name is misspelled or the source isn't connected. Check the name in the portal and whether GA4 or Search Console is marked as connected there.

2. Cross-check the sources against each other

This is the step that turns the report from a wall of numbers into a statement. A single source tells you that something moved, never why. Have your agent hold the sources against each other and name the contradictions.

Cross-check the sources. Where do GA4, Google Ads and Search Console contradict each other,
and what is the most plausible explanation?
For every notable movement, tell me whether it sits in a single channel
or runs across all channels.

What you get back:

Contradiction: GA4 reports conversions −46%, Google Ads reports its own conversions stable (−7%).
The gap sits almost entirely in the "Direct" channel (−86%), not in Paid or Organic.
Most plausible explanation: not a channel slump, but a tracking or one-off effect on a single path.

This is exactly where cross-checking pays off. GA4 alone would have put you in a panic (conversions nearly halved). Ads alone would have reassured you (all stable). The two side by side show: the drop sits in a single channel while the others run quietly. That's the fingerprint of a measurement error or an outlier in the previous week, not of a performance problem.

✓ Checkpoint: You have at least one named contradiction between two sources plus an assessment of whether the movement sits in one channel or runs across all of them, not just repeated numbers.

Doesn't work? If the agent only repeats the tables, the prompt was too tame. Add: "Name the specific number pairs that contradict each other, and for each, tell me which source I should check first."

Only one source connected? Then you cross-check not source against source, but channel against channel within GA4: "Compare the movement per channel: organic, paid, direct. Where does the outlier sit?" With only Search Console, this step falls away; jump to step 3.

3. Prioritize the anomalies

A report without prioritization is a to-do list with no order. Have the movements sorted by impact so you know where to look first on Monday.

Sort the anomalies by impact on revenue.
Give me the top 3, each with one concrete next step,
and mark where I should look more closely first.

What you get back:

1. Conversion drop in the "Direct" channel (biggest lever) → double-check tracking on the thank-you page.
2. "app developer [city]": 620 impressions, 0 clicks, avg. position 8 → test title and snippet.
3. Paid search stable, no pressure to act.

✓ Checkpoint: You have at most three prioritized points, each with one concrete next step, sorted by impact, not by how eye-catching they are.

Doesn't work? If ten equally ranked points come back, focus is missing. Ask explicitly for "the three with the biggest revenue lever, leave out the rest".

4. Make the report recurring

The report only pays off once it runs without you. Whether your agent can create scheduled tasks depends on the client and your plan, not on the connector: in Claude the feature is called Scheduled Tasks (or a recurring project task), in ChatGPT Tasks. If it's available in your plan, simply tell your agent when to run the report.

Run this report every Monday at 8 a.m. and send me the result.

What you get back:

Scheduled task created: weekly report for [workspace], every Monday 08:00.
You'll receive the result automatically from now on.

✓ Checkpoint: The scheduled task appears in your client's task overview and names the time and the recurrence.

Doesn't work? If your agent finds no such feature, it isn't included in your plan or client. Then the prompt from step 1 stays your one-click report: saved once, pasted in on Monday.

Variations

• Monthly report: "Build the same report for the last calendar month, compared to the previous month."
• Only one channel: "Limit the report to GA4 and Search Console, leave out Google Ads."
• For the client, without jargon: "Phrase the same report for a client without technical terms and explain each metric in one sentence."
• Include AI visibility: "Also show me whether visitors came via AI assistants (traffic source chatgpt.com and similar)." That's a rough approximation via the referrer, not proof, but a first hint of whether AI answers are recommending you.

Honest limit

The report is read-only: it reads your accounts but never changes anything in them. And it's only as good as the connected sources. An empty or unconnected source produces an empty section, not an estimated number. Just as important: the report shows you that and where something moved, not the why. Diagnosing the cause is audit work. And because the last one to three days are still incomplete due to attribution lag, the report works with the last completed week. For small numbers: a handful of conversions swing wildly, that's noise, not a trend.

What's next

When the report shows an organic anomaly (clicks gone, position dropped, many impressions without a click), the next step is finding the cause. That's exactly what Your First SEO Audit does: "something is moving here" becomes "this is the reason, and here is how you fix it".