Skip to content

[waiting @ P7]Unsynced consent status #5

Description

@taimooralam

Although we discussed this before that the user could open the page on their 2nd screen using QR code, and the status could be out of consent and we can address this via a cookie flag everytime the user jumps to the 2nd layer, this still poses a problem.

Here is a scenario where the consent status will still be out of sync.

  1. User jumps to 2nd layer (cookie flag is set)
  2. User goes to the 2nd screen via the QR code (keeps the tab opened on their 2nd screen browser)
  3. User gives full consent on the 2nd layer
  4. User zaps out and zaps back into the channel
  5. The cookie flag is detected, server status is synced.
  6. Now the user, on their already opened 2nd screen browser tab, opts out of a vendor.
  7. User zaps out and zaps into a channel.
  8. There is no consent check asked from the server.
  9. The the local cookie always has full opt-in, it never asks the server for the server status.
  10. This leads to a permanent out of sync consent status.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions