unexpected behavior with TCF control and permutive RTD module

[jdelhommeau]

Hi prebid community!

We had an issue with our EID (utiq.com) being transmitted in the various prebid bidder.
Upong investigation, we identified the issue being due to a RTDModule, unrelated to our EID (Permutive RTD). The module had no TCF consent and was getting below warning:

WARNING: Activity control: TCF2 denied 'transmitEids' for 'rtd.permutive'

This seemed to cause the EIDs (including ours) not to be passed in any of the other prebid bidders.
I was able to solve this by "bypassing" the TCF control module, using the gvlMapping prebid configuration to force the GVL id on the permutive RTD.

You can see the issue on this test page:
https://jdelhommeau.fr/prebid/prebid_issue_rtd.html

and same test page but with the gvlMapping fix applied:
https://jdelhommeau.fr/prebid/prebid_issue_rtd_fix.html

Is it expected that lack of consent for the Permutiv RTD module would also impact the ability for other conented bidders to get access to the EIDs?

Notes:

prebid version here is v9.53.2 and prebid download configuration is below:

{
"version": "9.53.2",
"modules": [
"equativBidAdapter",
"consentManagementGpp",
"consentManagementTcf",
"gppControl_usnat",
"gppControl_usstates",
"gptPreAuction",
"storageControl",
"tcfControl",
"permutiveRtdProvider",
"utiqIdSystem",
"utiqMtpIdSystem"
]
}

[andyblackwell]

oh good I was just banging my head on this issue too, from what I can tell it looks like if you have more than one RTD module, and one of them is denied transmitEids, then the user.ext.eids gets redacted entirely from the ortb2 object, so all bidders who rely on user.ext.eids being populated in the ortb aren't receiving them, but ones who grab them from userIdAsEids still get them fine. will test out that PR fix