Daily campaign pulse
Each morning Memtro records yesterday's sent, delivered, opened, clicked and converted counts per running campaign, so you can ask what changed since last week.
Campaign metrics and customer journeys from Customer.io.
Connect Customer.io with an App API key for your US or EU workspace. Memtro reads campaigns, newsletters and broadcasts with their delivery, open, click and conversion metrics, segment sizes, and individual profiles with their attributes, segments, events and messages. Read-only.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Customer.io tool, reads what it needs, and answers with the source cited.
Each morning Memtro records yesterday's sent, delivered, opened, clicked and converted counts per running campaign, so you can ask what changed since last week.
When a customer writes in, ask what Customer.io has sent them: Memtro returns their recent messages, whether they opened them, their attributes and segments.
Questions people ask once Customer.io is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from Customer.io in Memtro, with the rest of their stack attached.
A record in Customer.io is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, 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.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Customer.io tools are the same everywhere.
Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.