Import consents

You can import user consents via the ReachFive Console just as you would import user profiles. This helps speed up importing user information and avoids manual work in ensuring consents are related to the specific user.

You can import all user consents in one file.

Import consents from the ReachFive Console

Follow the instructions below to import user consents from the ReachFive Console.

Prerequisites

  • You must have access to the ReachFive Console.

  • You must have a Developer, Manager, or Administrator role.

  • You must have the Import Jobs feature enabled.

Instructions

The instructions below apply to both creating and editing an import job definition for user consents.

If editing an existing import job, be sure to select the edit icon instead of creating a new definition.
  1. Go to Settings  Import definitions.

  2. Select New definition.

  3. Under General, give the import job a name and description. Don’t forget to Enable the job.

  4. Under Source, choose the protocol you wish to use to import the file.

    • SFTP

    • S3

    • GCS

    1. Specify the Server host for the secure FTP site.

    2. Specify the Server port.

    3. Enter the User name for the server.

    4. Enter the Password for the server.

    5. Specify the Path where the import file is located.

      For example

      <serverhost>/path-to-file/consents.json.

    1. Specify the URL for the S3 bucket.

    2. Specify the name Bucket.

    3. Enter the Region for the server.

    4. Enter the Access key for AWS.

    5. Enter the Secret key for AWS.

    6. Specify the Path where the import file is located.

      For example

      <serverhost>/path-to-file/consents.json.

    1. Specify the Project ID for the Google Cloud Storage.

    2. Specify the App name.

    3. Enter the User name for the server.

    4. Specify the name Bucket.

    5. Enter the Credentials in JSON format.

    6. Specify the Path where the import file is located.

      For example

      <serverhost>/path-to-file/consents.json.

  1. Under Schedule, if desired, use a cron expression for scheduling the job.

  2. Under File format, select the file format type you wish to import. This will be either JSON or CSV.

    • JSON

    • CSV

    Choose the Encoding standard for your JSON file.

    JSON example
    {
        "consents": {
            "consentA": {
                "date": "2021-12-14T10:50:30.039Z",
                "granted": true,
                "consent_type": "opt-in"
            },
            "consentB": {
                "date": "2021-12-14T10:50:30.039Z",
                "granted": false,
                "consent_type": "opt-in"
                }
           },
        "email": "JulioCabrera@company.co.uk"
    }
    1. Choose the Encoding standard for your CSV file.

    2. Enter your Delimiter. The default is ;.

    3. Enter your Quote char. The default is ".

    4. Enter your Escape character. The default is \.

    CSV example
    email;consents.consentA.date;consents.consentA.granted;consents.consentA.consent_type;consents.consentB.date;consents.consentB.granted;consents.consentB.consent_type
    "JulioCabrera@company.co.uk";"2021-12-13T14:50:30.039Z";"true";"opt-in";"2021-12-13T14:50:30.039Z";"false";"opt-in"
  1. If desired, enable the End Job Notification Webhook.

    For more information on the webhook, see the End Job Notification Webhook page.
  1. Under Advanced:

    1. If desired, select testing mode.

    2. If importing LITE profiles only, select LITE profile only.

Feedback