Check a VWO campaign's goals before it takes traffic

A VWO campaign names goals and a traffic split, and the check shows whether those goals can actually settle the question the campaign asks.

How it works

  1. Connect Wingify's MCP server at https://mcp.wingify.ai/mcp to your AI assistant or coding agent, then sign in with the VWO account holding the campaign.
  2. Install the ExpLint MCP at https://explint.com/mcp to enable your agent to audit tests.
  3. Run the prompt below to audit these plans before the work starts.

How the check runs

  1. It reads the campaign's hypothesis, variations with what each changes, traffic split, and goals, then builds one text with headings taken from those fields and flags the empty ones before checking.
  2. It sends that text to ExpLint with explint__lint, which returns errors, warnings, and passes, each finding naming the rule behind it.
  3. You edit the campaign in VWO and ask for a fresh read and lint, and the report should come back with the errors cleared before the campaign goes live.

Copy and paste this prompt

Change the words in square brackets to name your own project, board, or test.

Prompt for your assistant
Read the VWO campaign [campaign name] with Wingify MCP tools. Build one text from hypothesis, variations and what each changes, traffic split, primary and other goals, and planned run time. Lint it with explint.com against [your ExpLint project name]. Show each error and warning with its VWO setup step. Do not start or edit it yet. Suggest fixes here and re-check after I update VWO.

What ExpLint looks for

ExpLint ships over 24 rules, and a project switches each one on or off or rewrites it in plain English. These are the rules the plans this guide reads break most often. An error means the test cannot answer its question as written, and a warning means the result will be hard to judge when it comes in.

RuleLevelIn plain words
hypothesis/names-metric-and-directionerrorThe campaign hypothesis has to name the goal and the direction it expects, since VWO records the goal as a setting and the prose carries the expectation.
metrics/has-one-primary-metricerrorVWO lets a campaign carry several goals, and the plan has to say which one decides the outcome when they disagree.
power/states-the-minimum-detectable-effecterrorThe campaign should name the smallest lift worth acting on, because a goal and a traffic split alone cannot say whether that lift is visible.
duration/covers-full-business-cycleserrorThe campaign should run across full weeks, since a window that starts on a Tuesday weighs the quieter weekend days differently from a full cycle.

Read more

Portrait of Kameron Tanseli

Kameron Tanseli

Founder, ExpLint

Kameron Tanseli is the founder of ExpLint and a growth engineer who has run more than 1,500 experiments across a nine-year career. As the founding growth hire at Fyxer he launched 540 experiments in a year while the company grew from $1M to $35M in annual revenue, and he now runs growth engineering at FLORA, where a one-person team ships six to eight experiments a week.

Don’t let a bad test make it to production

Install the MCP and start flagging ticket slop before it reaches your users