Creating Dynamic Collection Points

You can create a Dynamic Collection Point by enabling dynamic configuration on a Custom API Collection Point. By creating a Dynamic Collection Point, you can gather information about all Purposes and Data Elements configured within the application without having to manually link each one individually to a Collection Point. This allows for additional flexibility when using Collection Points to meet multiple different use cases, reduces the need to create new versions of the Collection Point when changes are required, and decreases the necessity to further configure the Collection Point after creation.

Note:

To access the Universal Consent & Preference Management APIs, see the OneTrust Developer Portal.

To create a Dynamic Collection Point

  1. On the Universal Consent & Preference Management menu, select Interfaces > Collection Points. The Collection Points screen appears.

  2. Click the Add New button. The Collection Point Types screen appears.

  3. Click the Select button on the Custom API tile. The Define Collection Points screen appears.

  4. Complete the fields, as necessary. For more information, see Define Collection Point Screen Reference.
  5. In the Configuration section, enable the Allow Dynamic Configuration setting. Once enabled, the Purposes, Data Subject Identifier, and Data Elements fields will disappear, allowing the values to be dynamically sent in the API payload for the Collection Point.
  6. Click the Create Collection Point button. A Collection Point is created in Draft status.
Note:

When setting up a Custom API that utilizes a Dynamic Collection Point, the identifierType is a required field in the POST v1/consentreceipts payload.

Define Collection Point Screen Reference



Section

Field

Description

Overview

Name

Enter a unique name for the Collection Point.

Description

Enter a brief description of the Collection Point.

Organization

Select the organizational group that will be responsible for the Collection Point and the data collected through it.

Responsible User (Optional)

Select the user that will be responsible for the Collection Point.

Configuration

Allow Dynamic Configuration

Enable this setting to set up the Custom API type Collection Point without having to define the Purposes, Data Subject Identifier, or Data Elements in the configuration. Once enabled, the Purposes, Data Subject Identifier, and Data Elements fields will disappear. You will then be able to dynamically send these values in the API payload for the Collection Point.