purpose: "transmitPreciseGeo" in consentManagement, dont think its working properly

[spormeon]

Type of issue

when we include in the consentManagement setup:

{
purpose: "transmitPreciseGeo",
enforcePurpose: true,
enforceVendor: true
}

no "geo" info is being passed to any bidder that has "special features" - Use precise geolocation data . In the cmp, such as Index Exchange:

geo omited: IX bidder

take the above config out, geo appears: IX bidder

Geo is also set in realTimeData:

when purpose: "transmitPreciseGeo" is on, these warning are thrown:

Platform details

chrome, mac P.V: 8.18.0

Other information

[dgirardi]

The screenshots do not tell me what you're looking at, but I tried and failed to reproduce for both the input and output of the IX adapter. Could you provide a test page?

I did confirm that the geolocation module always gets denied, because the gdpr rules expect it to provide a GVL ID. I'll need to think about how to fix it; I'm not sure transmitPreciseGeo is a good fit for it.

[spormeon]

professor prebid those top 2 screenshots are from (timeline menu tab, click on the bidder, IX in this occasion)& the bottom one with the 2 warnings in it, events menu item

[dgirardi]

OK I think I understand - they are the same problem; when the geolocation module gets denied it won't put geo in the bid stream so IX doesn't see it. If you set it through other means (through for example setConfig([ortb2 -> device -> geo])) the bidder part works as expected, although IX in particular does not look at device.geo, only user.geo.

A workaround, for now, is to override with:

setConfig({
    allowActivities: {
        transmitPreciseGeo: {
            rules: [{
                condition: ({component}) => component === 'rtd.geolocation',
                allow: true
            }]
        }
    }
})

This effectively disables GDPR enforcement for the geolocation module, but I don't think that matters since each bidder (and other RTD modules) still need to pass the consent check to get the data.

[spormeon]

ok, does that give a knock on issue then in the geolocation module, i.e the module only pushes to device, so any bidder picking up on user, its useless? Shouldn't there be 1 p;ace where they all pick it up from, be that dvice or user, to harmonise it all?

[dgirardi]

They are both part of the ORTB spec; I think they are supposed to be two different pieces of information - where the device is compared to where the user lives. Bidders are supposed to pick up both, but I wouldn't blame them if they didn't know what to do with two sets of coordinates.

[patmmccann]

We need to make the geolocation module vendorless; we need to check the publisher consents, not the vendor consents as we do in some other vendorless modules; we need to also never pop a dialogue asking user for precise location when the publisher doesnt have consent to it.