Teads Bid Adapter: Add ORTB2 device data to request payload

[jwrosewell]

Type of change

• Feature
• Updated bidder adapter

Description of change

This PR enhances the Teads bid request by incorporating device data from the global ORTB2 object.

The device object has previously been populated by simplistic parsers, if at all, and was inaccurate as a result. Prebid now benefits from RTD modules such as 51Degrees that enrich all the device object fields including Apple iPhone model category and device ID. The PR enables Teads' users to benefit from the device object.

Other information

cc: @github-saad-elmahfoudi, @github-baptiste-haudegand, @github-christophe-oudar, @github-matthieu-wipliez, @github-mickael-leclerc, @github-ishara-chan-tung

[jwrosewell]

@github-saad-elmahfoudi, @github-baptiste-haudegand, @github-christophe-oudar, @github-matthieu-wipliez, @github-mickael-leclerc, @github-ishara-chan-tung - this PR will ensure Teads benefits from publishers efficiently populating the device object with enriched data including iPhone model categories and other features not obtainable via SUA and UA. As publishers progress rollout this becomes more critical.

[github-tom-kuhnen]

Hi @jwrosewell !
Why do you see it's critical to merge this one ?
As I understand, it's new kind of data but the field we are using (like ortb2.device.sua) still continue to be populated, right ?

[jwrosewell]

@github-tom-kuhnen - the Structured User Agent (SUA) field and User-Agent (UA) field continue to be populated but do not provide sufficient detail to accurately identify the device including iPhone model category. GetHighEntropyValues on which SUA relies are also experimental, not always available, and subject to change. During trials earlier in the year publishers that accurately enriched the device object observed 9% CPM increases. Publishers working with Teads will not have any possibility of achieving similar results unless the full device object is passed. This PR ensures the the full enriched device object is passed and thus Teads and their partners have more information to work with.

BTW We see many many problems with the parsing of SUA and have an open source project that provides guidance to those using it. See here.

[github-baptiste-haudegand]

Hello @jwrosewell, ok we could indeed add it to our adapater