Skip to content

Separate purpose and feature lists for publisher vs global consent #41

Open

Description

@anissaconnor

Allow publishers to get consent for themselves for a different list of purposes and features than the purposes and features they get for their partners. In the MVP there will be no distinction to the user in the UX about whether the purposes/features are applicable to the vendors or the publisher but there will be a distinction in the formation of the publisher and global cookies.

We can make the distinction in the UX in a later version if this is deemed important to publishers.

Activity

  1. added
    BetaSupport 300 Display Clients
    and removed
    MVPSupport Test Rig - 4/26
    on Apr 25, 2018
  2. added and removed
    BetaSupport 300 Display Clients
    on May 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions