Analysis of Transaction IDs in Programmatic Bid Requests

Executive Summary

This report delivers a comprehensive analysis of the role of identifiers within the programmatic advertising ecosystem. The term "transaction ID" is not a singular concept but rather a class of distinct yet interconnected identifiers, including the Bid Request ID, the Deal ID, and Seat/Buyer IDs. The Bid Request ID serves as the immutable digital fingerprint of a single ad auction, while the Deal ID functions as a digital handshake for pre-negotiated, private transactions. These identifiers are indispensable for enabling the lightning-fast, highly scalable real-time bidding (RTB) market. For publishers, they are a vital tool for revenue optimization and control; for supply-side platforms (SSPs), they form the foundation for efficient bid routing and transparent reporting; and for demand-side platforms (DSPs), they are the key to granular targeting and campaign optimization.

However, the analysis also reveals that these identifiers, while a necessary tool for transparency and reconciliation, are not a panacea. The report uncovers systemic challenges, including persistent data discrepancies and new forms of ad fraud that exploit the very nature of these IDs. It concludes by outlining a strategic roadmap for stakeholders to navigate a future defined by user privacy, first-party data, and the continuous evolution of programmatic identity.

Section 1: The Anatomy of Programmatic Identifiers

1.1 Deconstructing the Bidstream

To understand the function of programmatic identifiers, it is essential to first grasp the environment in which they operate: the bidstream. The bidstream is the continuous, high-speed flow of data that underpins real-time bidding. It is not merely a technical process but a fundamental economic paradigm shift that enables the buying and selling of digital ad inventory in milliseconds.1 This stands in stark contrast to the traditional, manual model of bulk ad sales.3

The process begins when a user visits a website or opens a mobile application. The publisher’s SSP or ad exchange detects an available ad slot and generates a bid request.4 This message, which is the foundational unit of the bidstream, contains detailed information about the impression opportunity, including anonymized user data, device type, browser, location, and contextual data about the page or app.4 This bid request is then broadcast to multiple DSPs and advertisers, who have less than a second to analyze the data, decide whether to bid, and submit their offer.1 This entire automated system, which operates like a high-speed stock exchange for ad inventory, is enabled by the ability to identify and track each individual impression.

1.2 Clarifying the Terminology

Within this complex ecosystem, several distinct identifiers are often conflated under the generic term "transaction ID." A clear understanding of each is crucial for navigating the programmatic supply chain.

• The Bid Request ID / Auction ID: This is the most fundamental identifier in the system. As specified by the OpenRTB protocol, the top-level bid request object contains a required, "globally unique bid request or auction ID".9 This ID acts as the unique identifier for a specific auction instance, making it the digital fingerprint for a single, fleeting economic event: the sale of one ad impression.5 It is the core innovation that enables the hyper-commoditization of ad inventory, allowing each impression to be individually valued and bid on.

• The Deal ID: A more strategic, secondary identifier, the Deal ID is a "unique identifier that facilitates transactional clarity and specificity" for private marketplaces (PMPs) and programmatic direct deals.3 It is a token that represents a "digital handshake" and encapsulates a set of pre-agreed terms between an advertiser and a publisher.3 These terms can include specifics on ad inventory, pricing, targeting criteria, campaign duration, and volume commitments.3 This identifier adds a layer of pre-negotiated terms on top of the base auction, enabling a high-value, bespoke market that exists in parallel with the open, commodity market.

• Seat and Buyer IDs: The wseat attribute in a bid request serves as an "allow list" of specific buyer seats (DSPs) that are permitted to bid on a private deal.13 In a bid response, the
  seat attribute communicates which buyer is placing the bid.13 This mechanism creates a secure, trusted environment for high-value transactions. A related concept is Google's
  buyer_reporting_id, a value populated in bid responses that helps in reporting and attributing billed impressions to a specific buyer, thereby aiding in discrepancy resolution.15 The hierarchy of these identifiers—from the base Bid Request ID to the strategic Deal ID and the secure Seat ID—is a direct result of market participants demanding more control and trust beyond the basic open auction.

• General Transaction IDs: The term "transaction ID" is a generic financial concept used broadly to track and reconcile sales and payments in e-commerce and other industries.16 In ad tech, this term is sometimes used to prevent duplicate conversions, such as when a user re-opens a confirmation page.18 This report distinguishes this broad financial term from the more specific programmatic identifiers.

