Developer Tools · Integration
VWO
Add VWO to your product for your customers, and give your AI agents governed access to it.
VWO runs experiments and, more recently, feature flags, which makes it two integrations wearing one name. On the experimentation side there are campaigns, the variations inside them, the goals that decide which variation won and the segments that decide who saw what. On the feature management side there are flags evaluated per user, which is a hot path rather than a reporting call and has to fall back to a default rather than block a render. Results carry the honest caveat: a lift is a statistical claim about a sample, so pulling numbers before a campaign has the data to support them produces confident nonsense. Each customer connects their own account, so experiment data and flag state stay inside their tenancy. fastn stores the credentials and absorbs the interface changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own VWO account so the experiments they run are visible inside your product.
Read campaign and variation results so your product can show which variant is ahead against the goal that matters.
Evaluate a feature flag for the user in front of you, with a safe default for when the evaluation cannot complete in time.
Read segments so your product understands who a campaign was shown to before anybody reads too much into a number.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which campaigns are running, how long they have been live and whether any has reached a decision.
An agent explains a result by reading the goal and the sample rather than declaring a winner from a percentage.
An agent checks which flags are on for a given segment, with the lookup recorded.
Example prompt
Which VWO campaigns are live right now, and has any of them reached a conclusive result yet?
Set up VWO in 4 steps
- 01Enable the VWO connector in your fastn dashboard.
- 02Have each customer authorise their own VWO account so campaign and flag data stays in their tenancy.
- 03Map the campaign, variation, goal, segment and feature flag fields your product uses, and decide the default for a flag that cannot be evaluated.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the VWO integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a VWO integration without building it. Your customers connect their own VWO account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a VWO update is not your on-call problem.
- One integration serves your product and your agents. The same governed VWO connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
Optimizely
LaunchDarklyWorks well with
MixpanelOften used alongside
Tools the same teams tend to run next to VWO, across other categories.
Slack
Snowflake
Airtable
PostgreSQLVWO integration FAQ
How do I add a VWO integration to my product?
Enable the VWO connector in your fastn dashboard, then let each customer authenticate their own VWO account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no VWO client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own VWO account?
Yes. Every connection is scoped to the individual customer, so each authorises their own VWO account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this VWO integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which campaigns are running, how long they have been live and whether any has reached a decision.
Who maintains the VWO integration?
fastn does. When VWO changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to VWO events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in VWO?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the VWO integration?
A common starting point: let each customer connect their own VWO account so the experiments they run are visible inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the VWO integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding VWO does not change your per-connector cost. You can start free with 3 connected accounts.
Add VWO to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.