Weekly Product Release Notes - February 3, 2021 | XM Community
Skip to main content

Entries that are bolded indicate recent product updates.

  • If you have any questions about the product updates featured in this list, our support team is happy to help you with your request. 

  • If you have questions about what’s on the product roadmap, please see our Product Updates page. If you’d like to contribute to the product roadmap, please visit the Product Ideas category.

  • CoreXM


    1. Response Weighting: Starting in February, all brands will be directed to the new and improved Response Weighting UX which has been opt-in available for several quarters. There are no actions required by customers as this front-end change does not modify existing weighting configurations in use today. This new experience features improved reporting, categorization, and a guided workflow that will support upcoming features in 2021.

    2. Organization Settings: Customers in the FedRAMP environment can now enable access to Basecamp for their users.

    3. CX Dashboards


    4. Benchmark Editor Enhancements: The benchmark editor now has improved instructions and links to download the full XMI Institute benchmark reports.

    5. Experience Journeys: Empowers brands to design, visualize, and monitor end-to-end customer journey across multiple touchpoints (i.e. website) and listening posts (i.e survey) so they can better understand where to take action to improve customer satisfaction and loyalty. This new feature consists of three new pages: Defining an Experience Journey, Configuring Dashboard Data for Journeys, and Journey Chart Widget.

    6. Saving Filters in CX Dashboards: Saved dashboard filters have a refreshed interface that is WCAG 2.0 accessible. Updated in both CX & EX dashboards.

    7. EX


    8. Saving Filters in CX Dashboards: Saved dashboard filters have a refreshed interface that is WCAG 2.0 accessible. Updated in both CX & EX dashboards.

    9. Ad Hoc Employee Research: The General Feedback EX project type has been renamed to “Ad Hoc Employee Research.” No changes in project functionality.

    10. BX


    11. Brand Drivers Analysis Widget: Measure how independent driving variables (drivers) affect key outcome metrics for a brand. For Brand Tracker dashboards only.

Hi GuinevereM
re the 'Experience Journeys'. I'm just trying to understand how this would benefit us in comparison to what you can already do by creating a grouped field in the dataset settings page and adding in the fields there? Perhaps it's the flexibility to use 'Stage' as a dynamic list, ie a list of journey stages that can change over time and you don't have to create a new field in the grouped field for each stage? I've read through the new help screens and feel this hasn't really been answered.
In addition and with regards to setting up an embedded field called stage and setting its value based on a conditional block via the survey flow, it looks like you can only do one value per response. Is that true? Ie. (referencing the examples on the help screens) in the same survey (same response) you can't ask for a CSAT rating for Purchasing AND Browsing stage as the embedded field 'Stage' will get overwritten with whatever is the latest value.

Furthermore, it would be so more useful if the widget could allow non static (eg. embedded fields) to be used for the colour red/amber/green settings.

Please could Qualtrics Support reply here with a little more information?

Thanks

Rod Pestell


Hi, Rod_Pestell, thanks for reaching out!
Regarding the comparisons question, it is certainly possible to create a grouped field in the settings page and add in the fields there, but journeys make this process much easier and more streamlined. As you mentioned, it allows you to have consistent stages, which function as a dynamic list.
Additionally, the journeys feature allows you to set the stage filter on the dashboards page, so that you can then perform driver and impact analysis for one or more stages. When combined with segments, the journeys feature enables deeper insights across both stages and segments.
To your second question, "In addition and with regards to setting up an embedded field called stage and setting its value based on a conditional block via the survey flow, it looks like you can only do one value per response. Is that true?" this is the case for the initial release of the feature. A future release of journeys (which our product team is currently working on!) will provide the ability to map one survey across multiple stages.
Finally, for the request to be able to map colors via embedded data fields, could you expand on what your use case is here? That will help us assess this further.
For additional questions specific to journeys feature functionality, I recommend that you reach out to our support team. If you have questions that are specific to how you can best leverage this new feature or how it fits into your XM Strategy, you can reach out to your Customer Success Manager!
Thanks so much!


Hi GuinevereM ,
'map colors via embedded data fields'
We'd like to be able to use different values / thresholds to represent a red, amber or green colour depending on which Hotel or site you are filtered against. Eg. site 1 has a lower threshold or target compared to site 2. Currently you can only choose a fixed value but if you were to allow the use of an embedded field then it would be possible.

This relates somewhat to displaying targets in a dashboard. Currently we can only display these targets as a number in the dashboards (by creating an extra source in the dataset setting page and connecting it to the hotel/site field). It would be great to be able to use these targets and assign a colour to then in comparisons to the score achieved from the responses. Different sites have different targets.

Hope that explains it a little better.

Thanks

Rod Pestell



GuinevereM I think this is supposed to be for February 23 not February 3 correct?


dkennedy These are the releases for February 3. There will be another weekly update today, February 24 as well :)


Leave a Reply