Scott Menzer

i'd love to see multi-floor support as well!

@jlukas79 can you please take a look at this?

given the approval by @jlukas79 i am merging this

> @smenzer is there something apparent to you that might help this user? @patmmccann I'm not sure exactly...we've always just used the built-in storage functionality of the user id module...

I can see the value in providing all relevant privacy jurisdiction fields in a single function/object like @bretg mentions, but I agree with @patmmccann that this is already partially implemented;...

@bretg maybe I’m missing something but can’t these values already be retrieved by shared Id and pubcommon? We are ingesting them in our module already as do a few others...

> Is https://github.com/prebid/Prebid.js/issues/6673 a duplicate @smenzer ? The difference in my request is that we modify the existing consent data parameter (which contains only GDPR today) to support everything (similar...

with the updates from @bretg I agree that these are the same now. I can close out #6673 in favor of this one. thanks Bret!

i'm getting the same type of error if i try to upgrade my laravel to 6.0 with composer: ``` ... Generating optimized autoload files > Illuminate\Foundation\ComposerScripts::postAutoloadDump > @php artisan package:discover...

@adtechnology as @patmmccann mentioned, this is cookie syncing and has nothing to do with the Prebid User ID module or our submodule. Based on the consent string we receive, we...