1.3 The Technical Foundations

The effectiveness of these identifiers is predicated on their technical underpinnings. Programmatic identifiers are generated using secure algorithms that combine timestamps, random data, and hash functions to ensure each is cryptographically unique and resistant to collision.16 This ensures that even if transactions occur at the exact same millisecond, their digital fingerprints remain distinct.16

Once generated, the ID is stored in a database or ledger, serving as a unique key for retrieving all associated transaction details, such as timestamps, user information, and campaign metadata.16 The ability to track a data asset from its origin to its destination is a concept known as data lineage, and the Bid Request ID serves as the atomic unit of this process.19 This allows every party in the supply chain to independently trace the entire journey of a single impression, which is a strategic necessity for compliance with data regulations and for performing audits.19 However, the challenge lies in managing this distributed lineage across a fragmented ecosystem with disparate systems, where consistency in format and generation logic is paramount to avoid mismatches during data integration and reconciliation.16

Section 2: The Publisher's Perspective: Monetization, Control, and Transparency

2.1 How IDs Empower Publishers

Historically, publishers sold ad space in bulk or at fixed prices, lacking granular control over their ad inventory. The advent of RTB, enabled by the Bid Request ID, shifted this power dynamic. The ID allows each ad impression to be auctioned individually, ensuring that the ad space is sold to the highest bidder in real time, thereby maximizing revenue.1 This capability represents more than just a technological advancement; it is a tool for economic empowerment, transforming ad inventory from a bulk commodity into a stream of high-value, individually tradable assets.

The Deal ID further empowers publishers by allowing them to create a high-value, non-commoditized segment of the market. This identifier provides a mechanism for publishers to set floor prices and ensure that premium inventory is sold under pre-negotiated terms.3 This re-establishes direct control over pricing and maintains the integrity of their most valuable ad space.

2.2 Advantages for Publishers

• Yield Optimization and Pricing Control: By including a unique Bid Request ID, a publisher's SSP can invite multiple DSPs to compete for a single impression, boosting competition and increasing the effective CPM (eCPM) for that inventory.4 Deal IDs and Seat IDs enable SSPs to route premium traffic to preferred deals, ensuring that the best inventory is sold at the best possible price.23

• Creation of Premium Private Marketplaces: Deal IDs are a core component of PMPs and Programmatic Guaranteed deals, offering exclusive access to premium inventory for a select group of pre-vetted buyers.3 This mechanism ensures exclusivity, prevents unwanted competition from other advertisers, and allows publishers to reach high-value advertisers seeking specific, targeted access.3

• Enhanced Transparency and Brand Safety: A Deal ID simplifies transactions by documenting and enforcing all agreed-upon terms between publishers and advertisers.3 This provides publishers with a clear view of where their ads will appear, helping them maintain control over their premium inventory and protecting their brand integrity.3

• Simplified Auditing and Revenue Reconciliation: The presence of these unique identifiers simplifies the transaction process, encapsulating all terms in a single token to reduce the potential for disputes.12 The bid-level logging performed by SSPs provides the necessary data for a publisher to reconcile their own ad server's impression counts with the revenue they receive from their SSP partners.23

2.3 Disadvantages for Publishers

Despite the numerous benefits, the reliance on programmatic identifiers introduces several challenges. The primary disadvantage is the added operational complexity that comes with managing multiple deal types, each with its own set of IDs and parameters.3

A more systemic challenge is the persistent issue of impression and revenue reconciliation. While identifiers provide the necessary reference points, discrepancies often arise from factors such as invalid traffic, latency, or different counting methodologies between systems.15 The research makes it clear that even with dedicated ID-based solutions, small discrepancies may still persist, requiring publishers to invest significant resources into auditing and reporting to align their impression counts with the billed impressions from their partners.15

Furthermore, these IDs can be exploited by sophisticated ad fraudsters. The IAB notes that unique auction_ids can be abused by botnets that cache ad impressions and then replay them in a rapid burst to create fraudulent win notifications and billing events.27 This forces publishers to invest in sophisticated fraud detection to protect their revenue and brand reputation, as invalid traffic (IVT) can devalue their inventory.28

Section 3: The Supply-Side Platform (SSP) Perspective: The Market Enabler

3.1 The Role of IDs in the SSP

