Inconvenient Content Targeting with User Segments in Search REST API
Content Targeting with User Segments just works with Content Search Web Parts but some additional work is needed if you want to leverage it with the Search REST API.
Innovation Matters
Microsoft 365 Developer Advocate
ISSN 2210-9390
A collection of 11 posts
Content Targeting with User Segments just works with Content Search Web Parts but some additional work is needed if you want to leverage it with the Search REST API.
Leveraging SharePoint 2013 Search REST API for anonymous users allows you to build powerful search-driven solutions. Often, particularly in the early stages of the project, queries might not work as expected. So how do you find out what’s wrong?
Leveraging the Search REST API allows you to build rich search-driven solutions. If you’re not careful however, you might get results other than intended even though everything seems to be working correctly.
Last Saturday I presented on the SharePoint Saturday Holland 2013 on building intelligent websites using SharePoint 2013. Following is the presentation deck from my presentation.
Enabling the Anonymous search results cache can help you improve the performance of your SharePoint 2013 public-facing website using the search-driven publishing model. So how do you ensure that your website is using the Anonymous search results cache?