# Filter internal traffic

Your dev machine, your internal tools, the tab you leave open on your own product all day — real traffic, but not your customers. Keep it out of your dashboards in one click, without ever losing the data.

Source: https://cross-deck.com/university/filter-internal-traffic/
Verified Crossdeck University lesson — prose plus real, runnable code.

## Your own activity skews the very numbers you're reading

You hammer your own product more than any customer does — testing, demos, the tab left open all day. That activity is real, but it isn't a customer, and left in your charts it quietly inflates every number you're trying to trust. Internal-traffic filtering keeps your account's own activity out of its dashboards, the way GA4's "internal traffic" does.

With one important difference: Crossdeck never drops the events. They're always collected and stored. The exclusion is a view applied at read time, on every surface, and it reverses with a single toggle — so a filtering mistake can never cost you data.

## One click for your network — or a rule by hand

The fast path is a single click. In Settings → Internal traffic → Exclude my network, Crossdeck detects the IP your dashboard is browsing from and adds it for you — the GA-style "exclude my traffic," with no IDs to copy or look up.

When you need more reach, you have two more tools:

One detail worth knowing: IPv6 is excluded by network, not by exact address. Privacy addressing rotates your IPv6 host suffix, so Crossdeck excludes the stable /64 prefix; on IPv4 it excludes the exact address. Either way, the rule keeps matching you tomorrow.

## Collected always, filtered on read

Every event is stored the moment it arrives — internal or not. Filtering is purely a query-time view, never an ingestion change, so a misconfigured rule cannot lose data; the full firehose stays auditable underneath. Every event is treated as a customer event until a rule says otherwise.

Because the classification happens on read, it's retroactive: add a rule today and your past events recategorize too — no waiting for new data to accumulate before your charts get clean. And when you want to see your internal activity (to debug your own integration, say), you flip the toggle and it's all there, exactly as it was recorded.

## Customers only — reversible anytime

Click Exclude my network and your charts drop your own noise immediately, including the history you'd already generated. The data underneath is untouched, so toggling internal traffic back on is instant and lossless.

my network · excluded
 Your activity filtered out of every surface, retroactively — events still stored, one toggle to bring them back.