add retailspot documentation

[rs-guian]

🏷 Type of documentation

• [*] new bid adapter

Related pull requests in prebid.js:

• Retailspot Bid Adapter : initial release Prebid.js#9824

[netlify]

✅ Deploy Preview for prebid-docs-preview ready!

Name	Link
🔨 Latest commit	7384358
🔍 Latest deploy log	https://app.netlify.com/sites/prebid-docs-preview/deploys/649003746e192d0008045298
😎 Deploy Preview	https://deploy-preview-4490--prebid-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[bretg]

@rs-guian - if you're going to claim GDPR support, you almost certainly require a GVL ID. Also, please supply the other metadata fields:

coppa_supported:
userIds:
safeframes_ok:
deals_supported:
fpd_supported:
ortb_blocking_supported:
gvl_id:
multiformat_supported:

[rs-guian]

I'll add those.

We haven't got a GVL id though. We claim to support GDPR as sellers: Transmitting user consent information to buyers. We don't need to request user consent ourselves as we won't read/store nor use user cookie informations. I will update our GVL ID accordingly if this should change.

In the meantime would you mind having a look at our test page where no ad is never shown whereas bid response is always filled up ?
Basic Prebid.js Example with Retailspot
Just in case you quickly see something we miss, thank you.

[fowler446]

Test page is looking good 👍 @rs-guian

[rs-guian]

Everything looks good.
Adapter has been merged into prebid.js

prebid/Prebid.js#9824

thank you

[muuki88]

As Bret mentioned, if you claim gdpr_support your must provide a gvl_id here.

gvl_id: <your id here>

[muuki88]

@rs-guian either add a gvl_id or set gdpr_support to false. Then this is good to merge.

[muuki88]

We haven't got a GVL id though. We claim to support GDPR as sellers: Transmitting user consent information to buyers. We don't need to request user consent ourselves as we won't read/store nor use user cookie informations

Thanks for your patience @rs-guian We'll discuss the GVL_ID topic today in the docs committee.

[bretg]

We discussed this topic @rs-guian . You have to set the gdpr_supported flag to false.

• Prebid cannot trust any entity with user data even through they claim not to look at it or touch it.
• Publishers rely on Prebid as part of their compliance toolset and being able to take action on GDPR consent rules is a part of that. Prebid cannot take action without mapping a user's vendor consent to the specific module. You must have a GVLID for that mapping.
• No one else has tried to claim GDPR support without having a GVLID
• You can attempt to convince your publisher clients that they should make an 'exception' and exempt you from Prebid's GDPR processing activities.

But in the end, from a Prebid perspective, you do not support GDPR if you don't have a GVLID.

[rs-guian]

Got it, thanks a lot for discussing it and giving me this well-argued answer.

[rs-guian]

Done. We'll claim our GDPR ID and update the value soon.

Thank you again.

[bretg]

Thanks

[bretg]

Released with PBJS 7.49. Merging.