Campaign attribution
Each sent campaign lands in the graph with recipients, unique opens and clicks, unsubscribes and the orders and revenue Klaviyo attributes to it, so marketing and finance read the same numbers.
Customer value, campaign revenue and flow performance from Klaviyo.
Connect Klaviyo with a read-only private key and ask what a customer is worth, how the last campaign converted, which flows drive revenue and how many orders Klaviyo tracked each day. Sent campaigns with their performance and a daily Placed Order summary are synced into the graph.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Klaviyo tool, reads what it needs, and answers with the source cited.
Each sent campaign lands in the graph with recipients, unique opens and clicks, unsubscribes and the orders and revenue Klaviyo attributes to it, so marketing and finance read the same numbers.
Before a support reply or a sales call, one question returns the customer's order count, average order value, predicted value and their last few events.
Questions people ask once Klaviyo 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 Klaviyo in Memtro, with the rest of their stack attached.
A record in Klaviyo 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 Klaviyo tools are the same everywhere.
Set it up as an MCP server →Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.