Users can be created, updated with audience attributes, and optionally deactivated by routinely uploading a file containing user data via SFTP. Brand Super Admins may subscribe to email confirmations when a file is processed via SFTP. This confirmation email includes information on updates to user access, and a link to a report on any errors.

To update the mailing list for these notifications, please contact Support.

Errors

Errors preventing the entire file from being processed will be shown in the body of the confirmation email. If any records could not be processed due to an error, details on the error(s) will be included in a hyperlinked report. To access this report, ensure you are first signed into Studio as a Brand Super Admin.

Universal Identifier or Email may be used as the Unique ID for users. If Universal Identifier (usually an employee ID) is used, then the email address for a user may be updated via the SFTP file. However, if Email is used as the Unique ID, then a user's email address cannot be changed. Updating a user's Unique ID will result in a duplicate user being created, or an error will prevent the record from being processed.

Two different advocates found.

Cause: The Universal Identifier and Email address in the file belong to two separate accounts.
Solution: Forget the user that has the Email in the file. Your next upload will then update the Email address of the user with the correct Universal Identifier.

Cannot assign additional identifiers to email users.

Cause: The account for this Email Address has a different Universal Identifier to the file. Universal Identifier is the Unique ID and cannot be updated.
Solution: Forget the user with the old [Universal Identifier]. This will free up their Email Address to be used by a new account, which will be created when the next SFTP upload is processed.

Emails value [email address] has already been taken.

Cause: The Email address is already in use by a different user with a different Universal Identifier.
Solution: Forget the user with the old Universal Identifier. This will free up their Email to be used by a new account, which will be created when the next SFTP upload is processed.

One or both of email or identifier must be specified.

Cause: The Universal Identifier and Email in the file are missing.
Solution: Update the record to ensure data is included for both the Universal Identifier and Email.

Emails value is an invalid email address.

Cause: When a user's Email address is not valid (i.e, there is a space in the email or missing the @ symbol etc.) they will receive this error.

Solution: Ensure a valid Email address is used for all records.

Line X is missing [attribute], which is a required field.

Cause: A required field is blank for a line in the file.

Solution: Ensure required fields are filled in for all lines. The relevant required field will be named in the error message (e.g. employee_id, email, first_name, last_name).

The uploaded file is not properly encoded as [character set]

e.g. The uploaded file is not properly encoded as UTF-8

Cause: At least one character in the file cannot be read in the configured encoding language.
Solution: Ensure all characters are valid in the configured encoding language. A regex search [^\x00-\x7F] can be used in a text editor to identify non-ASCII characters in a CSV file and remove or replace them.

The uploaded file has an unsupported MIME type.

Cause: File is not in the expected format (CSV/PGP/TXT).
Solution: Convert to the correct format based on file setup.

The uploaded file could block more than X% of the user base, which may not be intended.

The blocked percentage is the percentage of users in the previous file that will be blocked by the latest file based on their Universal Identifier. If a user's existing Universal Identifier is not in the latest file, and it was in the previous file, then this will contribute to the blocked percentage even if they are still in the file but with a new ID or have been replaced by another user.

By default, a maximum of 10% of the user base (users in the previous file) can be blocked by a user sync file. If a higher volume of users to be deactivated is expected, contact Support to temporarily increase the maximum blocked percentage.