Excluded Visitors

Stop tracking specific visitors while keeping their historical data. Excluded visitors won't have new sessions recorded, but you can still view their past activity.

Overview

Excluding a visitor is different from blocking:

Action Recording Access to Store Historical Data
Exclude Stopped Allowed Preserved
Block Stopped Denied Preserved

Use exclusion when you don't want to track someone but don't need to block their access.

When to Exclude Visitors

Your Own Team

Exclude yourself and team members to avoid skewing your analytics:

  • Store owners
  • Developers
  • Marketing team
  • Customer support

Testing Accounts

Exclude accounts used for testing:

  • Quality assurance
  • Staging tests
  • Demo accounts

Known Non-Customers

Exclude visitors who aren't relevant to track:

  • Partners or vendors
  • Competitors (when you don't want their data)
  • Personal visits to your own store

How to Exclude a Visitor

From the Visitor Profile

  1. Go to Visitors
  2. Find and click on the visitor you want to exclude
  3. Click Exclude Visitor button
  4. Confirm in the modal

Viewing Excluded Visitors

Access the exclusion list at Visitors > Excluded Visitors

The list shows:

Column Description
Visitor ID Unique identifier
Location Country and city
Sessions Historical session count
Pages Total pages viewed
Duration Total time spent
Last Visit When they last visited
Excluded At When you excluded them

Removing an Exclusion

To start tracking a visitor again:

From the Excluded Visitors List

  1. Go to Visitors > Excluded Visitors
  2. Find the visitor
  3. Click Remove
  4. Confirm the action

From the Visitor Profile

  1. Open the visitor's profile
  2. Click Remove from Exclusion

Once removed, new sessions will be recorded again.

Important Notes

Data Preservation

Excluding a visitor:

  • Keeps all historical session data
  • Keeps their visitor profile
  • Stops recording new sessions
  • Stops including them in analytics

Exclusion vs. Blocking

Choose the right action:

Exclude when:

  • You don't want to track them
  • They should still access your store
  • You're cleaning up your own test data

Block when:

  • You want to prevent store access
  • Dealing with bad actors
  • Geographic restrictions needed

Immediate Effect

Exclusions take effect immediately. Any session in progress when you exclude will be the last recorded session.

Best Practices

Exclude Your Own Visits

Your visits can significantly skew analytics:

  • Find your visitor ID (check from your device)
  • Exclude it to keep data clean
  • Do this for all team members

Use Static IPs When Possible

If excluding by IP is needed, use IP-based access control rules for more reliable results.

Regular Review

Periodically review your exclusion list:

  • Remove outdated exclusions
  • Check if anyone should be re-included
  • Verify team members are still excluded

Document Your Exclusions

Keep track of why visitors were excluded:

  • "Own team member"
  • "Test account"
  • "Partner company"

This helps when reviewing the list later.

Limitations

  • Exclusion is visitor-specific (tied to their cookie)
  • Same person on a new device = new visitor (not excluded)
  • For IP-based exclusion, use Access Control instead
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us