Fix #3830 and add ESP registerSignalSources docs#3957
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
| {: .alert.alert-info :} | ||
| To use this function, include the [UserId module](/dev-docs/modules/userId.html) in your Prebid.js build. | ||
|
|
||
| This function will register all configured encrypted signals as described in the [UserId module ESP configuration](/dev-docs/modules/userId.html#esp-configurations). |
There was a problem hiding this comment.
It might make sense to list which known signals google will take up
Gam dialogue lists these; one's that are not id providers are not clear what they send
AdColony
Adform ID Fusion
AppLovin
Criteo
ID5
Index Exchange
LiveRamp Authenticated Traffic Solution (ATS)
Lotame Panorama ID
OpenX
Parrable
PubMatic
RTB House
SharedID by Prebid.org
Tapjoy
Unified ID 2.0
Vungle
There was a problem hiding this comment.
I guess a link to the Google docs or the respective ad manager page would be a more reliable source. WDYT?
dgirardi
left a comment
dgirardi
left a comment
There was a problem hiding this comment.
LGTM, but the feature itself seems harder than normal to use? if this is a gpt-only thing I think we could take care of the call timing in Prebid, maybe if you pass setConfig({userSync: {registerSignalSources: true}}). Could be added as a separate feature if there's demand for it.
|
I thought so as well. We were a bit surprised as prebid usually takes care once a configuration is in place. Not sure why it was initially implemented this way. I'm not even sure if the check as it's in place at the moment is necessary. The encrypted signal provider array seems like a command queue. |
4 participants
🏷 Type of documentation
📋 Checklist
userId Module: Added getEncryptedSignalfromSources and registerSignalsources fun… Prebid.js#8117