Skip to main content
Loading...
  • Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM
  • Design XM
    Design XM

Carrying Unique Identifiers into a Dashboard Dataset

What's on This Page:


Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!


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.

Qtip: Once you’ve finished linking unique identifier to a dashboard dataset using one of the methods described on this page, see Adding Org Hierarchies to CX Dashboards for how to filter data by hierarchy.

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.

Qtip: This option is only available if you are using a level-based hierarchy.
  1. Go to the Survey flow.
    Survey flow button, second int toolbar along the top of the survey editor. Add a new element here is in green at the bottom of the list of elements. Above that, a yellow menu appears with a green embedded data option.
  2. Add a new element.
  3. Select Embedded Data.
  4. For the field name, enter the name of the unique identifier field you will be using.
    Adding a unique ID embedded data to the survey flow
    Warning: This must match what’s in your mailing lists exactly, with the same capitalization, spacing, and spelling.
  5. Move this element to the top of the flow.
  6. Click Add below on the embedded data element.
  7. Select CX Org Hierarchy.
  8. Select one or more hierarchies from the dropdown.
    Adding a org hierarchy element

    Qtip: Please note that only level-based hierarchies are supported at this time.
  9. Select the embedded data field that will contain unique identifier.
  10. Apply changes to your survey flow.
Qtip: You cannot create this element under any other survey flow element – e.g., you cannot add it under a branch, randomizer, or group. You can select multiple hierarchies within the same element.

Qtip: Hierarchy levels will be available in the dashboard in a drill down field group:

Image of hierarchy as 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.

Qtip: Contact lists can be used to distribute surveys through email, SMS text, personal links, and authenticators. Authenticators allow you to use one link to distribute your survey, putting the onus on the respondent to login with certain credentials before they can complete the survey. If your organization uses single sign-on (SSO), it’s even easier to capture user information using an SSO authenticator.

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.

Qtip: This option is recommended if you are using an ad-hoc or parent level hierarchy.

A picture of a unique id embedded data element at the top of the screen

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.

Qtip: The embedded data can even be added to the survey flow retroactively, so long as you included this information in the contact list before you collected your survey data.
Qtip: Contact lists can be used to distribute surveys through email, SMS text, personal links, and authenticators. Authenticators allow you to use one link to distribute your survey, putting the onus on the respondent to login with certain credentials before they can complete the survey. If your organization uses single sign-on (SSO), it’s even easier to capture user information using an SSO authenticator.

Existing Survey Data

If you’ve already collected survey data and need to add unique identifiers, then try these steps:

  1. Add a new embedded data field or custom field to your survey where you’ll capture unique identifiers.
  2. 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.