Skip to main content

OneTrust Module

The OneTrust Module integrates with the OneTrust system to either retrieve the status of a consent receipt or create/update a consent receipt for a customer.

info

The email address is taken automatically from the LoyJoy variables. You need to use either an Email Module or a Sign In Module to let users enter their email address so that it can be used in the Optimizely module.

Process variable​

You can save the consent receipt’s purpose status to a defined process variable for later use. The status values include: ACTIVE, ALWAYS_ACTIVE, EXPIRED, EXTEND, HARD_OPT_OUT, NONE, NO_CONSENT, OPT_OUT, PENDING, WITHDRAWN.

Required Inputs​

  • Customer: Specify the environment (e.g., app-{env}, such as app-eu).
  • Client ID and API Secret: These OneTrust credentials are necessary for generating an access token. Further details on the Client ID and the API Secret can be found in the Onetrust documentation.
  • Collection Point ID and Purpose ID: Use these IDs to filter the consent receipts.

Required Inputs​

  • Customer: Specify the environment (e.g., privacyportal-{env}, such as privacyportal-eu).
  • Collection Point JWT Token: Access token for the collection point.
  • Purpose ID: Defines the purpose for which the status is being updated.
  • Purpose Status: Set the new status of the consent receipt to one of the following values: CANCEL, CHANGE_PREFERENCES, CONFIRMED, EXPIRED, EXTEND, HARD_OPT_OUT, NOTGIVEN, NO_CHOICE, OPT_OUT, PENDING, WITHDRAWN.

Dynamic Data Mapping​

Dynamic data from the chat can be passed to the OneTrust system. Configure the data source and target fields through mappings.

For more information on Collection Points in OneTrust, have a look at the documentation