OctoberDOOH targeting and delivery controlsSee what changed →
Elemental TVDOOH
Digital out-of-home · OpenRTB 2.6

Connect screens.
Control delivery.

Bring digital out-of-home inventory into your ad operations. Target placements and venues, account for multiplied impressions, and measure physical ad plays. Integration starts with your inventory and demand setup.

Integration
OpenRTB 2.6 · VAST tags
Venue targeting
OpenOOH 1.0 and 1.1
Measurement
Impressions + physical plays

From inventory to delivery

For publishers, screen networks, and ad-ops teams working in the ElementalTV App.

Identify and target

Describe the placement. Use DOOH ID, name, domain, and keywords in targeting profiles.
Select venues. Choose venue types from OpenOOH 1.0 or 1.1, with the taxonomy version kept alongside the venue values.
Separate inventory types. Target Site, App, or DOOH traffic with Inventory Type.
Use the right ID. Inventory ID follows the request's inventory object. App ID, Site ID, and DOOH ID each apply to their own object.

Control and measure

Set outbound values. Override DOOH fields sent to demand. Venue overrides set the taxonomy and venue values together.
Keep fractional delivery. Impression caps, budget accounting, and planning use multiplied delivery without truncating it to whole impressions.
Measure physical plays. Report Physical Impressions and Avg Imp Multiplier alongside Impressions.
Use physical rates. Physical fill rates support Dynamic CPM, QPS controls, and the DSP Bidding Optimizer.
Match the venue taxonomy. Venue targeting compares values within the selected taxonomy. Confirm your incoming taxonomy and missing-value settings before enabling a profile.

Start with your screen network

A shared setup for publishers, network operators, and their integration teams.

Share your inventory. Send your screen network, venue types, expected volume, and integration format to our team.
Confirm the request mapping. Agree on placement IDs, publisher fields, venue taxonomy, and impression quantities for your OpenRTB or VAST tag integration.
Configure delivery. Set the DOOH inventory type, demand connections, targeting profiles, and any required overrides.
Validate a sample. Check outbound fields and reconcile Impressions, Physical Impressions, and spend before expanding traffic.

Send your integration details →

DOOH integration reference

Supported fields for OpenRTB 2.6 and VAST tag integrations. Your endpoint and required request fields depend on your setup.

FieldOpenRTB pathVAST tag parameterDemand tag macro
DOOH IDdooh.iddoohid${DOOH_ID}
DOOH Namedooh.namedoohname${DOOH_NAME}
DOOH Domaindooh.domaindoohdomain${DOOH_DOMAIN}
DOOH Keywordsdooh.keywordsdoohkeywords${DOOH_KEYWORDS}
Venue Typedooh.venuetypevenuetype${VENUE_TYPE}
Venue Taxonomydooh.venuetypetaxvenuetypetax${VENUE_TYPE_TAX}
Impression Multiplierimp.qty.multiplierqtymultiplier${QTY_MULTIPLIER}

Venue versions: venuetypetax=1 identifies OpenOOH 1.0; venuetypetax=5 identifies OpenOOH 1.1. The multiplier must be greater than zero and may be less than one.

Inventory IDs: on a DOOH ad unit, doohid takes precedence over the shared inventoryid parameter. Inventory ID targets or overrides the active object's ID; DOOH ID applies only to dooh.id.

If one override sets both Inventory ID and DOOH ID, the DOOH ID rule controls the DOOH object, including its Override Empty setting.

Standards: OpenRTB 2.6 · OpenOOH venue taxonomy. Contact support@elementaltv.com for the mapping for your integration.

For demand integrators

Connect demand that can receive DOOH inventory and its impression quantities.

What Elemental TV provides

DOOH request fields. Placement information, venue values, and quantity fields travel through the configured integration.
Demand routing. DOOH traffic is routed to demand sources with DOOH support enabled and OpenRTB 2.6 compatibility.
Outbound controls. Targeting and overrides let ad-ops teams define the inventory a demand source receives.

What to confirm together

Inventory mapping. Confirm placement IDs, domains, publishers, and the venue taxonomy your integration expects.
Quantity handling. Agree on multiplier handling and impression tracking for the integration.
Reporting units. Reconcile multiplied impressions, physical plays, and spend using the same traffic sample.

Discuss your demand integration →

Two counts. One clear view of delivery.

A physical ad play and a multiplied impression answer different questions.

Impressions reflect the quantity attributed to each ad play. Physical Impressions count the plays themselves. Keeping both lets you plan delivery and evaluate fill rates in the right units.

3Physical ad plays
× 14.2Illustrative multiplier per play
42.6Multiplied impressions
Control or metricWhat it counts
Impression caps and planningMultiplied impressions, including fractional quantities.
Budget capsMonetary spend that includes the multiplier.
Request capsRequests.
Frequency capsPhysical ad plays per identifier.
Delivery limits use response-time estimates. The final response can take delivery over a configured cap. Plan for that behavior when setting limits.

In ElementalTV App reports, Physical Fill Rate compares physical plays with bid requests. Physical Bid Fill Rate compares them with bids. Demand reporting also includes Physical Win Fill Rate, measured against winning bids.

For example, 20 physical plays from 1,000 demand bids give a 2% Physical Bid Fill Rate. At a multiplier of 14.2, the same delivery records 284 impressions and a 28.4% Bid Fill Rate.

Changelog

The DOOH foundation and the controls added since then.