Skip to main content
How to prepare the user CSV?

On this page, you'll find what data Spencer needs in our CSV Overview:

Tom Segers avatar
Written by Tom Segers
Updated over a month ago

We provide the option to use a CSV which you can:

  • Upload in the back-office

  • Sync through an SFTP

Spencer expects the following conditions when you complete a user in the CSV:

  • New users that should be created in the database

  • Updating information of users

  • Archiving users

You can update the CSV as preferred, you can leave columns out or add them manually. important: When Spencer imports the CSV we expect column headers.

Additional information

Formatting character set - UTF-8 Field delimiter - ; String delimiter - "

Multilingual columns

Below the fields that require a column per language

  • tags

  • contract_type

  • Departement

  • division

  • subdivision

  • job_title

  • domain

  • region

  • zone

Example is shown below

Required fields

  • external_id

  • first name

  • last name

  • country

  • preferred language

  • authentication_type

    • username_password = Login via Spencer authentication

    • company_account = Login via your SSO

  • authentication_id (only if the method is company_account).This field expects the UPN value to identify the user in your SOR. This is usually your company email-address.

  • One of the following 4 elements in order to receive a one-time verification code before setting a personal password

    • Mobile phone (business or private)

    • E-mail (business or private)

Best Practices/additional information

  • external_id - length 256 characters

  • Column headers - needs to be lower case.

  • manager - the value inserted is going to be the external_id

  • default_site - requires the external_id of a site. it isn't possible to add multiple sites.

  • phone numbers- phone numbers should be formatted as follow

    • country code with (+)

    • all numbers without space

    • ex - +32488063309

  • tags - tags are being used to as additional information attached to the user. You can use tags to create specific userlists. a tag exists of the following:

    • ID : value - below some examples

      • mkt:marketing

      • sexem:male

    • you can't give multiple values to an ID so no sexe:male and sexe:female or Gender:m or Gender:f

    • if you want to add multiple tags to a user you can separate them with a ,

      • mkt:marketing,sexem:male

      • streetfood:Tony’s Street Food,mkt:marketing

  • preferred_language- is a combination (language-country) of the following ISO standards:

  • Dates

    • YYYY-MM-DD

      • 2020-03-06

Did this answer your question?