Implementing vCPM in Programmatic DOOH: A Technical Blueprint

The evolution of programmatic digital out of home (pDOOH) is undergoing a massive paradigm shift, fundamentally altering how media is bought, sold, and measured in the physical world. For decades, the out-of-home advertising sector has been characterized by static billboards and loop-based digital screens, operating in a silo separate from the highly measurable, data-driven world of online digital advertising.

For years, the industry relied on estimated reach metrics, modeled multipliers based on historical census data, and self-reported proof-of-play data that often amounted to little more than a spreadsheet generated by a local media player. Today, the ecosystem is moving toward strict transactional accountability driven by verifiable hardware telemetry, edge computing, and real-time data ingestion. Buyers are no longer satisfied with "scheduled" impressions; they demand cryptographic proof that their creative was rendered to a live audience.

A new standard has emerged for Demand-Side Platforms (DSPs) and publishers alike: Verified CPM (vCPM). This metric mirrors the viewability standards of desktop and mobile advertising, ensuring that an advertiser's budget is only depleted when an ad is definitively proven to have played on a functional, visible screen.

With 60,000+ DOOH screens under contract and 26,643+ screens actively onboarded and emitting live heartbeats, Trillboards is at the forefront of this transition. We provide the programmatic infrastructure-as-a-service required to make vCPM a reality, bridging the gap between legacy hardware and modern ad exchanges.

This technical blueprint outlines exactly how DSPs and network operators can implement vCPM in programmatic DOOH, leveraging OpenRTB 2.6, OM SDK, and real-time impression validation. By adopting these frameworks, the industry can unlock billions of dollars in omnichannel ad spend that previously bypassed out-of-home due to a lack of measurable ROI.

---

The Commercial and Technical Mechanics of vCPM DOOH

Historically, advertisers purchasing DOOH inventory paid based on a media owner's self-reported data. If a Content Management System (CMS) scheduled an ad to play in a loop, the impression was assumed to have occurred. This created a massive blind spot. If a screen was unplugged, experiencing a network outage, or displaying a Windows OS error message over the ad, the CMS would still record a successful play, and the advertiser would still be billed.

This "scheduled equals played" model lacked the rigorous verification standards seen in desktop and mobile programmatic advertising. In the web environment, pixels and viewability scripts confirm that an ad was actually rendered in the user's viewport. DOOH is finally adopting these identical technical standards, forcing media owners to upgrade their infrastructure or risk losing access to premium demand.

In August 2026, the industry reached a major milestone in accountability. As PPC Land reported, adtech platform Big Happy partnered with independent verification provider Veridooh to launch the first Verified CPM programmatic model in the U.S. This partnership proved that the technology to independently verify physical plays at scale was not only possible but commercially viable and highly sought after by major brands.

Under this new model, buyers pay exclusively for plays and impressions that are independently validated as active, fully rendered, and correctly displayed. If a screen loses its internet connection mid-play, or if the hardware reports a display failure, the impression is invalidated in real-time, and the DSP is not charged.

Why vCPM Changes the Programmatic Landscape

The shift to vCPM brings digital-style accountability to physical-world screens. For omnichannel media buyers,who are accustomed to tracking every click, view, and conversion across connected TV (CTV), mobile, and desktop,the ambiguity of legacy DOOH was a major deterrent.

As noted by Street Fight, proving that a DOOH ad actually played in its entirety is critical for capturing larger shares of omnichannel digital ad budgets. When a DSP can look at a DOOH impression and trust it with the same confidence as a pre-roll YouTube ad, DOOH ceases to be an "experimental" budget item and becomes a core pillar of performance marketing.

Implementing vCPM requires a highly synchronized technical stack. It demands real-time hardware telemetry to monitor screen health, independent OM SDK verification to monitor video playback states, and an OpenRTB exchange capable of handling complex impression multipliers dynamically. It requires sub-second latency and an architecture capable of processing millions of concurrent websocket connections and heartbeat payloads.

The Trillboards Revenue Model: Built for Transparency

Transitioning to vCPM requires a Supply-Side Platform (SSP) that prioritizes transparency over opaque fees. Legacy DOOH software providers often operate on a SaaS model, charging network operators exorbitant monthly licensing fees just to keep their screens running, regardless of whether those screens actually generate ad revenue. This model stifles growth and penalizes operators for scaling their networks.

