How can you prevent your own team’s views and testing from skewing our engagement data?

We understand that during testing or internal reviews, you want to ensure that your activity is not recorded as "user engagement" in your performance dashboard. How we handle this depends on which environment you are viewing.

Staging Environments

We have configured our system to automatically disable analytics tracking on all Staging environments. Any testing, clicking, or navigation performed on a staging URL is completely ignored by the reporting system.

Live Environments

If you are reviewing your Live experience and do not want your visit to count toward your analytics, you must Decline Cookies upon entry.

• How to do it: When you load the tour, the Cookie Consent banner will appear. Select "Decline" (or "Reject").

• The Result: If cookies are declined, the platform will not send any analytics "pings" for that session. You can browse freely without affecting your data.

Why don't we just block our IP Address?

We are frequently asked if we can block specific University IP ranges to filter out staff traffic automatically. We do not implement IP blocking for the following reason:

University IP ranges are often shared across the entire campus network. This means that staff, faculty, and students often share the same IP address. If we were to block your University IP to filter out your marketing team, we would inadvertently block valid traffic from current students or on-campus visitors, resulting in a loss of valuable data.