Automation · Operations and reporting

Find out on WhatsApp whether your VWO A/B test has enough visits to decide

An AI agent works out how many visits your VWO A/B test needs, compares them with what it has and tells you on WhatsApp whether you can decide.

Show me this with my own operation See every automation

How do I know if my VWO A/B test already has enough visits or I need to wait more days?

You write to your Met "can I close the pricing page test yet?". The Met finds the campaign in VWO, pulls its report with variations and goals, and its day by day performance to see how many visits it has and how fast they come in. It works out with VWO the sample size the test needs and tells you whether it got there or how many more days it needs at the current pace. If you ask why a variation wins, it checks the page's heatmap. Stopping the campaign starts switched off: the Met only does it if the admin turned that action on.

What starts it

When someone asks for it

It starts when someone on the team asks the Met on WhatsApp about a test. Each check is on demand; the Met does not watch campaigns on its own in this procedure.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Internal Met that follows your VWO A/B tests

This is not a named, seeded Met. It is an internal Met with VWO connected, for the owner or the agency testing changes on the website: it is done when it tells you whether the test has enough sample or how much it still needs.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

VWO Research and analyze

6 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Find the campaign

The Met lists your account's campaigns with their summary and keeps the one you named, by the page or by the name you gave the test in VWO.
- get_campaigns_overview_tool VWO
2
Pull the test's report

The Met pulls the campaign's full report, with its variations and goals, to know how each version compares with the original according to what VWO records.
- fetch_campaign_report_tool VWO
3
See the daily visit pace

The Met pulls the campaign's metrics day by day to see how many visits it has and how many come in each day, which is what defines how much is left.
- fetch_campaign_daywise_data_report_tool VWO
4
Work out the sample it needs

The Met asks VWO for the sample size the test needs and compares it with the visits it has. With the daily pace it tells you whether it got there or how many days are left if nothing changes.
- calculate_sample_size_tool VWO
5
Look at where people click, if you ask why

If you want to understand why a version performs differently, the Met analyzes the page's heatmap and tells you where visitors click and how far down they scroll.
- get_heatmap_clicks_tool VWO
6
Stop the test, only if it is on

If you decide to close the test and the admin turned that action on, the Met changes the campaign's status. That action starts switched off; if it stays that way, the Met tells you to stop it in VWO.
- update_campaign_status VWO

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

An A/B test running in VWO

Your team has an active A/B campaign in VWO with at least one goal defined. Without a goal, there is nothing to compare the versions on.
VWO connected in Met

In Met, open Connections → VWO → Connect and choose the account and the permission level. Browse is enough for this procedure; stopping campaigns also needs that action turned on.
An internal Met on WhatsApp

A team Met with VWO connected that you write to on WhatsApp. It is not the Met that answers your customers: it is for whoever decides the website changes.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not decide for you. The Met tells you whether the test has enough sample and how each version is doing; keeping one and publishing it is your team's decision.
It does not raise your visits. If the test needs months at the current pace, the Met tells you; bringing more traffic is a different job.
It does not stop the campaign with the initial setup: that action starts switched off and the admin decides whether to turn it on.
It does not promise an exact date. The days left come from the test's current visit pace, and that pace can change.
It does not work as is for VWO accounts hosted in Europe or Asia, which use a different server address.

FAQ

Questions about this automation

That it has the visits that, according to VWO's calculation, are needed for the result to be reliable. Before that, a version can be ahead by chance.

Yes. The Met lists your campaigns and pulls the report of each one you name, one by one.

Because changing a campaign's status starts switched off in the connector. If you want the Met to do it, the admin turns that action on and the VWO permission has to allow it.

You do, with your VWO plan. Meteor does not resell VWO: the connector uses your business's account.

Keep going