Home Data-Driven Thinking Ad Tech Desperately Needs Data Exchange Standards

Ad Tech Desperately Needs Data Exchange Standards

SHARE:

Data-Driven Thinking” is written by members of the media community and contains fresh ideas on the digital revolution in media.

Today’s column is written by Sanjay Agarwal, vice president of engineering at Drawbridge.

In the ad tech ecosystem before OpenRTB, proprietary protocols caused long integration cycles, more code complexity and maintenance and custom logic for parsing requests.

The OpenRTB protocol replaced all proprietary protocols for sending ad requests from supply-side platforms (SSPs) to demand-side platforms (DSPs), resulting in faster integrations and a scaled ecosystem as a whole.

While this solved the SSP-DSP interaction almost a decade ago, there is still unfortunately no standard format for exchanging data between data management platforms (DMPs) and DSPs, posing a major point of friction in connections between DMPs and DSPs. There is a strong need for the standardization of data formats and the transport layer to push data from a DMP to a DSP.

While this problem has been around for a decade or so now, the proliferation of data providers has made standardization all the more pressing. While the DMPs and DSPs certainly stand to benefit from standardization, the real winners at the end of the day would be marketers. They would be able to more seamlessly leverage first- and third-party data, get campaigns set up quicker, more easily receive data back and never have to worry about integration timelines.

Today, the typical timeframe for adding a new integration from DMP to a DSP is anywhere from two to four months. The “standard” options for the transport layer can be via the file transfer protocol, S3 bucket or HTTP, and the data format itself can be proprietary. Product and engineering teams from both sides are involved in the integration, with calls, email threads and a lot of back-and-forth that could easily be avoided with a standardized data format.

The friction of sending and receiving data has resulted in niche DMPs using bigger DMPs like BlueKai to channel the data to media platforms. But usually this third-party onboarding results in a loss of functionality and scale, with a drop-off occurring at every data hop. Some companies also act as intermediaries to funnel the data from data producers to data consumers, which again results in loss of scale because of cookie translation. Data debugging becomes harder when third parties are involved, but unfortunately, due to today’s landscape, it’s required.

Offline transfer of data, such as through S3 or the file transfer protocol, results in less robust data validation. There is no feedback given to the sender on whether the data is received and processed correctly. Plus, if the data is time sensitive, such as first-party data used for retargeting, offline transfer will usually cause further delays, rendering the data useless.

Data formats are fragmented. Typically, audience data is organized by storing segment IDs by cookies, device IDs or email hashes. Whatever data format is chosen, it should support both adding and removing segment IDs to cookies or device IDs.

Another ideal feature would be bulk updates, where multiple user IDs can be modified, and each modification could even be accompanied by an expiration date until which the segment is valid. This could also support consumer choice and respect privacy through a standard opt-out that resonates across all IDs associated to the consumer. I could go on.

Subscribe

AdExchanger Daily

Get our editors’ roundup delivered to your inbox every weekday.

Having a standard format to send data across would drastically cut down the time taken for integration between DMPs and DSPs, resulting in a more seamless exchange of data. Plus, new integrations could be turned on with a flip of a switch, and a real-time transport layer could support time-sensitive data.

Just like OpenRTB has resulted in seamless integrations between SSPs and DSPs, the time is ripe to have a standard data format and transfer process for exchanging audience data between DMPs and DSPs. This will result in more platforms participating in the ecosystem, faster integrations and, ultimately, greater efficiencies for marketers.

The question is, who will lead the charge?

Follow Drawbridge (@Drawbridge) and AdExchanger (@adexchanger) on Twitter.

Must Read

Viant Acquires Data Biz IRIS.TV To Expand Its Programmatic CTV Reach

IRIS.TV will remain an independent company, and Viant will push for CTV platforms to adopt its IRIS ID to provide contextual signals beyond what streamers typically share about their ad inventory.

Integral Ad Science Goes Big On Social Media As Retail Ad Spend Softens In Q3

Integral Ad Science shares dropped more than 10% on Wednesday, after the company reported lackluster revenue growth and softened its guidance for the Q4 season.

Comic: Gen AI Pumpkin Carving Contest

Meet Evertune, A Gen-AI Analytics Startup Founded By Trade Desk Vets

Meet Evertune AI, a startup that helps advertisers understand how their brands and products appear in generative AI search responses.

Privacy! Commerce! Connected TV! Read all about it. Subscribe to AdExchanger Newsletters

Private Equity Firm Buys Alliant As The Centerpiece To Its Platform Dreams

The deal is a “platform investment,” in which Inverness Graham sees Alliant as a foundation to build on, potentially through further acquisitions.

Even Sony Needed Guidance For Its First In-Game Ad Campaign

In-game advertising is uncharted territory even for brands like Sony Electronics that consumers associate with gaming.

Comic: Always Be Paddling

The Trade Desk Maintains Its High Growth Rate And Touts New Channels

“It’s hard not to be bullish about CTV when it’s both our largest channel and our fastest growing,” said The Trade Desk Founder and CEO Green during the company’s earnings report on Thursday.