2024 marked a significant year. AI became integral to our workflows, commerce and retail media networks soared, and Google did not deprecate cookies. Amidst these changes, ID bridging emerged as a hot topic, raising questions around identity reliability and transparency, which necessitated industry-wide standards. We believe the latest IAB OpenRTB specifications, produced in conjunction with supply and demand-side partners, set up the advertising industry for more transparent and effective practices.
So, what exactly is ID bridging?
As signals, like third-party cookies, fade, ID bridging emerged as a way for the supply-side to offer addressability to the demand-side. ID bridging is the supply-side practice of connecting the dots between available signals, that were generated in a way that is not the expected default behavior, to understand a user’s identity and communicate it to prospective buyers. It enables the supply-side to extend user identification beyond the scope of one browser or device.
Imagine you visit a popular sports website on your laptop using Chrome. Later, you use the same device to visit the same sports website, but this time, on Safari. By using identity resolution tools, a supply-side partner can infer that both visits are likely from the same user and communicate with them as such.
ID bridging is not inherently a bad thing. However, the practice has sparked debate, as buyers want full transparency into the use of a deterministic identifier versus an inferred one. This complicates measurement and frequency capping for the demand-side. Before OpenRTB 2.6, ID bridging led to misattribution as the demand-side could not attribute ad exposures, which had been served to a bridged ID, to a conversion, which had an ID different from the ad exposure.
OpenRTB 2.6 sets us up for a more transparent future
In 2010, the IAB, along with supply and demand-side partners, formed a consortium known as the Real-Time Bidding Project for companies interested in an open protocol for the automated trading of digital media. The OpenRTB specifications they produced became that protocol, adapting with the evolution of the industry.
The latest evolution, OpenRTB 2.6, sets out standards that strive to ensure transparency in real-time bidding, mandating how the supply-side should use certain fields to more transparently provide data when inferring users’ identities.
What’s new in OpenRTB 2.6?
Here are the technical specifications for the industry to be more transparent when inferring users’ identities:
- Primary ID field: This existing field now can only contain the “buyeruid,” an identifier mutually recognized and agreed upon by both buyer and seller for a given environment. For web environments, the default is a cookie ID, while for app activity, it is a mobile advertising ID (MAID), passed directly from an application downloaded on a device. This approach ensures demand-side partners understand the ID’s source.
- Enhanced identifier (EID) field: The EID field, designated for alternative IDs, now accommodates all other IDs. The EID field now has additional parameters that provide buyers transparency into how the ID was created and sourced, which you can see in the visual below:
Using the above framework, a publisher who wants to send a cross-environment identifier that likely belongs to the same user would declare the ID as “mm=5,” while listing the potential third-party identity resolution partner under the “matcher” field, which the visual below depicts. This additional metadata gives the demand-side the insights they need to evaluate the reliability of each ID.
“These updates to OpenRTB add essential clarity about where user and device IDs come from, helping buyers see exactly how an ID was created and who put it into the bidstream. It’s a big step toward greater transparency and trust in the ecosystem. We’re excited to see companies already adopting these updates and can’t wait to see the industry fully embrace them by 2025.”
Hillary Slattery, Sr. Director, Programmatic, Product Management, IAB Tech Lab
Experian will continue supporting transparency
As authenticated signals decrease due to cookie deprecation and other consumer privacy measures, we will continue to see a rise in inferred identifiers. Experian’s industry-leading Digital Graph has long supported both authenticated and inferred identifiers, providing the ecosystem with connections that are accurate, scalable, and addressable. Experian will continue to support the industry with its identity resolution products and is supportive of the IAB’s efforts to bring transparency to the industry around the usage of identity signals.
Supply and demand-side benefits of adopting the new parameters in OpenRTB 2.6
- Partner collaboration: Clarity between what can be in the Primary ID field versus the EID field provides clear standards and transparency between buyers and sellers.
- Identity resolution: The supply side has an industry-approved way to bring in inferred IDs while the demand side can evaluate these IDs, expanding addressability.
- Reducing risk: With accurate metadata available in the EID field, demand-side partners can evaluate who is doing the match and make informed decisions on whether they want to act on that ID.
Next steps for the supply and demand-sides to consider
For supply-side and demand-side partners looking to utilize OpenRTB 2.6 to its full potential, here are some recommended steps:
For the supply-side:
- Follow IAB Specs and provide feedback: Ensure you understand and are following transparent practices. Ask questions on how to correctly implement the specifications.
- Vet identity partners: Choose partners who deliver the most trusted and accurate identifiers in the market.
- Be proactive: Have conversations with your partners to discuss how you plan to follow the latest specs, which identity partners you work with, and explain how you plan to provide additional signals to help buyers make better decisions.
We are beginning to see SSPs adopt this new protocol, including Sonobi and Yieldmo.
“The OpenRTB 2.6 specifications are a critical step forward in ensuring transparency and trust in programmatic advertising. By aligning with these standards, we empower our partners with the tools needed to navigate a cookieless future and drive measurable results.”
Michael Connolly, CEO, Sonobi
These additions to the OpenRTB protocol further imbue bidding transactions with transparency which will foster greater trust between partners. Moreover, the data now available is not only actionable, but auditable should a problem arise. Buyers can choose, or not, to trust an identifier based on the inserter, the provider and the method used to derive the ID. While debates within the IAB Tech Lab were spirited at times, they ultimately drove a collaborative process that shaped a solution designed to work effectively across the ecosystem.”
Mark McEachran, SVP of Product Management, Yieldmo
For the demand side:
- Evaluation: Use the EID metadata to assess all the IDs in the EID field, looking closely at the identity vendors’ reliability. Select partners who meet high standards of data clarity and accuracy.
- Collaboration: Establish open communication with supply-side partners and tech partners to ensure they follow the best practices in line with OpenRTB 2.6 guidelines and that there’s a shared understanding of the mutually agreed upon identifiers.
- Provide feedback: As OpenRTB 2.6 adoption grows, consistent feedback from demand-side partners will help the IAB refine these standards.
Moving forward with reliable data and data transparency
As the AdTech industry moves toward a cookieless reality, OpenRTB 2.6 signifies a substantial step toward a sustainable, transparent programmatic ecosystem. With proactive adoption by supply- and demand-side partners, the future of programmatic advertising will be driven by trust and transparency.
Experian, our partners, and our clients know the benefits of our Digital Graph and its support of both authenticated and inferred signals. We believe that if the supply-side abides by the OpenRTB 2.6 specifications and the demand-side uses and analyzes this data, the programmatic exchange will operate more fairly and deliver more reach.
Latest posts
As many folks within the email eco-system probably know by now, Spamhaus, an organization known for compiling several widely used anti-spam lists, has been extremely active this week. Over the past week, Spamhaus has listed a number of potentially hazardous IP addresses used by some of the world’s largest email service providers due to the way their newsletters signups are set up. According to most of the listings, Spamhaus has stated: Unfortunately, the said newsletter service is not verifying the email address of new subscribers. Due to this, the service can be easily abused to "listbomb" internet users. Problem resolution ============================ The newsletter service needs to clean up their email address list and ensure that bulk emails are only being sent to recipients who have verifiably subscribed to their bulk email service. In addition, the newsletter service should take appropriate actions to prevent further abuse of their service: a) Implementing CAPTCHA to prevent automated subscriptions b) Implementing Confirmed Opt In (COI) to prevent abusers from adding random email addresses to the newsletter service that are not owned by the subscriber For the most part these listings should not directly impact marketers’ current ability to send their campaigns and reach their customers as they are listed as “warnings” within the Spamhaus system. What is important to understand is that these types of listings will likely continue to happen as Spamhaus has seen a dramatic increase in malicious use of newsletter sign-ups to "email bomb" various addresses, especially government (.gov) domains. While we understand that implementing CAPTCHA, or COI into any marketing system is not something that can be done quickly, Experian Marketing Services has recommended that our clients begin to investigate how they can potentially implement this process into their newsletter sign-ups. By asking customers to simply perform the CAPTCHA check, it will not only protect marketers from adding addresses from automated signup systems, but will also reduce the possibility of being listed with Spamhaus for these types of issues in the future. Some additional resources: Massive Email Bombs Target .Gov Addresses Subscription bombing, ESPs and Spamhaus, August 15, 2016 by laura in Best Practices Comment on the latter blog post on WordtotheWise.com from the CEO of Spamhaus: Excellent well summarized article Laura. No, we’ve not changed SBL policy to require COI. It’s something we very strongly advise but we cannot make a requirement. We’ll have to consider it if list-bombing of this magnitude cannot be kept in check by list managers. This incident involved a large number of government addresses belonging to various countries being subscribed to very large numbers of lists in a very short space of time by scripts run by the attacker(s). Most of the lists hit by the attack used COI and therefore only sent confirmation requests and did not subscribe any addresses. The attack undoubtedly also hit lists which used Captcha in addition to COI and thus did not even proceed to COI (those list admins deserve some sort of community ‘hi 5’ award, since one can imagine how hard it is to convince one’s management to implement COI let alone put Captcha in front of it). The issue is the badly-run ‘open’ lists which happily subscribed every address without any consent verification and which now continue as participants in the list-bombing of government addresses. These we are trying to address with SBL listings to prompt resolution by the Senders. As you noticed, most of these particular incident listings are for IPs ending “.0/32” which does not cause any mail issue to the Sender and is deliberately used where we have a good relationship with the Sender and know they will act quickly on the alert. Steve Linford Chief Executive The Spamhaus Project
Five Norwegian startups selected to establish U.S. presence NEW YORK, Aug. 15, 2016 /PRNewswire/ — Tapad, the leader in cross-device marketing technology and now a part of Experian, has announced its new entrepreneurial mentorship initiative, the Propeller Program. Five early-stage startups from Norway have been chosen by Are Traasdahl, native of Norway and Tapad’s CEO and founder. The selected companies will share Tapad’s New York City workspace, receive C-level guidance and help establish a U.S. presence. The following companies have been selected to participate in the inaugural Propeller Program – a 12-month program beginning September 19, 2016: Bubbly – Developers of a platform that enables in-store customer feedback with dashboards and tools that facilitate real-time store response BylineMe – A marketplace for freelancers, publishers and brands to connect for content creation and distribution services Eventum – A property-sharing group that digitally assists in securing venues for meetings and corporate events Socius – A content provider for publishers to tell stories using social media Xeneta – A database that organizes the best contracted freight rates in real time and on demand “We are supporting startups that we feel represent the future of service offerings,” said Traasdahl. “It is with incredible pride that we invite these entrepreneurial teams from Norway to join us in New York Citythis year. Mentorship opportunities for early-stage companies are so important, particularly for those based outside the U.S. I look forward to giving the Propeller Program participants access to the expertise of my seasoned team and to our wide network of resources. Hopefully, it will be a game-changing year for many of them.” Contact us today!
As partnership deals mount, aggressive hiring underway for unified cross-screen technology leaders NEW YORK, July 19, 2016 /PRNewswire/ — Tapad, the leader in cross-device marketing technology and now a part of Experian, has announced plans for aggressive expansion in the Asia Pacific (APAC) region. This move capitalizes on Tapad's exceptional performance for brands and marketing technology companies in North America and Europe. With it's proprietary Tapad Device Graph™, the company will enable global, regional and local clients and partners to understand, monetize and measure marketing to users across screens. The Tapad Device Graph is recognized as the most accurate, scalable cross-screen solution in the market today. The decision to expand into APAC was based on increased demand from global, as well as local, brands and clients, many of which have a strong market presence throughout the region. In addition to expanding its roster of world-class data partners, plans include building a world-class team in Singapore. Over the next few months, Tapad APAC will also establish local entities in additional markets. To accelerate its ramp-up, Tapad APAC is actively recruiting in many areas, ranging from skilled and experienced solutions engineers to seasoned sales and marketing professionals. "Tapad is thrilled to be answering the call for cross-device excellence in APAC," said Pierre Martensson, GM of Tapad APAC. "Our Device Graph is adding millions of devices daily and achieves unmatched levels of scale and accuracy while protecting consumer privacy. This meets a critical need in the region." Tapad appointed Martensson as General Manager of Tapad APAC in May, kicking off expansion in the region. Martensson comes to Tapad with nearly a decade of operations experience throughout APAC, having transformed, developed and grown global organizations. To learn more about partnership and employment opportunities available with Tapad in APAC, visit www.experian.com/careers. Contact us today!