What Cloaking Means in Traffic Routing

A cloaking flow places a decision layer between an incoming request and its eventual response. The layer evaluates available context, then sends or serves one destination to some visits and another destination to others according to configured policy.

A practical setup includes a public URL, a White Page, a Target Page, signal collection, decision rules or a risk model, and a delivery method. Event records connect these pieces by showing which flow handled a request and what outcome it selected.

Traffic filtering describes the classification step and may end with observation, tagging, or rejection. Cloaking specifically involves differentiated destinations, while redirecting every visitor to the same landing page is routing without that distinction.

An IP range, user agent, referrer, language, or browser trait provides evidence about a request, not certainty about a person's identity or intent. Reliable designs combine signals, preserve uncertainty, and avoid claiming that one technical attribute proves who is visiting.

Teams need named owners, versioned policy changes, known test cases, and a safe fallback for ambiguous or failed decisions. They should also confirm that their use complies with applicable advertising rules, contracts, privacy obligations, and law.