Document JS dynamic creatives#5120
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
a03c78c to
f1e1377
Compare
|
Hi Thanks for this initial docs. We are using prebid native through GAM native designs.
Do you mean that there's a need for prebidjs in order to support native? This is IMHO not true, as native can be requested via prebid server as well, and thus rendered too.
We have never get passed web, as native demand was basically none existent for us . However the initial approach, send all assets via key values, should support AMP. If all assets are sent as key values, they can be accessed through macros and used in native design templates
IIRC
That is true. I guess 🤔 |
That sounds right, but otoh, how? I was stuck in trying to update that page, since I've never seen it done and it only talks about JS. |
|
Looking over it quickly:
Here's an older test creative I found in our GAM instance. Besides the source of the script being a pre-release version, the gist is similar to what's documented at https://docs.prebid.org/adops/gam-native.html We recently tested something along these lines with in-app mobile native, and didn't get complaints. Will bring it up again with the testers to make sure this specific case worked. So bottom line is I don't see a major problem with https://docs.prebid.org/prebid/native-implementation.html except that mobile rendering is way more complicated now that there are multiple ways of rendering every type of creative. So it is lacking all the mobile native rendering choices, but I'm not qualified to add those. |
|
Ok, worked with our PostIndustria contact and found that there are indeed issues with the docs. It's on my list, but may take a few weeks to resolve. |
Document new option to set up creatives with Prebid.js - prebid/Prebid.js#10819
Note
There are many references to PUC in native documentation that shoud, but did not, get updated:
https://docs.prebid.org/prebid/native-implementation.html
I am not sure on how to approach it because:
sendTargetingKeysandrequestAllAssetsoptions. Those are irrelevant for the new approach. The first may be relevant for AMP/mobile - again, I don't know if those work at all. The second is, to the best of my knowledge, just a relic and there's never a reason not set it totrue.To me it looks like native docs need an overhaul which is a bit more than I am prepared to chew for this feature.
🏷 Type of documentation
📋 Checklist