Diagnosing and Fixing Internal Traffic Inflation in Microsoft Clarity

Recognizable condition

When reviewing Microsoft Clarity reports you see an unexplained surge in page views or sessions that originate from IP addresses you know belong to your corporate network. This internal traffic skews conversion rates, bounce rates, and other engagement metrics.

Cause and diagnostic table

Ordered checks

1. Verify IP filter configuration
   Open the Clarity portal, select your project, go to Project Settings → IP filters. Confirm that each internal network range you wish to exclude is present as a valid CIDR (e.g., 10.0.0.0/16) or single IP. Permission required: Project Owner or Admin.
2. Check format and syntax
   Ensure there are no extra spaces, commas, or line‑breaks inside an entry. Correct format examples: 203.0.113.0/24 or 192.168.1.5. Incorrect examples: 203.0.113.0/24, or 203.0.113.0/24 .
3. Save and note the timestamp
   Click Save. The UI should display a "Last updated" timestamp. If the timestamp does not change, the change may not have been persisted.
4. Wait for data to refresh
   Clarity applies IP filters to newly collected events only. Allow up to 24 hours for the change to affect incoming data.
5. Validate with Live View
   After the waiting period, open Live View (or the real‑time dashboard) and trigger a page load from a known internal IP. Verify that the session does not appear in the live list.
6. Export a sample for confirmation
   Navigate to Data → Export, request a CSV of sessions for the last hour filtered by the internal IP range. Open the file and confirm the row count is zero.

Fixes tied to findings

• If the IP filter list is missing or contains wrong CIDR blocks – add the correct entries, save, and repeat steps 3‑5.
• If the format is malformed – edit each line to match the CIDR syntax, save, and repeat steps 3‑5.
• If the filter appears saved but the timestamp does not update – try saving again after a brief pause; if the issue persists, contact Clarity support as the backend may have failed to persist the change.
• If internal traffic still appears after a correct filter and 24‑hour wait – investigate CSP or firewall: open browser dev tools on an internal host, look for blocked requests to https://www.clarity.ms/tag/. If blocked, work with network team to allow the domain or adjust the CSP header to include script-src https://www.clarity.ms.

Escalation criteria

Escalate to Microsoft Clarity support when:

• IP filter entries are correct, saved, and timestamp updates, yet internal traffic continues to appear in Live View after 48 hours.
• Export data shows non‑zero sessions from the internal IP range despite the filter.
• Network traces confirm the Clarity snippet loads successfully from internal hosts but the filter is ignored.

Limitations and practical verification

IP filter changes affect only data collected after the update; historical reports retain the inflated numbers. To verify the fix, compare the "Overview" graph before and after the 24‑hour window, focusing on the internal IP segment (you can add a temporary filter for that range to see if it drops to zero).

Rollback

If you need to revert, return to Project Settings → IP filters, restore the previous CIDR list (copy from a backup or screenshot), save, and wait another 24 hours for the change to take effect.