Prebid.js + 51Degrees RTD demo
See the OpenRTB 2.6 bid request Prebid.js generates with and
without the 51Degrees RTD module enriching
device.* and user.eids. Run a live
Prebid auction in this browser, or pick a sample device to see
what the enriched bid request would look like for that
User-Agent. Scroll down and try it out.
IP address
The box starts with the address this site sees for your browser, and is empty where that address is a private one.
Choose a different address to see the
device.ip, device.geo.*, and
identifier enrichment change.
51Degrees identifier preference
Pick one use for the 51Degrees identifier (51Did). With none selected the demo asks for non-marketing, because without a usage 51Degrees creates no 51Did at all, and a non-marketing 51Did is then deliberately kept out of the bid request.
| Allowed use | Your choice |
|---|---|
|
non-marketing Use that is not marketing, such as measurement, security and fraud prevention. A non-marketing 51Did must never be sent to a demand source. |
|
|
standard Targeted marketing and other content unrelated to your browsing history or interactions, such as content based on time, region and the page you are on. |
|
|
personalized Targeted marketing and other content related to your browsing history or interactions. |
|
Only one option can be selected at a time, and each option includes the ones above it, so standard also allows non-marketing, and personalized also allows standard and non-marketing. That is how a 51Did records its usage, one answer per visitor covering every use below it.
Standard and personalized 51Dids need a License Key that carries the 51Did product, which 51Degrees grants after its know your customer checks. Non-marketing 51Dids are available without one.
Optional email
The sample devices return a Probabilistic
51Did, derived from the device and the network, and a
Random 51Did, a GUID 51Degrees creates.
Enter an email and they also return a
Hashed Email 51Did. The address is sent
to the cloud only as id.email evidence,
paired with a salt, and is used solely to compute the
hash. The live auction shows only the Probabilistic
51Did, because the Prebid.js module in this demo adds
only that one. For more on each 51Did and what its Match
Key means, see the
51Did documentation.
Run a demo
Use the pills at the bottom of this section to pick which
device drives the auction. Live (this
browser) runs two Prebid.js auctions in this
browser against a test placement and shows the
ortb2 Prebid hands to the bid adapter.
Whichever pill you pick, the 51Did is created in your
browser, and it is left out of the bid request when its
usage is non-marketing, because such a 51Did must never
reach a demand source.
The other pills are Sample triggers. Each
one loads the 51Degrees client script in
your browser with that device's
User-Agent and client hints as query
parameters, because a browser cannot set those headers for
another device. The script finishes its round from here,
so the 51Did is created in your browser rather than on a
server, and the page then builds the device
and user.eids blocks from the cloud's answer.
The 51DegreesRtdProvider module in this demo
adds only the Probabilistic entry, so the Random and
Hashed Email entries shown here are the page's own.
Evidence this browser sent to 51Degrees
Your browser sent these values to
cloud.51degrees.com as query parameters,
because it cannot set User-Agent or
Sec-CH-UA-* headers for another device. The
51Did that comes back is created in your browser, so its
creator context describes this connection while the device
fields describe the device above.
No sample loaded yet.
OpenRTB request: Without 51Degrees
Full bid request as it would go to the bidder, before the RTD provider runs.
No trigger run yet.
OpenRTB request: With 51Degrees (enriched)
After the 51Degrees RTD provider runs.
Highlighted device.* and
user.eids fields are what 51Degrees added.
No trigger run yet.