"They clearly were unable to flag that we made an unintentional mistake. I'm not confident they would have been able to detect a malicious implementation, either. This source felt very strongly that TTD should have caught these errors in the course of its DSP ingesting the publisher's bid requests, adding that TTD's failure to do so gave the publisher serious doubts about TTD's oversight of the data underlying UID2s."
"TTD confirmed that this publisher's errors would have made its UID2s useless for ad targeting. But TTD also told AdExchanger that it wouldn't have had enough information to flag anything wrong with this publisher's UID2 setup, revealing a critical gap in The Trade Desk's validation and monitoring capabilities for alternative ID implementations."
Publishers face pressure to include alternative IDs like The Trade Desk's Unified ID 2.0 in bid requests to access programmatic CTV demand and enable omnichannel targeting. However, significant gaps exist in data validation and consent verification for these alternative IDs. The Trade Desk serves as the sole administrator of UID2 but lacks stringent oversight mechanisms. A major CTV publisher discovered that The Trade Desk failed to detect encryption errors in their UID2 implementation that rendered the IDs useless for ad targeting. This oversight failure raises concerns about TTD's ability to detect both unintentional mistakes and potentially malicious implementations, suggesting inadequate validation processes for alternative ID data quality and legitimacy.
Read at AdExchanger
Unable to calculate read time
Collection
[
|
...
]