Exclude authenticated visits from your analytics
Filter out authenticated user visits from your analytics to get accurate visitor data and focus on genuine website visitors.
Step 1: Access Filter Settings
- Go to your dashboard and select the website you wish to filter out internal traffic
- Click on the dropdown menu for your website in the top left of your dashboard

- Click on "Site Settings"
- Under "Filter" tab, enable the "Exclude authenticated visits" toggle
Private Routes Configuration
Define which routes in your application should be considered private. Visits to these routes will be used to identify authenticated users.
Example Routes:
/dashboard/**- Matches all dashboard routes/settings/**- Matches all settings pages/profile/**- Matches all profile related pages
Configuration Tips
- Wild card tags (
/**) will be automatically added to your private routes - You can add multiple routes to cover different private sections
- Routes are case-sensitive
How It Works
When a user visits any of the configured private routes, VersaTailor identifies them as an authenticated user. All subsequent visits from that user (including to public pages) will be excluded from your analytics until they clear their browser data or the session expires.
Best Practices
- Include all private areas: Make sure to include all routes that require authentication
- Use wildcards: Use
/**to match all sub-routes under a path - Test thoroughly: Verify that authenticated users are properly excluded
- Monitor results: Check your analytics to ensure the filtering is working correctly
Troubleshooting
Authenticated visits still appearing
If authenticated visits are still showing up:
- Check that the private routes are correctly configured
- Verify that the routes are case-sensitive and match exactly
- Ensure users are actually visiting the private routes
- Clear browser data and test again
Too many visits being excluded
If legitimate visitors are being excluded:
- Review your private route configuration
- Make sure you're not including public routes
- Check that route patterns are specific enough
- Test with different user scenarios
Next Steps
Now that you've configured authenticated visit exclusion:
Need help? Contact us for assistance.
Suggest features? We'd love your feedback