The SSP serves as the central orchestrator of the ad auction, functioning as the "seller's stock exchange" for publishers.23 Its primary role is to receive ad requests from publishers, package them into OpenRTB-compliant bid requests with a unique ID, and then broadcast them to DSPs.4 The Bid Request ID is the master key the SSP uses to link all subsequent events in the auction: the bids received from various DSPs, the selection of the winning bid, and the final creative delivery.23 The SSP's ability to efficiently manage this complex process, prioritize bids, enforce floor prices, and provide transparent reporting is entirely dependent on its capacity to manage and track every action tied to this single, unique ID. Without this, the system would be a chaotic, untraceable mess.

3.2 Advantages for SSPs

• Streamlined Bid Routing and Deal Prioritization: SSPs use the wseat attribute in bid requests to create an "allow list" of buyers, ensuring that bids for private deals are properly routed and prioritized over open-auction bids.13 This ensures that the SSP fulfills the terms of its deals with both publishers and advertisers.

• Increased Competition and Revenue Uplift: By exposing a single ad impression to multiple DSPs via a unique bid request, SSPs increase competition and help publishers maximize their revenue.4

• Robust Reporting and Analytics: SSPs log bid-level data, including the buyer IDs and clearing prices associated with each Bid Request ID.23 This data is essential for their analytics and reporting platforms, which help publishers understand how their inventory is performing and how they can best monetize it.22

• Improved Ad Quality and Fraud Detection: SSPs leverage information within the bid request to enforce brand safety controls, block content from specific advertisers or categories, and filter and reject invalid traffic.14

3.3 Disadvantages for SSPs

The technical burden of managing IDs in a massive, real-time environment is a significant challenge for SSPs. They must process a colossal volume of bid requests at extremely low latency.2 This requires a highly scalable, robust infrastructure and a considerable upfront investment, especially for platforms that are custom-built.22

Furthermore, SSPs face a constant challenge in reconciling their own billing data with the payments from DSPs.15 The existence of dedicated tools like Google's "Demand Discrepancy Resolution" is a clear indication that this is a persistent, systemic problem that is not fully solved.15 While identifiers provide the reference points, the complexity of the "last mile" of the transaction, where different counting methodologies, invalid traffic adjustments, and timing delays occur, can cause misalignment.15

Finally, SSPs are bound by the standards of multiple ad exchanges and demand partners, which requires them to manage a variety of different IDs and APIs.14 This fragmentation adds to the operational complexity and burden, as they must ensure their systems are compatible with the unique requirements of each partner.

Section 4: The Demand-Side Platform (DSP) Perspective: The Buyer's Agent

4.1 The DSP's Utilization of IDs

As the advertiser's agent, the DSP receives bid requests and uses sophisticated algorithms and machine learning to analyze the included data—user, device, and context—to decide whether to bid and at what price.1 The Bid Request ID is a fundamental data point that allows the DSP’s algorithms to operate. The ID, as a single, unique string, allows the DSP to connect a vast array of internal data—audience segments, campaign budgets, bid factors, and historical performance—to a single, unique impression opportunity.32 Without this ID, the DSP's entire data pipeline and optimization engine would cease to function. The DSP’s bid response, which may include a

seat attribute, is then sent back to the SSP to participate in the auction.13

4.2 Advantages for DSPs

• Granular Targeting Precision: Bid requests provide DSPs with detailed information about a user, such as their browsing history, location, and device type.4 This enables highly granular audience segmentation and bid adjustments based on a multitude of factors.31 Deal IDs further refine this by giving advertisers access to specific, pre-vetted audiences on premium sites.3

• Efficient Bid-to-Impression Matching: The Bid Request ID enables a DSP to match its internal bid logs to the eventual win notification, the impression event, and post-click data.23 This end-to-end data lineage is crucial for accurate attribution, performance measurement, and campaign optimization.29

• Access to Exclusive Inventory: Deal IDs give DSPs and their advertisers access to premium, high-value inventory in PMPs and Programmatic Guaranteed deals that would otherwise be unavailable in the open market.3

• Accurate Reporting and ROI Measurement: DSPs provide advertisers with real-time analytics on campaign performance, including impressions, clicks, conversions, and cost metrics.34 The Bid Request ID and other transaction IDs are fundamental for this reporting, ensuring that revenue, spend, and performance are accurately attributed to the correct campaign and impression.23

4.3 Disadvantages for DSPs

