Solve CTV Frequency Capping Duplication in DV360
To solve CTV frequency capping duplication across multiple SSPs in Display & Video 360 (DV360), programmatic traders must consolidate supply paths, enforce strict Identifier for Advertising (IFA) validation, and implement campaign-level frequency capping. By restricting inventory sources to direct Supply-Side Platform (SSP) paths and filtering out bid requests missing valid device identifiers, you prevent DV360 from bidding on concurrent auctions for the same ad slot. Additionally, utilizing DV360’s household-level co-viewing frequency settings helps align delivery across fragmented publisher environments.
Key Takeaways
- Up to 30% of CTV bid requests lack a standard, unhashed IFA, causing DV360 to treat the same physical device as a new user.
- Consolidating programmatic buying to 1-2 direct SSPs per publisher eliminates concurrent auction duplication where DV360 wins multiple bids for the same ad pod.
- Campaign-level frequency capping in DV360 prevents multi-line item bid collision, whereas line-item-level caps fail during high-concurrency auctions.
- Leveraging DV360’s household-level frequency capping uses a combination of IP address, IFA, and Google’s Graph to model co-viewing, reducing over-exposure by up to 20%.
The Root Causes of CTV Frequency Duplication
Frequency capping in Connected TV (CTV) is fundamentally more complex than in web or mobile app environments. In standard display, cookies and mobile advertising IDs (MAIDs) provide a relatively stable identity layer. In CTV, the industry relies on the IFA (Identifier for Advertising) passed within the OpenRTB bid stream by various operating systems, including Roku OS, Apple tvOS, Amazon Fire OS, Samsung Tizen, and LG webOS. When multiple SSPs represent the same publisher inventory, the identity signal often breaks down, leading to severe ad duplication.
The Identity Crisis: Missing and Malformed IFAs
For DV360 to enforce a frequency cap, it must recognize that two separate bid requests originate from the same physical device. However, SSPs do not always pass the IFA uniformly. One SSP may pass a raw, unhashed IFA, while another passes a SHA-256 hashed version, and a third may omit the IFA entirely, falling back on an ephemeral IP address or user-agent string.
When DV360 receives these mismatched signals, its bidder cannot resolve them to a single device profile. Consequently, the platform treats each variation as a distinct user. If your programmatic campaign targets the same publisher across multiple SSPs, you will inevitably serve duplicate impressions to the same viewer because the DSP treats each SSP's bid request as an isolated event.
The Concurrent Auction Problem (Bid Collision)
Even when IFAs are passed perfectly, the mechanics of real-time bidding (RTB) introduce a timing window issue known as the concurrent auction problem. When a user launches an ad-supported CTV app (such as Pluto TV or Peacock), the publisher's ad server often sends simultaneous bid requests to multiple SSPs (e.g., Magnite, FreeWheel, and PubMatic) to maximize yield for a single ad slot or ad pod.
DV360 receives these separate bid requests within milliseconds of one another. At the moment of evaluation, DV360 checks its real-time frequency cache. Because none of the pending bids have actually won or served yet, the frequency cap appears intact. DV360 bids on all three requests, wins two of them, and serves back-to-back ads to the same viewer in the same commercial break. This bid collision is a primary driver of wasted ad spend and poor viewer experience.
To understand how this impact cascades down to private marketplace setups, traders should refer to the guide on Fixing DV360 PMP Deals Not Spending to ensure deals are configured to receive clean, non-duplicated bid requests from the outset.
Supply-Path Optimization (SPO) as a Frequency Solution
The most effective structural solution to CTV frequency duplication is Supply-Path Optimization. If you target a publisher through four different SSPs, you multiply your exposure to concurrent auctions and IFA mapping errors by four.
Consolidating to Direct Paths
Programmatic traders must audit their supply paths and restrict targeting to direct, highly integrated SSP routes. For instance, if you are buying Disney CTV inventory, routing your spend exclusively through Disney’s direct Clean Room integration or a single preferred SSP (like Google Ad Manager or FreeWheel) drastically limits bid duplication. By closing off tertiary and quaternary supply paths, you force all bid requests through a single pipe, allowing DV360's bidder to serialize the auctions and accurately enforce your frequency caps.
For advanced programmatic setups, traders can write custom bidding algorithms to deprioritize redundant supply paths automatically. Incorporating custom logic ensures your bids prioritize the most direct and cost-effective path. For a deep dive into implementing this programmatic control, read about DV360 Custom Bidding for CTV SPO.
| Supply Strategy | IFA Consistency | Concurrent Auction Risk | Frequency Control Effectiveness |
|---|---|---|---|
| Multi-SSP Open Auction | Low (Highly Fragmented) | High (Severe Duplication) | Poor (30-40% over-exposure) |
| Consolidated PMP (1-2 SSPs) | Medium-High | Medium | Moderate-Good |
| Direct PG / Single-SSP Custom Bidding | High (Standardized) | Low | Excellent (<5% duplication) |
Practical DV360 Configurations to Eliminate Duplication
Beyond structural supply changes, programmatic traders must configure DV360 campaigns specifically for the nuances of CTV inventory. Default settings designed for web display will fail in CTV environments.
1. Enforce Strict IFA-Only Bidding
To prevent DV360 from bidding on inventory where it cannot track frequency, you should restrict your targeting to bid requests that contain a valid, standardized IFA. While this may reduce overall bid volume, it protects your frequency caps.
To execute this in DV360, navigate to your Line Item or Insertion Order settings. Under the "Device" targeting section, ensure you are targeting specific CTV operating systems and environments that natively support and pass hardware IFAs. Avoid running broad, un-targeted Open-Exchange CTV campaigns that pool desktop, mobile, and CTV traffic together, as this makes device resolution highly inaccurate.
2. Implement Campaign-Level Frequency Capping
Setting frequency caps at the Line Item (LI) level is a common operational mistake. If you have five different Line Items targeting CTV—divided by geography, audience demographics, or creative length—each Line Item operates with its own independent frequency bucket. A single household could easily be exposed to your ad five times if each LI has a cap of 1 per day.
To solve this, set a strict frequency cap at the Campaign Level. When configured at the campaign level, DV360 shares the frequency state across all child Insertion Orders and Line Items. Even if multiple line items bid on a user, the global campaign cap limits total exposure.
3. Utilize CTV Co-Viewing and Household Capping
CTV is inherently a shared-screen medium. Traditional device-level frequency capping fails to account for multiple people watching the same television screen. DV360 offers specialized CTV frequency capping options that model co-viewing patterns and manage frequency at the household level.
DV360 uses Google’s Graph to link multiple individual device IDs (mobile phones, laptops) to a single CTV device based on shared IP addresses and login signals. By setting a household-level frequency cap (for example, 3 impressions per household per week), you prevent over-saturating a home, even if different family members use different streaming apps on the same smart TV network.
Pacing and Delivery Coordination in Programmatic Guaranteed (PG) Deals
Programmatic Guaranteed (PG) deals present a distinct challenge for frequency capping. In a PG deal, the publisher’s ad server (such as Google Ad Manager or FreeWheel) controls pacing and delivery first. The publisher's ad server determines which ad slot to fill and passes the bid to DV360 as a pre-filtered request that DV360 is contractually obligated to buy.
If you mix PG deals with PMPs or Open Auction buying, DV360 cannot easily enforce a unified frequency cap. The PG deal will always take priority, frequently bypassing the active frequency caps set on your PMP campaigns. This overlap leads to massive duplication for users who fall into both targeting pools.
To mitigate this, you must coordinate closely with the publisher during the negotiation phase. Ensure that the publisher applies frequency capping on their ad server before the bid is sent to DV360. Additionally, when troubleshooting delivery anomalies, understanding how your PG setup interacts with your DSP bidding logic is critical. If your PG deals are under-delivering due to competing targeting layers, review the troubleshooting steps outlined in Fixing DV360 Programmatic Guaranteed Deal Under-Pacing to realign your spend without sacrificing frequency control.
Frequently Asked Questions
How does DV360 handle frequency capping when a CTV device ID is missing?
When a bid request lacks a standard IFA, DV360 falls back on temporary identifiers, such as IP address and user-agent combinations, to estimate frequency. However, this fallback method is far less accurate than hardware-based IFAs and often results in double-serving ads to the same household because IP addresses rotate and fail to isolate individual devices.
Why do I see back-to-back ads on CTV if my line item has a 1 per hour cap?
This occurs due to concurrent bidding across multiple SSPs for the same ad pod. DV360 receives and bids on multiple requests before the first impression is recorded and updated in its frequency cache, resulting in multiple won bids served consecutively.
Should I set frequency caps at the Partner, Campaign, or Insertion Order level in DV360?
For CTV campaigns, you should set frequency caps at the Campaign level. This ensures that all underlying Insertion Orders, Line Items, and creative variations share a single, unified frequency counter, preventing different line items from double-serving ads to the same user.
Can I enforce frequency caps across both PG and PMP deals in DV360?
No, DV360 cannot strictly limit PG impressions based on PMP frequency because PG deals have guaranteed delivery terms enforced by the publisher's ad server. To manage frequency across both, you must request that the publisher apply frequency capping on their side, or exclude PG-exposed users from your PMP targeting parameters.