Why does one version of my Wingify test get fewer visitors?
The Wingify help pages give 3 common reasons. The first to rule out: An error in code added to a test can stop Wingify from counting visitors to its versions.
What causes it?
An error in code added to a test can stop Wingify from counting visitors to its versions.
In the Wingify help:
If there is an error in the JS code, Wingify does not count the number of visitors in test variations.
Troubleshooting: Test Pages Recording Uneven Visitor Data in Wingify, read 2026-11-12.When another split URL test runs on the control page of a split URL test, the requests that log control visitors can be cut off, so the control can show fewer visitors.
In the Wingify help:
For example, a different split URL campaign is running on the control page of another split URL campaign. It will cause log visitor requests for control to get aborted in most cases.
Troubleshooting: Test Pages Recording Uneven Visitor Data in Wingify, read 2026-11-12.In a split URL test, Wingify code placed at the bottom of a page can lead to fewer visits being counted.
In the Wingify help:
Also, if the Wingify code is installed at the bottom of the page, it can lead to fewer visits being tracked.
Troubleshooting: Test Pages Recording Uneven Visitor Data in Wingify, read 2026-11-12.
How do I check it myself?
For a split URL test, check that the Wingify code is not added through a tag manager.
In the Wingify help:
Make sure that the Wingify code is not installed through a tag manager.
Troubleshooting: Test Pages Recording Uneven Visitor Data in Wingify, read 2026-11-12.Open the variation's address and check that it does not redirect to another address.
In the Wingify help:
The Variation URL you specified in the test should not redirect to another URL.
Troubleshooting: Test Pages Recording Uneven Visitor Data in Wingify, read 2026-11-12.If the variation is on a different domain from the control, check that cross-domain tracking is on.
In the Wingify help:
Enable Cross-Domain Tracking if the Variation URL is on a different domain.
Troubleshooting: Test Pages Recording Uneven Visitor Data in Wingify, read 2026-11-12.
How does Wingify work with Feder?
- Connect Wingify to Feder and it joins your Visits apps.
- When you connect Wingify, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.
See whether you can trust the numbers in Wingify, one of your Visits apps. Feder only reads. It never changes anything in Wingify.
What else goes wrong with these numbers?
- Why did my Wingify test's visitor numbers disappear?Wingify
- Why did the visitor count drop in my Wingify test?Wingify
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Wingify help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.