prebid
GAM Rendering API key values issue
We're attempting to migrate from GAM original to GAM rendering API but have run into an issue accommodating all elements of our current stack into the new integration and are wondering how to proceed.
Currently for display ads, we send requests to Prebid, Amazon TAM and Nimbus to conduct auctions before building the GAM request object. Each SDK returns a key value pair that gets dynamically inserted into GAM request, along with our own set of custom key values that we use for our direct sold efforts.
Under the Rendering API setup, we're noticing that calls to the TAM and Nimbus SDKs no longer occur (which we can look into with our internal team), but the other issue we've noticed is those custom key value pairs we initially would build into the GAM request object aren't present with the rendering API set up. Would these key values need to be passed into the Prebid SDK instead since the Rendering API removes AdManagerAdRequest where these would normally be added?
Hi @acampbellthescore ! I can confirm that Rendering API doesn't support passing "external" targeting parameters to GAM. So, no TAM or Nimbus line items can be targeted.
It can be supported.
However, can you please share the demo code of how exactly your solution is built? No IDs are needed; we just need to inspect how and when you pass, collect, and pass the keywords.
Hey @YuriyVelichkoPI, sorry for the delay in reply here. We checked with our team and they aren't able to provide demo code, unfortunately, but perhaps I can try to describe what we're looking for to transition to rendering API.
SInce we're a sports app, the key values we're passing into GAM are usually contextual to what page the user is viewing in the app. For example, if the user is viewing an NBA page for information on a specific game, we will pass information like league = nba and match_id = 12345 and these are targetable key values in GAM for potential direct sold buys. There could be an application to add these into Prebid as First Party Inventory (Context) Data targeting parameters if DSPs can match against them, but ideally, we would want to still have these show in a GAM request so any line items we use these key values for are considered as part of the GAM auction and whether GAM determines it needs to render the ad instead of the Prebid SDK.
If the Nimbus/TAM use case could also be looked at, that would be very helpful for us in what we're trying to do.
Let me know if you have any follow up questions.