Your team visits your website constantly. You test features. You review content. You check the site daily. Every visit appears in your analytics. Your traffic looks higher than it actually is. Your bounce rate looks better than real visitors experience. Your conversion rate is inflated. You're measuring your team's behavior, not visitor behavior. Internal traffic filtering solves this. You identify your team's traffic and exclude it from reports. Real visitor data stays clean.
This article explains how to identify internal traffic and filter it so your analytics measure real visitors only.
What Is Internal Traffic
Internal traffic is visits from your company's office, your development team, your agency partners, or anyone else working on the website. These visits aren't from real customers or prospects. They're noise in your data.
Internal traffic includes your own visits. You testing features. You previewing changes. You checking how the site looks. These visits get counted as real traffic. They skew your metrics.
The goal of filtering is to separate real visitor data from internal team data. You keep both in your analytics but in different views. One view shows all traffic including internal. Another view shows only real visitors. You analyze the filtered view for decision-making.
Identify Your Company's IP Address
The easiest way to identify internal traffic is by IP address. Your company's office has an IP address or a range of IP addresses. All traffic from that IP is internal traffic.
Find your IP address. Search "what's my IP" in Google. Your browser shows your IP. Write it down.
Some companies have multiple office locations. Each location has a different IP. Document all of them. Some companies use VPNs. VPN traffic comes from the VPN's IP, not your office. Document the VPN IP.
Create an Internal Traffic View
In your analytics platform, create a new view. Call it "Internal Traffic Only" or "Testing." This view shows only traffic from your internal IPs.
In the view settings, create a filter. Filter by IP address. Include only your company's IPs. Save the view.
This view shows you what your team is doing on the site. How many pages your team visits. Which features your team uses. This helps you understand team behavior separately from visitor behavior.
Exclude Internal Traffic From Your Main View
Create another view or modify your existing main view. This view excludes your internal traffic. It shows only real visitors.
In the view settings, create a filter. Filter by IP address. Exclude your company's IPs. Save the view.
This view shows you real visitor behavior. Use this view for decision-making. How many real visitors come to your site. What pages do they visit. How do they convert. This is the data that matters for your business.
Keep a Reference View With All Traffic
Keep one unfiltered view that shows all traffic including internal. This is your reference view. Use it for troubleshooting.
If you're debugging a problem, the reference view shows you all traffic. You can see both real and internal traffic. You can compare to understand what's different.
Don't use the reference view for decision-making. It's polluted with internal traffic. Use it for understanding and troubleshooting only.
Handle VPN and Remote Workers
If your team uses VPNs, you need the VPN IP addresses too. When team members work remotely through a VPN, their traffic appears to come from the VPN IP, not their home IP.
Document all VPN IPs. Add them to your internal traffic filters. Make sure your filter captures all team traffic whether in office or remote.
If your company has changed VPNs, you might have old VPN IPs still in your filter. Clean them up. Old VPN IPs that nobody uses anymore pollute your filter logic.
Test Your Filter
After you set up your filter, test it. Visit your website from your office. Check your internal traffic view. Do you see your visit?
Check your main visitor view. Do you see your visit? You shouldn't. If you do, your filter isn't working. Troubleshoot it.
Test from different locations. From home if you work remote. From the office. From different devices. Make sure your filter catches all internal traffic.
Frequently asked questions
What if we don't know our IP address?
Search "what's my IP" on Google. It shows your IP. Some companies have multiple office IPs. Ask your IT department. They know all company IPs. Document them. Add them to your filter. With WEMASY's website builder, you can set this up directly on your website.
Can we filter by username instead of IP?
Not directly in most platforms. IP filtering is simpler. But if your site requires login, you could create a user role for internal users and filter by role. This requires setting up user roles on your site, which adds complexity. IP filtering is easier.
We moved offices. Our IP changed. Do we need to update the filter?
Yes. Find your new IP. Update your filter to include the new IP. Remove the old IP if nobody uses it anymore. Test the filter. Make sure it captures traffic from your new office.
Contractors and agencies work on our site. Should we filter them?
Yes. Get their IPs. Add them to your internal filter. They're not real visitors. Their traffic skews your data. Filter them the same as your own team.
Our IP range keeps changing. How do we handle that?
If your IP range is dynamic, filtering becomes harder. Ask your IT department for your IP range. Most companies have stable IP ranges. If yours is dynamic, use VPN that provides static IPs. Or work with your IT department to find a stable identifier for your office traffic.
We filtered internal traffic but still see spikes from our office. What's wrong?
Your filter might be missing some IPs. If you have multiple offices, maybe you forgot one. If you use VPNs, maybe a new VPN IP isn't in the filter. Ask your IT department to audit all IPs your team uses. Update your filter.