Item: Constructor.io Search
Rating: 9
Author: Verified User

Use Cases and Deployment Scope

We use Constructor.io Search to power our overall product discovery experience -- across browse, search, and search autocomplete. We also leverage the Constructor.io framework to power a product comparison feature.

Pros and Cons

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.

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

Most Important Features

Behaviorally-driven algorithm
Personalized results
Cognitive embeddings search results

Return on Investment

53% in revenue
7% lift in search usage
13% lift in search conversion rate

Key Insights

Do you think Constructor.io Search delivers good value for the price?

Yes

Are you happy with Constructor.io Search's feature set?

Yes

Did Constructor.io Search live up to sales and marketing promises?

Yes

Did implementation of Constructor.io Search go as expected?

Yes

Would you buy Constructor.io Search again?

Yes

Likelihood to Recommend

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.

Constructor.io puts your businesses KPIs first

Overall Satisfaction with Constructor.io Search