| Direct | United States | 13,273 |
| Cross-network | United States | 9,736 |
| Organic Search | Ireland | 1,776 |
The dashboard you already know
One question, in the chat you're already in
The three layers
Caybl.ai sits between three things that don't normally talk to each other: your Google Analytics property, your AI agent, and you.
1. Google Analytics, and optionally Google Ads (the data)
When you click "Connect Google Analytics," you go through Google's standard OAuth consent screen and grant Caybl.ai Google's Analytics scope, which covers running reports plus two narrow write actions (marking a GA4 key event, linking a Google Ads account). Connecting Google Ads is separate and optional, and read access there works on its own - write access to campaigns and budgets only turns on for an account when you explicitly allow it. Caybl.ai stores the resulting refresh token encrypted and uses it only to call the official Google APIs on your behalf.
2. Caybl.ai (the connector)
Caybl.ai runs an MCP (Model Context Protocol) server - the open standard both Claude and ChatGPT use for custom, private connectors. Once you add your Caybl.ai endpoint, your agent sees a small set of tools (for example, "run a GA4 report") it can call mid conversation. Each call maps your question to a real Google Analytics Data API request, fetches the result, and hands it back.
3. Where you ask (the reasoning)
Two options, same tools. In your own agent, Claude or ChatGPT decides which tool to call, with which parameters, based on what you asked - then writes the answer. The AI runs on your own plan; Caybl.ai never sees your prompts, it only fetches the numbers.
In Ask, Caybl.ai’s built-in assistant, you ask right in the dashboard with nothing to set up. Your question and the data the tools return are sent to Anthropic’s Claude to write the answer, and any change it suggests waits for your click.
A question, end to end
- You ask your agent: "Which landing pages lost the most traffic last month?"
- Your agent calls Caybl.ai's report tool with the right GA4 dimensions and metrics -
landingPageandsessions, compared across two 28-day periods. - Caybl.ai calls the Google Analytics Data API with your stored credentials and returns the rows.
- Your agent turns the rows into a ranked, plain-English answer, in the same chat.
In Ask it’s the same loop, with Caybl.ai’s assistant in place of your agent: you see each source it checks, then the answer with tables you can copy - and if it spots a fix, like negative keywords for wasted search terms, a card you can apply with one click.
What Caybl.ai can and can't do today
The Google Analytics connector matches the full read tool surface of Google's own official Google Analytics MCP server, plus two write tools:
| Tool | What it does |
|---|---|
run_report | GA4 reports - metrics × dimensions over any date range |
run_realtime_report | Who's on your site right now |
run_funnel_report | Step-by-step drop-off between events you define |
get_account_summaries | List the GA accounts and properties you can access |
get_property_details | Name, timezone, currency, and type for a property |
get_custom_dimensions_and_metrics | The custom dimensions/metrics configured on a property |
list_google_ads_links | Which Google Ads accounts are linked to a property |
mark_key_event (write) | Mark a GA4 custom event as a key event |
create_google_ads_link (write) | Link a Google Ads account to a GA4 property |
Beyond those two write tools, nothing can change GA4 settings, audiences, or your website. If you connect Google Ads separately, its own connector adds campaign, ad group, and performance reporting - and, only for accounts where you turn it on, tools to create and change campaigns, budgets, keywords, and ads.
Security in one paragraph
Caybl.ai requests Google's Analytics scope (which also covers the two write tools above), stores your credentials encrypted, processes requests in the EU, and gives you a one-click disconnect that immediately revokes access. Google Ads write access is opt-in per account, with dry-run and paused-by-default safeguards. Full detail on how Caybl.ai handles your data.
Try it on your own GA4 property
Connect once, then ask in Claude or ChatGPT. No tokens, no setup.
Get started free →FAQ
No. Caybl.ai fetches data from the Google Analytics Data API on demand, when your agent asks a question, and doesn't warehouse it. Caybl.ai's own database only stores the connection itself (which GA4 property, encrypted refresh token) and usage metadata (which tool ran, when, how long it took) - never the analytics content or your query results.
Whichever you ask. In your own agent - Claude or ChatGPT, on your own plan - Caybl.ai is an MCP server: it exposes tools like 'run a GA4 report', fetches the numbers, and your agent writes the answer. In Ask, Caybl.ai's built-in assistant, Anthropic's Claude writes the answer from the same tools.
For Google Analytics: the seven read tools from Google's own official Google Analytics MCP server - standard reports, realtime reports, funnel reports, account/property lookup, custom dimension and metric listing, and listing linked Google Ads accounts - plus two narrow write tools, marking a GA4 event as a key event and linking a Google Ads account to a property. It still can't change GA4 audiences or your website. If you also connect Google Ads, a separate connector adds campaign, ad group, and performance reporting, plus optional write access you turn on per account.
Your dashboard's 'Disconnect' revokes Caybl.ai's OAuth access immediately and deletes the stored connection. Nothing further can be read after that.
No. You sign in with your normal Google account and approve a standard consent screen. Caybl.ai holds one shared OAuth client; you never create credentials or paste a key.
Sources
- Google Analytics Data API - official Google documentation
- Model Context Protocol (MCP) - the open standard Claude and ChatGPT use for custom connectors