---
title: 'Invalid traffic | Plainrouter'
description: 'Traffic classified as unsuitable for a measurement purpose; not an automatic deduction from Plainrouter arrivals.'
last_updated: 2026-09-10
---

# Invalid traffic

Invalid traffic is traffic classified as unsuitable for a particular measurement purpose, for example automated or otherwise non-qualifying visits. The classification method and its deployment status matter.

## Does Plainrouter currently subtract invalid traffic from arrivals?

No. Until invalid-traffic classification is live, every arrival counts. The current arrival total is not an invalid-traffic-filtered or human-only audience.

## Is a rejected request an invalid-traffic classification?

No. Rejecting a malformed or unauthorized request validates an ingestion boundary. It does not establish that an accepted visit is human or that a complete invalid-traffic classifier is operating.

## Does a counting difference prove invalid traffic?

No. Different time windows, collection boundaries, and counting rules can produce different totals. A discrepancy needs investigation rather than a classification label.

## Related reading

- [Arrival counting and pricing](/pricing.md)
- [All definitions](/definitions)
- [Signals](/product/signals)
- [Actions](/product/actions)
- [Implementation guides](/library)
- [API documentation](https://plainrouter.com/docs/api/conversions)