Try setting it up like this:

Hello! I hope you are doing well. I am attaching a screenshot of an example you could leverage to get the NPS Group into Data & Analysis. Please note this will only work if you use the NPS Question. If you are using a multiple choice question instead, you will need to adjust the branch logic to say something like, “if Q1 is between 0 and 6, set NPS Group as Detractor”:

A few things to note. First, once you set up the first option, simply click Duplicate and then it will repeat the Branch and Embedded Data, making it so you only have to adjust the NPS Group and the name in the Embedded Data field!

Second, I would recommend putting the branch logic after the block the NPS question is in. This ensures that the Group is captured as quickly as possible in the survey. For example, if a respondent abandons the survey early, but the branch logic is at the bottom of all blocks in the survey, we could risk having Qualtrics not capture this information. If you only have one block, I would put the NPS in its own block to further reduce the chances of not capturing this vital information.

Lastly, the NPS Question will naturally capture the NPS group in Dashboards, so if you leverage that, the data will be automatically added. However, for your purposes, this will work just fine! 

Just to add I believe you have to add the nps group embedded data at the beginning of the survey in amd embeded data block, and you do not assign any value. Then the field is going to be populated according to the branch that corresponds to the response

Amazing, thanks :)

Hey Ana, thank you for the callout! This is correct. By having the Embedded Data field at the beginning, combined with the Branch Logic after your NPS, you’ll be able to accomplish the use case you brought up. Thank you!

Hello! I hope you are doing well. I am attaching a screenshot of an example you could leverage to get the NPS Group into Data & Analysis. Please note this will only work if you use the NPS Question. If you are using a multiple choice question instead, you will need to adjust the branch logic to say something like, “if Q1 is between 0 and 6, set NPS Group as Detractor”:

A few things to note. First, once you set up the first option, simply click Duplicate and then it will repeat the Branch and Embedded Data, making it so you only have to adjust the NPS Group and the name in the Embedded Data field!

Second, I would recommend putting the branch logic after the block the NPS question is in. This ensures that the Group is captured as quickly as possible in the survey. For example, if a respondent abandons the survey early, but the branch logic is at the bottom of all blocks in the survey, we could risk having Qualtrics not capture this information. If you only have one block, I would put the NPS in its own block to further reduce the chances of not capturing this vital information.

Lastly, the NPS Question will naturally capture the NPS group in Dashboards, so if you leverage that, the data will be automatically added. However, for your purposes, this will work just fine! 

Although I just tested this and worked as expected. Would you advise changing anything?

So with these new embedded data fields in a contact could I build out a new NPS dashboard widget as I would have both Group and Score? Or is this not possible and could only build this from a NPS question? 

Hello! I hope you are doing well. I am attaching a screenshot of an example you could leverage to get the NPS Group into Data & Analysis. Please note this will only work if you use the NPS Question. If you are using a multiple choice question instead, you will need to adjust the branch logic to say something like, “if Q1 is between 0 and 6, set NPS Group as Detractor”:

A few things to note. First, once you set up the first option, simply click Duplicate and then it will repeat the Branch and Embedded Data, making it so you only have to adjust the NPS Group and the name in the Embedded Data field!

Second, I would recommend putting the branch logic after the block the NPS question is in. This ensures that the Group is captured as quickly as possible in the survey. For example, if a respondent abandons the survey early, but the branch logic is at the bottom of all blocks in the survey, we could risk having Qualtrics not capture this information. If you only have one block, I would put the NPS in its own block to further reduce the chances of not capturing this vital information.

Lastly, the NPS Question will naturally capture the NPS group in Dashboards, so if you leverage that, the data will be automatically added. However, for your purposes, this will work just fine! 

 

Although I just tested this and worked as expected. Would you advise changing anything?

As long as you set it up as the screenshot shows, along with Ana’s suggestion of adding an Embedded Data field at the top of the survey, that will be good and all responses will include this information going forward!

Yes, you certainly could! Those fields are automatically brought in as metrics in the Dashboard with the NPS question (see screenshot).

However, if you did not use the NPS question, you could still bring in the Embedded Data field you created as a metric in the Dashboard! Then, you can create something such as a Table widget that shows the NPS for each respondent along with their NPS Group! Does this help clarify?

Then assign labels to source code and save it.

Then you can use same field into your dashboard.

Please refer my amswer here: https://community.qualtrics.com/cx-dashboards-8/concatenating-fields-in-a-cx-dashboard-23153