DSPs face significant challenges related to data integrity and reliability. While IDs are meant to ensure accuracy, a transactionID may sometimes conflict with other IDs when integrating data from multiple offline channels, which can cause unexpected results.21 This highlights the broader challenge of data consistency in a fragmented environment.16

Security risks and fraud concerns are a persistent issue. DSPs must implement robust fraud detection to avoid bidding on invalid traffic.27 The IAB notes that unique

auction_ids can be exploited by botnets that cache and replay ad impressions to trigger fraudulent win notifications.27 This requires DSPs to evolve their fraud detection systems from simple ID checks to a more sophisticated analysis of the patterns of IDs, using behavioral analytics and velocity checks to monitor the rate of events per unique ID and place suspicious signatures in a "penalty box".27

Finally, DSPs constantly face the challenge of managing discrepancy resolution. They must reconcile the impressions they pay for with the impressions billed by exchanges.15 The existence of dedicated tools like Google's "Demand Discrepancy Resolution" underscores that this is a persistent issue that cannot be fully solved by the mere presence of IDs alone.15

Section 5: Cross-Stakeholder Functions and Strategic Implications

5.1 Data Lineage and Auditing

Data lineage, the process of tracking data from its source to its destination, is a strategic imperative for every party in the programmatic supply chain.19 The Bid Request ID, created at the origin of the auction, serves as the perfect anchor for a data lineage system. It provides an immutable record of a specific economic event that can be audited to ensure that ad placements are valid, payments are accurate, and data is handled in a compliant manner. Given the intense regulatory scrutiny of data flows, this ability to trace an ad's journey is a necessity for all stakeholders.19

5.2 Discrepancy Resolution and Financial Reconciliation

Revenue reconciliation is a critical accounting process that aligns financial data from different sources.36 In ad tech, this involves comparing impression counts and revenue across SSPs and DSPs.15 The research shows that while identifiers are a necessary tool for this process, a persistent challenge exists in the "last mile" of the transaction. Even with dedicated, ID-based solutions like Google's "Demand Discrepancy Resolution," which uses

google_query_id and buyer_reporting_id, small discrepancies may still persist.15 This is not due to the absence of an ID, but rather the complexity of the ecosystem, where different counting methodologies, invalid traffic adjustments, and timing delays cause misalignment.15

5.3 Combating Ad Fraud

Identifiers play a dual role in the fight against ad fraud. Their uniqueness is leveraged to detect fraudulent payment attempts and to prevent duplicate conversions.18 However, this same uniqueness can be exploited by sophisticated fraudsters who generate unique, fraudulent

auction_ids to mimic legitimate traffic.27 Fraudsters can cache bid requests and replay them in a rapid burst, creating a flood of fraudulent win notifications and billing events that exploit the uniqueness of the ID itself.27 Therefore, the programmatic ecosystem must evolve its fraud detection from simple ID checks to a more sophisticated analysis of the patterns of IDs, using behavioral analytics and velocity checks to monitor the rate of events per unique identifier.27

5.4 The Future of Identifiers

The deprecation of third-party cookies is forcing a fundamental change in programmatic identity. The Bid Request ID will remain as the core auction identifier, but the user-level identifiers within it will shift from universal, third-party IDs to a fragmented ecosystem of encrypted, publisher-specific first-party IDs.10 This strategic shift decentralizes identity and gives more control to publishers and advertisers.39 New privacy-centric solutions like Publisher Advertiser Identity Reconciliation (PAIR) are emerging to facilitate data matching in a privacy-safe manner.39 These solutions, which rely on advanced encryption and data clean rooms, allow advertisers and publishers to reconcile their first-party data without a shared, universal ID, thereby future-proofing their strategies and protecting consumer privacy.39

Section 6: Conclusions and Recommendations

6.1 Recommendations for Publishers

To thrive in the evolving ad tech landscape, publishers should focus on providing detailed and accurate data within their bid requests.4 They should strategically embrace Deal IDs to maintain control over their premium inventory and ensure pricing integrity.3 Furthermore, publishers must adopt new privacy-centric, first-party solutions like PAIR to future-proof their revenue strategy and ensure they can continue to monetize their audience in a cookie-less future.39

6.2 Recommendations for SSPs

SSPs should invest in robust, scalable infrastructure to handle the immense volume of bid requests at low latency.2 They must also prioritize advanced fraud detection and work with their partners to improve discrepancy resolution, providing transparent and consistent reporting to build trust and accountability.15

