Consent Groups

Released on 14 June

We are working on a new feature that groups consents. By grouping consents for users, you maximize the chances of users opting-in by consolidating potentially lengthy consent options. You should properly inform your users about what data is collected and how it is processed to remain GDPR compliant.

Standalone consents

All existing consents are not impacted by this new feature. We are creating a dedicated page to administer and manage Consent Groups in the ReachFive Console, under the Settings  Consents menu which is separate from the existing standalone consents pages.

Essentially, Consent Groups are a more user-friendly way to validate multiple standalone consents at once and function in one direction (from group to consents). This feature has been developed to allow brands to display a group of consents to end users in a signup process for instance, instead of showing a full list of standalone consents that might take away from their user experience or even completely deter them from signing up.

Consent Group rules

  • Groups can have one or more standalone consents in them.

  • A standalone consent can be part of multiple groups, and in that case, the latest group acceptance or rejection defines the status of the standalone consent.

  • The acceptance or rejection is only one way (from group to consents).

  • Groups themselves are not a state of consents, but rather act as a facilitator to validate multiple standalone consents at once, meaning that we do not maintain a logical acceptance or rejection status of the group if the elements of the group have been granted or rejected at a later point in time.

  • Groups acceptances or rejections can be found in the User consent log.

  • Groups acceptance or rejections are not found directly in the user profile; we only store standalone consents here.

  • Groups are one level deep only; nested groups are not supported.

API operations

The endpoint for Consent Groups is the same as for standalone Consents. The primary difference is the associated_consents field in the JSON payload.

Consent Group endpoint
/api/v1/consents
The operations below reflect the planned development for Consent Groups. The Release Notes and Management API will contain the official information.
Consent Group operations
Operation Notes

GET /api/v1/consents

List all known consent groups.

GET /api/v1/consents/:key

Retrieve a specific consent group where key is the unique group.

POST /api/v1/consents

+ JSON payload

Create a consent group.

PUT /api/v1/consents/:key

+ JSON payload

Update a consent group where key is the unique group.

DELETE /api/v1/consents/:key

Delete a consent group where key is the unique group.

 
{
    "key": "cgu",
    "consent_type": "opt-in",
    "tags": [
        "web",
        "weekly"
    ],
    "versions": [
        {
            "version_id": 1,
            "author_name": "auser@mailbox.com",
            "translations": {
                "en": {
                    "description": "I agree to the End User License Agreement.",
                    "title": "EULA"
                }
            }
        }
    ],
    "status": "active",
    "associated_consents" : ["key1", "key2"] (1)
}
1 The associated_consents array contains the keys of all standalone consents that are part of this specific Consent Group.