Why did the visitor count drop in my Wingify test?

The Wingify help pages give 5 common reasons. The first to rule out: Wingify treats the http and https versions of a page as different addresses, so a test set up for one can miss visitors who land on the other.

What causes it?

  1. Wingify treats the http and https versions of a page as different addresses, so a test set up for one can miss visitors who land on the other.

    In the Wingify help: Wingify differentiates the URLs on the basis of http and https. Visitors Not Being Tracked Properly by Wingify, read 2026-11-12.

  2. Visitors whose browsers have JavaScript turned off are not tracked, so they do not appear in the visitor count.

    In the Wingify help: Wingify does not track visitors who have disabled JavaScript in their browser settings. Visitors Not Being Tracked Properly by Wingify, read 2026-11-12.

  3. Only pages included in a campaign are tracked, so visitors on other pages are left out of its count.

    In the Wingify help: Tracking will not be done on the URLs which have not been included in the campaign. Troubleshooting: Data Discrepancy Between Wingify and GA, read 2026-11-12.

  4. Visitors who use ad blockers or privacy tools can be missed, and Wingify notes the same can happen in other analytics tools.

    In the Wingify help: Visitors using ad blockers or privacy tools could hinder proper tracking by Wingify or GA. Troubleshooting: Data Discrepancy Between Wingify and GA, read 2026-11-12.

  5. A page that loads only partly, because of an error or a slow connection, can keep the tracking script from running for that visit.

    In the Wingify help: Partial page loading due to errors or slow connections may affect proper script firing for either tool Troubleshooting: Data Discrepancy Between Wingify and GA, read 2026-11-12.

How do I check it myself?

  1. Check that visitors land on exactly the address your test includes, including after any redirect.

    In the Wingify help: Check if the visitors are landing on the exact URL that is specified in the “Included URLs”. Visitors Not Being Tracked Properly by Wingify, read 2026-11-12.

  2. Make sure the Wingify tracking code is installed on every page you want tracked.

    In the Wingify help: Ensure that Wingify tracking code / GA code is installed across all the website pages where tracking needs to be done. Troubleshooting: Data Discrepancy Between Wingify and GA, read 2026-11-12.

  3. If the test only includes some visitors, check that the condition choosing them is the one you meant.

    In the Wingify help: Check if the segmentation condition (if any) applied is correct. Visitors Not Being Tracked Properly by 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.

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.

Know the day a number breaks, not the month after.