About Carrying Unique Identifiers into a Dashboard Dataset
In order to add an org hierarchy to a CX Dashboard, your dataset needs to contain the users’ unique identifiers. If you are directly uploading a CSV as a source to your dashboard, this is as simple as including a column with each user’s unique identifier in your CSV file.
However, if you are working with a survey project, you need to make sure the correct information is pulling into the survey before you can map it to the dashboard. There are two ways to do this. We will describe these methods in the next sections of the page.
Please note that this page describes functionality that is different from dashboarding in EmployeeXM projects.
Option One: Dynamic Hierarchies
This first method allows you to link the hierarchy directly to the survey response data. This means that if adjustments are made to the hierarchy after data is collected, they will be reflected in the dashboard.
- Go to the Survey flow.
- Add a new element.
- Select Embedded Data.
- For the field name, enter the name of the unique identifier field you will be using.
Warning: This must match what’s in your mailing lists exactly, with the same capitalization, spacing, and spelling.
- Move this element to the top of the flow.
- Click Add below on the embedded data element.
- Select CX Org Hierarchy.
- Select one or more hierarchies from the dropdown.
Qtip: Please note that only level-based hierarchies are supported at this time.
- Select the embedded data field that will contain unique identifier.
- Apply changes to your survey flow.
Qtip: Hierarchy levels will be available in the dashboard in a drill down field group:
You can remap these fields and use them as a filter, but changes to the hierarchy will not be dynamic with this filter. We instead recommend following these steps to filter by org hierarchy.
Distributing Your Survey
Just add it as a column to your list (XM Directory, non-XM Directory contacts) and then include an embedded data field at the top of your survey flow. Make sure the way you spell the field’s name is consistent between the contact list and the survey flow.
Option Two: Static Hierarchies
This second method allows you to only link the hierarchy to the dashboard data, not the survey response itself. As a result, if the hierarchy changes, it will not be reflected in the data.
If you haven’t collected data in your survey project yet, you can include unique identifiers with contact lists used to distribute the survey. Just add it as a column to your list (XM Directory, non-XM Directory contacts) and then include an embedded data field at the top of your survey flow. Make sure the way you spell the field’s name is consistent between the contact list and the survey flow.
Existing Survey Data
If you’ve already collected survey data and need to add unique identifiers, then try these steps:
- Add a new embedded data field or custom field to your survey where you’ll capture unique identifiers.
- Manually edit responses, or use a CSV/TSV to edit and re-upload the survey responses. If you are importing edits, remember that you will need to delete the original responses afterwards. See Combining Responses for tips on uploading survey response edits.
Alternatively, if you aren’t worried about user error, you can add a text entry question to the survey that asks for the unique identifier, then send respondents retake links. This is not recommended if you used an authenticator.