Data to AI™ / Claude/Google Analytics 4
Ask Claude which channels, landing pages and products actually convert, using the GA4 metrics and dimensions you choose, without building another exploration or export.
Less tokens, better answers.
Claude
Which channel brought the most key events for its traffic last month?
Organic Search brought the most Key Events, 1,446. Email converted best, with 7 key events per 100 sessions against 5 for Paid Search and 3 for Organic Search.
| Channel | Sessions | Key Events | Engagement Rate |
|---|---|---|---|
| Organic Search google / organic | 48,200 | 1,446 | 61% |
| Paid Search google / cpc | 21,500 | 1,075 | 58% |
| Email newsletter / email | 6,400 | 448 | 72% |
Sessions are taken by channel without a Page Path breakdown, so no session is counted twice.
Google Analytics 4 measures how people reach and use your website and apps. Dataddo extracts one flexible GA4 dataset: pick from 184 standard metrics and 374 dimensions, plus custom ones defined in your property.
Which Landing Page values had over 2,000 Sessions last month but an Engagement Rate under 50%, and what do those pages have in common?
A content marketer gets a short list of high-traffic pages that fail to engage, then asks Claude to group them by template or topic before planning the next rewrite sprint.
How did Key Events by Session Default Channel Grouping change last week against the week before? Break any falling channel down by Session Campaign Name.
The marketing lead starts the week in one conversation instead of rebuilding a dashboard, moving from the channel that dropped to the campaigns behind the drop.
Use the dataddo server to list every Event Name with its Event Count since Monday, then compare the list with analytics/events.yaml in this repo.
A developer runs Claude Code in the site repository after a release and spots events that are missing, renamed or firing far less often than the tracking plan expects.
Data to AI™ is free while in private pre-release. We onboard teams in waves and shape the product with their feedback. At launch, it will be priced like the AI assistants your team already uses. Need tailored contracts or volume pricing? Talk to us about Enterprise.
Serve governed business data to Claude, ChatGPT and other AI tools over MCP.
Free during pre-release
Flexibly deploy Dataddo in any cloud or hybrid environment.
We have a payment model that works for you
| Without Dataddo |
With Dataddo
|
Outcome for you | |
|---|---|---|---|
| Getting GA4 into Claude | Build an exploration in GA4, export it, attach the file to the chat, and repeat the whole routine for every new breakdown someone asks about. | Claude asks Dataddo for Sessions, Key Events or Landing Page by name, straight from the GA4 source you scheduled, with no file in between. | No files to attach |
| Days Google is still processing | A morning export includes the last three days, which Google may still change for up to 72 hours, and nothing marks them as provisional. | Claude can call data_status before answering, and a relative date range re-reads recent days on each run until the numbers settle. | Provisional days called out |
| Sessions counted twice | Adding Page Path to a session export counts one visit once per page viewed, so the summed total is higher than the real number of sessions. | Field descriptions from the semantic layer tell Claude what each GA4 metric means, so channel totals come from a source without page dimensions. | Totals that hold up |
| Access for the marketing team | Analysts forward GA4 files around, and nobody can say which export, property or date range a quoted number came from. | On Claude Team and Enterprise an Owner adds Dataddo Data Access once, and every member signs in with their own Dataddo account. | One setup, personal logins |
| Token consumption | Claude spends tokens exploring raw Google Analytics 4 columns, sampling rows and retrying until it understands the data. | Field definitions and relations are supplied up front, so the model skips the exploration and goes straight to the answer. | Less tokens per answer |
| Answer quality | Prone to wrong joins, invented fields and numbers that are hard to check. | Answers grounded in defined fields. In the Dataddo benchmark, 78.5% of questions were answered correctly, against 65.5% with plain CSV files. | Better answers |
The Google Analytics 4 datasets marketing teams use most, with their real field names. Claude queries them by name through the Dataddo semantic layer.
Runs on your schedule with a relative date range. Google needs 24 to 72 hours to process data, so the last 3 days can still change, and the GA4 API allows up to 1 year of history.
Google Analytics 4 connector →We asked 43 pre-registered questions of three real datasets - Google Search Console, HubSpot deals and Google Ads - and delivered the same rows to the same model in four ways. Only the data layer changed.
of questions answered correctly - the best of the four delivery methods tested
fewer confidently wrong answers - 14.0% of runs against 24.0% and 26.3%
more correct answers on messy CRM data - better on 8 questions, worse on none
Same model, prompts and rows in every condition; 759 graded runs, ground truth frozen before any run. On Google Search Console alone, documented CSV files did as well as Data to AI™ - the advantage comes from messier data such as HubSpot deals.
Read the benchmark →Create a Google Analytics 4 source in Dataddo, choose metrics such as Sessions, Key Events and Purchase Revenue with dimensions such as Session Default Channel Grouping, and attach it to a Claude destination or AI Model. In Claude, add the custom connector https://headless.dataddo.com/mcp-data and sign in, or run claude mcp add in Claude Code.
No. Dataddo extracts GA4 on your schedule and serves it through the Data Access MCP server. Claude signs in there with your Dataddo account, never to GA4.
Google needs 24 to 72 hours to process GA4 data, so the latest three days can still move. Ask Claude to check data_status, and treat very recent figures as provisional.
Yes. Run claude mcp add with the Dataddo URL, sign in with /mcp, and Claude Code queries the same GA4 entities while you work in a repository.
One session can visit several pages, so a Page Path breakdown counts it once per page. For channel totals, ask Claude about a GA4 source without page dimensions.
Yes. Dataddo pulls the custom metrics and dimensions defined in your GA4 property, so once you select them in the source, Claude can query them by name like any standard field.
Any plan works. Free allows one custom connector, Pro and Max users add it themselves, and on Team and Enterprise an Owner adds Dataddo Data Access once for everyone.