6.3 Recommendations for DSPs

DSPs should leverage IDs for granular targeting and end-to-end data lineage to ensure accurate attribution and campaign optimization.23 They must implement sophisticated fraud detection that analyzes the patterns of IDs to detect new forms of ad fraud.27 Finally, DSPs should prepare for the future by embracing first-party data solutions and new identity frameworks like UID2, which will become essential for maintaining addressable audience targeting.40

6.4 Concluding Summary

Programmatic identifiers are the indispensable backbone of the ad tech ecosystem, enabling a marketplace of unprecedented scale and efficiency. The Bid Request ID has transformed ad inventory into a tradable commodity, while the Deal ID has introduced the ability for bespoke, private transactions. While these IDs have introduced transparency and control for all stakeholders, they also come with inherent challenges, from persistent data discrepancies to new forms of ad fraud. The future of the industry hinges on the ability of all parties to leverage these identifiers strategically while navigating a new era of privacy and decentralization, where the value of first-party data and the protocols that enable its secure exchange will define the winners and losers of the next decade.

Table 2: Stakeholder Benefits and Challenges

Works cited

1. How Does Programmatic Advertising Work? A Complete Walkthrough - BidsCube, accessed on August 21, 2025, https://bidscube.com/blog/2025/06/13/how-does-programmatic-advertising-work-a-complete-walkthrough/

2. Understanding Real-Time Bidding (RTB) - Aerospike, accessed on August 21, 2025, https://aerospike.com/blog/real-time-bidding/

3. Deal ID Explained: Its Role and Importance in Programmatic Direct - Publift, accessed on August 21, 2025, https://www.publift.com/blog/deal-id

4. Bid Request Explained: What Every Publisher Needs to Know - Sevio Blog, accessed on August 21, 2025, https://blog.sevio.com/bid-request/

5. Everything You Need to Know About Bid Request - HeaderBidding.com, accessed on August 21, 2025, https://headerbidding.com/programmatic-101/everything-you-need-to-know-about-bid-request/

6. Bidstream Data - AppLovin, accessed on August 21, 2025, https://www.applovin.com/glossary/bidstream-data/

7. What Is a Bid Request? - AdQuick, accessed on August 21, 2025, https://www.adquick.com/adtech/bid-request

8. Introduction to real-time bidding (RTB) - Authorized Buyers Help, accessed on August 21, 2025, https://support.google.com/authorizedbuyers/answer/6136272?hl=en

9. OpenRTB Protocol Buffer 2.6 | Real-time Bidding | Google for ..., accessed on August 21, 2025, https://developers.google.com/authorized-buyers/rtb/downloads/openrtb-proto

10. OpenRTB Integration | Real-time Bidding - Google for Developers, accessed on August 21, 2025, https://developers.google.com/authorized-buyers/rtb/openrtb-guide

11. OpenRTB Version 2.6 - IAB Tech Lab, accessed on August 21, 2025, https://iabtechlab.com/wp-content/uploads/2022/04/OpenRTB-2-6_FINAL.pdf

12. Deal ID | What is Deal ID? | Programmatic Advertising Glossary - Gourmet Ads, accessed on August 21, 2025, https://www.gourmetads.com/glossary/deal-id/

13. Support center | Amazon Ads, accessed on August 21, 2025, https://advertising.amazon.com/help/G658WQMCSVXXMKXU

14. Incoming Bid Request from SSPs | Microsoft Learn, accessed on August 21, 2025, https://learn.microsoft.com/en-us/xandr/supply-partners/incoming-bid-request-from-ssps

15. Open Bidding Discrepancy Resolution and Impression ..., accessed on August 21, 2025, https://support.google.com/authorizedbuyers/answer/13531755?hl=en

16. What is a transaction ID? | Stripe, accessed on August 21, 2025, https://stripe.com/resources/more/what-is-a-transaction-id-here-is-what-you-need-to-know

17. What Is a Transaction ID & How Can They Help Merchants? - PaymentCloud, accessed on August 21, 2025, https://paymentcloudinc.com/blog/transaction-id/

18. Use a transaction ID to minimize duplicate conversions - Google Ads Help, accessed on August 21, 2025, https://support.google.com/google-ads/answer/6386790?hl=en

