If you use Visitor Queue to spot which companies visit your website, you’ve probably noticed a dirty little secret: your own team shows up in the data. Maybe it’s marketing checking a new landing page, or someone in sales refreshing the site during a demo. Either way, internal traffic can really mess with your lead reports and make you chase ghosts.
This guide is for anyone who wants cleaner data in Visitor Queue—marketers, sales folks, or business owners who are tired of seeing their own company in the leads list. Let's cut through the fluff and get your analytics showing what matters: real visitor interest.
Why Filtering Internal Traffic Actually Matters
Let’s be blunt: if your team’s visits aren’t filtered out, your reports are misleading. You’ll see inflated visitor counts, “repeat” leads that are just your own people, and general confusion about what’s working.
Common headaches: - Wasting time investigating your own company. - Bad data feeding into sales or ad decisions. - Trouble showing real progress to your boss or clients.
If you care about accuracy (and your sanity), filtering internal traffic isn’t optional.
How Visitor Queue Tracks Visitors (and What That Means for Filtering)
First, a quick reality check on Visitor Queue. It identifies companies visiting your site mainly by matching IP addresses against business databases. It’s not tracking individual users by cookies, and it doesn’t always catch remote workers on home Wi-Fi or people on mobile.
What this means for you:
Filtering out internal traffic is mostly about blocking your office’s IP addresses. But if your team works from home, or your office uses a dynamic IP, things get trickier. Still, let’s start with the basics.
Step 1: Find Your Office’s Public IP Address
Visitor Queue can’t filter traffic unless you tell it what to filter. You’ll need your office’s public IP address (the one your internet provider gives you—not the number you see in your computer’s settings).
How to find it:
1. Open a browser from your office network.
2. Go to a site like whatismyip.com or just Google “What is my IP”.
3. Copy the IP address you see—it’ll look something like 203.0.113.42.
Pro tip:
If you have multiple offices, repeat this process in each location.
What if your IP changes?
Some businesses have a static IP (rare for small offices), but most get a dynamic IP that can change. If you notice your filtered IP stops working, check if your provider gave you a new one, and update Visitor Queue with it.
Step 2: Add Your IP Address to Visitor Queue’s Filters
Now you’re ready to tell Visitor Queue to ignore visits from your office.
Here’s how: 1. Log in to your Visitor Queue dashboard. 2. Go to Settings (usually a gear icon, or find it in the main menu). 3. Look for an option like IP Filtering or Exclude IP Addresses. 4. Paste your office’s public IP address into the list. 5. Save your changes.
That’s it. Visitor Queue should now ignore visits from any device using that IP.
If you have multiple IPs:
Add each one on a separate line, or however the interface allows.
What if you don’t see an IP filter setting?
Some plans may not have this feature, or it could be buried. If you can’t find it: - Check Visitor Queue’s help docs or support chat. - Or email their support team—sometimes features roll out quietly.
Step 3: Check That It’s Working
Don’t just trust that things work because you clicked “save.” Test it.
Simple test: 1. Visit your website from the filtered office/location. 2. Wait for Visitor Queue to process new visits (sometimes there’s a lag). 3. Check your Visitor Queue reports—your company shouldn’t show up.
If you still see your own company, double-check the IP address you entered, and make sure you’re testing from the right network.
Heads up:
Visitor Queue updates its data on a schedule. Don’t panic if things take an hour to reflect.
Step 4: Filter Out Internal Traffic from Remote Teams (The Hard Part)
This is where things get messy. If your colleagues work from home, coffee shops, or are always on the move, filtering by office IP doesn’t help.
The honest truth:
Visitor Queue isn’t designed for bulletproof remote filtering. Here’s what you can try:
Option 1: Have remote employees use a VPN
If your company has a VPN that routes all traffic through your office, remote workers will appear to be on the office IP. You can then filter that IP.
Reality check:
Most small businesses don’t have a VPN set up, and asking everyone to use one just for analytics is overkill.
Option 2: Manual filtering
Ask remote workers to avoid visiting the site, or at least warn you before they do so you can disregard those visits.
Let’s be real:
This only works if your team is small and disciplined. It’s not scalable.
Option 3: Ignore it and accept some noise
If remote visits are rare, it may be easier to just live with a little “internal” noise. Focus on the big trends, not the occasional blip.
Step 5: Clean Up Old Data (If You Want)
Filtering only works from the moment you set it up. Old visits from your team will still be in your reports.
Options: - Manually ignore internal visits when reviewing old reports. - Tag or note known internal visits for future reference, if Visitor Queue allows.
Don’t bother with complicated data cleanses unless you really need historical accuracy.
What About Filtering by Cookie or User-Agent?
Some analytics tools let you filter by browser cookie or user agent. Visitor Queue doesn’t—because it identifies companies by IP, not individuals or device fingerprints. Don’t waste time looking for these options.
How to Handle Dynamic IPs
If your office or ISP changes the IP regularly, you’ll need a process: - Check your IP monthly or if you notice internal visits sneaking through. - Update your filter in Visitor Queue with the new address.
If your provider can give you a static IP, it’s worth asking—just don’t expect it to be free.
Other “Filtering” Tricks That Don’t Work
There are plenty of myths out there. Here’s what not to bother with: - Robots.txt: Won’t help—Visitor Queue doesn’t use web crawlers. - Browser plugins: No plugin will stop Visitor Queue from seeing your company’s IP. - Incognito/private browsing: Still uses the same IP; doesn’t help.
Stick to IP filtering.
Quick Checklist: Internal Traffic Filtering in Visitor Queue
- [x] Find your office’s public IP address.
- [x] Add it to Visitor Queue’s IP filter list.
- [x] Test to confirm your company disappears from reports.
- [x] Repeat for all offices or major remote locations (if possible).
- [x] Set a reminder to re-check your IP if your ISP changes it.
Final Thoughts: Keep It Simple, Keep It Honest
Filtering internal traffic in Visitor Queue isn’t rocket science, but it does take a little attention. Most of the time, adding your office IP will get you 90% of the way there. Don’t sweat the rare remote visit—focus on clear trends and real leads. If you’re spending more time fighting your analytics than acting on them, it’s time to step back.
Keep it simple. Check your filters now and then, and get back to the work that matters. Clean data beats perfect data—every time.