Two things quietly ruin tracking data: your own testing, and low quality traffic. Both are handled from the Settings tab.
Blocking Your Own IP:
Go to the Settings tab, then the 🛡️ IP Blocking card, and click 🛡️ Block My Own IP. That one button adds the IP you are currently browsing from to the blocked list, so your visits stop being counted. Do this on day one, before you start clicking your own links to check they work.
Blocking Any Other IP:
There are two routes.
- Add the address manually in the IP Blocking card on the Settings tab.
- Click the Block button next to any click in the per link Stats click log, which is faster when you have spotted the offender in your data.
Unblocking:
The blocked list on the Settings tab shows every blocked address with an Unblock action beside it. Removing an address takes effect immediately.
What Blocking Actually Does:
Blocked visitors are still redirected to the destination URL exactly as normal. Their clicks simply are not written to the database. Nobody hits a wall, and nobody knows they were excluded, you just stop paying for that traffic in your reports.
If Your IP Changes:
Many home connections have dynamic addresses. If your own clicks start reappearing in the data, click 🛡️ Block My Own IP again to add the new address.
Clearing Old Click Data:
The ⚠️ Danger Zone card has 🧹 Clear Old Click Data. Pick a date, use Preview to see how many rows are affected, then confirm. It deletes non conversion click records before that date to free up database space. Conversion records are always preserved, so revenue history survives the cleanup.
Resetting All Stats:
The same Danger Zone card has 🚨 Reset All Stats, which is the full wipe. Treat it as a last resort, and export your links and clicks first if there is any chance you will want the history.
Debug Tools:
Between the two, the 🪲 Debug Tools card can log every incoming IPN from WarriorPlus and JVZoo to a file in the plugin folder, and gives you a viewer and a Clear Log button. Turn it on while diagnosing a specific problem and turn it off again afterwards, because the log grows quickly under live traffic.