bid id uniqueness

232 views
Skip to first unread message

james....@blis.com

unread,
Apr 4, 2018, 6:02:34 AM4/4/18
to openrtb-dev
The spec (2.5) says "Unique ID of the bid request, provided by the exchange"

It turns out that at least one exchange will send requests with duplicate bid ids.
Unfortunately the imp.id field of the duplicate bid requests are also the same.

Is this conformant to the spirit of the OpenRTB spec?

Thanks
James

Jim Butler

unread,
Apr 10, 2018, 10:53:45 PM4/10/18
to openr...@googlegroups.com
Since bids and their IDs are sent by bidders and not exchanges, I’m not exactly sure what you mean.  Can you be specific as to which attribute you’re referring?

Thanks,
:JB
__________________________
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Blis Ltd, a company registered in England and Wales with registered number 06455773. Its registered office is 7th Floor, 10 Bloomsbury Way, WC1A 2SL, United Kingdom.

If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.

--
You received this message because you are subscribed to the Google Groups "openrtb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrtb-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

james....@blis.com

unread,
Apr 12, 2018, 10:10:25 AM4/12/18
to openrtb-dev
I'm talking about the id of the BidRequest being sent by the SSP.

Jim Butler

unread,
Apr 15, 2018, 1:51:41 PM4/15/18
to openr...@googlegroups.com
Ah gotcha.  Yes the bid request ID is supposed to identify the auction uniquely.  The scope of uniqueness is not explicit, but the spirit is that it would at least be unique among all auctions executed by the exchange.  That said, it's fairly common practice for exchanges to use GUIDs for this field making them globally unique.

On a related note, there's the "Source.tid" attribute which is supposed to link multiple auctions for the same impression opportunity (e.g., a header bidding scenario).  This should be globally unique since those multiple auctions usually come from separate exchanges, but within the same impression opportunity, you might see the same ID which is the point (i.e., to know that these 3 auctions are really all the same impression opportunity).

Since you mentioned "Imp.id", its scope only needs to be unique within the auction itself and it's common to use ordinal numbers (i.e., 1, 2, 3,...).  This is for the case where multiple impressions are offered within the same auction so that a bid can reference which one is of interest.

:JB

To unsubscribe from this group and stop receiving emails from it, send an email to openrtb-dev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
James M. Butler, Ph.D.
Chief Technology Officer, Global Supply Platforms
: Deliver the Future
 

OATH_TAGLINE_BLUE_RGB_170221-01.png

This electronic message transmission contains information from Oath Inc., which may be confidential or privileged. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this information is strictly prohibited. If you have received this electronic transmission in error, please notify sender immediately and delete all copies.

Reply all
Reply to author
Forward
0 new messages