Import user profiles

You can import user profiles from the ReachFive Console. The instructions below guide you step-by-step in importing your users. The visual below shows you a high-level flow of the process.

I just want to see a video

Skip ahead to a short video tutorial that shows you how to configure an import job using a csv file on a SFTP server.

import jobs user flow

Import users from the console

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

Not all User Profile Object fields can be imported. See the table on the User Profile data model page to see which profiles can be imported.

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.
Unless you choose the Force data update from file option, the following applies to importing user profiles:
- Updating existing user: The updated_at value in the import file must be more recent than the existing profile.
- Importing new user: The updated_at value is not mandatory.

Managed vs Lite profiles

Whether you are importing new profiles or updating existing ones, managed profiles and lite profiles should be imported separately as different jobs.

If you try to import a mixed group of managed and lite profiles, it could cause production issues.

Instructions

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

If editing an existing import job, be sure to select the

instead of creating a new definition.

Go to Settings Import definitions.
Select New definition.
Under General, give the import job a name and description. Don’t forget to Enable the job.
Under Source, choose the protocol you wish to use to import the file.
- SFTP
- S3
- GCS
Specify the Server host for the secure FTP site.

Specify the Server port.

Under Authentication method, choose the authentication method type:

Username and password:

Enter the Username for the server.

Enter the Password for the server.

OpenSSH:

Enter the Username for the server.

Enter the OpenSSH private key.

example

-----BEGIN ENCRYPTED PRIVATE KEY----- MIIBpjBABgkqhkiG9w0BBQ0wMzAbBgkqhkiG9w0BBQwwDgQI5yNCu9T5SnsCAggA MBQGCCqGSIb3DQMHBAhJISTgOAxtYwSCAWDXK/a1lxHIbRZHud1tfRMR4ROqkmr4 kVGAnfqTyGptZUt3ZtBgrYlFAaZ1z0wxnhmhn3KIbqebI4w0cIL/3tmQ6eBD1Ad1 nSEjUxZCuzTkimXQ88wZLzIS9KHc8GhINiUu5rKWbyvWA13Ykc0w65Ot5MSw3cQc w1LEDJjTculyDcRQgiRfKH5376qTzukileeTrNebNq+wbhY1kEPAHojercB7d10E +QcbjJX1Tb1Zangom1qH9t/pepmV0Hn4EMzDs6DS2SWTffTddTY4dQzvksmLkP+J i8hkFIZwUkWpT9/k7MeklgtTiy0lR/Jj9CxAIQVxP8alLWbIqwCNRApleSmqtitt Z+NdsuNeTm3iUaPGYSw237tjLyVE6pr0EJqLv7VUClvJvBnH2qhQEtWYB9gvE1dS BioGu40pXVfjiLqhEKVVVEoHpI32oMkojhCGJs8Oow4bAxkzQFCtuWB1 -----END ENCRYPTED PRIVATE KEY-----

If you are importing files with additional encryption:

Select Encrypt.

Enter your password that is used as part of the encryption.

Specify the number of PBKDF2 iterations you used.

PBKDF2 encryption command

openssl aes-256-cbc -salt -pbkdf2 -iter 10000 -in file_to_import -out file_to_import.enc

See encrypting an import file for more details.
Specify the URL for the S3 bucket.

Specify the name Bucket.

Enter the Region for the server.

Enter the Access key for AWS.

Enter the Secret key for AWS.

Specify the Path where the import file is located.

For example

<serverhost>/path-to-file/file.csv.
Specify the Project ID for the Google Cloud Storage.

Specify the App name.

Enter the User name for the server.

Specify the name Bucket.

Enter the Credentials in JSON format.

Specify the Path where the import file is located.

For example

<serverhost>/path-to-file/file.csv.

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

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.

{
  "external_id": "1",
  "email": "foo@gmail.com"
} \n (1)
{
  "email": "bar@gmail.com",
  "name": "Joe",
  "gender": "M",
  "custom_fields": { (2)
      "has_loyalty_card": true
  },
  "consents": { (3)
    "exampleConsent": {
      "date": "2021-11-23T11:42:40.858Z",
      "consent_version": {
        "language": "fr",
        "version_id": 1
      },
      "granted": true,
      "consent_type": "opt-in",
      "reporter": "managed"
    }
  }
}

1 Each profile must separated by a line feed character (\n).

2 Import custom_fields as an object containing a series of fields.

Import consents as an object or as a flattened field with the format consents.<consent>.<parameter> shown below.

...
  "consents.cgu.date": "2021-09-03T19:08:01Z",
  "consents.cgu.granted": true,
  "consents.cgu.consent_version.version_id": 2,
  "consents.cgu.consent_version.language": "fr",
  "consents.cgu.consent_type": "opt-in",
  "consents.cgu.reporter": "managed"
...

Choose the Encoding standard for your CSV file.
Enter your Delimiter. The default is ;.
Enter your Quote char. The default is ".
Enter your Escape character. The default is \.

email,name,gender,custom_fields.has_loyalty_card,consents.newsletter.consent_type,consents.newsletter.granted,consents.newsletter.date,consents.newsletter.reporter
bar@gmail.com,Joe,M,true,opt-in,true,2018-05-25T15:41:09.671Z,managed

If desired, enable the End Job Notification Webhook.

For more information on the webhook, see the End Job Notification Webhook page.

Under Advanced:

Select Import/Update for the Type.

For the Delete type, see Delete user profiles in bulk.
If desired, select Testing mode.
When you import profiles in Testing mode, ReachFive tests:
- access to the server
- access to the import file
- whether the the import file content is valid
Testing mode does not handle database modifications.

If importing Lite profiles only, select Lite profile only.

When you import Lite profiles only, you are not importing the fully managed profiles, but rather those lite profiles that registered with your site. You have to import Lite profiles separately from managed profiles.