Unlike legacy platforms that charge expensive monthly CMS licenses, Trillboards operates as a free ad server where publishers pay $0/screen/month. We believe that software should enable monetization, not act as a tax on it. By removing the barrier to entry, we allow independent venue owners and massive network operators alike to deploy enterprise-grade programmatic technology instantly.

The platform monetizes exclusively through ad demand via a strict 60/40 revenue split. The venue or publisher keeps 60% of the programmatic ad revenue, while Trillboards keeps 40%. There are no hidden serving fees, no markup on data ingestion, and no punitive costs for API usage.

Key Insight: This 60/40 split aligns the SSP's incentives directly with the publisher's fill rate and eCPM optimization, ensuring that only verified, monetizable impressions are processed. If our publishers do not make money from verified ad plays, neither do we. This mutual reliance drives our relentless focus on maximizing yield, minimizing invalid traffic, and ensuring our vCPM technology is the most trusted in the industry.

---

OpenRTB Ad Verification: Integrating the DOOH Object

To implement OpenRTB ad verification for physical screens, DSPs must fully support the OpenRTB 2.6 specification. Prior to version 2.6, programmatic DOOH was often shoehorned into the site or app objects designed for web and mobile inventory. This led to messy workarounds, where a physical billboard was passed to a DSP as a "website," causing massive confusion for targeting algorithms and reporting systems.

The IAB Tech Lab introduced specific objects to handle the unique physics of out-of-home advertising. Chief among these are the dooh and qty objects, which finally provide a standardized language for machines to negotiate the buying and selling of physical space.

Dissecting the OpenRTB 2.6 DOOH Object

The dooh object replaces the traditional site or app objects in a bid request. It provides the DSP with critical context about the physical venue, screen size, and audience taxonomy. This allows buyers to apply geo-fencing, weather-based triggers, and context-aware creative strategies dynamically.

Trillboards enriches the dooh object using hardware-level data pulled directly from the device via our Partner SDK. We do not rely on static, manually updated spreadsheets; our data is dynamically generated based on the live state of the physical device.

Key attributes of the DOOH object include:

• venuetype: The taxonomy of the physical location (e.g., identifying if the screen is in a transit hub, a retail store, or a medical office).
• venuetypetax: The taxonomy standard in use (e.g., IAB OpenOOH), ensuring the DSP knows exactly how to interpret the venue code.
• plcmt: The placement type (e.g., standalone kiosk, billboard, elevator screen), which helps buyers understand the physical orientation and likely viewing distance of the ad.
• publisher: The entity operating the screen network, crucial for supply path optimization (SPO) and direct deal negotiations.

Trillboards currently supports 38 venue categories under the IAB OpenOOH taxonomy, providing granular targeting for DSPs. This means a buyer looking to target health-conscious consumers can specifically isolate screens in gyms, yoga studios, and health food stores, completely bypassing irrelevant inventory.

Handling the Impression Multiplier via the QTY Object

In traditional digital advertising, one ad render equals one impression. If an ad loads on your smartphone, you are the single individual viewing it. In DOOH, a single ad play is viewed by multiple people simultaneously. A digital billboard on a busy highway might be seen by hundreds of commuters during an 8-second spot.

To account for this, the qty (quantity) object is used to pass the impression multiplier to the DSP. This multiplier is calculated using complex geospatial data, historical foot traffic, and real-time sensor data.

{
  "imp": [{
    "id": "1",
    "dooh": {
      "venuetype": ["1"],
      "venuetypetax": 2
    },
    "qty": {
      "multiplier": 4.5,
      "sourcetype": 1,
      "vendor": "Geopath"
    }
  }]
}

In this payload, the multiplier indicates that a single play of the ad will generate 4.5 viewer impressions. DSPs must ingest this multiplier to accurately calculate the vCPM and pacing of the campaign. For example, if a DSP bids a $10 CPM (Cost Per Mille, or thousand impressions), and the multiplier is 4.5, the DSP will be charged for 4.5 impressions,meaning the actual cost of that single physical play is $0.045. If the DSP's bidding algorithm ignores the qty object, their budget pacing will be wildly inaccurate, leading to severe overspending or underspending.

---

DOOH Impression Validation Standards in Practice

