Constructor.io Search vs. Lucidworks Fusion

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

Very well suited for out of the box enterprise search applications.

• 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

• Signals feature to boost search results helps search relevancy
• Business Rules feature for tuning search results
• Query pipeline design gives great flexibility in application development

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

Incentivized

• Documentation can be improved

It is incredibly intuitive and so easy to use that business people can now complete functions that used to be limited to software developers only.

It has continued to improve over the years.

IDOL seems to be a blackbox solution. Fusion is much more flexible with more features and options for developers to choose from.

• Allowed us to move software developers from enterprise search to other customer focused applications due to built in signals processing and related popularity boosting out of the box.
• Enabled business experts to work directly with Fusion to influence search results and not be so dependent on developers.