RTB (Real-Time Bidding)

RTB is the millisecond-scale auction protocol that runs inside ad exchanges. When a page loads, the impression is put up for auction, DSPs submit bids based on user and context, and the highest bid wins and serves. Ad-tech components are the plumbing between an impression, a bid and a recorded conversion. You rarely touch them directly day to day, but when they are misconfigured every downstream number is wrong — and the symptom looks like a creative or targeting problem. Read it next to Ad Exchange, DSP (Demand-Side Platform), SSP (Supply-Side Platform).

Document the data path end to end: what fires, where it is sent, what identifiers travel with it and what consent state applies. Prefer server-side event delivery for durability, dedupe events explicitly, and re-verify after any site or checkout change.

Validate rather than assume. Compare event counts against orders in your commerce system, check event match quality where the platform exposes it, and watch for silent drops after releases. A five percent signal loss is invisible in a dashboard and material in delivery. Why this matters commercially: RTB is why programmatic works at scale. Manual buying couldn't price 100,000 different impressions per second; RTB does it automatically.

Clean signal is what lets an automated creative loop work at all: Xeli attributes results back to concepts and SKUs, and that mapping is only as good as the events underneath it. Fix the plumbing first, then let the loop compound. In the context of ad tech & ecosystem, that means the concept stops being something a person re-applies by hand every campaign and becomes a rule the system enforces on every asset it produces.