WhoKnew Views™ | View Count Stuck at Zero

Skip to main content
Table of Contents
Print

Diagnose why your product’s view counter shows zero and understand how view tracking works

Your view counter is showing 0 views, but you know people are visiting the product. Before troubleshooting, it’s important to understand how WhoKnew Views™ tracks views—because several types of visits are intentionally excluded to keep your data accurate.


🔍 How View Tracking Works

When a visitor lands on a product page, WhoKnew Views™ runs through a series of checks before recording a view:

// View tracking decision flow
1. Is this a single product page? → No = Skip
2. Is visitor a logged-in admin? → Yes = Skip
3. Is visitor's IP whitelisted? → Yes = Skip
4. Is visitor a bot? → Yes = Skip
5. Has visitor been here recently? → Yes = Skip (cooldown)
6. ✓ Record the view timestamp

If any of these checks fails, the view is not recorded. This is by design—you want accurate data from real, unique customers.


⚠️ Common Reasons for Zero Views

1

You’re Testing as an Admin

Logged-in administrators are automatically excluded from view tracking. This prevents your own browsing from inflating counts.

✅ Solution: Log out of WordPress, clear cookies, and visit the product page in an incognito/private window

2

Your IP Is Whitelisted

If you’ve added your IP address (or your office/home network) to the IP Whitelist, your visits won’t be tracked.

✅ Check:WhoKnew Views → Admin → Scroll to “IP Whitelist” section → Review listed IPs

3

No Real Traffic Yet

If the product is brand new or hasn’t had any genuine visitor traffic, the count will legitimately be zero.

✅ Solution:PRO Use Number Padding to add a realistic baseline to new products

4

Views Expired Outside the Window

The counter shows views within the configured View Window (default: 48 hours). If all views are older than this, they expire and the count drops to zero.

✅ Check:WhoKnew Views → General → “View Counting Window (Hours)” setting
💡 Lifetime views are still tracked in _wkv_total_real_views_ever meta—they never disappear

5

Bot Traffic Was Filtered

The bot filter blocks 50+ known crawlers and bots. If most of your “traffic” is from search engine crawlers, it won’t count.

📊 This is good! You want human traffic only. Bots don’t buy products.
✅ Check: Enable WP_DEBUG_LOG to see blocked bot activity

6

Same Visitor, Still in Cooldown

The Refresh Cooldown (30 minutes default in Free) prevents the same visitor from being counted multiple times. If you keep refreshing, you’re not adding new views.

✅ Solution: Wait for the cooldown to expire, or test from a different device/browser

7

Page Caching Serving Stale Count

If your site uses aggressive page caching, the counter HTML might be cached from when the count was zero.

✅ Fix: Clear all caches (page cache, CDN, object cache) and test in incognito mode


🧪 Testing View Tracking

Here’s how to verify that view tracking is working correctly:

  1. Log out of WordPress completely
  2. Open an incognito/private window
  3. Visit a product page on your store
  4. Wait 30 seconds, then hard refresh (Ctrl+Shift+R / Cmd+Shift+R)
  5. Check if the counter now shows 1 view
  6. Log back in as admin → WhoKnew Views → Analytics → View the product to confirm the view was recorded

✅ Success: If you see “1 view” after this test, tracking is working. The previous zero was simply because no valid traffic had occurred yet.


📊 Free vs Pro View Display

It’s important to understand what the Free and Pro versions display:

VersionWhat’s DisplayedCan It Show Zero?
FreeReal views only (within view window)Yes — if no real views in window
ProReal views + Baseline Padding + VariationsRarely — baseline provides a floor

💡 Pro Tip: With WhoKnew Views™ Pro, the Baseline Padding feature ensures products always display a credible minimum view count (e.g., 96-178 views for “Medium Traffic” preset). This prevents the “0 views” problem for new products.


🔧 Debug Logging

To see exactly what’s happening with view tracking, enable WordPress debug logging:

Add to wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Then check /wp-content/debug.log for entries like:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🤖 WKV BOT FILTER CHECK
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1…)
✅ BOT DETECTED – BLOCKING tracking
Matched Pattern: “Googlebot”

This tells you exactly why a particular visit wasn’t counted.


📋 Quick Diagnosis Checklist

✅ Is This Expected?

  • New product with no traffic yet?
  • Views expired outside window?
  • Only you (admin) visited?
  • Only bot traffic so far?

If yes: Zero is correct!

⚠️ Something’s Wrong?

  • Tested from incognito & still 0?
  • Analytics shows no real views?
  • Other products working, this isn’t?

If yes: Enable debug log & test


🎯 Summary: Why Zero Isn’t Always a Problem

Zero views means:

  • No real, unique human visitors within the view window
  • Your admin/staff visits are correctly excluded
  • Bot crawlers are correctly filtered
  • IP whitelisted users are correctly skipped

This is accurate data. If you want to display higher numbers for social proof on new products, use PRO Number Padding.

If you’ve verified that real human traffic should be counting and it’s still zero, generate a System Info Report and contact support with the details and your debug log.

Share