Passing data in a bid request is only the first half of the equation. It represents the intent to play an ad. The second half, and the core of the vCPM model, is DOOH impression validation.

Validation requires physical proof that the scheduled ad actually rendered on the screen. This prevents advertisers from paying for ads that were sent to offline screens, hidden behind error dialogs, or interrupted by hardware failures. Without this validation loop, programmatic DOOH is no better than the legacy paper-based reporting systems of the past.

Independent Verification via OM SDK

The Open Measurement Software Development Kit (OM SDK) is the industry standard for independent ad verification. Originally designed by the IAB Tech Lab for mobile in-app environments, it has been successfully adapted for the unique requirements of digital out-of-home media players.

Trillboards integrates the OM SDK natively into our Partner SDK (@trillboards/ads-sdk). This allows third-party verification vendors to measure viewability and render status without requiring custom integrations for every publisher. By standardizing the measurement layer, we eliminate the friction that historically prevented independent auditing in DOOH.

When a VAST tag is executed, the OM SDK initializes an OMID (Open Measurement Interface Definition) session. It monitors the video player's state, tracking quartiles (25%, 50%, 75% completion), completion rates, and error codes. If the video player crashes midway through a 15-second spot, the OM SDK registers the failure, the impression is flagged as incomplete, and the vCPM transaction is voided. The buyer pays nothing.

Hardware Telemetry and Screen State

Software-level verification must be paired with hardware-level telemetry to achieve true vCPM. Software alone can be fooled; a media player might successfully render a video in its internal memory while the physical HDMI cable connecting it to the monitor is unplugged.

Networks like JUUCE, which operate portable phone charger rental kiosks with digital signage in high-traffic venues, rely on this telemetry. Their systems must verify that the kiosk screen is powered on, un-obscured, and actively displaying content before firing an impression beacon. Because these kiosks are placed in dynamic physical environments like bars and restaurants, they are susceptible to being unplugged by staff, losing Wi-Fi connectivity, or experiencing power surges.

Trillboards requires screens to emit live heartbeats. These heartbeats transmit vital signs including CPU load, network latency, display power state, and volume levels. If a screen misses a heartbeat threshold, it is automatically excluded from the OpenRTB exchange, protecting DSPs from bidding on dead inventory. This hardware-software synchronization is what makes our vCPM guarantee bulletproof.

---

Supply Chain Transparency and the 14-Check Runbook

Programmatic DOOH is not immune to Invalid Traffic (IVT) or supply path spoofing. As budgets shift to physical screens, bad actors attempt to misrepresent inventory. We have seen instances of "ghost screens" where fraudulent publishers generate synthetic bid requests claiming to represent premium billboards in Times Square, when in reality, the traffic is generated by a server farm.

To combat this and enforce strict vCPM standards, Trillboards executes a rigorous 14-check OpenRTB 2.6 supply-chain validation runbook on every ad request. This process occurs in milliseconds, ensuring that only pristine, verified inventory reaches our demand partners.

The Pillars of Supply Chain Validation

Our validation runbook ensures that every node in the transaction path is authorized and verified. We leave no room for unauthorized resellers or domain spoofing.

Critical checks include:

1. ads.txt validation: Ensuring the publisher has explicitly authorized Trillboards to sell their inventory. We crawl and cache these files continuously.
2. sellers.json verification: Publishing our own sellers.json file to map publisher IDs to known business entities, ensuring DSPs know exactly who they are paying.
3. schain (SupplyChain Object) validation: Appending and verifying the cryptographic chain of custody for the bid request. This prevents bad actors from injecting themselves into the middle of a transaction to siphon off revenue.
4. IP & Geo-Bounding Box Cross-referencing: We verify that the IP address of the requesting device matches the physical GPS coordinates claimed in the dooh object, flagging impossible geography (e.g., a screen claiming to be in New York but pinging from a datacenter in Eastern Europe).
5. Timestamp Freshness: Rejecting any bid requests or impression beacons that fall outside acceptable latency windows, preventing replay attacks.

If a request fails any of these 14 checks, it is immediately dropped from the VAST waterfall. This guarantees that DSPs only receive IVT-compliant, highly verified inventory, dramatically reducing the operational overhead required for post-campaign make-goods.

Creative Classification and Brand Safety

vCPM also requires ensuring that the ad content is appropriate for the physical venue. In web advertising, a misplaced ad might be annoying; in DOOH, a misplaced ad can be a public relations disaster and violate local laws.

