You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: build a extendable module which will take decisions on showing a UI or not.
Possible scenarios:
A: the user does not have any cookie
B: the user has a cookie, but it does not cover all the requested vendors, purposes
C: the user has a cookie and it consents to all needed vendors
Case A = show UI
Case B = client configurable showRule : strict || relaxed
Case C = do not show UI
What cookie to select?
if 1st party (.client-website.com) present default to use, otherwise use 3rd party (.consensu.org)
What needs to be compared?
iab consent string, from the priority cookie if present (local) - already available from loader
iab consent string, from the global cookie if present (local) - already available from loader
does the client use a custom vendor/purposes? if yes - DB???
check the custom cookie plutoconsent -> a structure for this needs to be decided, but for now this can simple be an object with two arrays of ids. - SHOULD already available from loader
check the client showRule- DB???
make the final decision isShow : true || false
As more client variations will be needed, this should be extensible - so we should decide on how to build in new logic.
Also how do we fetch the client config, should these be loaded on the server, or sent to the UI as soon as we have the initLoader() executed...
Goal: build a extendable module which will take decisions on showing a UI or not.
Possible scenarios:
Case A = show UI
Case B = client configurable
showRule : strict || relaxed
Case C = do not show UI
What cookie to select?
What needs to be compared?
loader
loader
plutoconsent
-> a structure for this needs to be decided, but for now this can simple be an object with two arrays of ids. - SHOULD already available fromloader
showRule
- DB???isShow : true || false
As more client variations will be needed, this should be extensible - so we should decide on how to build in new logic.
Also how do we fetch the client config, should these be loaded on the server, or sent to the UI as soon as we have the
initLoader()
executed...Inspiration:
https://github.com/dimichgh/oja
https://github.com/peasy/peasy-js
The text was updated successfully, but these errors were encountered: