Weekly Product Release Notes - August 24, 2022 | XM Community

Weekly Product Release Notes - August 24, 2022

  • 24 August 2022
  • 4 replies
  • 4 views
CarolineH
Rank
Userlevel 7
Badge +10

Weekly Product Release Notes bannerRecent Update bannerReleased On Or Before August 24, 2022


BX Dashboards


  • Data Freshness for BX Widgets: Brand Drivers Analysis widgets and Brand Drivers Analysis Quadrant Chart widgets now display the date and time the widget data was last updated.

    • Predict iQ


  • Predict iQ v1 Deprecation: We’ve reimagined Predict iQ with a seamless new user experience and a prediction engine that leverages state-of-the-art machine learning algorithms. The support page now covers this new experience. Not all users who had access to v1 will have access to v2; v2 is available only as requested.

    • Upcoming Features bannerStarting On & After August 31, 2022


    CoreXM


  • Collaborative Preview Links: Survey creators can now control who can access survey preview links. Links can be limited to only users within the brand, or made public so anyone with the link can access. This feature will be gradually rolled out to customers starting August 31, 2022 and concluding September 28, 2022.

    • Feedback & Questions Banner*Disclaimer: Release dates are approximate and are subject to change. Not every feature is guaranteed to be included in Upcoming Features.


  • 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 Roadmap page. If you’d like to contribute to the product roadmap, please visit the Product Ideas category.

  • You can provide feedback on the Weekly Product Release Notes here.

4 replies

jwiggington
Badge +3

Is the recommendation to not put the deployment code in the global header or footer intended to limit the intercept views just based on licensing limitations? Are there other reasons that this should be avoided? If there is an Always On intercept on every page, does it matter if the code is in the header/footer or on the pages themselves?

AmaraW
Rank
Badge +48

Thanks for your questions!

  • Is the recommendation to not put the deployment code in the global header or footer intended to limit the intercept views just based on licensing limitations?

  • Yes, this recommendation is just based on licensing limitations, as we charge by views to the intercept.

  • Are there other reasons that this should be avoided?

  • No.

  • If there is an Always On intercept on every page, does it matter if the code is in the header/footer or on the pages themselves?

  • If you want to display the same thing on every page it is fine to add the deployment code to the global header/footer. If you’re looking to hide the intercept on some pages, the global header/footer should not be added because it eats up views for intercepts not actually displayed.


jwiggington
Badge +3

Excellent, thank you so much for the clarification!

AmaraW
Rank
Badge +48

@jwiggington I wanted to follow up on your questions:
The website / app feedback update from last week was added in error and we have corrected the support page to reflect this. We still recommend adding the code snippet to the global header/footer within your website. The benefits of this include only needing to do a one-time code placement, allowing website visitors to provide feedback on any page of the website, and collecting aggregate operational data such as Time Spent on Site and Page Count. If you prefer to only add a digital touchpoint to a handful of pages instead of the full site, you’re welcome to add the code snippet directly to those pages instead, but you may miss out on some of the benefits mentioned above.

Leave a Reply


Terms & Conditions