To date, Trillboards has performed 176,868 creative-level classifications across 129 IAB Content Taxonomy top-level categories. This ensures brand safety and categorization compliance before an ad ever reaches a public screen. Our automated systems, backed by human QA, scan incoming VAST creatives to identify restricted content such as alcohol, gambling, political messaging, or adult themes.

DSPs can bid with confidence, knowing that a liquor ad will never play in a high school gymnasium, and a competitor's ad will not play in a branded retail environment. Venue owners retain ultimate control over their screens, utilizing our blocklists to ensure that the programmatic demand perfectly aligns with their physical brand guidelines.

---

Hardware-Level Verification and Audience Intelligence

The most advanced implementations of vCPM leverage real-time audience sensing to validate impressions dynamically. The traditional DOOH multiplier model relies on static, historical data,for example, assuming a subway station has 5,000 commuters every Tuesday at 8 AM. But what happens if a train is delayed, or a global event drastically alters foot traffic?

Rather than relying purely on historical foot traffic models, modern DOOH networks use edge-computing sensors to detect actual human presence during the ad play. This shifts the multiplier from a "modeled estimate" to a "deterministic fact."

Real-Time Audience Telemetry

Trillboards supports advanced hardware integration for real-time audience intelligence. By interfacing with privacy-compliant edge-computing cameras and LiDAR sensors, our platform can count the exact number of people looking at a screen at the exact millisecond an ad is rendered.

Currently, our system includes 219 sensing-enabled screens emitting segtax=600 audience signals during peak windows. These sensors detect dwell time, attention metrics, and active foot traffic, passing this data back to DSPs in real-time. Because the processing is done on the edge (at the device level), no personally identifiable information (PII) or facial imagery is ever stored or transmitted, ensuring complete compliance with GDPR and CCPA regulations.

IAB Audience Taxonomy Integration

To standardize this data for programmatic buyers, we map all audience signals to the IAB Audience Taxonomy. Raw sensor data is useless to a DSP unless it speaks the language of their existing targeting algorithms.

Our network currently supports 1,558 IAB Audience Taxonomy 1.1 nodes (segtax=4) in OpenRTB requests. Furthermore, we have recorded 588 IAB audience segments observed in live impressions over the past 60 days. This means our sensors are not just counting bodies; they are utilizing contextual and location-based heuristics to classify audiences,such as identifying a surge of "Business Travelers" at an airport lounge or "Fitness Enthusiasts" at a gym network.

This granular audience data allows DSPs to move beyond simple location targeting and execute true audience-based buying in the physical world. A buyer can set a campaign to only bid when a specific audience segment is physically present and verified by hardware sensors.

Pro Tip: DSPs should configure their listening endpoints to ingest segtax=600 signals. This data is the key to transitioning from estimated multipliers to deterministic, verified audience counts. By ingesting this data, DSPs can offer their advertisers unprecedented accuracy in physical-world attribution modeling.

---

Building the Architecture: Webhooks and Event-Driven Validation

For developers and CTOs building DSP integrations, polling REST APIs for impression status is highly inefficient. When you are dealing with tens of thousands of screens emitting data every second, a polling architecture will quickly exhaust server resources, inflate cloud computing bills, and introduce unacceptable latency into the verification process.

Trillboards solves this through a robust, webhook-driven event architecture. This system pushes state changes to your infrastructure in real-time, forming the backbone of our vCPM capability. It is designed for massive concurrency and fault tolerance.

The Webhook Event Lifecycle

Our OpenAPI spec (available at /developer/docs) defines a comprehensive suite of webhook events for device status, impressions, payouts, and audience spikes. By subscribing to these webhooks, DSPs receive an immediate, asynchronous stream of truth regarding their campaigns.

When an ad is delivered, the following event lifecycle occurs:

1. device.heartbeat.verified: Confirms the hardware is online, the screen is powered on, and the network connection is stable enough to download the creative.
2. ad.scheduled: The VAST tag is successfully parsed and queued by the local player's internal memory.
3. impression.rendered: The OM SDK confirms the first frame of the video has painted onto the physical display panel.
4. impression.verified: Trillboards validates the supply chain, OM SDK data, and hardware telemetry, confirming a billable vCPM event. This is the final, authoritative signal that the transaction is complete.

