Constructor.io Search vs. Netcore Unbxd

Constructor.io Search takes all of the guesswork out of maintaining a search engine. As merchandisers or product teams, we have educated guesses at how search relevance should work but the customer is always king. We can't always predict the ways in which consumers will search or what their intent is. That's why the behavioral-driven approach that Constructor.io employs works so well. It means that merchandisers can focus on their sales and promotional responsibilities, instead of wasting time and bandwidth on base-level relevance questions.

Incentivized

Best scenarios: To explain to the customers how the product works in searching any operation and to give the demo to customers. Less appropriate: To describe the customers in a very short span of time.

• Optimizes for business KPIs, not string matches, so merchandisers can focus on strategy instead of maintaining a dictionary.
• Gives merchandisers control to curate the right customer experience per their expert understanding.
• Customer/technical support during and after implementation.

Incentivized

• Auto suggest widgets
• Visual workbench
• A/B testing

• Visibility of the personalization algorithm.
• Exposing detailed analytics within the customer-facing dashboard.
• "Top searches" available via API.

Incentivized

• Animated toons
• Some short video explanations
• Fast and ready suggestions

They have some good graphics and displays for overall reports. Reports and data analytics reports are having good insights into all the data. The reports are enough to calculate each time series analysis.

• Positive impact: Reports , Speed of report generation.
• Negative feature: AI feature : sometimes it didn't work.