DV360 Custom Bidding for CTV SPO
Setting up Custom Bidding algorithms in Display & Video 360 (DV360) for Connected TV (CTV) supply-path optimization (SPO) requires shifting focus from standard cost-per-mille (CPM) minimization to evaluating deterministic path value and inventory directness. Standard bidding models often treat all CTV inventory equally, failing to account for multi-hop reseller chains, hidden tech fees, and variable publisher bid-stream signals. By deploying a custom script utilizing Google Cloud, ad ops teams can programmatically score incoming bid requests based on exchange hop count, seller.json transparency, and direct publisher relationships, ensuring budget flows exclusively through optimized, low-latency pathways.
Key Takeaways
- Custom Bidding scripts in DV360 evaluate incoming bid requests using Python-like syntax, allowing traders to assign bid multipliers based on specific supply-path attributes.
- CTV supply-path optimization requires filtering out multi-hop reseller paths where intermediary SSP take-rates can consume over 30 percent of working media.
- Integrating sellers.json validation directly into custom scoring logic prevents ad spend from leaking into unauthorized reselling domains.
- Algorithms must balance strict path efficiency rules with delivery constraints to avoid severe under-pacing on targeted CTV campaigns.
The Mechanics of CTV Supply-Path Inefficiencies
Connected TV inventory commands the highest CPMs in programmatic advertising, making it the primary target for supply-path arbitrage. Reseller chains frequently dilute working media. A single publisher impression might pass through three or four supply-side platforms (SSPs) before reaching DV360. Each intermediary extracts a margin, resulting in a bloated effective CPM (eCPM) for the buyer and diminished yield for the content owner.
Traditional DV360 targeting settings allow traders to restrict inventory sources by selecting specific exchanges or preferred deals. However, open-exchange CTV buying remains vulnerable to authorized digital sellers (ads.txt) discrepancies and opaque reseller paths. When an SSP offers a direct publisher ID (DIRECT) versus a reseller ID (RESELLER), standard bidding strategies treat both identically if they match targeting criteria. Custom Bidding bridges this gap by enabling real-time evaluation of the supply path before the bid is calculated.
Structuring the Custom Bidding Algorithm for CTV SPO
Implementing a custom bidding model for CTV SPO begins in the Google Cloud environment linked to your DV360 partner or advertiser. You must write a Python script that ingests contextual, geographical, and supply-chain signals, outputting a score that modifies the base bid. For CTV SPO, the core variables used in the script include exchange ID, supply chain object (`sc_object`), and inventory source type.
The script evaluates the OpenRTB SupplyChain object to count the number of nodes between the DSP and the original publisher. If the node count equals one (indicating a direct integration or a single-hop path through the publisher's primary monetization partner), the script applies a positive multiplier. Conversely, if the node count exceeds two, or if the `sgi` (seller node validation) status indicates a third-party reseller, the algorithm heavily penalizes the bid or drops the score to zero, effectively suppressing the bid.
# Conceptual logic for a CTV SPO Custom Bidding scoring function
def calculate_bid(bid_request):
base_bid = bid_request.suggested_bid
supply_chain = bid_request.supply_chain
# Check for direct or single-hop path
if supply_chain.complete and len(supply_chain.nodes) == 1:
multiplier = 1.3 # Prioritize direct paths
elif len(supply_chain.nodes) == 2:
multiplier = 1.0 # Acceptable single-reseller path
else:
multiplier = 0.0 # Drop multi-hop or opaque paths
return base_bid * multiplier
Ad ops teams must test these scripts in evaluation mode within DV360 before shifting spend. Running the algorithm in observation mode allows you to track potential impression loss and adjust your multipliers without risking campaign performance or delivery metrics.
Integrating Verification and Quality Signals
Supply-path optimization is inextricably linked to ad quality and brand safety. Routing budget through direct paths reduces the surface area for ad fraud, but verification partners like Integral Ad Science (IAS) and DoubleVerify still play a critical role in CTV measurement. High block rates or invalid traffic (IVT) can occur even on direct paths if the underlying CTV app is miscategorized or spoofed.
When constructing your custom bidding logic, incorporate historical verification data alongside supply-chain metrics. If an inventory source has a history of high pre-bid avoidance flags or elevated IVT rates according to your verification vendor, your script should down-weight that path regardless of its directness. For teams dealing with measurement discrepancies, reviewing troubleshooting IAS and DoubleVerify block rates in DV360 ensures that optimization rules do not conflict with required brand safety thresholds.
Combining SPO rules with quality metrics creates a dual-filter algorithm. You stop paying unnecessary tech taxes while simultaneously protecting your brand against unverified apps and CTV spoofing schemes. This approach directly improves your video completion rates (VCR) and lowers your cost per completed view (CPCV).
Managing Delivery Trade-Offs and Pacing
Aggressive supply-path optimization often introduces a distinct operational challenge: severe under-delivery. Restricting your inventory pool to strictly direct paths cuts off a massive volume of available impressions, particularly in niche CTV genres or long-tail FAST (Free Ad-supported Streaming TV) apps. If your custom bidding algorithm drops bids on 80 percent of incoming requests due to multi-hop penalties, your line items will struggle to pace.
To prevent delivery collapse, configure your custom bidding script with dynamic scaling thresholds based on campaign pacing. When a line item falls behind its delivery schedule, the script should temporarily relax its path constraints, allowing single-reseller inventory back into the auction pool. Conversely, when the line item is pacing ahead or on target, the algorithm tightens its rules, forcing 100 percent of spend through direct and verified paths.
Monitoring delivery health alongside SPO metrics requires constant vigilance. If you encounter persistent pacing bottlenecks while trying to enforce strict inventory paths, consult structured playbooks on fixing DV360 programmatic guaranteed under-pacing to identify whether the bottleneck stems from custom bidding stringency or underlying deal configuration issues.
Frequently Asked Questions
How do custom bidding algorithms access supply-chain data in DV360?
Custom bidding scripts in DV360 evaluate bid requests using the OpenRTB protocol fields passed by exchanges, including the SupplyChain object (`sc_object`) and seller ID data. These attributes allow the script to parse the exact hop count and intermediary identifiers before submitting a bid.
Can a custom bidding algorithm completely eliminate intermediary fees in CTV?
While custom bidding cannot force an exchange to drop its fees, it can prioritize bids that route through direct publisher integrations or single-hop paths. This effectively starves multi-hop reseller paths of your ad dollars, shifting your media investment toward efficient inventory.
What happens to campaign pacing when CTV SPO rules are too strict?
Overly restrictive custom bidding rules drastically reduce the pool of eligible bid requests, leading to under-delivery and missed delivery targets. Ad ops leads must build dynamic flexibility into their scripts to relax path constraints when pacing falls behind schedule.
How do verification tools impact custom CTV supply paths?
Verification tools provide pre-bid and post-bid signals regarding invalid traffic and viewability. Integrating these signals into your custom bidding logic ensures that optimized paths also meet strict brand safety standards before money changes hands.