For buyers
Plan and send a DOOH RFP
Search current DOOH inventory, build an allocation, separate supplier-facing fields from Tap-only context, and send or replace an RFP.
2 min readUpdated
Something missing from this page? Email help@tap.co
For buyers
Search current DOOH inventory, build an allocation, separate supplier-facing fields from Tap-only context, and send or replace an RFP.
2 min readUpdated
Something missing from this page? Email help@tap.co
Open a Campaign and its DOOH workstream. Campaign objective, budget, flight, Brand, and Product context give the allocation a grounded starting point. DOOH remains separate from radio and TV inventory.
Search the current published catalog by country, region, or locality. Tap groups matching screens by supplier, environment, screen type, geography, and currency. Results can show a screen-count band, daily opportunity, indicative CPM range, coverage precision, and catalog update time.
Choose grouped inventory preferences or exact screens, then set geography, currency, budget, and flight. Opportunity, CPM, coverage, screen count, and the estimate are directional planning evidence. They do not reserve inventory or guarantee delivery.
The send confirmation separates two kinds of information:
| Scope | Included information |
|---|---|
| Supplier-facing request | Counterparty, markets, represented inventory suppliers, screen count, budget, flight, objective, and response deadline. |
| Tap-only planning context | Directional estimated impressions and selected Tap screen identifiers. |
Tap sends the selection as a count and preference summary. It does not send Tap's internal screen identifiers or directional impression estimate as supplier commitments.
Choose Send RFP to counterparty only after reviewing the current revision. Sending queues an immutable revision for delivery and makes that allocation read-only. Retrying the same revision does not create a duplicate send.
If delivery fails, use the retry path without changing the revision. If Campaign requirements change after delivery, create a replacement from the delivered allocation. Tap resolves the saved preferences against the current catalog, keeps the historical allocation addressable, and marks the new allocation current.
The configured DOOH counterparty can return a final written response and optional reference. The result remains a planning-review record in Tap and is not currently converted into a Tap Order.