Cloaking and Traffic Filtering: Terms, Boundaries, and Choices

Filtering classifies request attributes or risk. Routing converts that decision into an action such as a White Page or Target Page response. Cloaking is the broader practice in which selected visitors receive materially different destinations, so it should not be used as a synonym for every filter.

Imagine a mobile visit carrying a campaign source, language, country, ASN, and browser signature. Rules and scoring evaluate those facts; the flow resolves conflicts; its delivery mode then serves or redirects to the chosen destination.

Fraud analysis may need observation and logging without alternate content. Campaign segmentation may need country or device routing. A White Page and Target Page arrangement adds a destination distinction, and therefore requires explicit operational and policy review.

Blocking an abusive IP is filtering, but not necessarily cloaking. A reverse proxy is a delivery mechanism, not a decision policy. Calling every automated classification 'AI cloaking' hides which signal made the decision and makes incidents harder to diagnose.

Draw the flow as inputs, evaluation, decision, and delivery. Label each arrow with the real setting that implements it; if a term cannot be connected to a visible configuration or event field, replace it with language that an operator can test.