How to connect Amplitude to an AI agent: what GTM AI agents can do with Amplitude in Day AI
Updated
The short answer. To connect Amplitude to an AI agent, give the agent Amplitude's MCP server with your own Amplitude sign-in, so GTM AI agents, the working end of AI for GTM, can read how an account uses your product in the same place they read every call and email with it. In Day AI, each person opens Settings > Connectors, clicks Connect on Amplitude and signs in, and their agent can then query product analytics, dashboards, experiments, cohorts and session replays from chat, whether you use Day AI in place of your CRM or on top of Salesforce or HubSpot.

Picture a Tuesday at 8:40 in the morning, and you own a mid-size account with a renewal call at ten. Three weeks ago their champion told you the team loves the new reporting. You ask your Day AI agent to get you ready. It reads every meeting and email with the account, then looks the account up in Amplitude: weekly active users are flat, but almost all of that use sits in one team, and the reporting feature the champion praised is used by four people. The agent lays the two side by side and drafts three questions for the call, starting with who else should be using reporting. You cut one question and add the finance lead to the invite. At ten you walk in knowing where the account is thin, and the conversation goes to expansion instead of a surprise.
Where the usual answer goes wrong. Ask a chatbot about an Amplitude chart and it explains the chart. The chart says what happened in the product; it can't say why, and it can't say what the customer asked for last month. Day AI starts from the conversations, which are the record of what the customer wants, and brings Amplitude in as the evidence of what they actually do. You may already export usage into a spreadsheet before big renewals. That was the right instinct; the steps below put that view in front of the rep every time, without the export.
The signal, story, move framework for Amplitude, with Day AI
Usage data helps a go-to-market team only when it turns into something a rep does. Three parts get it there, in this order.
- Signal: what the product says. Amplitude shows who is active, which features they touch and how that is changing. In Day AI, your agent reads that from Amplitude live, inside your own Amplitude access, when you ask about an account.
- Story: what the customer says. A drop in usage means one thing after a reorg and another after a bad support week. In Day AI, the agent reads every meeting, email and Slack thread with the account and puts the usage next to what the customer told you.
- Move: what the rep does about it. A signal and a story are only useful if they become a question, a follow-up or a task. In Day AI, the agent drafts the training offer for the team that isn't using the feature, and it waits in your drafts until you send it.
How to connect Amplitude to Day AI
Step 1: Connect your Amplitude account in Day AI
Open Settings > Connectors, search for Amplitude (or open Browse connectors), and click Connect. Sign in to Amplitude and approve access. There is nothing for a workspace Owner to save first: each person connects for themselves, and the agent works within that person's Amplitude permissions. You can also type "connect Amplitude" in a chat, and your Day AI agent sends you the sign-in link. A connector you just connected works in the same chat.
Step 2: Set Amplitude's tool permissions in Day AI
Open the Amplitude connector to see its Tool permissions, under Read-only and Write & delete. Each tool is Always allow, Needs approval or Off, and each group has Set all. Read tools start at Always allow, which is what you want for looking up charts and cohorts mid-conversation. Any write tool starts at Needs approval, so it waits for you as an approval card in the chat. If you want a chat without Amplitude, turn it off for that chat from the + menu in the composer.
Step 3: Ask your Day AI agent account questions that need usage
Ask in plain words. "How has Northwind's usage changed since their kickoff, and does it match what they said on the last QBR?" "Which features does this account use most, and which did they ask about on calls?" "Show me the cohort this account's new users fall into." Your agent queries Amplitude, reads the account's conversations in Day AI, and answers with both.
Step 4: Turn usage into work in Day AI
From the same chat, ask the agent to draft the follow-up email that offers a training session for the team that isn't using reporting, or to create a task to check adoption again in two weeks. Drafts land in your drafts for you to edit and send, and any Amplitude write tool waits as an approval card in the chat.
Step 5: Put Amplitude in a Day AI skill for the weekly read
For a recurring view, ask your agent to create a skill, such as a Friday digest of usage for every account renewing this quarter, and choose Amplitude in the skill's Connectors picker. The skill reads Amplitude through its owner's connection, so pick the owner whose Amplitude access covers those accounts. Keep skills to reading and reporting; send the follow-ups that come out of them from chat, where you see them first.
To see what else your agent can reach, browse every Day AI integration and connector.
Where a usage report on its own breaks
- The chart has no context. A dashboard shows a dip but not the reorg the customer mentioned on Tuesday. In Day AI, the agent reads the account's meetings and email before it explains the number.
- Someone has to pull it. A pre-renewal export depends on a person remembering to run it. In Day AI, a skill reads Amplitude on a schedule and hands you the summary.
- Session replays go unwatched. Nobody on the account team opens replays before a call. In Day AI, ask the agent to query the account's session replays in Amplitude when a customer says they're confused, and it lists them next to that call.
- Insight stops at the slide. A usage review ends with a note nobody turns into an email. In Day AI, the agent drafts the follow-up and creates the task in the same conversation.