Creating External Web Form Collection Points

You can create External Web Form type Collection Points if you have an existing web form hosted on an external website for which you want to record consent. Creating a Collection Point using the External Web Form type allows you to map field attributes for an existing web form to the Purposes, Purpose Preferences, and Data Elements defined on the Collection Point.

To create an External Web Form 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 Create New Collection Point screen appears.

  3. Click the External Web Form Integration tile. The Define Collection Point screen appears.

  4. Complete the fields, as necessary. For more information, see Define Collection Point Screen Reference.

    In the Configuration section, create as many Purposes, Data Subject Identifiers, and Data Elements as needed clicking the Create New button in the corresponding fields.



  5. Click the Create Collection Point button. A Collection Point is created in Draft status.
    Note:

    Once the Collection Point is published, Purposes created from the Purposes field will be published as well. For more information, see Previewing and Publishing Collection Points.

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

Form URL (Optional)

Enter the URL at which the Collection Point web form will appear.

Purposes

Select the Purposes of processing to include in the Collection Point.

Data Subject Identifier

Select the Data Element type that will be used to uniquely identify data subjects that interact with the Collection Point. You can configure what Data Element types can be used as identifiers on Collection Points using the Data Elements screen.

If you want to track data subject consent preferences across multiple Collection Points, ensure you use the same data subject identifier in each Collection Point.

Note:

The user identifier value supplied by the data subject is passed through to our systems as consent records are created.

To protect our service, we operate a safelist of accepted keyboard characters.  This includes all letters and numbers plus a select set of additional characters: \/-@.*#() _',:;+~{}|`^?=!$%()\\[]

If any identifier values are submitted with characters outside of this set, they will be rejected and no consent record will be generated.

If you expect valid user identifiers that contain characters outside of these, please contact OneTrust Support to have the safelist updated.

Consent Interaction Type

Select the type of consent interaction that your web form is using. The following options are available:

  • Form Submission Only - The web form includes a standard HTML Submit button that a data subject can click to give consent.

  • Opt In Checkbox + Form Submission - The web form includes blank check boxes that a data subject can select to indicate consent for those selections before submitting the form.

  • Uncheck to Opt Out + Form Submission - The web form includes pre-selected options that a data subject will have to clear before submitting the form, otherwise a consent record will be created for those options.

  • Check to Opt Out + Form Submission - The web form includes blank check boxes that a data subject will have to select to indicate no consent for those selections before submitting the form.

  • Custom Single Trigger - The web form includes a single action that is not an HTML submit button that a data subject can use to give consent.

  • Custom Conditional Trigger - The web form includes two (or more) actions or conditions, which are not standard HTML form actions, that a data subject must complete or meet to give consent.

    Note:

    Using custom triggers usually requires custom code on the website to trigger the generation of a receipt.

Data Elements

Select additional Data Elements to collect from the data subject when interacting with the Collection Point.