Confirm your whitelist rules are working with debug logs, activity tracking, and browser tests
You’ve added IP addresses to your whitelist—but how do you know they’re actually working? A misconfigured pattern could either block nothing or accidentally block real customers. Here’s how to verify everything is functioning perfectly.
🔬 Three Verification Methods
📋
Method 1
Debug LoggingTECHNICAL
📊
Method 2
Activity LogPRO
🌐
Method 3
Browser TestingEASY
📋 Method 1: WordPress Debug Logging
The most detailed verification method—see exactly what’s happening behind the scenes when the whitelist checker runs.
⚙️ Step 1: Enable Debug Logging
Add these lines to your wp-config.php file (before the line that says “That’s all, stop editing!”):
// Enable WordPress debugging
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);⚠️ Important: Never leave WP_DEBUG enabled on production sites! It can expose sensitive information. Enable it only for testing, then disable immediately.
⚙️ Step 2: Visit a Product Page
With your whitelisted IP, visit any product page on your store. This triggers the whitelist check.
⚙️ Step 3: Read the Debug Log
Check wp-content/debug.log for entries like this:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔍 WKV IP WHITELIST CHECK
Visitor IP: 203.45.167.89
Whitelist Data Type: array
Whitelist Empty: NO
Whitelist is Array: YES
Whitelist Count: 3
Whitelist Contents: Array
(
[0] => Array ( [ip] => 203.45.167.89 [added] => 1736179200 )
[1] => Array ( [ip] => 192.168.1.0/24 [added] => 1736092800 )
)
Checking entry #0: Array ( [ip] => 203.45.167.89 ... )
Comparing: 203.45.167.89 vs 203.45.167.89
✅ IP MATCHED - BLOCKING tracking for 203.45.167.89
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━🔎 What to Look For
| Log Message | Meaning |
|---|---|
| ✅ IP MATCHED – BLOCKING tracking | Success! IP was blocked correctly |
| ❌ No match found – ALLOWING tracking | Problem: IP not matching any pattern |
| Whitelist is empty – ALLOWING tracking | Check: No IPs in whitelist |
| Comparing: X vs Y | Shows each pattern being tested |
💡 Pro Tip: Use a text editor with “tail” functionality (or tail -f wp-content/debug.log in terminal) to watch logs in real-time as you test.
📊 Method 2: System Info Activity Log PRO
WhoKnew Views™ Pro automatically logs whitelist blocks to the System Info page—no debug mode needed!
📍 Finding the Activity Log
WhoKnew→WhoKnew Views→📊 System Info
📋 What Gets Logged
Every time a whitelisted IP triggers the blocking mechanism, an entry is added:
IP_BLOCKEDWhitelisted IP 203.45.167.89 matched 203.45.167.89 – view blocked
Jan 6, 2026 14:32:15
IP_BLOCKEDWhitelisted IP 192.168.1.50 matched 192.168.1.0/24 – view blocked
Jan 6, 2026 14:28:03
IP_BLOCKEDWhitelisted IP 10.0.45.123 matched 10.0.*.* – view blocked
Jan 6, 2026 14:15:47
ℹ️ Note: The activity log keeps the last 50 entries to stay lightweight. Old entries are automatically purged as new ones are added.
🌐 Method 3: Browser Testing (No Tech Required)
The simplest verification: test from different networks and watch what happens to view counts.
🧪 The Test Process
- Note the current view count
Pick a product and record its current displayed views - Visit from your whitelisted IP
Open the product page from your computer/office (whitelisted network) - Wait for the refresh cooldown
Default is 30 minutes—or use a private/incognito window - Check the view count again
It should be unchanged—your visit was blocked! - Verify from a different network
Use mobile data (not WiFi) to visit the same product - Confirm the count increased
The view should be tracked normally from the non-whitelisted IP
📱 Getting a Different IP for Testing
📱
Mobile Data
Turn off WiFi and use cellular network—gives you a completely different IP
🔒
VPN Service
Connect to a VPN to appear from a different location/IP
☕
Public WiFi
Coffee shop, library, or any network you haven’t whitelisted
👥
Ask a Friend
Have someone from another location visit your store
🔍 Common Issues & Solutions
❌ Problem: IP Not Being Blocked
| Possible Cause | Solution |
|---|---|
| IP changed since whitelisting | Check your current IP and update the whitelist |
| CIDR notation miscalculated | Use a CIDR calculator to verify your range is correct |
| Wildcard pattern too specific | Broaden the pattern (e.g., 192.168.* instead of 192.168.1.*) |
| Behind a proxy/CDN | Whitelist your real IP, not the proxy’s IP |
✅ Problem: Not Sure What IP to Whitelist
- Go to WhoKnew → WhoKnew Views → Admin tab → IP Whitelist
- Look at the green “Your Current IP Address” box
- WhoKnew Views™ auto-detects your IP—even behind proxies!
- Click “Add My IP” to add it instantly
✅ Verification Checklist
☐IP appears in the whitelist table with correct type badge
☐Debug log shows ✅ IP MATCHED for your IP
☐View count doesn’t increase when visiting from whitelisted IP
☐View count DOES increase when visiting from a different IP
☐System Info Activity Log shows IP_BLOCKED events (Pro)
💡 Pro Tip: Test at least once per month! Home IPs can change when your router restarts or your ISP refreshes DHCP leases. A quick verification ensures your analytics stay clean.