Configuring Customer Profiles
Use the Customer Profile tab to import and configure customer-related data that you can then use to create predictors. You must gather the desired data into a CSV file. Make sure the data is formatted with a consistent schema. After importing, you can append data, which enables you to make updates.
- To open the configuration menu, click the Settings gear icon, located on the right side of the top menu bar: .
- See Supported Encodings and Unsupported Characters for information on how to configure your data.
The List of Customer Profile Fields
When you navigate to the Settings > Customer Profile page, and you have imported a Customer Profile schema, your data is displayed in a table. Each row presents a schema column.
- The columns in the Customer Profile list are the following:
- ID Field - The field containing the employeeID value.
- Visible - Show which fields are visible on the Customer Details tab.
- Indexed - Shows which fields are indexed, which makes lookups faster for that field. The field you specified as the ID_FIELD is indexed by default.
- Cardinality - The number of unique values that appear in this field. If there are more than 1000, the number appears as 1001. Click this number to see the actual values that appear in this field.
- Label - The name of the field as specified in the Customer Profile schema.
- Type - The datatype for the field.
- Expression - If configured, an arithmetical operation to be performed on the value of this field.
- Click Upload to append more data to your Customer Profile schema.
- ImportantYour appended data must have the same schema structure as the existing data. You can add fields and values, but you cannot change the existing schema. If you need to change the structure of your schema, delete the existing schema and upload your corrected data as a new Customer Profile schema.
- To delete your Customer Profile schema, click the trash can icon next to the Customer Profile page title.
- When you upload additional data, cardinalities are automatically updated after every 1,000 new rows are uploaded.
- To view updated Customer Profile data, including cardinalities, re-load your browser page.
By default, GPR handles data using UTF-8 encoding. However, starting with release 9.0.014.00, GPR supports importing of data that uses certain legacy encodings. Appendix: Supported Encodings lists those encodings currently supported. This list is updated as new encodings are verified. If you use an encoding type that is not listed, contact your Genesys representative for assistance.
Unsupported Characters in Agent and Customer Profiles and Datasets
The following characters are not supported for column names in Datasets or Agent and Customer Profile schemas. If GPR encounters these characters in a CSV file, it reads them as column delimiters and parses the data accordingly.
- | (the pipe character)
- \t (the TAB character)
- , (the comma)
Workaround: To use these characters in column names, add double quotation marks (" ") around the entire affected column name, except in the following situations:
- If you have a comma-delimited CSV file, add double quotations marks around commas within column names; you do not need quotations for the \t (TAB) character.
- If you have a TAB-delimited CSV file, add double quotations marks around TAB characters within column names; you do not need quotations for the , (comma) character.
- You must always use double quotations for the | (pipe) character.
Unsupported characters in releases prior to 9.0.014.00
In releases prior to 9.0.014.00, certain characters in column names are ignored, are unsupported, or cause an upload to fail, as explained in the following points:
- Columns with the following symbols in their column names are not added to Agent Profiles or Customer Profiles:
- *, !, %, ^, (, ), ', &, /, â, è, ü, ó, â, ï
- Columns with the following symbols in their column names are ignored and the column is added with the symbol dropped out as though it had not been entered:
- [Space], -, <
- Non-ASCII characters are not supported. How they are handled differs depending on what data you are uploading:
- In Agent Profiles and Customer Profiles, columns with non-ASCII characters in the column name are not added.
- In Datasets, when a column name contains a mix of ASCII and non-ASCII characters, GPR removes the non-ASCII characters from the column name as though they had not been entered and correctly uploads all column values.
- In Datasets, when a column name contains only non-ASCII characters, the column name is entirely omitted. All the column values are preserved, but you cannot modify or save the schema. In this scenario, GPR generates the following error message: An unhandled exception has occurred: KeyError('name').
Logs for Unsupported Characters
The following Agent State Connector log messages record issues with unsupported characters:
- <datetime>  ERROR <BOTTLE> schema_based.py:63 Invalid expression while parsing: <fieldname> = None
- <datetime>  ERROR <BOTTLE> agents.py:172 Fields set([u'<fieldname>']) were ignored because names were invalid.