Consent groups

If you want to group multiple standalone consents into a more user-friendly way, you may wish to use consent groups. It presents the same consents as multiple standalone consents but in a collection presented as a single touchpoint that can be reviewed and accepted by your users. This page provides you with information on how consent groups work as well as how to create one from the ReachFive Console.

Groups can only contain one level, meaning there are no nested groups.

Consent Groups are a 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.

The example scenarios below give you a visual of how consent group acceptance works.
  • 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 state of the standalone consent being either archived or active.

  • 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.

Example scenarios

The scenarios in the tabs below provide three example scenarios.

This is not an exhaustive list of scenarios, but acts as a guide for you to understand the basic logical flow for how Consent Groups work with ReachFive.
History

The term history below essentially means the user had accepted or rejected a standalone consent that is part of the consent group.

  • Users accepts (no history)

  • User accepts (history)

  • User accepts and rejects (history)

In this first example scenario, a user opts into a consent group with no prior interaction with any of the standalone consents that are part of the group.

consent group no history

In this second example scenario, a user opts into a consent group when they had previously rejected Consent A and Consent C.

consent group 1 previous rejection

In this third example scenario, a user opts into Group 1 and rejects Group 2 when they had previously rejected Consent A and accepted Consent C.

consent group 2 previous rejection

You can create, update, and archive user Consent groups easily from the ReachFive Console.

If you do not see the Consent group option available on your ReachFive Console, get in touch with ReachFive Support as the feature may need to be enabled.

Prerequisites

  • You must have access to the ReachFive Console.

  • You must have a Developer, Manager, or Administrator role.

  • You must have the Consents feature enabled.

Instructions

  1. Log in to your ReachFive Console.

  2. Navigate to Settings  Consents  Consent Group.

  3. Create, edit, or archive a Consent group.

    • Create

    • Edit

    • Archive

    1. Click New Consent group.

    2. Enter a Key for your Consent group.

    3. Choose the Consent group Type.

      • opt-in: Requires explicit action by the user on signup.

      • opt-out: Automatically accepted on user signup. If a user does not want to accept the given processing purpose, the user must explicitly opt out of it.

        Opt-outs are considered lawful only if justified by legitimate interest.
    4. Add a Tag. Hit Enter to ensure the tag is received.

      Tags are normalized before being saved. This means that trailing spaces are removed and all letters are converted to lowercase. Duplicate tags are also removed.
    5. Under the Version 1 tab, add a Translation for your Consent.

      Make sure you first add a translation for the account’s default language. After that, you can add as many translations as you like.
    1. Choose the language for your translation from the dropdown menu.

    2. Give the consent translation a Title.

      This is the primary text that the user sees when consenting.
    3. Write a Description for the consent translation.

      This describes the consent to the user. For example, "Sign up to our newsletter".
    1. Associate the standalone consents you want to include as part of the consent group.

    2. Don’t forget to Save your input.

    1. Click the edit icon under Actions.

    2. Update your Consent group as needed.

      It is okay to edit an existing Consent group version. However, if there are substantial changes that impact what the user is agreeing (or not agreeing) to. We highly recommend that you create a new version.
    1. To add a new Consent group version, click Add new version.

    2. Choose the language for your translation from the dropdown menu.

    3. Give the consent translation a Title.

      This is the primary text that the user sees when consenting.
    4. Write a Description for the consent translation.

      This describes the consent to the user. For example, "Sign up to our newsletter".
    1. Don’t forget to Save your input.

    1. Find the Consent group that you would like to archive.

    2. Click the archive icon under Actions.

    3. Click Yes when the pop-up asks if you want to archive the consent.

    You can see the consent is archived when it is greyed out as shown in the image below.

    console view of archived consent

    You can reactivate a consent at any time.

This section provides important definitions and interface help for using and managing Consent group from the ReachFive Console.

Here you find definitions or common items and terms on the Consents UI as well as a description of icons.

Definitions

Item Required Description

Key

Uniquely identifies a Consent group. This key is used to reference the Consent group in the ReachFive SDK.

consents key

Title

The title of the Consent group.

consents title

This is what the user reads to decide to opt-in or opt-out.

Description

Describes the Consent group to the user in more detail.

consents description

Type

Specifies the Consent group type.

  • opt-in: requires an explicit action by the user on signup.

  • opt-out: is automatically accepted on user signup. If a user does not want to accept the given processing purpose, the user must explicitly opt out of it.

consents type

Tags

A string tag (label) that can be added to Consent groups. This improves filtering and categorizing Consent groups via the ReachFive Console.

End users (those accepting consents) cannot see any tag associated with the Consent group.

consents tags

Versions

Consent group versions allow you to offer different versions of a single Consent group. For example, if you need to what is accepted in the Consent group, but the Consent group is standard across your offerings, creating a new Consent group version allows you to manage this from one place in the ReachFive Console.

When creating a Consent group, Version 1 is automatically available to you where you (at a minimum) add the translation for your default account language.

Translations

Allows you to set different translation for the Consent group title and description.

You must first set the translation for the default language of your account.
Currently supported languages
  • de - Deutsch

  • en - English

  • es - Español

  • fr - Français

  • it - Italiano

  • nl - Nederlands

  • ru - Ру́сский (Russian)

  • pt - Portuguese

consents translation

UI help

Item Description

edit icon

Edits a Consent group.

filter items

Filters Consent groups. You can search by title, key, or tag.

archive icon

Archives a Consent group. You can reactivate an archived Consent group at any time.

Users can refuse a previously accepted Consent group if the Consent group is archived. However, if they refused a Consent group in the first instance, they cannot accept an archived Consent group.

reactivate icon

Reactivates a previously archived Consent group.

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

Consent Group endpoint
/api/v1/consents
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

Create a consent group.

PUT /api/v1/consents/:key

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",
    "associatedConsents" : ["key1", "key2"] (1)
}
1 The associatedConsents array contains the keys of all standalone consents that are part of this specific Consent Group.
Feedback