Ingesting the Verified Impression Payload

DSPs must listen for the impression.verified webhook to trigger their billing and pacing engines. This payload contains everything required to clear the transaction financially and report the success back to the agency or brand.

{
  "event": "impression.verified",
  "timestamp": "2026-09-15T14:32:01Z",
  "data": {
    "transaction_id": "tx_987654321",
    "device_id": "dev_abc123",
    "multiplier_applied": 3.2,
    "verification_source": "omsdk_v1.4",
    "supply_chain_status": "valid"
  }
}

By building an event-driven ingestion pipeline, DSPs can process thousands of concurrent screen events without dropping validation data. The multiplier_applied field ensures that the DSP applies the exact same math that Trillboards used to clear the auction, preventing any billing discrepancies at the end of the month.

---

MRC Compliance and the Future of Programmatic DOOH

The push toward vCPM is heavily influenced by the Media Rating Council (MRC). The MRC acts as the independent watchdog for media measurement, and their guidelines dictate how billions of dollars in ad spend are allocated by major holding companies.

The MRC released Phase 1 of their OOH Measurement Standards in 2024, focusing on physical play verification. This phase mandated that an ad must be proven to have played on a screen to be counted as an impression. In mid-2025, they opened Phase 2, which standardizes Audience measurement and dynamic multipliers, pushing the industry to adopt the real-time sensor technologies discussed above.

Aligning with MRC Standards

DSPs and networks that fail to adopt these standards will find themselves excluded from premium omnichannel campaigns. Major advertising agencies are increasingly writing MRC compliance into their Master Service Agreements (MSAs), meaning non-compliant inventory is automatically blacklisted.

As Invidis detailed, the partnership between Big Happy and Veridooh proves that buyers are willing to pay premium rates for MRC-aligned, verified inventory. Brands are happy to pay a higher CPM if they are guaranteed zero waste and absolute transparency.

Trillboards' architecture is designed to support these evolving standards out-of-the-box. Our three API tiers,Basic, Developer, and Enterprise,allow networks of all sizes to access MRC-compliant ad verification tools without building them from scratch. Whether you are operating 50 screens in local coffee shops or 5,000 screens in transit shelters, our platform ensures your inventory meets the strictest global standards for programmatic trading.

---

Actionable Takeaways for DSPs and Publishers

Implementing vCPM in programmatic digital out of home campaigns requires coordinated effort between buyers and sellers. It is not enough for one side of the marketplace to upgrade; the entire supply path must be modernized.

Here are the critical steps for technical teams looking to modernize their DOOH infrastructure and capitalize on the vCPM revolution:

For Demand-Side Platforms (DSPs)

• Upgrade to OpenRTB 2.6: Ensure your bidder can parse the dooh object and correctly apply the qty.multiplier to your CPM calculations. If your system still treats DOOH screens like mobile phones, you will fail to pace campaigns correctly.
• Integrate OM SDK Data: Do not rely solely on publisher pixels or server-side impression beacons. Ingest and validate OM SDK telemetry to confirm ad viewability and quartile completion.
• Enforce Supply Chain Checks: Reject bids that fail schain or ads.txt validation to protect your advertisers from IVT. Build strict logic that drops any bid request lacking a valid cryptographic signature.

For DOOH Publishers and Network Operators

• Ditch Legacy CMS Fees: Stop paying monthly fees for software that doesn't generate revenue. Explore our pricing model to see how our free ad server works and how you can transition to a purely revenue-sharing model.
• Implement Hardware Telemetry: Ensure your screens can report their power state and network status in real-time. If your current media players cannot emit live heartbeats, it is time to upgrade your hardware or firmware.
• Leverage the Partner SDK: Use the @trillboards/ads-sdk to instantly add VAST waterfall capabilities and OM SDK verification to your React, Flutter, or CTV applications. Our SDK handles the heavy lifting of OpenRTB compliance so you can focus on expanding your physical footprint.

Key Insight: If you operate a specific venue type, understanding your exact earning potential is crucial. For example, operators can review our comprehensive hub of venue monetization guides to optimize their specific screen placements. Whether you are looking at dwell times, screen positioning, or audience demographics, our resources, such as the nail salon digital signage income guide, provide the exact blueprints needed to maximize your programmatic yield.

---