Most of my week is in Search Console, but the questions I get asked are about GA4: sessions were down last week, and someone wants to know why. GA4 reports the drop. The cause is usually in another tool, a ranking change in Search Console, a paused or cut campaign in Meta Ads or Google Ads, or a tracking problem on the site, and checking each one and matching the dates is the slow part.
So I connected GA4, Search Console and the ad accounts to Windsor.ai and added Windsor to Claude, where I already do my search work. I ask which channel moved and by how much, and the answer covers all three sources with the dates already matched. ChatGPT, Gemini and Perplexity work the same way.
🚀 Ready to see it live? Try Windsor.ai free, free forever plan, no credit card.
Already using Claude? Add the Windsor.ai for Web Analytics connector directly from the Claude directory. On ChatGPT, Gemini or Perplexity, add Windsor the same way from that assistant’s own connector or app directory.
Connecting your web analytics data to your AI assistant with Windsor: 2 steps
Windsor.ai is a single connector that reads from 350+ data sources, including GA4, Google Search Console and every major ad platform, and sends it wherever you work. Setup is two steps: connect your sources in Windsor, then add Windsor to your assistant.
Google also ships its own official GA4 MCP server, built for querying a single GA4 property directly. Windsor.ai does a different job. It blends GA4 with your ad accounts, Search Console and 350+ other sources in the same conversation, which is what a traffic-change question usually needs.
Before you start
- A GA4 property, plus a Meta Ads or Google Ads account and/or a Google Search Console property
- A Windsor.ai account (free for the first 30 days to test; paid plans start at $19/month for 3 sources, $99/month for 7)
- A Claude, ChatGPT, Gemini or Perplexity account
Step 1: Connect GA4 and your ad accounts to Windsor
Go to onboard.windsor.ai/app/googleanalytics4 and sign in to authorize your property. Then add what you want to explain traffic changes with:
- Meta Ads or Google Ads, for spend context
- Google Search Console, for organic visibility in the same view
The free plan lets you test multiple sources for the first 30 days, then drops to a single source with no credit card required. Keeping your properties and ad accounts connected long-term takes a paid plan: $19/month for 3 sources, $99/month for 7, with data going back further.
Step 2: Add Windsor to your AI assistant
- Claude: Customize → Connectors → search Windsor → Add
- ChatGPT: install Windsor’s native app from the ChatGPT apps directory
- Gemini and Perplexity: add Windsor from that assistant’s own connector or app directory
Sign in to your Windsor.ai account when prompted, then confirm it works with a simple question: “how did sessions change last week compared to the week before.”
The numbers I track once it’s connected
| Metric | What it tells you |
|---|---|
| Sessions and users (GA4) | How much traffic the site got |
| Engagement rate / engaged sessions (GA4) | Whether that traffic did anything |
| Conversions (GA4) | Whether traffic turned into a result |
| Ad spend (connected ad platforms) | Whether paid traffic explains a traffic change |
| Clicks and impressions (Search Console) | Organic search demand and visibility |
| Average position (Search Console) | Where you rank for the queries driving that traffic |
The reports web analytics teams run most
These are the questions web analytics teams ask Windsor most often.
Conversions and revenue
- Which events drove the most conversions this week, broken down by event name?
- What’s our purchase revenue and transaction count by channel this month?
Traffic and channels
- How have sessions trended by channel group over the last 30 days?
- Which landing pages get the most sessions and page views?
- Compare sessions by campaign and source across our GA4 accounts this month.
- Which keywords are we paying for in Google Ads that already rank on page 1 organically in Search Console?
Bonus: analyze web analytics alongside your full stack
The same Windsor install covers every source I have connected, so one question can cross GA4, Search Console and the ad accounts. Three I use most:
- “Did the Meta Ads campaign we launched last month move GA4 sessions or conversions?”
- “Compare Search Console impressions to GA4 organic sessions for the same pages.”
- “Which channel in GA4 has the best conversion rate, and how does that compare to its ad spend?”
Conclusion
With GA4, Search Console and the ad accounts connected, a traffic question gets answered in the chat where I already work, with the cause and the dates in the same reply. If you want to try it, start with GA4 and the one ad platform you spend most on, and add Search Console after the first answer looks right.
Connectors mentioned in this guide
🚀 Ready to get started? Try Windsor.ai free. Free forever plan, no credit card. Paid plans from $19/month.
FAQs
Does Windsor.ai change anything in GA4 or Search Console?
No. Windsor reads and analyzes your web analytics data so you can ask questions about it. It doesn’t create or modify properties, goals or settings.
Which web analytics metrics can I ask about?
Sessions, users, engagement, conversions and channel data from GA4, ad spend from every connected ad platform, plus clicks, impressions and position from Search Console, whatever fields each connected source exposes.
Can I connect GA4, Search Console and my ad accounts together?
Yes, that’s the main use case here. GA4 pairs most often with ad platforms like Meta Ads and Google Ads, and Search Console adds organic visibility, all through the same Windsor install, so one conversation can cross all of them.
Is the data live?
Yes. Once a source is connected, Claude (or ChatGPT, Gemini, Perplexity) queries it directly, no manual export or CSV step.


