Visits, pages, sources and conversions for every site, remembered day by day.
Connect Fathom Analytics with an API token and Memtro reports how a site did over any period against the one before: visits, visitors, pageviews and bounce rate, with top pages and referrers. It breaks visits down, counts event conversions and says who is on the site now. The hourly sync writes each site's finished day into memory. With a manage or Admin token, and once an administrator has granted each action by name, it can mark milestones, rename sites, turn a public share link on or off, and create sites. Deleting a site erases its data permanently.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fathom Analytics tool, reads what it needs, and answers with the source cited.
These tools change something in Fathom Analytics. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Fathom Analytics is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How did the marketing site do in October compared with September?
Which blog posts got the most pageviews in the last 30 days?
Where did last week's visitors come from, and how many were on mobile?
How many times did the sign-up event convert this month, and from which campaigns?
Add a milestone called Pricing launch on 4 November to the marketing site
The founder asks how the site did last week. Memtro answers from Fathom with visits, unique visitors and bounce rate against the week before, the pages that did the work and the sites that sent the traffic, each change as a percentage.
After the pricing page goes live, Kate Morris asks Memtro to mark the day on the marketing site's charts. Memtro adds a milestone called Pricing launch on that date in Fathom, and everyone who views the dashboard sees it against the traffic.
The teams that lean on Fathom Analytics most, a question each of them asks, and what they connect beside it.
A record in Fathom Analytics is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
CallRail
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowIn Fathom open Settings → API → Create new. Read only (all sites) covers every site and keeps Memtro to reading. A site-specific token with manage permission is needed for milestones and site settings, and an Admin token only to create or delete a site
Copy the token when it is created: it is shown once. Fathom counts API requests against the account's pageviews
In Memtro open Connections → Fathom Analytics, paste the API token, add Site ids from the tracking code only for a site-specific token, and connect
Ask how the site did last month against the month before
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fathom Analytics tools are the same everywhere.
Only when you ask, and only what it has been granted: add, rename, move or delete a milestone on a site's charts; set the currency an event's value is reported in; rename a site, change its reporting timezone, or turn its public share link on or off; create a site, or delete one and all its data permanently. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Fathom Analytics records into memory as entities.
API token. In Fathom open Settings → API → Create new. Read only (all sites) covers every site and keeps Memtro to reading. A site-specific token with manage permission is needed for milestones and site settings, and an Admin token only to create or delete a site.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
