Brokered Traffic
Some traffic arrives already packaged.
It is purchased, not generated. Aggregated, not sourced. Delivered in volumes that correspond to budgets rather than audiences. The transaction precedes the visit.
A traffic broker does not sell users. The broker sells delivery: sessions per day, geographic distribution, device mix, dwell approximations. Origin is included as a parameter, not a history.
By the time the traffic enters a system, its journey has already been abstracted. What matters is that it arrives in the agreed shape.
The receiving system treats this traffic the same as any other. Sessions initialize. Pages load. Metrics record movement. From the inside, there is no visible distinction between purchased arrival and incidental discovery.
The distinction exists only upstream, and even there it is administrative.
Brokered traffic is useful because it is predictable. It can be scaled, throttled, paused, or redirected without changing the underlying system. It behaves like infrastructure rather than attention. This makes it legible to planning tools.
Intent is distributed across multiple layers:
- The buyer intends volume
- The broker intends fulfillment
- The traffic intends nothing
Downstream analysis rarely accounts for this diffusion. Performance is evaluated on outcomes that assume a unified source, even when the source is contractual rather than organic. Reports do not ask why traffic exists; they ask whether it moved.
Over time, brokered traffic normalizes itself by repetition. Once it appears regularly in dashboards, it becomes part of the baseline. Absence becomes more noticeable than presence.
At that point, the traffic no longer needs to perform. It has already done its work by arriving.
Brokered traffic does not distort systems. It reveals what systems are willing to accept as equivalent, provided it arrives on schedule and in the correct quantities.