You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No need to create additional DFP line items, targeting hb_format=native. Can use existing banner line items.
No concerns over passing KVPs that are too long, as no additional KVPs are required to be passed to DFP. This is more of an issue when using single request mode for DFP.
No concerns over encoding characters DFP does not allow.
You lose DFP click tracking metrics.
The ad is not rendered in an iframe. Is this an issue?
Are there other downsides or concerns?
This seems to work using existing prebid.js without modifications. I'm interested in any feedback on this approach. Thanks!
Type of issue
Request for feedback.
Description
From #3224 (comment) I created an example that demonstrates another approach to rendering native ads through prebid using the existing renderer option:
https://gist.github.com/nanek/cfcd43a1dc343dabfad505eb4e63653c
No need to create additional DFP line items, targeting hb_format=native. Can use existing banner line items.
No concerns over passing KVPs that are too long, as no additional KVPs are required to be passed to DFP. This is more of an issue when using single request mode for DFP.
No concerns over encoding characters DFP does not allow.
You lose DFP click tracking metrics.
The ad is not rendered in an iframe. Is this an issue?
Are there other downsides or concerns?
This seems to work using existing prebid.js without modifications. I'm interested in any feedback on this approach. Thanks!
/cc @mkendall07
The text was updated successfully, but these errors were encountered: