To connect Amplitude to Claude, link your project at onboard.windsor.ai/app/amplitude, then add the Windsor.ai connector in Claude. That’s it. Open a new chat and ask about your product usage data.
Here’s the problem it solves: Amplitude’s own dashboards are built for exploring one project at a time, so answering a question that spans product usage and everything else usually means exporting a chart or CSV and rebuilding it by hand in a spreadsheet.
That works for a single question, but it leaves session, cohort, and event data disconnected from your acquisition and marketing numbers.
Connecting Amplitude to Claude through Windsor.ai skips that step. Claude gets a live connection to your session, cohort, and event data, and can blend it with your other connected sources in the same conversation.
2 steps to connect Amplitude to Claude
Connecting Amplitude to Claude via Windsor.ai takes two steps and no code.
📖 For the full walkthrough, see Windsor’s documentation on integrating data into Claude.
Prerequisites
- An active Windsor.ai account (free or paid)
- An Amplitude account with an active project tracking events
- A Claude account
Step 1. Connect Amplitude to Windsor
Log in to onboard.windsor.ai/app/amplitude and select Amplitude as your data source.
Authorize Windsor.ai to read your project’s data. Repeat the authorization step for any additional Amplitude projects you want Windsor.ai to pull from.
Step 2. Add the Windsor.ai connector in Claude
In Claude, open the Windsor.ai connector page and select Connect.
💡 Pro tip: Set permissions to “Always allow” so Claude can query your Amplitude data without asking for confirmation on every prompt.
Confirm the connection is live before you start analyzing anything:
Show my average session length by week for the last two months.
If Claude returns real session-length numbers by week, the connection is working and you’re ready to query your product data in natural language.
The metrics that matter for Amplitude
| Metric | What it tells you |
|---|---|
| Event type | The specific action a user performed, such as a button click or purchase, the core building block of every Amplitude report. |
| Session ID | Groups the sequence of events a user generated in one active session, the basis for session-length and engagement metrics. |
| Platform | Whether the event came from web, iOS, or Android, so you can compare behavior across platforms. |
| Paying | Flags whether the user was a paying customer at the time of the event, useful for separating free vs. paid behavior. |
| Average session length | How long, on average, users stay active in a session, a core engagement signal for whether a product is getting stickier or losing people faster. |
| Active users | The daily count of users active in your product, the base metric for tracking product-wide engagement over time. |
| Cohort size | How many users belong to a saved cohort, so you can track how a specific audience segment grows or shrinks. |
| Cohort popularity | How often a saved cohort gets used across your team’s charts and reports, a read on which audience segments people actually rely on. |
| Event properties | The custom properties attached to an event, such as a plan tier or button label, as instrumented in your own project. |
What to ask Claude about your Amplitude data: prompt ideas
Engagement trend
Break down active users by date for the last quarter and flag any week with a drop.
Cohort growth comparison
Compare the size and popularity of my saved cohorts over the last 30 days.
Event volume by platform
List the event types firing most often in my Amplitude project this month, broken down by platform.
Feature adoption check
Which events have seen the biggest increase in volume this month compared to last month?
Bonus: analyze Amplitude alongside your full marketing stack
Windsor.ai connects 350+ data sources, so Amplitude doesn’t have to sit in its own silo. A few practical blends:
- Amplitude + Google Ads: See which acquisition channel brings in users who actually stick around, not just install and disappear.
- Amplitude + Stripe: Connect product engagement and cohort data to what a user is actually worth over time.
- Amplitude + AppsFlyer: Trace the full path from ad click to install to real in-app engagement.
Conclusion
Amplitude captures the sessions, cohorts, and events that show how people actually use your product, but that data only tells the full story once you can query it in plain language alongside the rest of your marketing stack.
Connecting Amplitude to Claude through Windsor.ai turns a two-step, no-code setup into a live line to your product data, so retention and engagement questions are just a prompt away.
🚀 Ready to talk to your product data? Connect Amplitude to Windsor.ai for free and start querying it in Claude today.
FAQs
Do I need to write any code to connect Amplitude to Claude?
No. The setup is entirely no-code: authorize your Amplitude project in Windsor.ai, then add the Windsor.ai connector in Claude.
Can I connect more than one Amplitude project?
Yes. You can authorize multiple Amplitude projects in Windsor.ai, useful for agencies or companies running separate projects per app or environment.
Can I combine Amplitude with other data sources?
Yes. Windsor.ai connects 350+ data sources, so you can blend Amplitude’s product data with sources like Google Ads or Meta Ads in the same Claude conversation.
Can Claude change anything in my Amplitude project?
No. The Amplitude connection is read-only. Claude can read and analyze your product data, but it can’t create, edit, or push any changes back into Amplitude.
Windsor vs Coupler.io

