Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logic to decide on showing the CMP UI #38

Open
ydennisy opened this issue Jun 14, 2018 · 0 comments
Open

Logic to decide on showing the CMP UI #38

ydennisy opened this issue Jun 14, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@ydennisy
Copy link
Member

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?

  1. iab consent string, from the priority cookie if present (local) - already available from loader
  2. iab consent string, from the global cookie if present (local) - already available from loader
  3. does the client use a custom vendor/purposes? if yes - DB???
  4. 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
  5. check the client showRule - DB???
  6. 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...

Inspiration:
https://github.com/dimichgh/oja
https://github.com/peasy/peasy-js

@ydennisy ydennisy assigned ydennisy and ittus and unassigned ydennisy and ittus Jun 14, 2018
@ydennisy ydennisy added the enhancement New feature or request label Jun 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants