Skip to main content

Consent Categories

When you set up a Consent Management template, you define the individual purposes you'll ask users to consent to — things like "Analytics Tracking" or "Marketing Emails." Each one appears as a separately toggleable option, giving users precise control over what they agree to.

Under GDPR, a single bundled "I agree" checkbox is generally not considered valid consent. Defining specific, named categories for each purpose is what makes your consent legally meaningful.

Coming Soon

Screenshot: consent form showing three category rows with individual accept/decline toggles and a Save button

Setting up categories​

  1. Go to Click → Templates and open (or create) a Consent type template.
  2. Navigate to the Categories tab in the template editor.
  3. For each consent purpose, add a row with:
    • Name — the label shown to users, written from their perspective (e.g., "Personalized Recommendations" rather than "behavioral_targeting")
    • Key — a short, unique identifier used in your code (e.g., marketing_emails)
  4. When all categories are defined, publish the template and create a deployment to make it live.
Coming Soon

Screenshot: template editor Categories tab with two sample categories and an Add Category button

The category key cannot be changed after publishing

Once a template is published, the key for each category is locked permanently. If you need to restructure or rename keys, you'll need to create a new template. Existing evidence records remain tied to the version the user saw. See Version Management for the current workflow.

Coming Soon

Screenshot: published Consent template Categories tab showing categories in a locked, view-only state with no Add or Edit controls visible — illustrating that keys cannot be changed after publishing

Displaying categories in multiple languages​

You can provide a translated label for each category for each language your template supports. The key stays the same across all languages — only the display label changes.

Set up translated labels in the template's localization settings.

Next steps​