Access Type: Configuration Tree - Editor
Premium Feature: Preference Management Platform
A processing rule defines the initial state of a purpose before the end-user has made a choice. By defining the processing rule for a purpose within the PMP configuration tree your organization is setting whether the purpose opted-into (accepted) or opted-out of (rejected) when an end-user views the preferences widget for the first time.
In this article, we will cover the following
- Processing rule overview
- Impact on purpose single purpose widget layout
- Configure processing rule for PMP purpose
Processing rule overview
Processing rules only apply to purposes within your organization's configuration tree and only define the initial consent state of a purpose. Refer to the table below for more information on the different processing rules you can configure for a PMP purpose:
| Processing rule | Description |
| Opt-in (default) | Purpose starts not selected and end-users have to explicitly opt-in if they agree |
| Opt-out | Purpose starts selected and end-users have to explicitly opt-out if they disagree |
Note: By default, the processing rule for every purpose in your PMP configuration tree is Opt-in unless otherwise edited.
Once an end-user saves their selections, the end-user’s choices always take precedence and the processing rule stops applying for that end-user.
Impact on purpose single purpose widget layout
For your convenience, Didomi as collated how configuring the processing rule for a purpose will change the presentation of the purpose for each single purpose widget layout.
| Widget layout | Opt-in (default) | Opt-out |
| Radio buttons | No option selected | The Yes button is preselected for the end-user |
| Single checkbox | Unchecked | Checkbox is preselected for the end-user |
| Tap to change sentence | Default Opt-in sentence shown | Default Opt-out sentence is shown |
Configure processing rule for PMP purpose
Processing rules are configured on a per-purpose basis within your organization's configuration tree and do not apply to preferences.
Note: Processing rules for a purpose cannot be adjusted for each preferences widget on which it is included. If processing rules need to vary by preferences widget we recommend creating separate purposes to account for the difference in processing rules.
In order to configure a processing rule for apurpose in your configuration tree, click Preference Management on the left-hand panel and select the Configuration Tree tab on the subsequent page.
Navigate to a specific purpose within the configuration tree and click the ellipsis inline with the purpose name.
Select the processing rule you wish to set for the purpose.
If required, confirm the decision to change the processing rule in the subsequent modal and click Yes, enable!
In order to reflect a change of processing rule for a purpose on a published preferences widget your organization will need to republish the preferences widget.
Updating the processing rule for a purpose will not change any existing end-user choices.