Visitor Filter
How it Works Features Pricing About Us Changelog Status

Troubleshooting

Common issues and their solutions when working with VisitorFilters.

Script Not Collecting Events

Symptom

The dashboard shows no events after installing the collector script.

Solutions

  • Verify the script is loading: Open browser DevTools → Network tab → filter by "vf.js". You should see a 200 response.
  • Check the Site ID: Ensure data-site matches your actual Site ID from the dashboard.
  • CSP blocking: Check the browser console for Content Security Policy violations. Add our domain to your CSP directives.
  • Ad blockers: Some ad blockers may intercept our script. Test in an incognito window with extensions disabled.
  • Domain verification: The site must be verified before events are processed. Check Sites → Status.

Rules Not Triggering

Symptom

You've created a rule but it doesn't seem to be enforced.

Solutions

  • Check priority: A higher-priority Allow rule may be matching before your block rule.
  • Rule is disabled: Ensure the rule's status is Active.
  • Condition mismatch: Double-check your condition configuration. Use the Rule Tester in the dashboard to simulate.
  • Cached response: If you're testing yourself, your browser may be serving a cached page. Clear cache or use incognito.

High Quota Usage

Symptom

Your monthly event quota is depleting faster than expected.

Solutions

  • Bot traffic: Bots generate events too. Add bot-blocking rules to reduce unnecessary event consumption.
  • SPA mode: If data-spa="true" is set, every route change counts as an event. Only use this for genuine SPAs.
  • Multiple script instances: Verify the script is only included once per page (check for duplicate inclusions in layouts/partials).

Webhook Delivery Failures

Symptom

Webhook deliveries show as failed in the dashboard.

Solutions

  • Endpoint unreachable: Ensure your server is publicly accessible and responding to HTTPS POST requests.
  • Timeout: Your endpoint must respond within 10 seconds. Process webhooks asynchronously.
  • Non-2xx response: Your endpoint must return a 200-299 status code to confirm receipt.
  • SSL certificate: Ensure your endpoint has a valid SSL certificate (self-signed certs are rejected).

Login / Account Issues

  • Can't log in: Use the password reset flow. If email doesn't arrive, check spam folder.
  • 2FA locked out: Use a recovery code. If you've lost recovery codes, contact support.
  • Email verification pending: Click "Resend verification" on the verification screen. Check spam folder.

Need More Help?

If your issue isn't covered here:

  • Use the Feedback form in your dashboard to report bugs or request features
  • Check the Status page for any ongoing incidents