# Configure the consent form
Economy+Overview
This guide explains the configurable consent form options and the decisions you should make before requesting personal data from users.
The consent form combines user transparency, privacy requirements, and data availability. For a simple setup, start with the basics: request only the required scopes, add a valid privacy policy URL, and provide a short explanation of why the data is needed.
Use advanced options only when they match your use case.
# Basic configuration
# Scopes
Scopes define which data categories can be released by the user. They are the technical basis for consent and control which fields are later available through the user data endpoint.
Configure:
- Which scopes are requested
- Which scopes are optional or mandatory
- Which scopes are available for the selected license
Effect in the consent form:
- Scopes are shown transparently to the user, depending on the scope type.
- Optional scopes can be deselected by the user.
- Granted scopes directly control the data that is provided to your application.
Before configuration, decide:
- Which data is required for the core functionality?
- Which data is optional but useful?
- Are all requested scopes covered by your privacy policy and use case?
Best practice
Request as few scopes as possible and as many as necessary.
For available scopes and returned fields, see User data endpoint return values.
# Privacy policy URL
The privacy policy URL links to your own privacy information and is required for informed consent.
Configure:
- Public URL to your privacy policy
Effect in the consent form:
- Always visible to the user
- Part of the informed consent flow
Before configuration, check:
- Is the URL current, public, and reachable?
- Does the privacy policy cover the exact scopes and data usage?
Important
Without a valid privacy policy URL, the consent flow is incomplete.
# Additional note
The additional note explains why the user sees the consent form and how the data will be used.
Configure:
- Customer-specific free text
Effect in the consent form:
- Sets expectations
- Builds trust
- Reduces questions and drop-offs
Before configuration, check:
- Is it clear who receives the data and why?
- Is the text short, understandable, and free of legal or marketing-heavy language?
Best practice
Keep the note short, factual, and specific to the use case.
# Advanced options
# Mandatory scopes
Mandatory scopes are required fields that the user cannot deselect. Use them only when the data is technically or professionally required for the offer.
Configure:
- Mark a scope as mandatory
Effect in the consent form:
- The scope cannot be deselected.
- It is shown as required.
- The data is only provided if the user accepts the consent flow as a whole.
Before configuration, decide:
- Is this data truly required to use the offer?
- Is there a technical, professional, or regulatory reason?
Recommendation
Use mandatory scopes sparingly. Too many required fields can reduce user trust and acceptance.
# Partial consent
Partial consent allows users to deselect optional scopes without losing access, as long as the remaining data is sufficient for the offer.
Configure:
- No separate activation is required. Partial consent results from optional scopes.
Effect in the consent form:
- Users can disable individual optional data categories.
- Access remains possible.
- The selected scope set applies to the current consent decision.
Before configuration, decide:
- Can the offer work with partial data?
- Which features depend on optional scopes?
# Anonymous access
Anonymous access allows users to continue without transferring personal data.
Configure:
- Enable or disable anonymous access per login client, if available for your setup.
Effect in the consent form:
- Additional call to action, for example “Enter anonymously”
- No personal consent is stored.
- A technical session key can be passed instead of personal data.
Before configuration, decide:
- Is anonymous access useful for the content?
- Can the content be delivered without personalization?
- Do you need personal reporting, CRM matching, or follow-up processes?
# Do not show again
This option skips the consent form on future logins if the user has already fully accepted the same consent version.
Configure:
- No additional configuration is required.
Effect in the consent form:
- The user can choose not to see the consent form again.
- Consent is stored for the current form version.
- Future logins can continue directly.
The consent form is shown again when relevant consent details change, for example:
- New scopes
- New mandatory fields
- New consent form version
- Reset consents
Best practice
Use this for stable, long-running offers where the requested data does not change frequently.
# Decision guide
| Goal | Recommendation |
|---|---|
| Maximize conversion | Keep required data low and use mandatory scopes only when necessary. |
| Maximize privacy transparency | Explain the purpose clearly and allow partial consent where possible. |
| Minimize repeated prompts | Keep the consent configuration stable and rely on “Do not show again”. |
| Lower the entry barrier | Enable anonymous access if the use case supports it. |
| Strict professional or regulatory flow | Use mandatory scopes carefully and document the reason. |