What changed in our VWO tests this week, and which campaigns are running?
VWO connects Memtro to your experimentation platform. It reads workspaces, campaigns with their status, URLs, goals and variations, and websites with their tracking status. It reads feature flags with their projects and environments, the workspace timeline of what was started, paused or changed, and metric reports with aggregated conversions and revenue. When asked and granted, it can create or rename a campaign, add a variation, create, update or delete a feature flag, and turn a flag on or off in an environment. Per-variation results are not available, and a new campaign stays not started until somebody starts it in VWO.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right VWO tool, reads what it needs, and answers with the source cited.
These tools change something in VWO. 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 VWO 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.
What changed in VWO this week?
Which campaigns are running right now?
Which websites have no SmartCode detected?
What conversions and revenue did the checkout report show?
Rename the homepage hero campaign to Hero banner test.
Maya Okafor, growth lead at Northwind, asked what had changed in VWO this week. Memtro read the workspace timeline, listing the campaigns started, paused or changed, then the checkout metric report's conversions and revenue. She shared it at the Monday growth meeting.
Tom Reilly, engineering manager at BigCo, asked Memtro to turn the new search flag off in production after customers reported errors. With the action granted to his team, Memtro switched the flag off in that environment. Every user served there saw the old search at once.
The teams that lean on VWO most, a question each of them asks, and what they connect beside it.
A record in VWO 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 VWO, open Developers, then Tokens, and create a token. It does not expire, so revoke it on the same page when it is no longer needed.
In Memtro, open Connections → VWO and paste the API token. Leave Workspace as current for the main workspace, or enter another workspace's number.
An administrator grants the campaign and feature flag actions by name to the teams that may use them, since a flag toggle changes live behaviour.
Ask what changed in VWO this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The VWO tools are the same everywhere.
Only when you ask, and only what it has been granted: create a campaign (created as not started); rename a campaign; add a variation to a campaign; create a feature flag; update a feature flag's name or description; delete a feature flag; turn a feature flag on or off in an environment. 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.
API token. In VWO, open Developers, then Tokens, and create a token. It does not expire, so revoke it on the same page when it is no longer needed.
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
