Adobe Global Community

Pages Tagged with ''

Website Voice Search with the WebSpeech API and Adobe Search&Promote

With the takeover of the web by mobile browsers, tailoring experiences to mobile users is critical to creating successful experiences. Nearly 21.6% of mobile visitors using voice search on a daily basis, so providing voice search on mobile web experiences helps to create a more native experience for mobile users. Historically there has not been a good API for integrating voice recognition into websites, however, the (relatively) new WebSpeech API makes this possible right through JavaScript. This API is still experimental and only works in certain browsers, but has significant promise to more closely align web and native mobile experiences. 

Creating Rich Web Experiences with AEM + Adobe Search&Promote

Adobe Search&Promote is a powerful SaaS search offering within the Adobe Marketing Cloud. By integrating Adobe Experience Manager (AEM) and Adobe Search&Promote, you can create extremely powerful search-driven experiences in AEM. You may ask, why do you need a 3rd party search service when AEM includes a Search component? This feature searches directly in the CMS using native Lucene searching to search the content in AEM’s repository. It is useful for small sites or basic needs, but is limited to only the contents of the AEM repository and does not support facets so more robust experiences will need a third party search tool. 

Quick Fix: AEM + Search&Promote Integration Uses Stage

Adobe Search&Promote is a powerful SaaS search offering within the Adobe Marketing Cloud. Adobe offers an integration between Adobe Experience Manager and Adobe Search&Promote using AEM’s Cloud Services. This integration is meant to allow authors to easily deploy and configure basic search experiences with the two tools. Unfortunately, there is an issue with the integration where AEM will cache the Stage URL for Adobe Search&Promote’s API endpoint. While you can force Adobe Search&Promote to use the Live index with the sp_staged parameter, it will still use the Stage configuration. This is a serious problem as it means that you may be using configurations which are not tested or not ready yet to be live.