19. What is Data Lineage? - Informatica, accessed on August 21, 2025, https://www.informatica.com/resources/articles/what-is-data-lineage.html

20. What Is Data Lineage? - DATAVERSITY, accessed on August 21, 2025, https://www.dataversity.net/what-is-data-lineage/

21. transactionID | Adobe Analytics - Experience League, accessed on August 21, 2025, https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/page-vars/transactionid

22. What is a supply-side platform (SSP)? | AppsFlyer glossary, accessed on August 21, 2025, https://www.appsflyer.com/glossary/supply-side-platform/

23. DSP vs SSP: Simple Breakdown for Smarter Ad Strategy - BidsCube, accessed on August 21, 2025, https://bidscube.com/blog/2025/06/20/ssp-vs-dsp-whats-the-difference-and-why-it-matters-in-programmatic/

24. RTB Project - OpenRTB Dynamic Native Ads API Specification Version 1.2 - IAB, accessed on August 21, 2025, https://www.iab.com/wp-content/uploads/2018/03/OpenRTB-Native-Ads-Specification-Final-1.2.pdf

25. openrtb2.x/implementation.md at main · InteractiveAdvertisingBureau/openrtb2.x · GitHub, accessed on August 21, 2025, https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md

26. Ad Manager report metrics - Google Help, accessed on August 21, 2025, https://support.google.com/admanager/table/7568664?hl=en

27. RTB Project OpenRTB Security Advisory 15-01 - GitHub Pages, accessed on August 21, 2025, https://interactiveadvertisingbureau.github.io/TechLabFAQ/doc-portal/assets/pdf/OpenRTBSecurityAdvisory_V2.pdf

28. IAB Europe Guide to Ad Fraud, accessed on August 21, 2025, https://iabeurope.eu/wp-content/uploads/IAB-Europe-Guide-to-Ad-Fraud-1-2.pdf

29. Guidance for Capturing Advertising OpenRTB (Real-Time Bidding ..., accessed on August 21, 2025, https://aws.amazon.com/solutions/guidance/capturing-advertising-openrtb-real-time-bidding-events-for-analytics-on-aws/

30. Bid on Behalf of Multiple Accounts | Real-time Bidding | Google for Developers, accessed on August 21, 2025, https://developers.google.com/authorized-buyers/rtb/response-guide/bid-multiple

31. About Smart Bidding - Google Ads Help, accessed on August 21, 2025, https://support.google.com/google-ads/answer/7065882?hl=en

32. Bid Adjustments - Amazon Ads, accessed on August 21, 2025, https://advertising.amazon.com/help/G298ZVT2MWD7ETWS

33. Incoming Bid Response from Bidder - Microsoft Learn, accessed on August 21, 2025, https://learn.microsoft.com/en-us/xandr/bidders/incoming-bid-response-from-bidders

34. DSP Advertising: How Demand-Side Platforms Work [2025] - Improvado, accessed on August 21, 2025, https://improvado.io/blog/what-is-a-dsp

35. What is payment fraud and how to prevent it - Adyen, accessed on August 21, 2025, https://www.adyen.com/knowledge-hub/payment-fraud

36. Revenue Reconciliation: The Ultimate Guide (2024) - HubiFi, accessed on August 21, 2025, https://www.hubifi.com/blog/revenue-reconciliation-guide

37. Mastering Revenue Reconciliation: Key Steps for Ensuring Financial Accuracy - Solvexia, accessed on August 21, 2025, https://www.solvexia.com/blog/revenue-reconciliation

38. Protect payment transactions with Fraud Prevention | reCAPTCHA Enterprise, accessed on August 21, 2025, https://cloud.google.com/recaptcha/docs/fraud-prevention

39. About PAIR (Publisher Advertiser Identity Reconciliation) (Beta) - Google Ad Manager Help, accessed on August 21, 2025, https://support.google.com/admanager/answer/15067908?hl=en

40. DSPs | Unified ID 2.0, accessed on August 21, 2025, https://unifiedid.com/docs/overviews/overview-dsps

41. PAIR (Publisher Advertiser Identity Reconciliation) protocol - IAB Tech Lab, accessed on August 21, 2025, https://iabtechlab.com/pair/

42. Publisher Bid Enrichment Solution - TrueData, accessed on August 21, 2025, https://www.truedata.co/publisher/

Reseach provided by Gemini AI